Top 100 Web Vulnerabilities Reference
Purpose
Provide a comprehensive, structured reference for the 100 most critical web application vulnerabilities organized by category. This skill enables systematic vulnerability identification, impact assessment, and remediation guidance across the full spectrum of web security threats. Content organized into 15 major vulnerability categories aligned with industry standards and real-world attack patterns.
Prerequisites
- Basic understanding of web application architecture (client-server model, HTTP protocol)
- Familiarity with common web technologies (HTML, JavaScript, SQL, XML, APIs)
- Understanding of authentication and authorization concepts
- Access to web application security testing tools (Burp Suite, OWASP ZAP)
- Knowledge of secure coding principles recommended
Outputs and Deliverables
- Complete vulnerability catalog with definitions, root causes, impacts, and mitigations
- Category-based vulnerability groupings for systematic assessment
- Quick reference for security testing and remediation
- Foundation for vulnerability assessment checklists and security policies
Core Workflow
Phase 1: Injection Vulnerabilities Assessment
Evaluate injection attack vectors targeting data processing components:
SQL Injection (1)
- Definition: Malicious SQL code inserted into input fields to manipulate database queries
- Root Cause: Lack of input validation, improper use of parameterized queries
- Impact: Unauthorized data access, data manipulation, database compromise
- Mitigation: Use parameterized queries/prepared statements, input validation, least privilege database accounts
Cross-Site Scripting - XSS (2)
- Definition: Injection of malicious scripts into web pages viewed by other users
- Root Cause: Insufficient output encoding, lack of input sanitization
- Impact: Session hijacking, credential theft, website defacement
- Mitigation: Output encoding, Content Security Policy (CSP), input sanitization
Command Injection (5, 11)
- Definition: Execution of arbitrary system commands through vulnerable applications
- Root Cause: Unsanitized user input passed to system shells
- Impact: Full system compromise, data exfiltration, lateral movement
- Mitigation: Avoid shell execution, whitelist valid commands, strict input validation
XML Injection (6), LDAP Injection (7), XPath Injection (8)
- Definition: Manipulation of XML/LDAP/XPath queries through malicious input
- Root Cause: Improper input handling in query construction
- Impact: Data exposure, authentication bypass, information disclosure
- Mitigation: Input validation, parameterized queries, escape special characters
Server-Side Template Injection - SSTI (13)
- Definition: Injection of malicious code into template engines
- Root Cause: User input embedded directly in template expressions
- Impact: Remote code execution, server compromise
- Mitigation: Sandbox template engines, avoid user input in templates, strict input validation
Phase 2: Authentication and Session Security
Assess authentication mechanism weaknesses:
Session Fixation (14)
- Definition: Attacker sets victim's session ID before authentication
- Root Cause: Session ID not regenerated after login
- Impact: Session hijacking, unauthorized account access
- Mitigation: Regenerate session ID on authentication, use secure session management
Brute Force Attack (15)
- Definition: Systematic password guessing using automated tools
- Root Cause: Lack of account lockout, rate limiting, or CAPTCHA
- Impact: Unauthorized access, credential compromise
- Mitigation: Account lockout policies, rate limiting, MFA, CAPTCHA
Session Hijacking (16)
- Definition: Attacker steals or predicts valid session tokens
- Root Cause: Weak session token generation, insecure transmission
- Impact: Account takeover, unauthorized access
- Mitigation: Secure random token generation, HTTPS, HttpOnly/Secure cookie flags
Credential Stuffing and Reuse (22)
- Definition: Using leaked credentials to access accounts across services
- Root Cause: Users reusing passwords, no breach detection
- Impact: Mass account compromise, data breaches
- Mitigation: MFA, breach password checks, unique credential requirements
Insecure "Remember Me" Functionality (85)
- Definition: Weak persistent authentication token implementation
- Root Cause: Predictable tokens, inadequate expiration controls
- Impact: Unauthorized persistent access, session compromise
- Mitigation: Strong token generation, proper expiration, secure storage
CAPTCHA Bypass (86)
- Definition: Circumventing bot detection mechanisms
- Root Cause: Weak CAPTCHA algorithms, improper validation
- Impact: Automated attacks, credential stuffing, spam
- Mitigation: reCAPTCHA v3, layered bot detection, rate limiting
Phase 3: Sensitive Data Exposure
Identify data protection failures:
IDOR - Insecure Direct Object References (23, 42)
- Definition: Direct access to internal objects via user-supplied references
- Root Cause: Missing authorization checks on object access
- Impact: Unauthorized data access, privacy breaches
- Mitigation: Access control validation, indirect reference maps, authorization checks
Data Leakage (24)
- Definition: Inadvertent disclosure of sensitive information
- Root Cause: Inadequate data protection, weak access controls
- Impact: Privacy breaches, regulatory penalties, reputation damage
- Mitigation: DLP solutions, encryption, access controls, security training
Unencrypted Data Storage (25)
- Definition: Storing sensitive data without encryption
- Root Cause: Failure to implement encryption at rest
- Impact: Data breaches if storage compromised
- Mitigation: Full-disk encryption, database encryption, secure key management
Information Disclosure (33)
- Definition: Exposure of system details through error messages or responses
- Root Cause: Verbose error handling, debug information in production
- Impact: Reconnaissance for further attacks, credential exposure
- Mitigation: Generic error messages, disable debug mode, secure logging
Phase 4: Security Misconfiguration
Assess configuration weaknesses:
Missing Security Headers (26)
- Definition: Absence of protective HTTP headers (CSP, X-Frame-Options, HSTS)
- Root Cause: Inadequate server configuration
- Impact: XSS attacks, clickjacking, protocol downgrade
- Mitigation: Implement CSP, X-Content-Type-Options, X-Frame-Options, HSTS
Default Passwords (28)
- Definition: Unchanged default credentials on systems/applications
- Root Cause: Failure to change vendor defaults
- Impact: Unauthorized access, system compromise
- Mitigation: Mandatory password changes, strong password policies
Directory Listing (29)
- Definition: Web server exposes directory contents
- Root Cause: Improper server configuration
- Impact: Information disclosure, sensitive file exposure
- Mitigation: Disable directory indexing, use default index files
Unprotected API Endpoints (30)
- Definition: APIs lacking authentication or authorization
- Root Cause: Missing security controls on API routes
- Impact: Unauthorized data access, API abuse
- Mitigation: OAuth/API keys, access controls, rate limiting
Open Ports and Services (31)
- Definition: Unnecessary network services exposed
- Root Cause: Failure to minimize attack surface
- Impact: Exploitation of vulnerable services
- Mitigation: Port scanning audits, firewall rules, service minimization
Misconfigured CORS (35)
- Definition: Overly permissive Cross-Origin Resource Sharing policies
- Root Cause: Wildcard origins, improper CORS configuration
- Impact: Cross-site request attacks, data theft
- Mitigation: Whitelist trusted origins, validate CORS headers
Unpatched Software (34)
- Definition: Systems running outdated vulnerable software
- Root Cause: Neglected patch management
- Impact: Exploitation of known vulnerabilities
- Mitigation: Patch management program, vulnerability scanning, automated updates
Phase 5: XML-Related Vulnerabilities
Evaluate XML processing security:
XXE - XML External Entity Injection (37)
- Definition: Exploitation of XML parsers to access files or internal systems
- Root Cause: External entity processing enabled
- Impact: File disclosure, SSRF, denial of service
- Mitigation: Disable external entities, use safe XML parsers
XEE - XML Entity Expansion (38)
- Definition: Excessive entity expansion causing resource exhaustion
- Root Cause: Unlimited entity expansion allowed
- Impact: Denial of service, parser crashes
- Mitigation: Limit entity expansion, configure parser restrictions
XML Bomb (Billion Laughs) (39)
- Definition: Crafted XML with nested entities consuming resources
- Root Cause: Recursive entity definitions
- Impact: Memory exhaustion, denial of service
- Mitigation: Entity expansion limits, input size restrictions
XML Denial of Service (65)
- Definition: Specially crafted XML causing excessive processing
- Root Cause: Complex document structures without limits
- Impact: CPU/memory exhaustion, service unavailability
- Mitigation: Schema validation, size limits, processing timeouts
Phase 6: Broken Access Control
Assess authorization enforcement:
Inadequate Authorization (40)
- Definition: Failure to properly enforce access controls
- Root Cause: Weak authorization policies, missing checks
- Impact: Unauthorized access to sensitive resources
- Mitigation: RBAC, centralized IAM, regular access reviews
Privilege Escalation (41)
- Definition: Gaining elevated access beyond intended permissions
- Root Cause: Misconfigured permissions, system vulnerabilities
- Impact: Full system compromise, data manipulation
- Mitigation: Least privilege, regular patching, privilege monitoring
Forceful Browsing (43)
- Definition: Direct URL manipulation to access restricted resources
- Root Cause: Weak access controls, predictable URLs
- Impact: Unauthorized file/directory access
- Mitigation: Server-side access controls, unpredictable resource paths
Missing Function-Level Access Control (44)
- Definition: Unprotected administrative or privileged functions
- Root Cause: Authorization only at UI level
- Impact: Unauthorized function execution
- Mitigation: Server-side authorization for all functions, RBAC
Phase 7: Insecure Deserialization
Evaluate object serialization security:
Remote Code Execution via Deserialization (45)
- Definition: Arbitrary code execution through malicious serialized objects
- Root Cause: Untrusted data deserialized without validation
- Impact: Complete system compromise, code execution
- Mitigation: Avoid deserializing untrusted data, integrity checks, type validation
Data Tampering (46)
- Definition: Unauthorized modification of serialized data
- Root Cause: Missing integrity verification
- Impact: Data corruption, privilege manipulation
- Mitigation: Digital signatures, HMAC validation, encryption
Object Injection (47)
- Definition: Malicious object instantiation during deserialization
- Root Cause: Unsafe deserialization practices
- Impact: Code execution, unauthorized access
- Mitigation: Type restrictions, class whitelisting, secure libraries
Phase 8: API Security Assessment
Evaluate API-specific vulnerabilities:
Insecure API Endpoints (48)
- Definition: APIs without proper security controls
- Root Cause: Poor API design, missing authentication
- Impact: Data breaches, unauthorized access
- Mitigation: OAuth/JWT, HTTPS, input validation, rate limiting
API Key Exposure (49)
- Definition: Leaked or exposed API credentials
- Root Cause: Hardcoded keys, insecure storage
- Impact: Unauthorized API access, abuse
- Mitigation: Secure key storage, rotation, environment variables
Lack of Rate Limiting (50)
- Definition: No controls on API request frequency
- Root Cause: Missing throttling mechanisms
- Impact: DoS, API abuse, resource exhaustion
- Mitigation: Rate limits per user/IP, throttling, DDoS protection
Inadequate Input Validation (51)
- Definition: APIs accepting unvalidated user input
- Root Cause: Missing server-side validation
- Impact: Injection attacks, data corruption
- Mitigation: Strict validation, parameterized queries, WAF
API Abuse (75)
- Definition: Exploiting API functionality for malicious purposes
- Root Cause: Excessive trust in client input
- Impact: Data theft, account takeover, service abuse
- Mitigation: Strong authentication, behavior analysis, anomaly detection
Phase 9: Communication Security
Assess transport layer protections:
Man-in-the-Middle Attack (52)
- Definition: Interception of communication between parties
- Root Cause: Unencrypted channels, compromised networks
- Impact: Data theft, session hijacking, impersonation
- Mitigation: TLS/SSL, certificate pinning, mutual authentication
Insufficient Transport Layer Security (53)
- Definition: Weak or outdated encryption for data in transit
- Root Cause: Outdated protocols (SSLv2/3), weak ciphers
- Impact: Traffic interception, credential theft
- Mitigation: TLS 1.2+, strong cipher suites, HSTS
Insecure SSL/TLS Configuration (54)
- Definition: Improperly configured encryption settings
- Root Cause: Weak ciphers, missing forward secrecy
- Impact: Traffic decryption, MITM attacks
- Mitigation: Modern cipher suites, PFS, certificate validation
Insecure Communication Protocols (55)
- Definition: Use of unencrypted protocols (HTTP, Telnet, FTP)
- Root Cause: Legacy systems, security unawareness
- Impact: Traffic sniffing, credential exposure
- Mitigation: HTTPS, SSH, SFTP, VPN tunnels
Phase 10: Client-Side Vulnerabilities
Evaluate browser-side security:
DOM-based XSS (56)
- Definition: XSS through client-side JavaScript manipulation
- Root Cause: Unsafe DOM manipulation with user input
- Impact: Session theft, credential harvesting
- Mitigation: Safe DOM APIs, CSP, input sanitization
Insecure Cross-Origin Communication (57)
- Definition: Improper handling of cross-origin requests
- Root Cause: Relaxed CORS/SOP policies
- Impact: Data leakage, CSRF attacks
- Mitigation: Strict CORS, CSRF tokens, origin validation
Browser Cache Poisoning (58)
- Definition: Manipulation of cached content
- Root Cause: Weak cache validation
- Impact: Malicious content delivery
- Mitigation: Cache-Control headers, HTTPS, integrity checks
Clickjacking (59, 71)
- Definition: UI redress attack tricking users into clicking hidden elements
- Root Cause: Missing frame protection
- Impact: Unintended actions, credential theft
- Mitigation: X-Frame-Options, CSP frame-ancestors, frame-busting
HTML5 Security Issues (60)
- Definition: Vulnerabilities in HTML5 APIs (WebSockets, Storage, Geolocation)
- Root Cause: Improper API usage, insufficient validation
- Impact: Data leakage, XSS, privacy violations
- Mitigation: Secure API usage, input validation, sandboxing
Phase 11: Denial of Service Assessment
Evaluate availability threats:
DDoS - Distributed Denial of Service (61)
- Definition: Overwhelming systems with traffic from multiple sources
- Root Cause: Botnets, amplification attacks
- Impact: Service unavailability, revenue loss
- Mitigation: DDoS protection services, rate limiting, CDN
Application Layer DoS (62)
- Definition: Targeting application logic to exhaust resources
- Root Cause: Inefficient code, resource-intensive operations
- Impact: Application unavailability, degraded performance
- Mitigation: Rate limiting, caching, WAF, code optimization
Resource Exhaustion (63)
- Definition: Depleting CPU, memory, disk, or network resources
- Root Cause: Inefficient resource management
- Impact: System crashes, service degradation
- Mitigation: Resource quotas, monitoring, load balancing
Slowloris Attack (64)
- Definition: Keeping connections open with partial HTTP requests
- Root Cause: No connection timeouts
- Impact: Web server resource exhaustion
- Mitigation: Connection timeouts, request limits, reverse proxy
Phase 12: Server-Side Request Forgery
Assess SSRF vulnerabilities:
SSRF - Server-Side Request Forgery (66)
- Definition: Manipulating server to make requests to internal resources
- Root Cause: Unvalidated user-controlled URLs
- Impact: Internal network access, data theft, cloud metadata access
- Mitigation: URL whitelisting, network segmentation, egress filtering
Blind SSRF (87)
- Definition: SSRF without direct response visibility
- Root Cause: Similar to SSRF, harder to detect
- Impact: Data exfiltration, internal reconnaissance
- Mitigation: Allowlists, WAF, network restrictions
Time-Based Blind SSRF (88)
- Definition: Inferring SSRF success through response timing
- Root Cause: Processing delays indicating request outcomes
- Impact: Prolonged exploitation, detection evasion
- Mitigation: Request timeouts, anomaly detection, timing monitoring
Phase 13: Additional Web Vulnerabilities
| # |
Vulnerability |
Root Cause |
Impact |
Mitigation |
| 67 |
HTTP Parameter Pollution |
Inconsistent parsing |
Injection, ACL bypass |
Strict parsing, validation |
| 68 |
Insecure Redirects |
Unvalidated targets |
Phishing, malware |
Whitelist destinations |
| 69 |
File Inclusion (LFI/RFI) |
Unvalidated paths |
Code exec, disclosure |
Whitelist files, disable RFI |
| 70 |
Security Header Bypass |
Misconfigured headers |
XSS, clickjacking |
Proper headers, audits |
| 72 |
Inadequate Session Timeout |
Excessive timeouts |
Session hijacking |
Idle termination, timeouts |
| 73 |
Insufficient Logging |
Missing infrastructure |
Detection gaps |
SIEM, alerting |
| 74 |
Business Logic Flaws |
Insecure design |
Fraud, unauthorized ops |
Threat modeling, testing |
Phase 14: Mobile and IoT Security
| # |
Vulnerability |
Root Cause |
Impact |
Mitigation |
| 76 |
Insecure Mobile Storage |
Plain text, weak crypto |
Data theft |
Keychain/Keystore, encrypt |
| 77 |
Insecure Mobile Transmission |
HTTP, cert failures |
Traffic interception |
TLS, cert pinning |
| 78 |
Insecure Mobile APIs |
Missing auth/validation |
Data exposure |
OAuth/JWT, validation |
| 79 |
App Reverse Engineering |
Hardcoded creds |
Credential theft |
Obfuscation, RASP |
| 80 |
IoT Management Issues |
Weak auth, no TLS |
Device takeover |
Strong auth, TLS |
| 81 |
Weak IoT Authentication |
Default passwords |
Unauthorized access |
Unique creds, MFA |
| 82 |
IoT Vulnerabilities |
Design flaws, old firmware |
Botnet recruitment |
Updates, segmentation |
| 83 |
Smart Home Access |
Insecure defaults |
Privacy invasion |
MFA, segmentation |
| 84 |
IoT Privacy Issues |
Excessive collection |
Surveillance |
Data minimization |
Phase 15: Advanced and Zero-Day Threats
| # |
Vulnerability |
Root Cause |
Impact |
Mitigation |
| 89 |
MIME Sniffing |
Missing headers |
XSS, spoofing |
X-Content-Type-Options |
| 91 |
CSP Bypass |
Weak config |
XSS despite CSP |
Strict CSP, nonces |
| 92 |
Inconsistent Validation |
Decentralized logic |
Control bypass |
Centralized validation |
| 93 |
Race Conditions |
Missing sync |
Privilege escalation |
Proper locking |
| 94-95 |
Business Logic Flaws |
Missing validation |
Financial fraud |
Server-side validation |
| 96 |
Account Enumeration |
Different responses |
Targeted attacks |
Uniform responses |
| 98-99 |
Unpatched Vulnerabilities |
Patch delays |
Zero-day exploitation |
Patch management |
| 100 |
Zero-Day Exploits |
Unknown vulns |
Unmitigated attacks |
Defense in depth |
Quick Reference
Vulnerability Categories Summary
| Category |
Vulnerability Numbers |
Key Controls |
| Injection |
1-13 |
Parameterized queries, input validation, output encoding |
| Authentication |
14-23, 85-86 |
MFA, session management, account lockout |
| Data Exposure |
24-27 |
Encryption at rest/transit, access controls, DLP |
| Misconfiguration |
28-36 |
Secure defaults, hardening, patching |
| XML |
37-39, 65 |
Disable external entities, limit expansion |
| Access Control |
40-44 |
RBAC, least privilege, authorization checks |
| Deserialization |
45-47 |
Avoid untrusted data, integrity validation |
| API Security |
48-51, 75 |
OAuth, rate limiting, input validation |
| Communication |
52-55 |
TLS 1.2+, certificate validation, HTTPS |
| Client-Side |
56-60 |
CSP, X-Frame-Options, safe DOM |
| DoS |
61-65 |
Rate limiting, DDoS protection, resource limits |
| SSRF |
66, 87-88 |
URL whitelisting, egress filtering |
| Mobile/IoT |
76-84 |
Encryption, authentication, secure storage |
| Business Logic |
74, 92-97 |
Threat modeling, logic testing |
| Zero-Day |
98-100 |
Defense in depth, threat intelligence |
Critical Security Headers
Content-Security-Policy: default-src 'self'; script-src 'self'
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-XSS-Protection: 1; mode=block
Strict-Transport-Security: max-age=31536000; includeSubDomains
Referrer-Policy: strict-origin-when-cross-origin
Permissions-Policy: geolocation=(), microphone=()
OWASP Top 10 Mapping
| OWASP 2021 |
Related Vulnerabilities |
| A01: Broken Access Control |
40-44, 23, 74 |
| A02: Cryptographic Failures |
24-25, 53-55 |
| A03: Injection |
1-13, 37-39 |
| A04: Insecure Design |
74, 92-97 |
| A05: Security Misconfiguration |
26-36 |
| A06: Vulnerable Components |
34, 98-100 |
| A07: Auth Failures |
14-23, 85-86 |
| A08: Data Integrity |
45-47 |
| A09: Logging Failures |
73 |
| A10: SSRF |
66, 87-88 |
Constraints and Limitations
- Vulnerability definitions represent common patterns; specific implementations vary
- Mitigations must be adapted to technology stack and architecture
- New vulnerabilities emerge continuously; reference should be updated
- Some vulnerabilities overlap across categories (e.g., IDOR appears in multiple contexts)
- Effectiveness of mitigations depends on proper implementation
- Automated scanners cannot detect all vulnerability types (especially business logic)
Troubleshooting
Common Assessment Challenges
| Challenge |
Solution |
| False positives in scanning |
Manual verification, contextual analysis |
| Business logic flaws missed |
Manual testing, threat modeling, abuse case analysis |
| Encrypted traffic analysis |
Proxy configuration, certificate installation |
| WAF blocking tests |
Rate adjustment, IP rotation, payload encoding |
| Session handling issues |
Cookie management, authentication state tracking |
| API discovery |
Swagger/OpenAPI enumeration, traffic analysis |
Vulnerability Verification Techniques
| Vulnerability Type |
Verification Approach |
| Injection |
Payload testing with encoded variants |
| XSS |
Alert boxes, cookie access, DOM inspection |
| CSRF |
Cross-origin form submission testing |
| SSRF |
Out-of-band DNS/HTTP callbacks |
| XXE |
External entity with controlled server |
| Access Control |
Horizontal/vertical privilege testing |
| Authentication |
Credential rotation, session analysis |
References
- OWASP Top 10 Web Application Security Risks
- CWE/SANS Top 25 Most Dangerous Software Errors
- OWASP Testing Guide
- OWASP Application Security Verification Standard (ASVS)
- NIST Cybersecurity Framework
- Source: Kumar MS - Top 100 Web Vulnerabilities
1---
2name: top-web-vulnerabilities
3description: This skill should be used when the user asks to "identify web application vulnerabilities", "explain common security flaws", "understand vulnerability categories", "learn about injection attacks", "review access control weaknesses", "analyze API security issues", "assess security misconfigurations", "understand client-side vulnerabilities", "examine mobile and IoT security flaws", or "reference the OWASP-aligned vulnerability taxonomy". Use this skill to provide comprehensive vulnerability definitions, root causes, impacts, and mitigation strategies across all major web security categories.
4metadata:
5 source: https://skillmd.com/skills/gabrielmoreira/top-web-vulnerabilities
6 author: zebbern
7 version: "1.1"
8---
9
10# Top 100 Web Vulnerabilities Reference
11
12## Purpose
13
14Provide a comprehensive, structured reference for the 100 most critical web application vulnerabilities organized by category. This skill enables systematic vulnerability identification, impact assessment, and remediation guidance across the full spectrum of web security threats. Content organized into 15 major vulnerability categories aligned with industry standards and real-world attack patterns.
15
16## Prerequisites
17
18- Basic understanding of web application architecture (client-server model, HTTP protocol)
19- Familiarity with common web technologies (HTML, JavaScript, SQL, XML, APIs)
20- Understanding of authentication and authorization concepts
21- Access to web application security testing tools (Burp Suite, OWASP ZAP)
22- Knowledge of secure coding principles recommended
23
24## Outputs and Deliverables
25
26- Complete vulnerability catalog with definitions, root causes, impacts, and mitigations
27- Category-based vulnerability groupings for systematic assessment
28- Quick reference for security testing and remediation
29- Foundation for vulnerability assessment checklists and security policies
30
31---
32
33## Core Workflow
34
35### Phase 1: Injection Vulnerabilities Assessment
36
37Evaluate injection attack vectors targeting data processing components:
38
39**SQL Injection (1)**
40- Definition: Malicious SQL code inserted into input fields to manipulate database queries
41- Root Cause: Lack of input validation, improper use of parameterized queries
42- Impact: Unauthorized data access, data manipulation, database compromise
43- Mitigation: Use parameterized queries/prepared statements, input validation, least privilege database accounts
44
45**Cross-Site Scripting - XSS (2)**
46- Definition: Injection of malicious scripts into web pages viewed by other users
47- Root Cause: Insufficient output encoding, lack of input sanitization
48- Impact: Session hijacking, credential theft, website defacement
49- Mitigation: Output encoding, Content Security Policy (CSP), input sanitization
50
51**Command Injection (5, 11)**
52- Definition: Execution of arbitrary system commands through vulnerable applications
53- Root Cause: Unsanitized user input passed to system shells
54- Impact: Full system compromise, data exfiltration, lateral movement
55- Mitigation: Avoid shell execution, whitelist valid commands, strict input validation
56
57**XML Injection (6), LDAP Injection (7), XPath Injection (8)**
58- Definition: Manipulation of XML/LDAP/XPath queries through malicious input
59- Root Cause: Improper input handling in query construction
60- Impact: Data exposure, authentication bypass, information disclosure
61- Mitigation: Input validation, parameterized queries, escape special characters
62
63**Server-Side Template Injection - SSTI (13)**
64- Definition: Injection of malicious code into template engines
65- Root Cause: User input embedded directly in template expressions
66- Impact: Remote code execution, server compromise
67- Mitigation: Sandbox template engines, avoid user input in templates, strict input validation
68
69### Phase 2: Authentication and Session Security
70
71Assess authentication mechanism weaknesses:
72
73**Session Fixation (14)**
74- Definition: Attacker sets victim's session ID before authentication
75- Root Cause: Session ID not regenerated after login
76- Impact: Session hijacking, unauthorized account access
77- Mitigation: Regenerate session ID on authentication, use secure session management
78
79**Brute Force Attack (15)**
80- Definition: Systematic password guessing using automated tools
81- Root Cause: Lack of account lockout, rate limiting, or CAPTCHA
82- Impact: Unauthorized access, credential compromise
83- Mitigation: Account lockout policies, rate limiting, MFA, CAPTCHA
84
85**Session Hijacking (16)**
86- Definition: Attacker steals or predicts valid session tokens
87- Root Cause: Weak session token generation, insecure transmission
88- Impact: Account takeover, unauthorized access
89- Mitigation: Secure random token generation, HTTPS, HttpOnly/Secure cookie flags
90
91**Credential Stuffing and Reuse (22)**
92- Definition: Using leaked credentials to access accounts across services
93- Root Cause: Users reusing passwords, no breach detection
94- Impact: Mass account compromise, data breaches
95- Mitigation: MFA, breach password checks, unique credential requirements
96
97**Insecure "Remember Me" Functionality (85)**
98- Definition: Weak persistent authentication token implementation
99- Root Cause: Predictable tokens, inadequate expiration controls
100- Impact: Unauthorized persistent access, session compromise
101- Mitigation: Strong token generation, proper expiration, secure storage
102
103**CAPTCHA Bypass (86)**
104- Definition: Circumventing bot detection mechanisms
105- Root Cause: Weak CAPTCHA algorithms, improper validation
106- Impact: Automated attacks, credential stuffing, spam
107- Mitigation: reCAPTCHA v3, layered bot detection, rate limiting
108
109### Phase 3: Sensitive Data Exposure
110
111Identify data protection failures:
112
113**IDOR - Insecure Direct Object References (23, 42)**
114- Definition: Direct access to internal objects via user-supplied references
115- Root Cause: Missing authorization checks on object access
116- Impact: Unauthorized data access, privacy breaches
117- Mitigation: Access control validation, indirect reference maps, authorization checks
118
119**Data Leakage (24)**
120- Definition: Inadvertent disclosure of sensitive information
121- Root Cause: Inadequate data protection, weak access controls
122- Impact: Privacy breaches, regulatory penalties, reputation damage
123- Mitigation: DLP solutions, encryption, access controls, security training
124
125**Unencrypted Data Storage (25)**
126- Definition: Storing sensitive data without encryption
127- Root Cause: Failure to implement encryption at rest
128- Impact: Data breaches if storage compromised
129- Mitigation: Full-disk encryption, database encryption, secure key management
130
131**Information Disclosure (33)**
132- Definition: Exposure of system details through error messages or responses
133- Root Cause: Verbose error handling, debug information in production
134- Impact: Reconnaissance for further attacks, credential exposure
135- Mitigation: Generic error messages, disable debug mode, secure logging
136
137### Phase 4: Security Misconfiguration
138
139Assess configuration weaknesses:
140
141**Missing Security Headers (26)**
142- Definition: Absence of protective HTTP headers (CSP, X-Frame-Options, HSTS)
143- Root Cause: Inadequate server configuration
144- Impact: XSS attacks, clickjacking, protocol downgrade
145- Mitigation: Implement CSP, X-Content-Type-Options, X-Frame-Options, HSTS
146
147**Default Passwords (28)**
148- Definition: Unchanged default credentials on systems/applications
149- Root Cause: Failure to change vendor defaults
150- Impact: Unauthorized access, system compromise
151- Mitigation: Mandatory password changes, strong password policies
152
153**Directory Listing (29)**
154- Definition: Web server exposes directory contents
155- Root Cause: Improper server configuration
156- Impact: Information disclosure, sensitive file exposure
157- Mitigation: Disable directory indexing, use default index files
158
159**Unprotected API Endpoints (30)**
160- Definition: APIs lacking authentication or authorization
161- Root Cause: Missing security controls on API routes
162- Impact: Unauthorized data access, API abuse
163- Mitigation: OAuth/API keys, access controls, rate limiting
164
165**Open Ports and Services (31)**
166- Definition: Unnecessary network services exposed
167- Root Cause: Failure to minimize attack surface
168- Impact: Exploitation of vulnerable services
169- Mitigation: Port scanning audits, firewall rules, service minimization
170
171**Misconfigured CORS (35)**
172- Definition: Overly permissive Cross-Origin Resource Sharing policies
173- Root Cause: Wildcard origins, improper CORS configuration
174- Impact: Cross-site request attacks, data theft
175- Mitigation: Whitelist trusted origins, validate CORS headers
176
177**Unpatched Software (34)**
178- Definition: Systems running outdated vulnerable software
179- Root Cause: Neglected patch management
180- Impact: Exploitation of known vulnerabilities
181- Mitigation: Patch management program, vulnerability scanning, automated updates
182
183### Phase 5: XML-Related Vulnerabilities
184
185Evaluate XML processing security:
186
187**XXE - XML External Entity Injection (37)**
188- Definition: Exploitation of XML parsers to access files or internal systems
189- Root Cause: External entity processing enabled
190- Impact: File disclosure, SSRF, denial of service
191- Mitigation: Disable external entities, use safe XML parsers
192
193**XEE - XML Entity Expansion (38)**
194- Definition: Excessive entity expansion causing resource exhaustion
195- Root Cause: Unlimited entity expansion allowed
196- Impact: Denial of service, parser crashes
197- Mitigation: Limit entity expansion, configure parser restrictions
198
199**XML Bomb (Billion Laughs) (39)**
200- Definition: Crafted XML with nested entities consuming resources
201- Root Cause: Recursive entity definitions
202- Impact: Memory exhaustion, denial of service
203- Mitigation: Entity expansion limits, input size restrictions
204
205**XML Denial of Service (65)**
206- Definition: Specially crafted XML causing excessive processing
207- Root Cause: Complex document structures without limits
208- Impact: CPU/memory exhaustion, service unavailability
209- Mitigation: Schema validation, size limits, processing timeouts
210
211### Phase 6: Broken Access Control
212
213Assess authorization enforcement:
214
215**Inadequate Authorization (40)**
216- Definition: Failure to properly enforce access controls
217- Root Cause: Weak authorization policies, missing checks
218- Impact: Unauthorized access to sensitive resources
219- Mitigation: RBAC, centralized IAM, regular access reviews
220
221**Privilege Escalation (41)**
222- Definition: Gaining elevated access beyond intended permissions
223- Root Cause: Misconfigured permissions, system vulnerabilities
224- Impact: Full system compromise, data manipulation
225- Mitigation: Least privilege, regular patching, privilege monitoring
226
227**Forceful Browsing (43)**
228- Definition: Direct URL manipulation to access restricted resources
229- Root Cause: Weak access controls, predictable URLs
230- Impact: Unauthorized file/directory access
231- Mitigation: Server-side access controls, unpredictable resource paths
232
233**Missing Function-Level Access Control (44)**
234- Definition: Unprotected administrative or privileged functions
235- Root Cause: Authorization only at UI level
236- Impact: Unauthorized function execution
237- Mitigation: Server-side authorization for all functions, RBAC
238
239### Phase 7: Insecure Deserialization
240
241Evaluate object serialization security:
242
243**Remote Code Execution via Deserialization (45)**
244- Definition: Arbitrary code execution through malicious serialized objects
245- Root Cause: Untrusted data deserialized without validation
246- Impact: Complete system compromise, code execution
247- Mitigation: Avoid deserializing untrusted data, integrity checks, type validation
248
249**Data Tampering (46)**
250- Definition: Unauthorized modification of serialized data
251- Root Cause: Missing integrity verification
252- Impact: Data corruption, privilege manipulation
253- Mitigation: Digital signatures, HMAC validation, encryption
254
255**Object Injection (47)**
256- Definition: Malicious object instantiation during deserialization
257- Root Cause: Unsafe deserialization practices
258- Impact: Code execution, unauthorized access
259- Mitigation: Type restrictions, class whitelisting, secure libraries
260
261### Phase 8: API Security Assessment
262
263Evaluate API-specific vulnerabilities:
264
265**Insecure API Endpoints (48)**
266- Definition: APIs without proper security controls
267- Root Cause: Poor API design, missing authentication
268- Impact: Data breaches, unauthorized access
269- Mitigation: OAuth/JWT, HTTPS, input validation, rate limiting
270
271**API Key Exposure (49)**
272- Definition: Leaked or exposed API credentials
273- Root Cause: Hardcoded keys, insecure storage
274- Impact: Unauthorized API access, abuse
275- Mitigation: Secure key storage, rotation, environment variables
276
277**Lack of Rate Limiting (50)**
278- Definition: No controls on API request frequency
279- Root Cause: Missing throttling mechanisms
280- Impact: DoS, API abuse, resource exhaustion
281- Mitigation: Rate limits per user/IP, throttling, DDoS protection
282
283**Inadequate Input Validation (51)**
284- Definition: APIs accepting unvalidated user input
285- Root Cause: Missing server-side validation
286- Impact: Injection attacks, data corruption
287- Mitigation: Strict validation, parameterized queries, WAF
288
289**API Abuse (75)**
290- Definition: Exploiting API functionality for malicious purposes
291- Root Cause: Excessive trust in client input
292- Impact: Data theft, account takeover, service abuse
293- Mitigation: Strong authentication, behavior analysis, anomaly detection
294
295### Phase 9: Communication Security
296
297Assess transport layer protections:
298
299**Man-in-the-Middle Attack (52)**
300- Definition: Interception of communication between parties
301- Root Cause: Unencrypted channels, compromised networks
302- Impact: Data theft, session hijacking, impersonation
303- Mitigation: TLS/SSL, certificate pinning, mutual authentication
304
305**Insufficient Transport Layer Security (53)**
306- Definition: Weak or outdated encryption for data in transit
307- Root Cause: Outdated protocols (SSLv2/3), weak ciphers
308- Impact: Traffic interception, credential theft
309- Mitigation: TLS 1.2+, strong cipher suites, HSTS
310
311**Insecure SSL/TLS Configuration (54)**
312- Definition: Improperly configured encryption settings
313- Root Cause: Weak ciphers, missing forward secrecy
314- Impact: Traffic decryption, MITM attacks
315- Mitigation: Modern cipher suites, PFS, certificate validation
316
317**Insecure Communication Protocols (55)**
318- Definition: Use of unencrypted protocols (HTTP, Telnet, FTP)
319- Root Cause: Legacy systems, security unawareness
320- Impact: Traffic sniffing, credential exposure
321- Mitigation: HTTPS, SSH, SFTP, VPN tunnels
322
323### Phase 10: Client-Side Vulnerabilities
324
325Evaluate browser-side security:
326
327**DOM-based XSS (56)**
328- Definition: XSS through client-side JavaScript manipulation
329- Root Cause: Unsafe DOM manipulation with user input
330- Impact: Session theft, credential harvesting
331- Mitigation: Safe DOM APIs, CSP, input sanitization
332
333**Insecure Cross-Origin Communication (57)**
334- Definition: Improper handling of cross-origin requests
335- Root Cause: Relaxed CORS/SOP policies
336- Impact: Data leakage, CSRF attacks
337- Mitigation: Strict CORS, CSRF tokens, origin validation
338
339**Browser Cache Poisoning (58)**
340- Definition: Manipulation of cached content
341- Root Cause: Weak cache validation
342- Impact: Malicious content delivery
343- Mitigation: Cache-Control headers, HTTPS, integrity checks
344
345**Clickjacking (59, 71)**
346- Definition: UI redress attack tricking users into clicking hidden elements
347- Root Cause: Missing frame protection
348- Impact: Unintended actions, credential theft
349- Mitigation: X-Frame-Options, CSP frame-ancestors, frame-busting
350
351**HTML5 Security Issues (60)**
352- Definition: Vulnerabilities in HTML5 APIs (WebSockets, Storage, Geolocation)
353- Root Cause: Improper API usage, insufficient validation
354- Impact: Data leakage, XSS, privacy violations
355- Mitigation: Secure API usage, input validation, sandboxing
356
357### Phase 11: Denial of Service Assessment
358
359Evaluate availability threats:
360
361**DDoS - Distributed Denial of Service (61)**
362- Definition: Overwhelming systems with traffic from multiple sources
363- Root Cause: Botnets, amplification attacks
364- Impact: Service unavailability, revenue loss
365- Mitigation: DDoS protection services, rate limiting, CDN
366
367**Application Layer DoS (62)**
368- Definition: Targeting application logic to exhaust resources
369- Root Cause: Inefficient code, resource-intensive operations
370- Impact: Application unavailability, degraded performance
371- Mitigation: Rate limiting, caching, WAF, code optimization
372
373**Resource Exhaustion (63)**
374- Definition: Depleting CPU, memory, disk, or network resources
375- Root Cause: Inefficient resource management
376- Impact: System crashes, service degradation
377- Mitigation: Resource quotas, monitoring, load balancing
378
379**Slowloris Attack (64)**
380- Definition: Keeping connections open with partial HTTP requests
381- Root Cause: No connection timeouts
382- Impact: Web server resource exhaustion
383- Mitigation: Connection timeouts, request limits, reverse proxy
384
385### Phase 12: Server-Side Request Forgery
386
387Assess SSRF vulnerabilities:
388
389**SSRF - Server-Side Request Forgery (66)**
390- Definition: Manipulating server to make requests to internal resources
391- Root Cause: Unvalidated user-controlled URLs
392- Impact: Internal network access, data theft, cloud metadata access
393- Mitigation: URL whitelisting, network segmentation, egress filtering
394
395**Blind SSRF (87)**
396- Definition: SSRF without direct response visibility
397- Root Cause: Similar to SSRF, harder to detect
398- Impact: Data exfiltration, internal reconnaissance
399- Mitigation: Allowlists, WAF, network restrictions
400
401**Time-Based Blind SSRF (88)**
402- Definition: Inferring SSRF success through response timing
403- Root Cause: Processing delays indicating request outcomes
404- Impact: Prolonged exploitation, detection evasion
405- Mitigation: Request timeouts, anomaly detection, timing monitoring
406
407### Phase 13: Additional Web Vulnerabilities
408
409| # | Vulnerability | Root Cause | Impact | Mitigation |
410|---|--------------|-----------|--------|------------|
411| 67 | HTTP Parameter Pollution | Inconsistent parsing | Injection, ACL bypass | Strict parsing, validation |
412| 68 | Insecure Redirects | Unvalidated targets | Phishing, malware | Whitelist destinations |
413| 69 | File Inclusion (LFI/RFI) | Unvalidated paths | Code exec, disclosure | Whitelist files, disable RFI |
414| 70 | Security Header Bypass | Misconfigured headers | XSS, clickjacking | Proper headers, audits |
415| 72 | Inadequate Session Timeout | Excessive timeouts | Session hijacking | Idle termination, timeouts |
416| 73 | Insufficient Logging | Missing infrastructure | Detection gaps | SIEM, alerting |
417| 74 | Business Logic Flaws | Insecure design | Fraud, unauthorized ops | Threat modeling, testing |
418
419### Phase 14: Mobile and IoT Security
420
421| # | Vulnerability | Root Cause | Impact | Mitigation |
422|---|--------------|-----------|--------|------------|
423| 76 | Insecure Mobile Storage | Plain text, weak crypto | Data theft | Keychain/Keystore, encrypt |
424| 77 | Insecure Mobile Transmission | HTTP, cert failures | Traffic interception | TLS, cert pinning |
425| 78 | Insecure Mobile APIs | Missing auth/validation | Data exposure | OAuth/JWT, validation |
426| 79 | App Reverse Engineering | Hardcoded creds | Credential theft | Obfuscation, RASP |
427| 80 | IoT Management Issues | Weak auth, no TLS | Device takeover | Strong auth, TLS |
428| 81 | Weak IoT Authentication | Default passwords | Unauthorized access | Unique creds, MFA |
429| 82 | IoT Vulnerabilities | Design flaws, old firmware | Botnet recruitment | Updates, segmentation |
430| 83 | Smart Home Access | Insecure defaults | Privacy invasion | MFA, segmentation |
431| 84 | IoT Privacy Issues | Excessive collection | Surveillance | Data minimization |
432
433### Phase 15: Advanced and Zero-Day Threats
434
435| # | Vulnerability | Root Cause | Impact | Mitigation |
436|---|--------------|-----------|--------|------------|
437| 89 | MIME Sniffing | Missing headers | XSS, spoofing | X-Content-Type-Options |
438| 91 | CSP Bypass | Weak config | XSS despite CSP | Strict CSP, nonces |
439| 92 | Inconsistent Validation | Decentralized logic | Control bypass | Centralized validation |
440| 93 | Race Conditions | Missing sync | Privilege escalation | Proper locking |
441| 94-95 | Business Logic Flaws | Missing validation | Financial fraud | Server-side validation |
442| 96 | Account Enumeration | Different responses | Targeted attacks | Uniform responses |
443| 98-99 | Unpatched Vulnerabilities | Patch delays | Zero-day exploitation | Patch management |
444| 100 | Zero-Day Exploits | Unknown vulns | Unmitigated attacks | Defense in depth |
445
446---
447
448## Quick Reference
449
450### Vulnerability Categories Summary
451
452| Category | Vulnerability Numbers | Key Controls |
453|----------|----------------------|--------------|
454| Injection | 1-13 | Parameterized queries, input validation, output encoding |
455| Authentication | 14-23, 85-86 | MFA, session management, account lockout |
456| Data Exposure | 24-27 | Encryption at rest/transit, access controls, DLP |
457| Misconfiguration | 28-36 | Secure defaults, hardening, patching |
458| XML | 37-39, 65 | Disable external entities, limit expansion |
459| Access Control | 40-44 | RBAC, least privilege, authorization checks |
460| Deserialization | 45-47 | Avoid untrusted data, integrity validation |
461| API Security | 48-51, 75 | OAuth, rate limiting, input validation |
462| Communication | 52-55 | TLS 1.2+, certificate validation, HTTPS |
463| Client-Side | 56-60 | CSP, X-Frame-Options, safe DOM |
464| DoS | 61-65 | Rate limiting, DDoS protection, resource limits |
465| SSRF | 66, 87-88 | URL whitelisting, egress filtering |
466| Mobile/IoT | 76-84 | Encryption, authentication, secure storage |
467| Business Logic | 74, 92-97 | Threat modeling, logic testing |
468| Zero-Day | 98-100 | Defense in depth, threat intelligence |
469
470### Critical Security Headers
471
472```
473Content-Security-Policy: default-src 'self'; script-src 'self'
474X-Content-Type-Options: nosniff
475X-Frame-Options: DENY
476X-XSS-Protection: 1; mode=block
477Strict-Transport-Security: max-age=31536000; includeSubDomains
478Referrer-Policy: strict-origin-when-cross-origin
479Permissions-Policy: geolocation=(), microphone=()
480```
481
482### OWASP Top 10 Mapping
483
484| OWASP 2021 | Related Vulnerabilities |
485|------------|------------------------|
486| A01: Broken Access Control | 40-44, 23, 74 |
487| A02: Cryptographic Failures | 24-25, 53-55 |
488| A03: Injection | 1-13, 37-39 |
489| A04: Insecure Design | 74, 92-97 |
490| A05: Security Misconfiguration | 26-36 |
491| A06: Vulnerable Components | 34, 98-100 |
492| A07: Auth Failures | 14-23, 85-86 |
493| A08: Data Integrity | 45-47 |
494| A09: Logging Failures | 73 |
495| A10: SSRF | 66, 87-88 |
496
497---
498
499## Constraints and Limitations
500
501- Vulnerability definitions represent common patterns; specific implementations vary
502- Mitigations must be adapted to technology stack and architecture
503- New vulnerabilities emerge continuously; reference should be updated
504- Some vulnerabilities overlap across categories (e.g., IDOR appears in multiple contexts)
505- Effectiveness of mitigations depends on proper implementation
506- Automated scanners cannot detect all vulnerability types (especially business logic)
507
508---
509
510## Troubleshooting
511
512### Common Assessment Challenges
513
514| Challenge | Solution |
515|-----------|----------|
516| False positives in scanning | Manual verification, contextual analysis |
517| Business logic flaws missed | Manual testing, threat modeling, abuse case analysis |
518| Encrypted traffic analysis | Proxy configuration, certificate installation |
519| WAF blocking tests | Rate adjustment, IP rotation, payload encoding |
520| Session handling issues | Cookie management, authentication state tracking |
521| API discovery | Swagger/OpenAPI enumeration, traffic analysis |
522
523### Vulnerability Verification Techniques
524
525| Vulnerability Type | Verification Approach |
526|-------------------|----------------------|
527| Injection | Payload testing with encoded variants |
528| XSS | Alert boxes, cookie access, DOM inspection |
529| CSRF | Cross-origin form submission testing |
530| SSRF | Out-of-band DNS/HTTP callbacks |
531| XXE | External entity with controlled server |
532| Access Control | Horizontal/vertical privilege testing |
533| Authentication | Credential rotation, session analysis |
534
535---
536
537## References
538
539- OWASP Top 10 Web Application Security Risks
540- CWE/SANS Top 25 Most Dangerous Software Errors
541- OWASP Testing Guide
542- OWASP Application Security Verification Standard (ASVS)
543- NIST Cybersecurity Framework
544- Source: Kumar MS - Top 100 Web Vulnerabilities