CWE-147 输入终结符转义处理不恰当

Improper Neutralization of Input Terminators

结构: Simple

Abstraction: Variant

状态: Draft

被利用可能性: unkown

基本描述

The software receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as input terminators when they are sent to a downstream component.

扩展描述

For example, a "." in SMTP signifies the end of mail message data, whereas a null character can be used for the end of a string.

适用平台

Language: {'cwe_Class': 'Language-Independent', 'cwe_Prevalence': 'Undetermined'}

常见的影响

范围	影响	注释
Integrity	Unexpected State

可能的缓解方案

策略:

Developers should anticipate that terminators will be injected/removed/manipulated in the input vectors of their software system. Use an appropriate combination of black lists and whitelists to ensure only valid, expected and appropriate input is processed by the system.

MIT-5 Implementation

策略: Input Validation

Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a whitelist of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs (i.e., do not rely on a blacklist). A blacklist is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, blacklists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.

MIT-28 Implementation

策略: Output Encoding

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 whitelist (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).

MIT-20 Implementation

策略: Input Validation

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 whitelist validation schemes by introducing dangerous inputs after they have been checked.

分析过的案例

标识	说明	链接
CVE-2000-0319	MFV. mail server does not properly identify terminator string to signify end of message, causing corruption, possibly in conjunction with off-by-one error.	https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2000-0319
CVE-2000-0320	MFV. mail server does not properly identify terminator string to signify end of message, causing corruption, possibly in conjunction with off-by-one error.	https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2000-0320
CVE-2001-0996	Mail server does not quote end-of-input terminator if it appears in the middle of a message.	https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2001-0996
CVE-2002-0001	Improperly terminated comment or phrase allows commands.	https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2002-0001

分类映射

映射的分类名	ImNode ID	Fit	Mapped Node Name
PLOVER			Input Terminator
Software Fault Patterns	SFP24		Tainted input to command

VULHUB ™