Description
The software receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as escape, meta, or control character sequences when they are sent to a downstream component.
As data is parsed, an injected/absent/malformed delimiter may cause the process to take unexpected actions.
Modes of Introduction:
– Implementation
Related Weaknesses
Consequences
Integrity: Unexpected State
Potential Mitigations
Phase:
Description:
Developers should anticipate that escape, meta and control characters/sequences will be injected/removed/manipulated in the input vectors of their software system. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.
Phase: Implementation
Description:
Phase: Implementation
Description:
While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).
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.
CVE References
- CVE-2002-0542
- The mail program processes special “~” escape sequence even when not in interactive mode.
- CVE-2000-0703
- Setuid program does not filter escape sequences before calling mail program.
- CVE-2002-0986
- Mail function does not filter control characters from arguments, allowing mail message content to be modified.
- CVE-2003-0020
- Multi-channel issue. Terminal escape sequences not filtered from log files.
- CVE-2003-0083
- Multi-channel issue. Terminal escape sequences not filtered from log files.
- CVE-2003-0021
- Terminal escape sequences not filtered by terminals when displaying files.
- CVE-2003-0022
- Terminal escape sequences not filtered by terminals when displaying files.
- CVE-2003-0023
- Terminal escape sequences not filtered by terminals when displaying files.
- CVE-2003-0063
- Terminal escape sequences not filtered by terminals when displaying files.
- CVE-2000-0476
- Terminal escape sequences not filtered by terminals when displaying files.
- CVE-2001-1556
- MFV. (multi-channel). Injection of control characters into log files that allow information hiding when using raw Unix programs to read the files.
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...