This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "CWE ESAPI"
From OWASP
(→CWE and ESAPI) |
(→CWE and ESAPI) |
||
| Line 42: | Line 42: | ||
* Access Control | * Access Control | ||
| + | |||
| + | ** CWE-639: Access Control Bypass Through User-Controlled Key | ||
| + | |||
| + | ** CWE-285: Missing or Inconsistent Access Control | ||
| + | |||
| + | ** CWE-647: Use of Non-Canonical URL Paths for Authorization Decisions | ||
* Encryption | * Encryption | ||
| + | |||
| + | ** CWE-311: Failure to Encrypt Sensitive Data | ||
| + | |||
| + | ** CWE-649: Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking | ||
| + | |||
| + | ** CWE-323: Reusing a Nonce, Key Pair in Encryption | ||
| + | |||
| + | ** CWE-327: Use of a Broken or Risky Cryptographic Algorithm | ||
* Randomizer | * Randomizer | ||
| + | |||
| + | ** CWE-330: Use of Insufficiently Random Values | ||
* Error Handling | * Error Handling | ||
| + | |||
| + | ** CWE-209: Error Message Information Leaks | ||
| + | |||
| + | ** CWE-392: Failure to Report Error in Status Code | ||
* Logging | * Logging | ||
| + | |||
| + | ** CWE-222: Truncation of Security-relevant Information | ||
| + | |||
| + | ** CWE-117: Incorrect Output Sanitization for Logs | ||
| + | |||
| + | ** CWE-532: Information Leak Through Log Files | ||
* Intrusion Detection | * Intrusion Detection | ||
Revision as of 19:45, 11 December 2008
CWE and ESAPI
This page covers the relationships between ESAPI controls and the CWE entries that are eliminated or reduced by the application of those controls.
- Validation
- CWE-20: Insufficient Input Validation
- CWE-116: Insufficient Output Sanitization
- CWE-228: Failure to Handle Syntactically Invalid Structure
- Canonicalization
- CWE-22: Path Traversal
- CWE-41: Failure to Resolve Path Equivalence
- CWE-178: Failure to Resolve Case Sensitivity
- Encoding
- CWE-113: Failure to Sanitize CRLF Sequences in HTTP Headers (aka 'HTTP Response Splitting')
- CWE-79: Failure to Sanitize Directives in a Web Page (aka 'Cross-site scripting' (XSS))
- CWE-89: Failure to Sanitize Data within SQL Queries (aka 'SQL Injection')
- Authentication
- CWE-287: Insufficient Authentication
- Session Management
- CWE-488: Data Leak Between Sessions
- CWE-613: Insufficient Session Expiration
- CWE-384: Session Fixation
- CWE-614: Sensitive Cookie in HTTPS Session Without "Secure" Attribute
- Access Control
- CWE-639: Access Control Bypass Through User-Controlled Key
- CWE-285: Missing or Inconsistent Access Control
- CWE-647: Use of Non-Canonical URL Paths for Authorization Decisions
- Encryption
- CWE-311: Failure to Encrypt Sensitive Data
- CWE-649: Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking
- CWE-323: Reusing a Nonce, Key Pair in Encryption
- CWE-327: Use of a Broken or Risky Cryptographic Algorithm
- Randomizer
- CWE-330: Use of Insufficiently Random Values
- Error Handling
- CWE-209: Error Message Information Leaks
- CWE-392: Failure to Report Error in Status Code
- Logging
- CWE-222: Truncation of Security-relevant Information
- CWE-117: Incorrect Output Sanitization for Logs
- CWE-532: Information Leak Through Log Files
- Intrusion Detection
- HTTP Protection
- Utilities
- Filters
Method
Only CWE identifiers associated with weaknesses were reviewed. (Some CWE entries are arbitrary groupings that organize weaknesses instead of being weaknesses themselves). Only the most abstract CWE identifiers were mapped, implying that lower-level variants are also covered (based on the hierarchy imposed by CWE-1000, the research view, which has a different hierarchical structure than CWE-699, the developer view).
