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 Base Incomplete
Unprotected Confidential Information on Device is Accessible by OSAT Vendors
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…
Definition
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.
Real-world impact
Real-world CVEs caused by CWE-1297
No public CVE references are linked to this CWE in MITRE's catalog yet.
How attackers exploit it
Step-by-step attacker path
- 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.
Vulnerable code example
Vulnerable pseudo
MITRE has not published a code example for this CWE. The pattern below is illustrative — see Resources for canonical references.
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
// Untrusted input flows directly into the sensitive sink.
return executeUnsafe(input);
} Secure code example
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.
Prevention checklist
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.
Detection signals
How to detect CWE-1297
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.
Frequently asked questions What is CWE-1297?
How serious is CWE-1297?
What languages or platforms are affected by CWE-1297?
How can I prevent CWE-1297?
How does Plexicus detect and fix CWE-1297?
Where can I learn more about CWE-1297?
Frequently asked questions
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.
How serious is CWE-1297?
MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.
What languages or platforms are affected by CWE-1297?
MITRE lists the following affected platforms: Verilog, VHDL, Not OS-Specific, Not Architecture-Specific, Processor Hardware, Not Technology-Specific.
How can I prevent 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…
How does Plexicus detect and fix CWE-1297?
Plexicus's SAST engine matches the data-flow signature for CWE-1297 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.
Where can I learn more about CWE-1297?
MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/1297.html. You can also reference OWASP and NIST documentation for adjacent guidance.
Related weaknesses
Weaknesses related to CWE-1297
CWE-285 Parent
Improper Authorization
This vulnerability occurs when an application fails to properly verify whether a user has permission to access specific data or perform…
CWE-1230 Sibling
Exposure of Sensitive Information Through Metadata
This vulnerability occurs when an application protects the primary source of sensitive data but fails to secure the metadata derived from…
CWE-1256 Sibling
Improper Restriction of Software Interfaces to Hardware Features
This vulnerability occurs when a system's software interfaces to hardware features—like power, clock, or performance management—are not…
CWE-1328 Sibling
Security Version Number Mutable to Older Versions
This vulnerability occurs when a hardware system's security version number can be changed, allowing an attacker to downgrade or roll back…
CWE-552 Sibling
Files or Directories Accessible to External Parties
This vulnerability occurs when an application exposes files or directories to users who shouldn't have access to them.
CWE-732 Sibling
Incorrect Permission Assignment for Critical Resource
This vulnerability occurs when a system grants overly permissive access to a sensitive resource, allowing unauthorized users or processes…
CWE-862 Sibling
Missing Authorization
This vulnerability occurs when an application fails to verify whether a user has permission to access specific data or execute certain…
CWE-863 Sibling
Incorrect Authorization
This vulnerability occurs when an application checks if a user is allowed to perform an action or access data, but the check is flawed or…
CWE-926 Sibling
Improper Export of Android Application Components
This vulnerability occurs when an Android app makes a component (like an Activity, Service, or Content Provider) available to other apps…
Resources
Further reading
- MITRE — official CWE-1297 https://cwe.mitre.org/data/definitions/1297.html
- Provably-Secure Logic Locking: From Theory To Practice https://dl.acm.org/doi/10.1145/3133956.3133985
- Trustworthy Hardware Design: Combinational Logic Locking Techniques https://link.springer.com/book/10.1007/978-3-030-15334-2
Ready to validate what matters?
Ready to validate what matters?
Plexicus is Proof-Driven AppSec: validated findings, contextual understanding, and reviewed remediation — anchored in evidence, scoped with you.