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, enprojectnment 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
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
1---2name: top-web-vulnerabilities3description: 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.4---56# Top 100 Web Vulnerabilities Reference78## Purpose910Provide 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.1112## Prerequisites1314- Basic understanding of web application architecture (client-server model, HTTP protocol)15- Familiarity with common web technologies (HTML, JavaScript, SQL, XML, APIs)16- Understanding of authentication and authorization concepts17- Access to web application security testing tools (Burp Suite, OWASP ZAP)18- Knowledge of secure coding principles recommended1920## Outputs and Deliverables2122- Complete vulnerability catalog with definitions, root causes, impacts, and mitigations23- Category-based vulnerability groupings for systematic assessment24- Quick reference for security testing and remediation25- Foundation for vulnerability assessment checklists and security policies2627---2829## Core Workflow3031### Phase 1: Injection Vulnerabilities Assessment3233Evaluate injection attack vectors targeting data processing components:3435**SQL Injection (1)**36- Definition: Malicious SQL code inserted into input fields to manipulate database queries37- Root Cause: Lack of input validation, improper use of parameterized queries38- Impact: Unauthorized data access, data manipulation, database compromise39- Mitigation: Use parameterized queries/prepared statements, input validation, least privilege database accounts4041**Cross-Site Scripting - XSS (2)**42- Definition: Injection of malicious scripts into web pages viewed by other users43- Root Cause: Insufficient output encoding, lack of input sanitization44- Impact: Session hijacking, credential theft, website defacement45- Mitigation: Output encoding, Content Security Policy (CSP), input sanitization4647**Command Injection (5, 11)**48- Definition: Execution of arbitrary system commands through vulnerable applications49- Root Cause: Unsanitized user input passed to system shells50- Impact: Full system compromise, data exfiltration, lateral movement51- Mitigation: Avoid shell execution, whitelist valid commands, strict input validation5253**XML Injection (6), LDAP Injection (7), XPath Injection (8)**54- Definition: Manipulation of XML/LDAP/XPath queries through malicious input55- Root Cause: Improper input handling in query construction56- Impact: Data exposure, authentication bypass, information disclosure57- Mitigation: Input validation, parameterized queries, escape special characters5859**Server-Side Template Injection - SSTI (13)**60- Definition: Injection of malicious code into template engines61- Root Cause: User input embedded directly in template expressions62- Impact: Remote code execution, server compromise63- Mitigation: Sandbox template engines, avoid user input in templates, strict input validation6465### Phase 2: Authentication and Session Security6667Assess authentication mechanism weaknesses:6869**Session Fixation (14)**70- Definition: Attacker sets victim's session ID before authentication71- Root Cause: Session ID not regenerated after login72- Impact: Session hijacking, unauthorized account access73- Mitigation: Regenerate session ID on authentication, use secure session management7475**Brute Force Attack (15)**76- Definition: Systematic password guessing using automated tools77- Root Cause: Lack of account lockout, rate limiting, or CAPTCHA78- Impact: Unauthorized access, credential compromise79- Mitigation: Account lockout policies, rate limiting, MFA, CAPTCHA8081**Session Hijacking (16)**82- Definition: Attacker steals or predicts valid session tokens83- Root Cause: Weak session token generation, insecure transmission84- Impact: Account takeover, unauthorized access85- Mitigation: Secure random token generation, HTTPS, HttpOnly/Secure cookie flags8687**Credential Stuffing and Reuse (22)**88- Definition: Using leaked credentials to access accounts across services89- Root Cause: Users reusing passwords, no breach detection90- Impact: Mass account compromise, data breaches91- Mitigation: MFA, breach password checks, unique credential requirements9293**Insecure "Remember Me" Functionality (85)**94- Definition: Weak persistent authentication token implementation95- Root Cause: Predictable tokens, inadequate expiration controls96- Impact: Unauthorized persistent access, session compromise97- Mitigation: Strong token generation, proper expiration, secure storage9899**CAPTCHA Bypass (86)**100- Definition: Circumventing bot detection mechanisms101- Root Cause: Weak CAPTCHA algorithms, improper validation102- Impact: Automated attacks, credential stuffing, spam103- Mitigation: reCAPTCHA v3, layered bot detection, rate limiting104105### Phase 3: Sensitive Data Exposure106107Identify data protection failures:108109**IDOR - Insecure Direct Object References (23, 42)**110- Definition: Direct access to internal objects via user-supplied references111- Root Cause: Missing authorization checks on object access112- Impact: Unauthorized data access, privacy breaches113- Mitigation: Access control validation, indirect reference maps, authorization checks114115**Data Leakage (24)**116- Definition: Inadvertent disclosure of sensitive information117- Root Cause: Inadequate data protection, weak access controls118- Impact: Privacy breaches, regulatory penalties, reputation damage119- Mitigation: DLP solutions, encryption, access controls, security training120121**Unencrypted Data Storage (25)**122- Definition: Storing sensitive data without encryption123- Root Cause: Failure to implement encryption at rest124- Impact: Data breaches if storage compromised125- Mitigation: Full-disk encryption, database encryption, secure key management126127**Information Disclosure (33)**128- Definition: Exposure of system details through error messages or responses129- Root Cause: Verbose error handling, debug information in production130- Impact: Reconnaissance for further attacks, credential exposure131- Mitigation: Generic error messages, disable debug mode, secure logging132133### Phase 4: Security Misconfiguration134135Assess configuration weaknesses:136137**Missing Security Headers (26)**138- Definition: Absence of protective HTTP headers (CSP, X-Frame-Options, HSTS)139- Root Cause: Inadequate server configuration140- Impact: XSS attacks, clickjacking, protocol downgrade141- Mitigation: Implement CSP, X-Content-Type-Options, X-Frame-Options, HSTS142143**Default Passwords (28)**144- Definition: Unchanged default credentials on systems/applications145- Root Cause: Failure to change vendor defaults146- Impact: Unauthorized access, system compromise147- Mitigation: Mandatory password changes, strong password policies148149**Directory Listing (29)**150- Definition: Web server exposes directory contents151- Root Cause: Improper server configuration152- Impact: Information disclosure, sensitive file exposure153- Mitigation: Disable directory indexing, use default index files154155**Unprotected API Endpoints (30)**156- Definition: APIs lacking authentication or authorization157- Root Cause: Missing security controls on API routes158- Impact: Unauthorized data access, API abuse159- Mitigation: OAuth/API keys, access controls, rate limiting160161**Open Ports and Services (31)**162- Definition: Unnecessary network services exposed163- Root Cause: Failure to minimize attack surface164- Impact: Exploitation of vulnerable services165- Mitigation: Port scanning audits, firewall rules, service minimization166167**Misconfigured CORS (35)**168- Definition: Overly permissive Cross-Origin Resource Sharing policies169- Root Cause: Wildcard origins, improper CORS configuration170- Impact: Cross-site request attacks, data theft171- Mitigation: Whitelist trusted origins, validate CORS headers172173**Unpatched Software (34)**174- Definition: Systems running outdated vulnerable software175- Root Cause: Neglected patch management176- Impact: Exploitation of known vulnerabilities177- Mitigation: Patch management program, vulnerability scanning, automated updates178179### Phase 5: XML-Related Vulnerabilities180181Evaluate XML processing security:182183**XXE - XML External Entity Injection (37)**184- Definition: Exploitation of XML parsers to access files or internal systems185- Root Cause: External entity processing enabled186- Impact: File disclosure, SSRF, denial of service187- Mitigation: Disable external entities, use safe XML parsers188189**XEE - XML Entity Expansion (38)**190- Definition: Excessive entity expansion causing resource exhaustion191- Root Cause: Unlimited entity expansion allowed192- Impact: Denial of service, parser crashes193- Mitigation: Limit entity expansion, configure parser restrictions194195**XML Bomb (Billion Laughs) (39)**196- Definition: Crafted XML with nested entities consuming resources197- Root Cause: Recursive entity definitions198- Impact: Memory exhaustion, denial of service199- Mitigation: Entity expansion limits, input size restrictions200201**XML Denial of Service (65)**202- Definition: Specially crafted XML causing excessive processing203- Root Cause: Complex document structures without limits204- Impact: CPU/memory exhaustion, service unavailability205- Mitigation: Schema validation, size limits, processing timeouts206207### Phase 6: Broken Access Control208209Assess authorization enforcement:210211**Inadequate Authorization (40)**212- Definition: Failure to properly enforce access controls213- Root Cause: Weak authorization policies, missing checks214- Impact: Unauthorized access to sensitive resources215- Mitigation: RBAC, centralized IAM, regular access reviews216217**Privilege Escalation (41)**218- Definition: Gaining elevated access beyond intended permissions219- Root Cause: Misconfigured permissions, system vulnerabilities220- Impact: Full system compromise, data manipulation221- Mitigation: Least privilege, regular patching, privilege monitoring222223**Forceful Browsing (43)**224- Definition: Direct URL manipulation to access restricted resources225- Root Cause: Weak access controls, predictable URLs226- Impact: Unauthorized file/directory access227- Mitigation: Server-side access controls, unpredictable resource paths228229**Missing Function-Level Access Control (44)**230- Definition: Unprotected administrative or privileged functions231- Root Cause: Authorization only at UI level232- Impact: Unauthorized function execution233- Mitigation: Server-side authorization for all functions, RBAC234235### Phase 7: Insecure Deserialization236237Evaluate object serialization security:238239**Remote Code Execution via Deserialization (45)**240- Definition: Arbitrary code execution through malicious serialized objects241- Root Cause: Untrusted data deserialized without validation242- Impact: Complete system compromise, code execution243- Mitigation: Avoid deserializing untrusted data, integrity checks, type validation244245**Data Tampering (46)**246- Definition: Unauthorized modification of serialized data247- Root Cause: Missing integrity verification248- Impact: Data corruption, privilege manipulation249- Mitigation: Digital signatures, HMAC validation, encryption250251**Object Injection (47)**252- Definition: Malicious object instantiation during deserialization253- Root Cause: Unsafe deserialization practices254- Impact: Code execution, unauthorized access255- Mitigation: Type restrictions, class whitelisting, secure libraries256257### Phase 8: API Security Assessment258259Evaluate API-specific vulnerabilities:260261**Insecure API Endpoints (48)**262- Definition: APIs without proper security controls263- Root Cause: Poor API design, missing authentication264- Impact: Data breaches, unauthorized access265- Mitigation: OAuth/JWT, HTTPS, input validation, rate limiting266267**API Key Exposure (49)**268- Definition: Leaked or exposed API credentials269- Root Cause: Hardcoded keys, insecure storage270- Impact: Unauthorized API access, abuse271- Mitigation: Secure key storage, rotation, enprojectnment variables272273**Lack of Rate Limiting (50)**274- Definition: No controls on API request frequency275- Root Cause: Missing throttling mechanisms276- Impact: DoS, API abuse, resource exhaustion277- Mitigation: Rate limits per user/IP, throttling, DDoS protection278279**Inadequate Input Validation (51)**280- Definition: APIs accepting unvalidated user input281- Root Cause: Missing server-side validation282- Impact: Injection attacks, data corruption283- Mitigation: Strict validation, parameterized queries, WAF284285**API Abuse (75)**286- Definition: Exploiting API functionality for malicious purposes287- Root Cause: Excessive trust in client input288- Impact: Data theft, account takeover, service abuse289- Mitigation: Strong authentication, behavior analysis, anomaly detection290291### Phase 9: Communication Security292293Assess transport layer protections:294295**Man-in-the-Middle Attack (52)**296- Definition: Interception of communication between parties297- Root Cause: Unencrypted channels, compromised networks298- Impact: Data theft, session hijacking, impersonation299- Mitigation: TLS/SSL, certificate pinning, mutual authentication300301**Insufficient Transport Layer Security (53)**302- Definition: Weak or outdated encryption for data in transit303- Root Cause: Outdated protocols (SSLv2/3), weak ciphers304- Impact: Traffic interception, credential theft305- Mitigation: TLS 1.2+, strong cipher suites, HSTS306307**Insecure SSL/TLS Configuration (54)**308- Definition: Improperly configured encryption settings309- Root Cause: Weak ciphers, missing forward secrecy310- Impact: Traffic decryption, MITM attacks311- Mitigation: Modern cipher suites, PFS, certificate validation312313**Insecure Communication Protocols (55)**314- Definition: Use of unencrypted protocols (HTTP, Telnet, FTP)315- Root Cause: Legacy systems, security unawareness316- Impact: Traffic sniffing, credential exposure317- Mitigation: HTTPS, SSH, SFTP, VPN tunnels318319### Phase 10: Client-Side Vulnerabilities320321Evaluate browser-side security:322323**DOM-based XSS (56)**324- Definition: XSS through client-side JavaScript manipulation325- Root Cause: Unsafe DOM manipulation with user input326- Impact: Session theft, credential harvesting327- Mitigation: Safe DOM APIs, CSP, input sanitization328329**Insecure Cross-Origin Communication (57)**330- Definition: Improper handling of cross-origin requests331- Root Cause: Relaxed CORS/SOP policies332- Impact: Data leakage, CSRF attacks333- Mitigation: Strict CORS, CSRF tokens, origin validation334335**Browser Cache Poisoning (58)**336- Definition: Manipulation of cached content337- Root Cause: Weak cache validation338- Impact: Malicious content delivery339- Mitigation: Cache-Control headers, HTTPS, integrity checks340341**Clickjacking (59, 71)**342- Definition: UI redress attack tricking users into clicking hidden elements343- Root Cause: Missing frame protection344- Impact: Unintended actions, credential theft345- Mitigation: X-Frame-Options, CSP frame-ancestors, frame-busting346347**HTML5 Security Issues (60)**348- Definition: Vulnerabilities in HTML5 APIs (WebSockets, Storage, Geolocation)349- Root Cause: Improper API usage, insufficient validation350- Impact: Data leakage, XSS, privacy violations351- Mitigation: Secure API usage, input validation, sandboxing352353### Phase 11: Denial of Service Assessment354355Evaluate availability threats:356357**DDoS - Distributed Denial of Service (61)**358- Definition: Overwhelming systems with traffic from multiple sources359- Root Cause: Botnets, amplification attacks360- Impact: Service unavailability, revenue loss361- Mitigation: DDoS protection services, rate limiting, CDN362363**Application Layer DoS (62)**364- Definition: Targeting application logic to exhaust resources365- Root Cause: Inefficient code, resource-intensive operations366- Impact: Application unavailability, degraded performance367- Mitigation: Rate limiting, caching, WAF, code optimization368369**Resource Exhaustion (63)**370- Definition: Depleting CPU, memory, disk, or network resources371- Root Cause: Inefficient resource management372- Impact: System crashes, service degradation373- Mitigation: Resource quotas, monitoring, load balancing374375**Slowloris Attack (64)**376- Definition: Keeping connections open with partial HTTP requests377- Root Cause: No connection timeouts378- Impact: Web server resource exhaustion379- Mitigation: Connection timeouts, request limits, reverse proxy380381### Phase 12: Server-Side Request Forgery382383Assess SSRF vulnerabilities:384385**SSRF - Server-Side Request Forgery (66)**386- Definition: Manipulating server to make requests to internal resources387- Root Cause: Unvalidated user-controlled URLs388- Impact: Internal network access, data theft, cloud metadata access389- Mitigation: URL whitelisting, network segmentation, egress filtering390391**Blind SSRF (87)**392- Definition: SSRF without direct response visibility393- Root Cause: Similar to SSRF, harder to detect394- Impact: Data exfiltration, internal reconnaissance395- Mitigation: Allowlists, WAF, network restrictions396397**Time-Based Blind SSRF (88)**398- Definition: Inferring SSRF success through response timing399- Root Cause: Processing delays indicating request outcomes400- Impact: Prolonged exploitation, detection evasion401- Mitigation: Request timeouts, anomaly detection, timing monitoring402403### Phase 13: Additional Web Vulnerabilities404405| # | Vulnerability | Root Cause | Impact | Mitigation |406|---|--------------|-----------|--------|------------|407| 67 | HTTP Parameter Pollution | Inconsistent parsing | Injection, ACL bypass | Strict parsing, validation |408| 68 | Insecure Redirects | Unvalidated targets | Phishing, malware | Whitelist destinations |409| 69 | File Inclusion (LFI/RFI) | Unvalidated paths | Code exec, disclosure | Whitelist files, disable RFI |410| 70 | Security Header Bypass | Misconfigured headers | XSS, clickjacking | Proper headers, audits |411| 72 | Inadequate Session Timeout | Excessive timeouts | Session hijacking | Idle termination, timeouts |412| 73 | Insufficient Logging | Missing infrastructure | Detection gaps | SIEM, alerting |413| 74 | Business Logic Flaws | Insecure design | Fraud, unauthorized ops | Threat modeling, testing |414415### Phase 14: Mobile and IoT Security416417| # | Vulnerability | Root Cause | Impact | Mitigation |418|---|--------------|-----------|--------|------------|419| 76 | Insecure Mobile Storage | Plain text, weak crypto | Data theft | Keychain/Keystore, encrypt |420| 77 | Insecure Mobile Transmission | HTTP, cert failures | Traffic interception | TLS, cert pinning |421| 78 | Insecure Mobile APIs | Missing auth/validation | Data exposure | OAuth/JWT, validation |422| 79 | App Reverse Engineering | Hardcoded creds | Credential theft | Obfuscation, RASP |423| 80 | IoT Management Issues | Weak auth, no TLS | Device takeover | Strong auth, TLS |424| 81 | Weak IoT Authentication | Default passwords | Unauthorized access | Unique creds, MFA |425| 82 | IoT Vulnerabilities | Design flaws, old firmware | Botnet recruitment | Updates, segmentation |426| 83 | Smart Home Access | Insecure defaults | Privacy invasion | MFA, segmentation |427| 84 | IoT Privacy Issues | Excessive collection | Surveillance | Data minimization |428429### Phase 15: Advanced and Zero-Day Threats430431| # | Vulnerability | Root Cause | Impact | Mitigation |432|---|--------------|-----------|--------|------------|433| 89 | MIME Sniffing | Missing headers | XSS, spoofing | X-Content-Type-Options |434| 91 | CSP Bypass | Weak config | XSS despite CSP | Strict CSP, nonces |435| 92 | Inconsistent Validation | Decentralized logic | Control bypass | Centralized validation |436| 93 | Race Conditions | Missing sync | Privilege escalation | Proper locking |437| 94-95 | Business Logic Flaws | Missing validation | Financial fraud | Server-side validation |438| 96 | Account Enumeration | Different responses | Targeted attacks | Uniform responses |439| 98-99 | Unpatched Vulnerabilities | Patch delays | Zero-day exploitation | Patch management |440| 100 | Zero-Day Exploits | Unknown vulns | Unmitigated attacks | Defense in depth |441442---443444## Quick Reference445446### Vulnerability Categories Summary447448| Category | Vulnerability Numbers | Key Controls |449|----------|----------------------|--------------|450| Injection | 1-13 | Parameterized queries, input validation, output encoding |451| Authentication | 14-23, 85-86 | MFA, session management, account lockout |452| Data Exposure | 24-27 | Encryption at rest/transit, access controls, DLP |453| Misconfiguration | 28-36 | Secure defaults, hardening, patching |454| XML | 37-39, 65 | Disable external entities, limit expansion |455| Access Control | 40-44 | RBAC, least privilege, authorization checks |456| Deserialization | 45-47 | Avoid untrusted data, integrity validation |457| API Security | 48-51, 75 | OAuth, rate limiting, input validation |458| Communication | 52-55 | TLS 1.2+, certificate validation, HTTPS |459| Client-Side | 56-60 | CSP, X-Frame-Options, safe DOM |460| DoS | 61-65 | Rate limiting, DDoS protection, resource limits |461| SSRF | 66, 87-88 | URL whitelisting, egress filtering |462| Mobile/IoT | 76-84 | Encryption, authentication, secure storage |463| Business Logic | 74, 92-97 | Threat modeling, logic testing |464| Zero-Day | 98-100 | Defense in depth, threat intelligence |465466### Critical Security Headers467468```469Content-Security-Policy: default-src 'self'; script-src 'self'470X-Content-Type-Options: nosniff471X-Frame-Options: DENY472X-XSS-Protection: 1; mode=block473Strict-Transport-Security: max-age=31536000; includeSubDomains474Referrer-Policy: strict-origin-when-cross-origin475Permissions-Policy: geolocation=(), microphone=()476```477478### OWASP Top 10 Mapping479480| OWASP 2021 | Related Vulnerabilities |481|------------|------------------------|482| A01: Broken Access Control | 40-44, 23, 74 |483| A02: Cryptographic Failures | 24-25, 53-55 |484| A03: Injection | 1-13, 37-39 |485| A04: Insecure Design | 74, 92-97 |486| A05: Security Misconfiguration | 26-36 |487| A06: Vulnerable Components | 34, 98-100 |488| A07: Auth Failures | 14-23, 85-86 |489| A08: Data Integrity | 45-47 |490| A09: Logging Failures | 73 |491| A10: SSRF | 66, 87-88 |492493---494495## Constraints and Limitations496497- Vulnerability definitions represent common patterns; specific implementations vary498- Mitigations must be adapted to technology stack and architecture499- New vulnerabilities emerge continuously; reference should be updated500- Some vulnerabilities overlap across categories (e.g., IDOR appears in multiple contexts)501- Effectiveness of mitigations depends on proper implementation502- Automated scanners cannot detect all vulnerability types (especially business logic)503504---505506## Troubleshooting507508### Common Assessment Challenges509510| Challenge | Solution |511|-----------|----------|512| False positives in scanning | Manual verification, contextual analysis |513| Business logic flaws missed | Manual testing, threat modeling, abuse case analysis |514| Encrypted traffic analysis | Proxy configuration, certificate installation |515| WAF blocking tests | Rate adjustment, IP rotation, payload encoding |516| Session handling issues | Cookie management, authentication state tracking |517| API discovery | Swagger/OpenAPI enumeration, traffic analysis |518519### Vulnerability Verification Techniques520521| Vulnerability Type | Verification Approach |522|-------------------|----------------------|523| Injection | Payload testing with encoded variants |524| XSS | Alert boxes, cookie access, DOM inspection |525| CSRF | Cross-origin form submission testing |526| SSRF | Out-of-band DNS/HTTP callbacks |527| XXE | External entity with controlled server |528| Access Control | Horizontal/vertical privilege testing |529| Authentication | Credential rotation, session analysis |530531---532533## References534535- OWASP Top 10 Web Application Security Risks536- CWE/SANS Top 25 Most Dangerous Software Errors537- OWASP Testing Guide538- OWASP Application Security Verification Standard (ASVS)539- NIST Cybersecurity Framework540- Source: Kumar MS - Top 100 Web Vulnerabilities541542## When to Use543This skill is applicable to execute the workflow or actions described in the overview.