This entry has been deprecated because it incorporated and confused multiple weaknesses. The issues formerly covered in this entry can be found at CWE-766 and CWE-767.
Modes of Introduction:
This weakness has been deprecated because it was a duplicate of CWE-493. All content has been transferred to CWE-493.
Modes of Introduction:
The application stores sensitive data under the web document root with insufficient access control, which might make it accessible to untrusted parties.
Besides public-facing web pages and code, applications may store sensitive data, code that is not directly invoked, or other files under the web document root of the web server. If the server is not configured or otherwise used to prevent direct access to those files, then attackers may obtain this sensitive data.
Modes of Introduction:
– Operation
Confidentiality: Read Application Data
Phase: Implementation, System Configuration
Description:
Avoid storing information under the web root directory.
Phase: System Configuration
Description:
Access control permissions should be set to prevent reading/writing of sensitive files inside/outside of the web directory.
The software validates input before applying protection mechanisms that modify the input, which could allow an attacker to bypass the validation via dangerous inputs that only arise after the modification.
Software needs to validate data at the proper time, after data has been canonicalized and cleansed. Early validation is susceptible to various manipulations that result in dangerous inputs that are produced by canonicalization and cleansing.
Modes of Introduction:
– Implementation
Access Control, Integrity: Bypass Protection Mechanism, Execute Unauthorized Code or Commands
An attacker could include dangerous input that bypasses validation protection mechanisms which can be used to launch various attacks including injection attacks, execute arbitrary code or cause other unintended behavior.
Phase: Implementation
Description:
Inputs should be decoded and canonicalized to the application’s current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
The software validates input before it is canonicalized, which prevents the software from detecting data that becomes invalid after the canonicalization step.
This can be used by an attacker to bypass the validation and launch attacks that expose weaknesses that would otherwise be prevented, such as injection.
Modes of Introduction:
– Implementation
Access Control: Bypass Protection Mechanism
Phase: Implementation
Description:
Inputs should be decoded and canonicalized to the application’s current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
The software validates data before it has been filtered, which prevents the software from detecting data that becomes invalid after the filtering step.
This can be used by an attacker to bypass the validation and launch attacks that expose weaknesses that would otherwise be prevented, such as injection.
Modes of Introduction:
– Implementation
Access Control: Bypass Protection Mechanism
Phase: Implementation, Architecture and Design
Description:
Inputs should be decoded and canonicalized to the application’s current internal representation before being filtered.
The software filters data in a way that causes it to be reduced or “collapsed” into an unsafe value that violates an expected security property.
Modes of Introduction:
– Implementation
Access Control: Bypass Protection Mechanism
Phase: Architecture and Design
Description:
Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.
Phase: Implementation
Description:
Phase: Implementation
Description:
Inputs should be decoded and canonicalized to the application’s current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
Phase:
Description:
Canonicalize the name to match that of the file system’s representation of the name. This can sometimes be achieved with an available API (e.g. in Win32 the GetFullPathName function).