Showing posts from April, 2011

Scanners are scanners

When scanning the XSS-Game site with various XSS scanners, I found most scanners are similiar in missing XSS in the following pages. Apparently, no scanners can detect all XSSes. Scanners are limited to their developers' skills and experience in security testing. This post might be of help to scanner developers to improve their scan engines or let them alone for the human analysis part. 1. solution: javascript:alert(/XSS/) Some real-world applications parse our GET/POST requests and put them in the links. It's likely that Scanner XYZ thinks javascript:alert(/XSS/) which is not its own submitted payload. 2. solution: This is a double-encoding XSS but it's likely that Scanner XYZ focused only on non-vulnerable parameter 'foo' and missed vulnerable

Storing both CHECKSUM data and files on the same server

Problem: A lot of people store their application source files and respective check-sum files on the same servers. Users will not notice even if their files and checksum data files become changed. Suggestion: - Separate CheckSum file and downloadable files on separate servers. - Use PGP Signature.