Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-144 (行分隔符转义处理不恰当) — Vulnerability Class 2

2 vulnerabilities classified as CWE-144 (行分隔符转义处理不恰当). AI Chinese analysis included.

CWE-144 represents an input validation weakness where software fails to properly sanitize line delimiter characters, such as carriage returns or newlines, within data received from upstream components. This vulnerability typically allows attackers to inject unexpected control sequences that downstream parsers interpret as structural boundaries rather than data content. Consequently, this manipulation can trigger logic errors, cause data corruption, or facilitate injection attacks like log forging or header injection by altering the expected flow of information processing. To mitigate this risk, developers must implement rigorous input validation strategies that explicitly filter or escape line-breaking characters before processing. Utilizing standardized libraries for parsing and enforcing strict schema definitions ensures that only expected data formats are accepted, thereby preventing malicious actors from exploiting delimiter ambiguities to compromise system integrity or confidentiality.

MITRE CWE Description
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as line delimiters 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.
Common Consequences (1)
IntegrityUnexpected State
Mitigations (4)
Developers should anticipate that line delimiters 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.
ImplementationAssume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list 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…
ImplementationWhile 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 allowlist (such as everything that is not alphanumeric or whit…
ImplementationInputs 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 IDTitleCVSSSeverityPublished
CVE-2025-24367 Cacti allows Arbitrary File Creation leading to RCE — cacti 8.8 -2025-01-27
CVE-2023-39212 Zoom Rooms 代码问题漏洞 — Zoom Rooms for Windows 7.9 High2023-08-08

Vulnerabilities classified as CWE-144 (行分隔符转义处理不恰当) represent 2 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.