Mailbox Initialization Accepts Untrusted Pointer in Trusted Firmware‑M
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| TrustedFirmware | Trusted Firmware-M | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Trustedfirmware | Trusted Firmware-m |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.173% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Mailbox Initialization Accepts Untrusted Pointer in Trusted Firmware‑M |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | On the Trusted Firmware-M (TF-M) 2 through 2.3.0 platform before 00d1b3e, mailbox initialization on PSOC64 and RP2350 accepts a non-secure, unvalidated, supplied pointer. | |
| First Time appeared |
Trustedfirmware
Trustedfirmware trusted Firmware-m |
|
| Weaknesses | CWE-283 | |
| CPEs | cpe:2.3:a:trustedfirmware:trusted_firmware-m:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Trustedfirmware
Trustedfirmware trusted Firmware-m |
|
| References |
| |
| Metrics |
cvssV3_1
|