CWE-150 转义、元或控制序列转义处理不恰当

admin 2022年1月5日21:01:11CWE(弱点枚举)评论12 views4712字阅读15分42秒阅读模式

CWE-150 转义、元或控制序列转义处理不恰当

Improper Neutralization of Escape, Meta, or Control Sequences

结构: Simple

Abstraction: Variant

状态: Incomplete

被利用可能性: unkown

基本描述

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.

相关缺陷

  • cwe_Nature: ChildOf cwe_CWE_ID: 138 cwe_View_ID: 1000 cwe_Ordinal: Primary

  • cwe_Nature: ChildOf cwe_CWE_ID: 138 cwe_View_ID: 699 cwe_Ordinal: Primary

适用平台

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

常见的影响

范围 影响 注释
Integrity Unexpected State

可能的缓解方案

策略:

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 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-2002-0542 The mail program processes special "~" escape sequence even when not in interactive mode. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2002-0542
CVE-2000-0703 Setuid program does not filter escape sequences before calling mail program. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2000-0703
CVE-2002-0986 Mail function does not filter control characters from arguments, allowing mail message content to be modified. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2002-0986
CVE-2003-0020 Multi-channel issue. Terminal escape sequences not filtered from log files. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2003-0020
CVE-2003-0083 Multi-channel issue. Terminal escape sequences not filtered from log files. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2003-0083
CVE-2003-0021 Terminal escape sequences not filtered by terminals when displaying files. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2003-0021
CVE-2003-0022 Terminal escape sequences not filtered by terminals when displaying files. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2003-0022
CVE-2003-0023 Terminal escape sequences not filtered by terminals when displaying files. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2003-0023
CVE-2003-0063 Terminal escape sequences not filtered by terminals when displaying files. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2003-0063
CVE-2000-0476 Terminal escape sequences not filtered by terminals when displaying files. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2000-0476
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. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2001-1556

分类映射

映射的分类名 ImNode ID Fit Mapped Node Name
PLOVER Escape, Meta, or Control Character / Sequence
The CERT Oracle Secure Coding Standard for Java (2011) IDS03-J Do not log unsanitized user input

相关攻击模式

  • CAPEC-134
  • CAPEC-41
  • CAPEC-81
  • CAPEC-93

文章来源于互联网:scap中文网

特别标注: 本站(CN-SEC.COM)所有文章仅供技术研究,若将其信息做其他用途,由用户承担全部法律及连带责任,本站不承担任何法律及连带责任,请遵守中华人民共和国安全法.
  • 我的微信
  • 微信扫一扫
  • weinxin
  • 我的微信公众号
  • 微信扫一扫
  • weinxin
admin
  • 本文由 发表于 2022年1月5日21:01:11
  • 转载请保留本文链接(CN-SEC中文网:感谢原作者辛苦付出):
                  CWE-150 转义、元或控制序列转义处理不恰当 http://cn-sec.com/archives/612846.html

发表评论

匿名网友 填写信息

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen: