CWE-326 Classe Rascunho

Inadequate Encryption Strength

This vulnerability occurs when an application protects sensitive information with encryption, but the specific algorithm or key strength used is too weak to withstand modern attack methods.

Definição

What is CWE-326?

This vulnerability occurs when an application protects sensitive information with encryption, but the specific algorithm or key strength used is too weak to withstand modern attack methods.

Using outdated or insufficient encryption—like short keys, deprecated algorithms (e.g., DES, RC4), or weak cipher modes—creates a false sense of security. Attackers can exploit this by running brute-force or cryptanalytic attacks to decrypt data with feasible computing power, potentially exposing credentials, personal data, or financial information. Identifying and upgrading weak encryption across a large codebase can be challenging. An ASPM platform like Plexicus not only detects these patterns through SAST/DAST but uses AI to generate specific remediation guidance, helping teams efficiently enforce strong cryptographic standards throughout their application portfolio.

Impacto no mundo real

Real-world CVEs caused by CWE-326

CVE-2001-1546

Weak encryption
CVE-2004-2172

Weak encryption (chosen plaintext attack)
CVE-2002-1682

Weak encryption
CVE-2002-1697

Weak encryption produces same ciphertext from the same plaintext blocks.
CVE-2002-1739

Weak encryption
CVE-2005-2281

Weak encryption scheme
CVE-2002-1872

Weak encryption (XOR)
CVE-2002-1910

Weak encryption (reversible algorithm).

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.

Vulnerável pseudo

// 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

Seguro 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-326

Architecture and Design Use an encryption scheme that is currently considered to be strong by experts in the field.

Sinais de deteção

How to detect CWE-326

Automated Static Analysis High

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-326

Don't catalog this weakness. Prove it's reachable.

Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.

Request AI Swarm Pentest

Perguntas frequentes

Frequently asked questions

O que é o CWE-326?

This vulnerability occurs when an application protects sensitive information with encryption, but the specific algorithm or key strength used is too weak to withstand modern attack methods.

Qual a gravidade do CWE-326?

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-326?

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-326?

Use an encryption scheme that is currently considered to be strong by experts in the field.

Como é que o Plexicus deteta e corrige o CWE-326?

O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-326 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-326?

A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/326.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.

Fraquezas relacionadas

Weaknesses related to CWE-326

CWE-693 Pai

Pronto para validar o que importa.

O Plexicus é Proof-Driven AppSec: achados validados, compreensão contextual e remediação revisada — ancorada em evidência, escopada com você.

Reservar Pentest

Inadequate Encryption Strength

What is CWE-326?

Real-world CVEs caused by CWE-326

Trajeto do atacante passo a passo

Vulnerable pseudo

Secure pseudo

How to prevent CWE-326

How to detect CWE-326

Don't catalog this weakness. Prove it's reachable.

Frequently asked questions

Weaknesses related to CWE-326

Protection Mechanism Failure

Inadequate Detection or Handling of Adversarial Input Perturbations in Automated Recognition Mechanism

Semiconductor Defects in Hardware Logic with Security-Sensitive Implications

Incorrect Selection of Fuse Values

Product Released in Non-Release Configuration

Missing Protection Against Hardware Reverse Engineering Using Integrated Circuit (IC) Imaging Techniques

Public Key Re-Use for Signing both Debug and Production Code

Missing Support for Security Features in On-chip Fabrics or Buses

Improper Protection against Electromagnetic Fault Injection (EM-FI)

Further reading

Pronto para validar o que importa.

Verifique se o AI Swarm Pentest se adequa ao seu ambiente.

Pedido recebido. Marque o próximo passo.

Sample evidence handover

Server-Side Request Forgery in `webhooks/receiver`