CWE-321 Variante Rascunho High likelihood

Use of Hard-coded Cryptographic Key

This vulnerability occurs when an application embeds a fixed, unchangeable cryptographic key directly within its source code or configuration files.

Definição

What is CWE-321?

This vulnerability occurs when an application embeds a fixed, unchangeable cryptographic key directly within its source code or configuration files.
Hard-coding cryptographic keys is a common but dangerous practice that undermines the security of encrypted data. Since the key is the same in every instance of the application and cannot be changed without modifying the code, an attacker who discovers the key (e.g., by inspecting the source code, binaries, or configuration files) can decrypt any sensitive data the application protects. This flaw effectively renders encryption useless, as the secret is no longer secret. To fix this, developers should use secure key management systems that allow keys to be stored externally, rotated regularly, and accessed securely at runtime. While SAST tools can detect the hard-coded pattern, Plexicus uses AI to suggest the actual code fix—such as integrating with a secrets manager or environment variables—saving hours of manual refactoring and helping you enforce secure key handling across your entire application portfolio.
Vulnerability Diagram CWE-321
Hard-coded Cryptographic Key crypto.go var aesKey = []byte( "0123456789abcdef") cipher.Encrypt(aesKey, …) // same key on every install Attacker strings binary | grep hex → 0123456789abcdef decrypt all encrypted data, forge tokens, sign things A literal AES/HMAC key in code = one extracted key compromises every customer.
Impacto no mundo real

Real-world CVEs caused by CWE-321

  • CVE-2022-29960

    Engineering Workstation uses hard-coded cryptographic keys that could allow for unathorized filesystem access and privilege escalation

  • CVE-2022-30271

    Remote Terminal Unit (RTU) uses a hard-coded SSH private key that is likely to be used by default.

  • CVE-2020-10884

    WiFi router service has a hard-coded encryption key, allowing root access

  • CVE-2014-2198

    Communications / collaboration product has a hardcoded SSH private key, allowing access to root account

Como os atacantes a exploram

Trajeto do atacante passo a passo

  1. 1

    The following code examples attempt to verify a password using a hard-coded cryptographic key.

  2. 2

    The cryptographic key is within a hard-coded string value that is compared to the password. It is likely that an attacker will be able to read the key and compromise the system.

  3. 3

    In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications.

  4. 4

    Multiple vendors used hard-coded keys for critical functionality in their OT products.

Exemplo de código vulnerável

Vulnerable C

The following code examples attempt to verify a password using a hard-coded cryptographic key.

Vulnerável C 
int VerifyAdmin(char *password) {
  		if (strcmp(password,"68af404b513073584c4b6f22b6c63e6b")) {
  				printf("Incorrect Password!\n");
  				return(0);
  		}
  		printf("Entering Diagnostic Mode...\n");
  		return(1);
  }
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-321

  • Architecture and Design Prevention schemes mirror that of hard-coded password storage.
Sinais de deteção

How to detect CWE-321

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.)

Correção automática do Plexicus

O Plexicus deteta automaticamente o CWE-321 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.

Obter uma demonstração Experimente o Plexicus gratuitamente
Perguntas frequentes

Frequently asked questions

O que é o CWE-321?

This vulnerability occurs when an application embeds a fixed, unchangeable cryptographic key directly within its source code or configuration files.

Qual a gravidade do CWE-321?

A MITRE classifica a probabilidade de exploração como Alta — esta fraqueza é ativamente explorada em campo e deve ser priorizada para remediação.

Que linguagens ou plataformas são afetadas pelo CWE-321?

MITRE lists the following affected platforms: ICS/OT.

Como posso prevenir o CWE-321?

Prevention schemes mirror that of hard-coded password storage.

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

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

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

Fraquezas relacionadas

Weaknesses related to CWE-321

CWE-798 Pai

Use of Hard-coded Credentials

This vulnerability occurs when software contains built-in, unchangeable authentication secrets like passwords or encryption keys within…

CWE-259 Irmão

Use of Hard-coded Password

This vulnerability occurs when an application embeds a password directly into its source code or configuration files. This hard-coded…

Recursos

Further reading

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.

Começar grátis Reservar uma demo