Incomplete List of Disallowed Inputs

CWE-184

Overtime trend (NVD)

CVSS severity (NVD, All Time)

Per technology (GHSA, All time)

63%-Maven
20%-Go
10%-NPM
6%-RubyGems

Short description

The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete, leading to resultant weaknesses.

Extended description

Developers often try to protect their products against malicious input by performing tests against inputs that are known to be bad, such as special characters that can invoke new commands. However, such lists often only account for the most well-known bad inputs. Attackers may be able to find other malicious inputs that were not expected by the developer, allowing them to bypass the intended protection mechanism.

Best practices to prevent this CWE

Phase: Implementation

Strategy: Input Validation

Do not rely exclusively on detecting disallowed inputs. There are too many variants to encode a character, especially when different environments are used, so there is a high likelihood of missing some variants. Only use detection of disallowed inputs as a mechanism for detecting suspicious activity. Ensure that you are using other protection mechanisms that only identify "good" input - such as lists of allowed inputs - and ensure that you are properly encoding your outputs.

Recently published CVEs

CVE-2024-23336
CVE-2024-20278
CVE-2024-28246
CVE-2021-1255
CVE-2021-1135

Recently published GHSA

GHSA-3wc5-fcw2-2329
GHSA-67hx-6x53-jw92
GHSA-23qf-3jf9-h3q9
GHSA-5p75-vc5g-8rv2
GHSA-cq2g-pw6q-hf7j

Prioritize and Uncover Reachable Vulnerabilities in Your Application Code

Identify externally reachable data flows and vulnerabilities for effective risk mitigation

Get a Demo