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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-155 (双字符或匹配符号转义处理不恰当) — Vulnerability Class 13

13 vulnerabilities classified as CWE-155 (双字符或匹配符号转义处理不恰当). AI Chinese analysis included.

CWE-155 represents a critical input validation weakness where software fails to properly sanitize special characters, such as wildcards or matching symbols, before passing them to downstream components. Attackers typically exploit this vulnerability by injecting malicious patterns that alter the intended behavior of the receiving system, potentially leading to unauthorized data access, denial of service, or remote code execution. For instance, an attacker might use a wildcard character to bypass file access controls or manipulate search queries to expose sensitive information. To mitigate this risk, developers must implement strict input validation and output encoding strategies. By explicitly defining allowed character sets and neutralizing potentially dangerous symbols before they reach interpretable contexts, engineers can prevent unintended interpretation and ensure that user-supplied data remains inert and safe within the application’s processing pipeline.

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 wildcards or matching symbols when they are sent to a downstream component. As data is parsed, an injected element may cause the process to take unexpected actions.
Common Consequences (1)
IntegrityUnexpected State
Mitigations (4)
Developers should anticipate that wildcard or matching elements 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.

Vulnerabilities classified as CWE-155 (双字符或匹配符号转义处理不恰当) represent 13 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.