CWE-1297: Unprotected Confidential Information on Device is Accessible by OSAT Vendors

Definição

What is CWE-1297?

This vulnerability occurs when a semiconductor chip does not properly secure sensitive data, making it accessible to third-party Outsourced Semiconductor Assembly and Test (OSAT) vendors during the manufacturing process.

Chipmakers often outsource manufacturing and testing to specialized OSAT vendors. During this pre-production stage, chips are in a vulnerable state with debug and test modes active. While NDAs are standard, the risk of accidental data leaks, IT security flaws at the OSAT facility, or insider threats remains high. Therefore, chip designers must minimize the confidential information left accessible on the device during this phase. Logic errors during design or synthesis can misconfigure debug components, granting improper access to sensitive data. Managing these hardware security flaws at scale is challenging; an ASPM platform like Plexicus can help you track and prioritize such vulnerabilities across your entire hardware and software stack, correlating them with SAST findings for a unified security posture.

Impacto no mundo real

Real-world CVEs caused by CWE-1297

Ainda não há referências CVE públicas associadas a este CWE no catálogo da MITRE.

Como os atacantes a exploram

Trajeto do atacante passo a passo

1
The following example shows how an attacker can take advantage of a piece of confidential information that has not been protected from the OSAT.
2
Suppose the preproduction device contains NVM (a storage medium that by definition/design can retain its data without power), and this NVM contains a key that can unlock all the parts for that generation. An OSAT facility accidentally leaks the key.
3
Compromising a key that can unlock all the parts of a generation can be devastating to a chipmaker.
4
The likelihood of such a compromise can be reduced by ensuring all memories on the preproduction device are properly scrubbed.

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

Architecture and Design - Ensure that when an OSAT vendor is allowed to access test interfaces necessary for preproduction and returned parts, the vendor only pulls the minimal information necessary. Also, architect the product in such a way that, when an "unlock device" request comes, it only unlocks that specific part and not all the parts for that product line. - Ensure that the product's non-volatile memory (NVM) is scrubbed of all confidential information and secrets before handing it over to an OSAT. - Arrange to secure all communication between an OSAT facility and the chipmaker.

Sinais de deteção

How to detect CWE-1297

Architecture or Design Review High

Appropriate Post-Si tests should be carried out to ensure that residual confidential information is not left on parts leaving one facility for another facility.

Dynamic Analysis with Manual Results Interpretation Moderate

Appropriate Post-Si tests should be carried out to ensure that residual confidential information is not left on parts leaving one facility for another facility.

CWE-1297

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

This vulnerability occurs when a semiconductor chip does not properly secure sensitive data, making it accessible to third-party Outsourced Semiconductor Assembly and Test (OSAT) vendors during the manufacturing process.

Qual a gravidade do CWE-1297?

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

MITRE lists the following affected platforms: Verilog, VHDL, Not OS-Specific, Not Architecture-Specific, Processor Hardware, Not Technology-Specific.

Como posso prevenir o CWE-1297?

- Ensure that when an OSAT vendor is allowed to access test interfaces necessary for preproduction and returned parts, the vendor only pulls the minimal information necessary. Also, architect the product in such a way that, when an "unlock device" request comes, it only unlocks that specific part and not all the parts for that product line. - Ensure that the product's non-volatile memory (NVM) is scrubbed of all confidential information and secrets before handing it over to an OSAT. - Arrange…

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

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

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

Fraquezas relacionadas

Weaknesses related to CWE-1297

CWE-285 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

Unprotected Confidential Information on Device is Accessible by OSAT Vendors

What is CWE-1297?

Real-world CVEs caused by CWE-1297

Trajeto do atacante passo a passo

Vulnerable pseudo

Secure pseudo

How to prevent CWE-1297

How to detect CWE-1297

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

Frequently asked questions

Weaknesses related to CWE-1297

Improper Authorization

Exposure of Sensitive Information Through Metadata

Improper Restriction of Software Interfaces to Hardware Features

Security Version Number Mutable to Older Versions

Files or Directories Accessible to External Parties

Incorrect Permission Assignment for Critical Resource

Missing Authorization

Incorrect Authorization

Improper Export of Android Application Components

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`