Description
The software 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.
Modes of Introduction:
– Implementation
Related Weaknesses
Consequences
Confidentiality: Read Application Data
Potential Mitigations
Phase: Architecture and Design
Description:
Perform a type check before interpreting files.
Phase: Architecture and Design
Description:
Do not store sensitive information in files which may be misinterpreted.
CVE References
- 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.
More Stories
The Most Dangerous Vulnerabilities in Apache Tomcat and How to Protect Against Them
Apache Tomcat is an open-source web server and servlet container that is widely used in enterprise environments to run Java...
ZDI-CAN-18333: A Critical Zero-Day Vulnerability in Microsoft Windows
Zero-day vulnerabilities are a serious threat to cybersecurity, as they can be exploited by malicious actors to gain unauthorized access...
CWE-669 – Incorrect Resource Transfer Between Spheres
Description The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere,...
CWE-67 – Improper Handling of Windows Device Names
Description The software constructs pathnames from user input, but it does not handle or incorrectly handles a pathname containing a...
CWE-670 – Always-Incorrect Control Flow Implementation
Description The code contains a control flow path that does not reflect the algorithm that the path is intended to...
CWE-671 – Lack of Administrator Control over Security
Description The product uses security features in a way that prevents the product's administrator from tailoring security settings to reflect...