Description
The product stores raw content or supporting code under the web document root with an extension that is not specifically handled by the server.
If code is stored in a file with an extension such as ".inc" or ".pl", and the web server does not have a handler for that extension, then the server will likely send the contents of the file directly to the requester without the pre-processing that was expected. When that file contains sensitive information such as database credentials, this may allow the attacker to compromise the application or associated components.
Potential Impact
Confidentiality
Read Application Data
Demonstrative Examples
<?php$dbName = 'usersDB';$dbPassword = 'skjdh#67nkjd3$3$';?><?phpinclude('database.inc');$db = connectToDB($dbName, $dbPassword);$db.authenticateUser($username, $password);?>Mitigations & Prevention
Perform a type check before interpreting files.
Do not store sensitive information in files which may be misinterpreted.
Real-World CVE Examples
| CVE ID | Description |
|---|---|
| CVE-2002-1886 | ".inc" file stored under web document root and returned unparsed by the server |
| CVE-2002-2065 | ".inc" file stored under web document root and returned unparsed by the server |
| CVE-2005-2029 | ".inc" file stored under web document root and returned unparsed by the server |
| CVE-2001-0330 | direct request to .pl file leaves it unparsed |
| CVE-2002-0614 | .inc file |
| CVE-2004-2353 | unparsed config.conf file |
| CVE-2007-3365 | Chain: uppercase file extensions causes web server to return script source code instead of executing the script. |
Related Weaknesses
Taxonomy Mappings
- PLOVER: — Unparsed Raw Web Content Delivery
Frequently Asked Questions
What is CWE-433?
CWE-433 (Unparsed Raw Web Content Delivery) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Variant-level weakness. The product stores raw content or supporting code under the web document root with an extension that is not specifically handled by the server.
How can CWE-433 be exploited?
Attackers can exploit CWE-433 (Unparsed Raw Web Content Delivery) to read application data. This weakness is typically introduced during the Implementation, Operation phase of software development.
How do I prevent CWE-433?
Key mitigations include: Perform a type check before interpreting files.
What is the severity of CWE-433?
CWE-433 is classified as a Variant-level weakness (Low-Medium abstraction). It has been observed in 7 real-world CVEs.