CWE-1264 Base Incomplet

Hardware Logic with Insecure De-Synchronization between Control and Data Channels

This vulnerability occurs when a hardware design incorrectly forwards data before its security or permission checks have finished processing. It's a timing flaw where the data channel gets ahead of…

Définition

What is CWE-1264?

This vulnerability occurs when a hardware design incorrectly forwards data before its security or permission checks have finished processing. It's a timing flaw where the data channel gets ahead of the control channel, potentially leaking information.
Modern hardware often uses separate control and data channels to boost performance. A bug in the logic that manages errors and security can allow data to 'race ahead' and be used or observed before the system confirms it's safe to do so. This desynchronization creates a critical window where unauthorized data access can happen. The real-world impact is a loss of data confidentiality, as seen in exploits like Meltdown. In that case, a CPU speculatively loaded privileged data for performance, assuming it could clean up all traces if the access was later deemed illegal. However, secret data remained in the microarchitectural state, proving that assumption false and allowing attackers to retrieve it.
Impact réel

Real-world CVEs caused by CWE-1264

  • CVE-2017-5754

    Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis of the data cache.

Comment les attaquants l'exploitent

Parcours de l'attaquant étape par étape

  1. 1

    Identifier un chemin de code qui traite des entrées non fiables sans validation.

  2. 2

    Élaborer une charge utile qui exploite le comportement non sécurisé — injection, traversal, débordement ou abus de logique.

  3. 3

    Délivrer la charge utile via une requête normale et observer la réaction de l'application.

  4. 4

    Itérer jusqu'à ce que la réponse divulgue des données, exécute le code de l'attaquant ou élève les privilèges.

Exemple de code vulnérable

Vulnerable Other

There are several standard on-chip bus protocols used in modern SoCs to allow communication between components. There are a wide variety of commercially available hardware IP implementing the interconnect logic for these protocols. A bus connects components which initiate/request communications such as processors and DMA controllers (bus masters) with peripherals which respond to requests. In a typical system, the privilege level or security designation of the bus master along with the intended functionality of each peripheral determine the security policy specifying which specific bus masters can access specific peripherals. This security policy (commonly referred to as a bus firewall) can be enforced using separate IP/logic from the actual interconnect responsible for the data routing.

Vulnérable Other 
The firewall and data routing logic becomes de-synchronized due to a hardware logic bug allowing components that should not be allowed to communicate to share data. For example, consider an SoC with two processors. One is being used as a root of trust and can access a cryptographic key storage peripheral. The other processor (application cpu) may run potentially untrusted code and should not access the key store. If the application cpu can issue a read request to the key store which is not blocked due to de-synchronization of data routing and the bus firewall, disclosure of cryptographic keys is possible.
Exemple de code sécurisé

Secure Other

Sécurisé Other 
All data is correctly buffered inside the interconnect until the firewall has determined that the endpoint is allowed to receive the data.
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-1264

  • Architecture and Design Thoroughly verify the data routing logic to ensure that any error handling or security checks effectively block illegal dataflows.
Signaux de détection

How to detect CWE-1264

SAST High

Exécuter une analyse statique (SAST) sur le code source à la recherche du motif non sécurisé dans le flux de données.

DAST Moderate

Exécuter des tests de sécurité applicative dynamique (DAST) contre le point de terminaison en ligne.

Runtime Moderate

Surveiller les journaux runtime pour détecter des traces d'exception inhabituelles, des entrées malformées ou des tentatives de contournement d'autorisation.

Code review Moderate

Revue de code : signaler tout nouveau code qui traite les entrées de cette surface sans utiliser les helpers du framework validés.

Correction automatique Plexicus

Plexicus détecte automatiquement CWE-1264 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-1264 ?

This vulnerability occurs when a hardware design incorrectly forwards data before its security or permission checks have finished processing. It's a timing flaw where the data channel gets ahead of the control channel, potentially leaking information.

Quelle est la gravité de CWE-1264 ?

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

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

Comment puis-je prévenir CWE-1264 ?

Thoroughly verify the data routing logic to ensure that any error handling or security checks effectively block illegal dataflows.

Comment Plexicus détecte et corrige CWE-1264 ?

Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-1264 à 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-1264 ?

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

Faiblesses associées

Weaknesses related to CWE-1264

CWE-821 Parent

Incorrect Synchronization

This vulnerability occurs when multiple parts of a program, such as threads or processes, access a shared resource like a variable, file,…

CWE-1088 Frère

Synchronous Access of Remote Resource without Timeout

This vulnerability occurs when an application makes a synchronous call to a remote service or resource but does not set a timeout, or sets…

CWE-572 Frère

Call to Thread run() instead of start()

This vulnerability occurs when a program incorrectly calls a thread's `run()` method directly, instead of using the `start()` method. This…

CWE-574 Frère

EJB Bad Practices: Use of Synchronization Primitives

This vulnerability occurs when an Enterprise JavaBeans (EJB) component improperly uses thread synchronization primitives, violating the…

CWE-1037 Pair

Processor Optimization Removal or Modification of Security-critical Code

This vulnerability occurs when a processor's performance optimization unintentionally strips out or alters security-critical code that a…

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