CWE-158 空字节或NULL字符转义处理不恰当

admin 2022年1月7日03:00:11CWE(弱点枚举)评论13 views4823字阅读16分4秒阅读模式

CWE-158 空字节或NULL字符转义处理不恰当

Improper Neutralization of Null Byte or NUL Character

结构: Simple

Abstraction: Variant

状态: Incomplete

被利用可能性: unkown


The software receives input from an upstream component, but it does not neutralize or incorrectly neutralizes NUL characters or null bytes when they are sent to a downstream component.


As data is parsed, an injected NUL character or null byte may cause the software to believe the input is terminated earlier than it actually is, or otherwise cause the input to be misinterpreted. This could then be used to inject potentially dangerous input that occurs after the null byte or otherwise bypass validation routines and other protection mechanisms.


  • 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 null characters or null bytes 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-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-2005-2008 Source code disclosure using trailing null.
CVE-2005-3293 Source code disclosure using trailing null.
CVE-2005-2061 Trailing null allows file include.
CVE-2002-1774 Null character in MIME header allows detection bypass.
CVE-2000-0149 Web server allows remote attackers to view the source code for CGI programs via a null character (%00) at the end of a URL.
CVE-2000-0671 Web server earlier allows allows remote attackers to bypass access restrictions, list directory contents, and read source code by inserting a null character (%00) in the URL.
CVE-2001-0738 Logging system allows an attacker to cause a denial of service (hang) by causing null bytes to be placed in log messages.
CVE-2001-1140 Web server allows source code for executable programs to be read via a null character (%00) at the end of a request.
CVE-2002-1031 Protection mechanism for limiting file access can be bypassed using a null character (%00) at the end of the directory name.
CVE-2002-1025 Application server allows remote attackers to read JSP source code via an encoded null byte in an HTTP GET request, which causes the server to send the .JSP file unparsed.
CVE-2003-0768 XSS protection mechanism only checks for sequences with an alphabetical character following a (
CVE-2004-0189 Decoding function in proxy allows regular expression bypass in ACLs via URLs with null characters.
CVE-2005-3153 Null byte bypasses PHP regexp check (interaction error).
CVE-2005-4155 Null byte bypasses PHP regexp check (interaction error).



映射的分类名 ImNode ID Fit Mapped Node Name
PLOVER Null Character / Null Byte
WASC 28 Null Byte Injection
Software Fault Patterns SFP24 Tainted input to command


  • CAPEC-52
  • CAPEC-53



特别标注: 本站(CN-SEC.COM)所有文章仅供技术研究,若将其信息做其他用途,由用户承担全部法律及连带责任,本站不承担任何法律及连带责任,请遵守中华人民共和国安全法.
  • 我的微信
  • 微信扫一扫
  • weinxin
  • 我的微信公众号
  • 微信扫一扫
  • weinxin
  • 本文由 发表于 2022年1月7日03:00:11
  • 转载请保留本文链接(CN-SEC中文网:感谢原作者辛苦付出):
                  CWE-158 空字节或NULL字符转义处理不恰当


匿名网友 填写信息

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