CWE-162: Improper Neutralization of Trailing Special Elements
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes trailing special elements that could be interpreted in unexpected ways when they are sent to a downstream component.
View on MITREExtended Description
As data is parsed, improperly handled trailing special elements may cause the process to take unexpected actions that result in an attack.
Technical Details
- Structure
- Simple
Applicable To
Security Consequences
Scope
Impact
Mitigation Strategies
Phase
Description
Developers should anticipate that trailing special elements will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.
Detection Methods
No detection method information available for this CWE.
Code Examples & CVEs
Observed CVE Examples (3)
web framework for .NET allows remote attackers to bypass authentication for .aspx files in restricted directories via a request containing a (1) "\" (backslash) or (2) "%5C" (encoded backslash)
View DetailsApplication server allows remote attackers to read source code for .jsp files by appending a / to the requested URL.
View DetailsCWE Relationships
Frequently Asked Questions
What is CWE-162: Improper Neutralization of Trailing Special Elements?+
CWE-162: Improper Neutralization of Trailing Special Elements is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes trailing special elements that could be interpreted in unexpected ways when they are sent to a downstream component. As data is parsed, improperly handled trailing special elements may cause the process to take unexpected actions that result in an attack.
What are the security consequences of Improper Neutralization of Trailing Special Elements?+
If exploited, CWE-162 (Improper Neutralization of Trailing Special Elements) it can compromise Integrity, leading to outcomes such as Unexpected State.
How do you prevent or mitigate Improper Neutralization of Trailing Special Elements?+
Recommended mitigations for CWE-162 include: Developers should anticipate that trailing special elements will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.
Which programming languages are affected by Improper Neutralization of Trailing Special Elements?+
CWE-162 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 Improper Neutralization of Trailing Special Elements?+
MITRE documents real CVEs mapped to CWE-162, including CVE-2004-0847, CVE-2002-1451 and CVE-2001-0446. 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-162 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.