Permissive List of Allowed Inputs

Opis

The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are explicitly allowed by policy because the inputs are assumed to be safe, but the list is too permissive - that is, it allows an input that is unsafe, leading to resultant weaknesses.

Inne nazwy

Allowlist / Allow List

This is used by CWE and CAPEC instead of other commonly-used terms. Its counterpart is denylist.

Safelist / Safe List

This is often used by security tools such as firewalls, email or web gateways, proxies, etc.

Whitelist / White List

This term is frequently used, but usage has been declining as organizations have started to adopt other terms.

Skutki

• Access Control

  Bypass Protection Mechanism

Przykłady podatności

• CVE-2019-12799 chain: bypass of untrusted deserialization issue (CWE-502) by using an assumed-trusted class (CWE-183)
• CVE-2019-10458 sandbox bypass using a method that is on an allowlist
• CVE-2017-1000095 sandbox bypass using unsafe methods that are on an allowlist
• CVE-2019-10458 CI/CD pipeline feature has unsafe elements in allowlist, allowing bypass of script restrictions
• CVE-2017-1000095 Default allowlist includes unsafe methods, allowing bypass of sandbox

Słabość nadrzędna

• CWE-697 Incorrect Comparison

Może prowadzić do

• CWE-434 Unrestricted Upload of File with Dangerous Type

Słabości podrzędne

• CWE-942 Permissive Cross-domain Security Policy with Untrusted Domains

Kiedy powstaje

• Implementation

Dotyczy

Not Language-Specific, Not Technology-Specific

Źródła

1. The Art of Software Security Assessment — Mark Dowd, John McDonald, Justin Schuh, Chapter 8, "Eliminating Metacharacters", Page 435, Addison Wesley, 2006