CWE-1328 Base Draft

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 the boot firmware to older, vulnerable versions.

Definition

What is CWE-1328?

This vulnerability occurs when a hardware system's security version number can be changed, allowing an attacker to downgrade or roll back the boot firmware to older, vulnerable versions.
Modern System-on-Chip (SoC) designs often use a security version number to enforce secure or verified boot, preventing the installation of older firmware with known security flaws. If an attacker can modify this version counter, they can force a downgrade to a vulnerable version, opening the device to exploitation and completely bypassing the intended update protection. For protection to be effective, the security version number must be stored in a tamper-proof, persistent location that survives resets. The core weakness arises when this critical value is stored in mutable memory, allowing unauthorized roll-back attacks. In some cases, an attacker might even manipulate the version to block legitimate upgrades, creating a denial-of-service condition against security updates and leaving the SoC permanently vulnerable.
Real-world impact

Real-world CVEs caused by CWE-1328

No public CVE references are linked to this CWE in MITRE's catalog yet.

How attackers exploit it

Step-by-step attacker path

  1. 1

    A new version of firmware is signed with a security version number higher than the previous version. During the firmware update process the SoC checks for the security version number and upgrades the SoC firmware with the latest version. This security version number is stored in persistent memory upon successful upgrade for use across power-on resets.

  2. 2

    In general, if the security version number is mutable, the implementation is vulnerable. A mutable security version number allows an adversary to change the security version to a lower value to allow roll-back or to a higher value to prevent future upgrades.

  3. 3

    The security version number should be stored in immutable hardware such as fuses, and the writes to these fuses should be highly access-controlled with appropriate authentication and authorization protections.

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.

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

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

  • Architecture and Design When architecting the system, security version data should be designated for storage in registers that are either read-only or have access controls that prevent modification by an untrusted agent.
  • Implementation During implementation and test, security version data should be demonstrated to be read-only and access controls should be validated.
Detection signals

How to detect CWE-1328

Automated Dynamic Analysis High

Mutability of stored security version numbers and programming with older firmware images should be part of automated testing.

Architecture or Design Review High

Anti-roll-back features should be reviewed as part of Architecture or Design review.

Plexicus auto-fix

Plexicus auto-detects CWE-1328 and opens a fix PR in under 60 seconds.

Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.

Get a demo Try Plexicus free
Frequently asked questions

Frequently asked questions

What is CWE-1328?

This vulnerability occurs when a hardware system's security version number can be changed, allowing an attacker to downgrade or roll back the boot firmware to older, vulnerable versions.

How serious is CWE-1328?

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

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

How can I prevent CWE-1328?

When architecting the system, security version data should be designated for storage in registers that are either read-only or have access controls that prevent modification by an untrusted agent. During implementation and test, security version data should be demonstrated to be read-only and access controls should be validated.

How does Plexicus detect and fix CWE-1328?

Plexicus's SAST engine matches the data-flow signature for CWE-1328 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-1328?

MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/1328.html. You can also reference OWASP and NIST documentation for adjacent guidance.

Related weaknesses

Weaknesses related to CWE-1328

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

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…

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

Ready when you are

Don't Let Security
Weigh You Down.

Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.