BaseStable

CWE-1231Improper Prevention of Lock Bit Modification

Category: other

Description

The product uses a trusted lock bit for restricting access to registers, address regions, or other resources, but the product does not prevent the value of the lock bit from being modified after it has been set.

Common consequences· 1

  • Access Control — Modify Memory
    Registers protected by lock bit can be modified even when lock is set.

Potential mitigations· 1

  • [Architecture and Design, Implementation, Testing]

Related CAPEC attack patterns· 1

CAPEC-680

References

  1. https://cwe.mitre.org/data/definitions/1231.html

Exploits (incoming)1

TypeTargetConfidenceTier
AttackPatternExploitation of Improperly Controlled Registerscapec-680100%live

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Security-Sensitive Hardware Controls with Missing Lock Bit Protection
CWE
Insufficient Granularity of Address Regions Protected by Register Locks
CWE
Improper Access Control for Register Interface
CWE
Improper Restriction of Software Interfaces to Hardware Features
CWE
Improper Handling of Overlap Between Protected Memory Ranges
CWE
Improper Access Control for Volatile Memory Containing Boot Code
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.