CWE-184: Incomplete List of Disallowed Inputs

What is CWE-184?

CWE-184 is Incomplete List of Disallowed Inputs. The flaw arises when 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. The database currently holds 105 vulnerabilities mapped to CWE-184 and 1 of them are in the CISA Known Exploited Vulnerabilities catalog.

Analyzing data...

OWASP Top 10 Rank-
Related CVES (365 days)105
AbstractionBase
Likelihood of exploit-

Vulnerabilities mapped to CWE-184

105 vulnerabilities2000% increase year over year

Vulnerabilities in CISA KEV for CWE-184

1 vulnerabilities

Official definition

ByMitre CWE

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.

Characteristics

Alternate terms

  • Denylist / Deny List — This is used by CWE and CAPEC instead of other commonly-used terms. Its counterpart is allowlist.
  • Blocklist / Block List — This is often used by security tools such as firewalls, email or web gateways, proxies, etc.
  • Blacklist / Black List — This term is frequently used, but usage has been declining as organizations have started to adopt other terms.

Modes of introduction

  • Implementation: Developers often try to protect their products against malicious input by checking against lists of known bad inputs, such as special characters that can invoke new commands. However, such lists often only address the most well-known bad inputs. As a quick fix, developers might rely on these lists instead of addressing the root cause of the issue. See [REF-141].
  • Architecture and Design: The design might rely solely on detection of malicious inputs as a protection mechanism.

Common consequences

ImpactScopeExplanation
Bypass Protection MechanismAccess ControlAttackers may be able to find other malicious inputs that were not expected by the developer, allowing them to bypass the intended protection mechanism.

Risk mitigations

  1. Input Validation · ImplementationDo 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.

Detection methods

MethodApproachEffectiveness
Black BoxExploitation of a vulnerability with commonly-used manipulations might fail, but minor variations might succeed.-

Representative vulnerabilities

Below are representative vulnerabilities related to this CWE, prioritized by severity.

Sources (2)

CWE™ Program, operated by The MITRE Corporation. Copyright © 2006–2026, The MITRE Corporation. The MITRE Corporation hereby grants you a non-exclusive, royalty-free license to use CWE for research, development, and commercial purposes. CWE Terms of Use.

Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.