CWE-1256 Base Stable

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 properly locked down. This allows attackers to misuse these…

Définition

What is CWE-1256?

This vulnerability occurs when a system's software interfaces to hardware features—like power, clock, or performance management—are not properly locked down. This allows attackers to misuse these interfaces from software to tamper with hardware memory or registers, or to gather sensitive data by observing physical side effects, without needing physical access to the device.
Many developers assume that attacks like fault injection or side-channel analysis require an attacker to physically touch the device. This assumption breaks down when software can directly control hardware features like voltage, clock speed, or power meters. Attackers can exploit these poorly restricted interfaces from a standard application to deliberately cause bit errors (faults) or to measure power consumption patterns, leading to privilege escalation, authentication bypass, or cryptographic key extraction. Common examples include abusing dynamic voltage and frequency scaling (DVFS) to induce faults, using hardware power meters (e.g., Intel RAPL) for side-channel analysis, or triggering Rowhammer-style bit flips via rapid memory accesses. Managing this at scale is difficult; an ASPM like Plexicus can help you track and remediate these hardware-interface flaws across your entire stack, correlating code patterns with potential runtime exploitation.
Impact réel

Real-world CVEs caused by CWE-1256

  • CVE-2019-11157

    Plundervolt: Improper conditions check in voltage settings for some Intel(R) Processors may allow a privileged user to potentially enable escalation of privilege and/or information disclosure via local access [REF-1081].

  • CVE-2020-8694

    PLATYPUS Attack: Insufficient access control in the Linux kernel driver for some Intel processors allows information disclosure.

  • CVE-2020-8695

    Observable discrepancy in the RAPL interface for some Intel processors allows information disclosure.

  • CVE-2020-12912

    AMD extension to a Linux service does not require privileged access to the RAPL interface, allowing side-channel attacks.

  • CVE-2015-0565

    NaCl in 2015 allowed the CLFLUSH instruction, making Rowhammer attacks possible.

Comment les attaquants l'exploitent

Parcours de l'attaquant étape par étape

  1. 1

    This example considers the Rowhammer problem [REF-1083]. The Rowhammer issue was caused by a program in a tight loop writing repeatedly to a location to which the program was allowed to write but causing an adjacent memory location value to change.

  2. 2

    Preventing the loop required to defeat the Rowhammer exploit is not always possible:

  3. 3

    While the redesign may be possible for new devices, a redesign is not possible in existing devices. There is also the possibility that reducing capacitance with a relayout would impact the density of the device resulting in a less capable, more costly device.

  4. 4

    Suppose a hardware design implements a set of software-accessible registers for scaling clock frequency and voltage but does not control access to these registers. Attackers may cause register and memory changes and race conditions by changing the clock or voltage of the device under their control.

  5. 5

    Consider the following SoC design. Security-critical settings for scaling clock frequency and voltage are available in a range of registers bounded by [PRIV_END_ADDR : PRIV_START_ADDR] in the tmcu.csr module in the HW Root of Trust. These values are writable based on the lock_bit register in the same module. The lock_bit is only writable by privileged software running on the tmcu.

Exemple de code vulnérable

Vulnerable Other

This example considers the Rowhammer problem [REF-1083]. The Rowhammer issue was caused by a program in a tight loop writing repeatedly to a location to which the program was allowed to write but causing an adjacent memory location value to change.

Vulnérable Other 
Continuously writing the same value to the same address causes the value of an adjacent location to change value.
Exemple de code sécurisé

Secure Other

Preventing the loop required to defeat the Rowhammer exploit is not always possible:

Sécurisé Other 
Redesign the RAM devices to reduce inter capacitive coupling making the Rowhammer exploit impossible.
What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Liste de contrôle de prévention

How to prevent CWE-1256

  • Architecture and Design / Implementation Ensure proper access control mechanisms protect software-controllable features altering physical operating conditions such as clock frequency and voltage.
Signaux de détection

How to detect CWE-1256

Manual Analysis

Perform a security evaluation of system-level architecture and design with software-aided physical attacks in scope.

Automated Dynamic Analysis Moderate

Use custom software to change registers that control clock settings or power settings to try to bypass security locks, or repeatedly write DRAM to try to change adjacent locations. This can be effective in extracting or changing data. The drawback is that it cannot be run before manufacturing, and it may require specialized software.

Correction automatique Plexicus

Plexicus détecte automatiquement CWE-1256 et ouvre une PR de correction en moins de 60 secondes.

Codex Remedium analyse chaque commit, identifie cette faiblesse précise et livre une pull request prête à être relue avec le correctif. Pas de tickets. Pas de transferts.

Obtenir une démo Essayer Plexicus gratuitement
Questions fréquentes

Frequently asked questions

Qu'est-ce que CWE-1256 ?

This vulnerability occurs when a system's software interfaces to hardware features—like power, clock, or performance management—are not properly locked down. This allows attackers to misuse these interfaces from software to tamper with hardware memory or registers, or to gather sensitive data by observing physical side effects, without needing physical access to the device.

Quelle est la gravité de CWE-1256 ?

MITRE n'a pas publié de note de probabilité d'exploitation pour cette faiblesse. Traitez-la comme un impact moyen jusqu'à ce que votre modèle de menace prouve le contraire.

Quels langages ou plateformes sont affectés par CWE-1256 ?

MITRE lists the following affected platforms: Not OS-Specific, Not Architecture-Specific, Not Technology-Specific, Memory Hardware, Power Management Hardware, Clock/Counter Hardware.

Comment puis-je prévenir CWE-1256 ?

Ensure proper access control mechanisms protect software-controllable features altering physical operating conditions such as clock frequency and voltage.

Comment Plexicus détecte et corrige CWE-1256 ?

Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-1256 à chaque commit. Lorsqu'une correspondance est trouvée, notre agent Codex Remedium ouvre une PR de correction avec le code corrigé, les tests et un résumé d'une ligne pour le relecteur.

Où puis-je en savoir plus sur CWE-1256 ?

MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/1256.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.

Faiblesses associées

Weaknesses related to CWE-1256

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 Frère

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-1297 Frère

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-1328 Frère

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 Frère

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 Frère

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 Frère

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 Frère

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 Frère

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…

Ressources

Further reading

Prêt quand vous l'êtes

Arrêtez de payer par développeur.
Commencez à fermer la boucle.

Plexicus est l'ASPM natif IA qui scanne, filtre, corrige, penteste et explique — de façon autonome. Développeurs illimités, dépôts illimités, actions IA à usage équitable. Vrai niveau gratuit, €269/mo annuel quand vous êtes prêt.

Commencer gratuitement Réserver une démo