CyberRota Analysis
AI-GeneratedThe vulnerability in Caliptra Core ROM and Core Firmware allows an attacker with access to the integrator's debug unlock signing service to unlock production debug on unintended devices by using a valid token meant for a different device, due to insufficient verification of data authenticity. While the risk is somewhat contained to devices sharing the same debug unlock key hash, it can lead to unauthorized access and loss of per-device security enforcement. Organizations utilizing affected versions (2.0.0 to 2.0.2 and 2.1.0 to 2.1.1) should prioritize remediation to mitigate potential security risks within their device ecosystems.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Insufficient verification of data authenticity in Caliptra Core ROM and Core Firmware (validate_debug_unlock_token()) in subsystem mode allows an attacker with access to the integrator's debug unlock signing service to unlock production debug on an unintended device by presenting a valid token issued for a different device sharing the same debug unlock key hash. The 384-bit challenge nonce continues to prevent replay of previously issued tokens. Practical impact is limited to loss of per-device scope enforcement within a set of devices that share the same unlock authority by design; it does not enable debug unlock on devices outside that set. This issue affects Core ROM: 2.0.0 through 2.0.2, 2.1.0 through 2.1.1; Core Firmware: 2.0.0 through 2.0.1, 2.1.0.