On this page

CWE-158: Improper Neutralization of Null Byte or NUL Character

Weakness Summary

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.

  • Canonical source: MITRE CWE-158 (opens in a new tab)
  • Published Atomicorp CVE observations: 1
  • Distinct affected products in those observations: 1
  • Active Atomicorp rules associated with this weakness: 4

Atomicorp Research Context

Atomicorp has published CVE-specific research observations associated with this weakness category. Each linked CVE page states whether the tested request was detected or blocked and is the authoritative customer-facing finding.

The CVEs and rules shown here are selected published examples, not a complete list of Atomicorp protections. If a CWE, CVE, or rule is absent from this page, no conclusion should be drawn about whether Atomicorp protects against that weakness or attack method.

A CWE describes a class of software weakness. It does not identify one exploit request, and association with a CWE does not mean that every vulnerability or exploitation path in that category is detected or blocked.

Selected Published CVE Observations

CVEVulnerabilityProductAtomicorp findingObserved rules
CVE-2025-47812Wing FTP Server <= 7.4.3 - Remote Code ExecutionwftpserverAttack Blocked by Atomicorp344362 , 344363 , 380026 , 390614

Associated Atomicorp WAF Rules

RuleStatusBehavior
344362Activedisruptive (deny)
344363Activedisruptive (deny)
380026Activedisruptive (deny)
390614Activedisruptive (deny)

MITRE associates this CWE with the following attack-pattern entries. These taxonomy relationships are context, not Atomicorp coverage claims:

CAPEC-52 (opens in a new tab) , CAPEC-53 (opens in a new tab)