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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

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

CWE-142 represents a critical input validation weakness where software fails to properly sanitize special characters that serve as value delimiters, such as commas, pipes, or semicolons, before passing data to downstream components. This flaw typically enables attackers to inject malicious payloads by manipulating these delimiters, thereby tricking the parser into misinterpreting the structure of the input. Consequently, the application may execute unintended commands, process unauthorized data, or trigger logic errors that compromise system integrity. To mitigate this risk, developers must rigorously validate and escape all incoming data, ensuring that delimiter characters are either strictly prohibited or safely neutralized before processing. Implementing robust parsing libraries that explicitly define expected formats and rejecting any input containing unexpected structural elements are essential practices for preventing delimiter-based injection attacks and maintaining secure data flow between system components.

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 value 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 value 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-61962 Fetchmail 安全漏洞 — fetchmail 5.9 Medium2025-10-04
CVE-2025-1774 Logs manipulation in BotSense — BotSense 9.4 -2025-03-17

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