Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
CWE-183 Base Rascunho
Permissive List of Allowed Inputs
This vulnerability occurs when an application's security filter uses an allowlist that is too broad, mistakenly permitting dangerous inputs that should have been blocked. The flawed assumption that…
Definição
What is CWE-183?
This vulnerability occurs when an application's security filter uses an allowlist that is too broad, mistakenly permitting dangerous inputs that should have been blocked. The flawed assumption that everything on the list is safe creates a direct path for attackers to exploit the system.
An overly permissive allowlist is like a faulty bouncer at a club's door—it lets in troublemakers because the guest list isn't specific enough. Developers often create these lists to validate data like filenames, URLs, or user roles, but if the criteria are vague (e.g., allowing all files with a '.pdf' extension without checking the actual content), attackers can slip malicious payloads through. This bypasses the primary defense, leading to issues like command injection, path traversal, or cross-site scripting.
Preventing this requires strict, context-aware validation rules that go beyond simple pattern matching. You must understand the exact, legitimate data your feature needs and deny everything else by default. Managing this at scale across hundreds of APIs and filters is difficult; an ASPM like Plexicus can help you track and remediate these flawed allowlist policies across your entire application stack, ensuring your validation logic is consistently robust.
Impacto no mundo real
Real-world CVEs caused by CWE-183
-
chain: bypass of untrusted deserialization issue (CWE-502) by using an assumed-trusted class (CWE-183)
-
sandbox bypass using a method that is on an allowlist
-
sandbox bypass using unsafe methods that are on an allowlist
-
CI/CD pipeline feature has unsafe elements in allowlist, allowing bypass of script restrictions
-
Default allowlist includes unsafe methods, allowing bypass of sandbox
Como os atacantes a exploram
Trajeto do atacante passo a passo
- 1
Identificar um caminho de código que trata input não confiável sem validação.
- 2
Criar um payload que explora o comportamento inseguro — injeção, traversal, overflow ou abuso de lógica.
- 3
Entregar o payload através de um pedido normal e observar a reação da aplicação.
- 4
Iterar até que a resposta exponha dados, execute código do atacante ou escale privilégios.
Exemplo de código vulnerável
Vulnerable pseudo
A MITRE não publicou um exemplo de código para este CWE. O padrão abaixo é ilustrativo — consulte os Recursos para referências canónicas.
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
// Untrusted input flows directly into the sensitive sink.
return executeUnsafe(input);
} Exemplo de código seguro
Secure pseudo
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
const safe = validateAndEscape(input);
return executeWithGuards(safe);
} What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Lista de verificação de prevenção
How to prevent CWE-183
- Architecture Use safe-by-default frameworks and APIs that prevent the unsafe pattern from being expressible.
- Implementation Validate input at trust boundaries; use allowlists, not denylists.
- Implementation Apply the principle of least privilege to credentials, file paths, and runtime permissions.
- Testing Cover this weakness in CI: SAST rules + targeted unit tests for the data flow.
- Operation Monitor logs for the runtime signals listed in the next section.
Sinais de deteção
How to detect CWE-183
O Plexicus deteta automaticamente o CWE-183 e abre um PR de correção em menos de 60 segundos.
O Codex Remedium analisa cada commit, identifica esta fraqueza exata e entrega um pull request pronto para revisão com o patch. Sem tickets. Sem transferências.
Perguntas frequentes O que é o CWE-183?
Qual a gravidade do CWE-183?
Que linguagens ou plataformas são afetadas pelo CWE-183?
Como posso prevenir o CWE-183?
Como é que o Plexicus deteta e corrige o CWE-183?
Onde posso saber mais sobre o CWE-183?
Frequently asked questions
O que é o CWE-183?
This vulnerability occurs when an application's security filter uses an allowlist that is too broad, mistakenly permitting dangerous inputs that should have been blocked. The flawed assumption that everything on the list is safe creates a direct path for attackers to exploit the system.
Qual a gravidade do CWE-183?
A MITRE não publicou uma classificação de probabilidade de exploração para esta fraqueza. Trate-a como impacto médio até o seu modelo de ameaças provar o contrário.
Que linguagens ou plataformas são afetadas pelo CWE-183?
A MITRE não especificou as plataformas afetadas por este CWE — pode aplicar-se à maioria das stacks de aplicações.
Como posso prevenir o CWE-183?
Use safe-by-default frameworks, validate untrusted input at trust boundaries, and apply the principle of least privilege. Cover the data-flow signature in CI with SAST.
Como é que o Plexicus deteta e corrige o CWE-183?
O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-183 em cada commit. Quando é encontrada uma correspondência, o nosso agente Codex Remedium abre um PR de correção com o código corrigido, testes e um resumo de uma linha para o revisor.
Onde posso saber mais sobre o CWE-183?
A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/183.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.
Fraquezas relacionadas
Weaknesses related to CWE-183
CWE-697 Pai
Incorrect Comparison
This weakness occurs when a security-critical decision relies on a flawed comparison between two pieces of data. The incorrect logic can…
CWE-1023 Irmão
Incomplete Comparison with Missing Factors
This weakness occurs when a program compares two items but fails to check all the necessary attributes that define their true…
CWE-1024 Irmão
Comparison of Incompatible Types
This vulnerability occurs when code directly compares two values of fundamentally different data types, which can lead to unreliable or…
CWE-1025 Irmão
Comparison Using Wrong Factors
This weakness occurs when a program compares two items but checks the wrong properties or attributes. This flawed comparison leads to…
CWE-1039 Irmão
Inadequate Detection or Handling of Adversarial Input Perturbations in Automated Recognition Mechanism
This vulnerability occurs when a system uses automated AI or machine learning to classify complex inputs like images, audio, or text, but…
CWE-1077 Irmão
Floating Point Comparison with Incorrect Operator
This vulnerability occurs when code compares two floating-point numbers using direct equality operators (like == or !=) without accounting…
CWE-1254 Irmão
Incorrect Comparison Logic Granularity
This vulnerability occurs when a system compares sensitive data, like passwords or authentication tokens, piece-by-piece instead of as a…
CWE-185 Irmão
Incorrect Regular Expression
This vulnerability occurs when a regular expression is written incorrectly, causing it to match or validate data in unintended and…
CWE-581 Irmão
Object Model Violation: Just One of Equals and Hashcode Defined
This vulnerability occurs when a Java class defines either the equals() method or the hashCode() method, but not both, breaking a…
Pronto quando você estiver
Pare de pagar por desenvolvedor.
Comece a fechar o ciclo.
O Plexicus é o ASPM nativo de IA que verifica, filtra, corrige, pentesta e explica — de forma autónoma. Programadores ilimitados, repos ilimitados, ações de IA de utilização justa. Nível gratuito real, €269/mo anual quando estiver pronto.