Improper Prevention of Lock Bit Modification

Opis

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.

In integrated circuits and hardware intellectual property (IP) cores, device configuration controls are commonly programmed after a device power reset by a trusted firmware or software module (e.g., BIOS/bootloader) and then locked from any further modification.

This behavior is commonly implemented using a trusted lock bit. When set, the lock bit disables writes to a protected set of registers or address regions. Design or coding errors in the implementation of the lock bit protection feature may allow the lock bit to be modified or cleared by software after it has been set. Attackers might be able to unlock the system and features that the bit is intended to protect.

Skutki

• Access Control

  Modify Memory

  Registers protected by lock bit can be modified even when lock is set.

Zapobieganie

• Architecture and Design, Implementation, Testing

  - Security lock bit protections must be reviewed for design inconsistency and common weaknesses.

  - Security lock programming flow and lock properties must be tested in pre-silicon and post-silicon testing.

  Skuteczność: High

Przykłady podatności

• CVE-2017-6283 chip reset clears critical read/write lock permissions for RSA function

Słabość nadrzędna

• CWE-284 Improper Access Control

Kiedy powstaje

• Architecture and Design — Such issues could be introduced during hardware architecture and design and identified later during Testing or System Configuration phases.
• Implementation — Such issues could be introduced during implementation and identified later during Testing or System Configuration phases.

Dotyczy

Not Language-Specific, Not OS-Specific, Not Architecture-Specific, Not Technology-Specific

Źródła

1. reglk_wrapper.sv — 2021
2. fix cwe 1199 in reglk — 2023