CPSA ยท Web application assessment: recon, access control and input
Web application reconnaissance
Mapping structure and identifying components, frameworks and technologies in use.
Key points
- Map the application before attacking it: pages, forms, parameters and entry points, plus the technology behind them.
- Fingerprint the framework from response headers (such as X-Powered-By), session cookie names, HTML source markers (generator meta tags, script paths), file extensions (.php, .aspx, .jsp) and error pages.
- Treat every marker as a hint, because administrators can hide or change them.
Practice questions
Which HTTP response header is the simplest first place to look for the framework behind a site?
- Content-Length
- X-Powered-By
- Date
- Accept-Ranges
Show answer
Answer: B. X-Powered-By
X-Powered-By often names the framework or language. Content-Length and Date are generic and say nothing about the technology; Set-Cookie can help but reveals a framework only through the cookie name.
Which sources can help identify the technology behind a web application?
- Session cookie names
- The tester's own browser version
- A generator meta tag in the HTML head
- URL file extensions such as .aspx or .jsp
- The colour palette of the stylesheet
Show answer
Answer: A. Session cookie names, C. A generator meta tag in the HTML head, D. URL file extensions such as .aspx or .jsp
Cookie names, generator meta tags and file extensions are all common fingerprints. The tester's own browser version and the site's colour palette describe the visitor or the design, not the server stack.
True or false: if the X-Powered-By header is removed, the framework can no longer be identified.
Show answer
Answer: False
False. Cookies, HTML source, file extensions, error pages and application-specific paths can still reveal the technology.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
