Entrust nShield Connect XC, nShield 5c, and nShield HSMi through 13.6.11, or 13.7, might allow a physically proximate attacker to gain access to the EOL legacy bootloader.
The product implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens generated in the system are incorrect.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Nshield_5c_firmware | Entrust | * | 13.6.12 (excluding) |
| Nshield_5c_firmware | Entrust | 13.7 (including) | 13.9.0 (excluding) |
Systems-On-a-Chip (SoC) (Integrated circuits and hardware engines) implement Security Tokens to differentiate and identify actions originated from various agents. These actions could be “read”, “write”, “program”, “reset”, “fetch”, “compute”, etc. Security Tokens are generated and assigned to every agent on the SoC that is either capable of generating an action or receiving an action from another agent. Every agent could be assigned a unique, Security Token based on its trust level or privileges.