CWE-158: Improper Neutralization of Null Byte or NUL Character
CWE版本: 4.18
更新日期: 2025-09-09
弱点描述
The product 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 product 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.
常见后果
影响范围: Integrity
技术影响: Unexpected State
潜在缓解措施
描述: Developers should anticipate that null characters or null bytes 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.
阶段: Implementation
策略: Input Validation
阶段: 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 allowlist validation schemes by introducing dangerous inputs after they have been checked.
观察示例
参考: CVE-2008-1284
NUL byte in theme name causes directory traversal impact to be worse
参考: 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 (<), so a non-alphabetical or null character (%00) following a < may be processed.
参考: 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).
引入模式
| 阶段 | 说明 |
|---|---|
| Implementation | - |
适用平台
编程语言
分类映射
| 分类名称 | 条目ID | 条目名称 | 映射适配度 |
|---|---|---|---|
| PLOVER | - | Null Character / Null Byte | - |
| WASC | 28 | Null Byte Injection | - |
| Software Fault Patterns | SFP24 | Tainted input to command | - |