CWE-433: Unparsed Raw Web Content Delivery

VariantIncomplete

The product stores raw content or supporting code under the web document root with an extension that is not specifically handled by the server.

View on MITRE
Back to CWE Lookup

Extended Description

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.

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-433 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-433, Unparsed Raw Web Content Delivery, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address Unparsed Raw Web Content Delivery during Architecture and Design

MITRE associates mitigation with Architecture and Design; recorded impacts include Read Application Data; observed examples include CVE-2002-1886, CVE-2002-2065, and CVE-2005-2029. Use these source-defined anchors to turn CWE-433 into implementation, review, and verification checks for the affected component.

CWE-433: Unparsed Raw Web Content Delivery — MITRE CWE

Triage CWE-433 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-433, Unparsed Raw Web Content Delivery, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-433

Apply MITRE's full root-cause mapping guidance when using CWE-433, Unparsed Raw Web Content Delivery. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-433 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-433, Unparsed Raw Web Content Delivery. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-433: Unparsed Raw Web Content Delivery?+

CWE-433: Unparsed Raw Web Content Delivery is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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.

What are the security consequences of Unparsed Raw Web Content Delivery?+

If exploited, CWE-433 (Unparsed Raw Web Content Delivery) it can compromise Confidentiality, leading to outcomes such as Read Application Data.

How do you prevent or mitigate Unparsed Raw Web Content Delivery?+

Recommended mitigations for CWE-433 include: Perform a type check before interpreting files. Do not store sensitive information in files which may be misinterpreted.

Which programming languages are affected by Unparsed Raw Web Content Delivery?+

CWE-433 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Unparsed Raw Web Content Delivery?+

MITRE documents real CVEs mapped to CWE-433, including CVE-2002-1886, CVE-2002-2065, CVE-2005-2029, CVE-2001-0330 and CVE-2002-0614. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-433 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

Find Related CVEs

Search for vulnerabilities that exploit CWE-433

CVE vs CWE: What's the Difference?

Understanding vulnerabilities vs weaknesses

Understanding CVSS Scoring

How vulnerability severity is measured

View Full MITRE Entry

Complete technical details and references

Advertisement