Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
No data.
No data.
No data available yet.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.810% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Trustedfirmware
Trustedfirmware trusted Firmware-m |
|
| Weaknesses | CWE-120 | |
| CPEs | cpe:2.3:a:trustedfirmware:trusted_firmware-m:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Trustedfirmware
Trustedfirmware trusted Firmware-m |
|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | An issue was discovered in Trusted Firmware-M through 2.1.0. User provided (and controlled) mailbox messages contain a pointer to a list of input arguments (in_vec) and output arguments (out_vec). These list pointers are never validated. Each argument list contains a buffer pointer and a buffer length field. After a PSA call, the length of the output arguments behind the unchecked pointer is updated in mailbox_direct_reply, regardless of the call result. This allows an attacker to write anywhere in the secure firmware, which can be used to take over the control flow, leading to remote code execution (RCE). | |
| References |
|