Entry point for security testing

Security, a lingering pain for all internet companies

Today, we would like to outline some of the safety issues that we should be aware of in our daily testing work (without involving the description of the security tools)

1, XSS class: including storage and reflective type

The most easily propagated of the reflective type is the search URL, which takes care to handle the XSS risk code in such URLs.

The harm of storage type is more than the damage of reflective type, and it is recommended to do unified processing on platform.

2, the front-end existence of business check

Any front-end inspection is done to improve the user experience, without any specific security

If you are involved in a business-critical check, you need to ensure that there is a consistent logical check

3. Post form redundancy data

The Post form submits data that is not allowed to be modified directly in the page or business logic

(commonly used such as mobile phone number, mailbox, etc. need to be verified before modification)

4, the number of breakthrough search parameters

Many sites will have a search, there are many conditions in the search, the business at design time to the number of partial search conditions are limited

After the request is intercepted, the concurrent request server, which expands the search criteria, can cause considerable pressure on the server.

This article is also related to the previous < front-end existence of business check >

5, Password class transmission

Mainly related to registration, login, change password, forget password these kinds of commonly used operations

It is very unsafe to use plaintext passwords during transmission.

6. Data operation class with ID

Pay close attention to edit, delete operation with data ID, the level of unauthorized operation of data, is a very dangerous vulnerability

7. Database Storage Length

Front end 100% can make a length or input type limit on the data input

We know that the limitations of the front end are not of any security significance, and the data type and length of the tool modification can also be submitted as normal, if the error is likely to expose the database key information

8. Duplicate Submission Request | Limited data quantity

For requests that do not allow duplicate submissions and a limited number of storage, not only in the front-end limit, but also in the server has a corresponding checksum limit

9, Data Backfill

The data entered by the user is backfill directly in the JSP, and then as a property value in the label is displayed in the HTML of the page, in which case, if not processed, there will be an XSS

If the user searches for records, searches for keywords

10. Automatic Login

When changing the password, resetting the password class operation, try not to append an automatic login action at the end

In particular, this judgment will not be given to the front end or browser

11. Crash Library

Many account password resources on the network, will be used to hit some of the site's user name password

12. Blasting

In the hardest hit area, retrieve the password verification code or any other important operation of the Digital Verification Code Section

It is recommended to increase the complexity of the verification code, while adding the verification code to increase the difficulty, and preferably other explosion-proof mechanism

Entry point for security testing