Make our services a little safer

In the face of XSS (cross site scripting, multi-site scripting attacks, embedding malicious scripts in Web pages to steal client cookies, etc., downloading Trojan programs, obtaining client admin privileges, etc.), the input code is escaped in our program;

In the face of CRSF (cross site request forgery), we generally set cookies to ReadOnly, add tokens, pass referer recognition, etc.

In the face of SQL injection (masquerading SQL commands as HTTP requests), we generally use precompiled statements, use ORM frameworks, avoid plaintext storage of passwords, etc.

In the face of File upload Vulnerability (using the server does not verify the upload file, thereby uploading malicious script), we read the first 28 bytes of the uploaded file, turn to 16 binary number, compared with the file header, determine the file type.

Common file links are as follows:

Jpeg:ffd8ff
Png:89504e47
gif:47494638
Tiff:49492a00
bmp:424d
dwg:41433130
psd:38425053
xml:3c3f786d6c
html:68746d6c3e
pdf:255044462d312e
zip:504b0304
rar:52617221
wav:57415645
avi:41564920

In the face of DDoS (distributed denial of service, distributed denial of service attacks, using reasonable client requests to consume server resources too much, causing customers to be unavailable), we generally need third-party partners ... Oh

Make our services a little safer