Vulnerability in Trustedfirmware Trusted Firmware-M
CVE-2023-51712
An issue was discovered in Trusted Firmware-M through 2.0.0. The lack of argument verification in the logging subsystem allows attackers to read sensitive data via the login function.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 4.7 (Medium). Vector: CVSS:3.1/AV:P/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N.
EPSS exploit prediction
EPSS: 0.003 (21.1th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 21st percentile — 21.1% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.003 · newest: 0.003 · change: 0.000
Affected products
Public proof-of-concept exploits
References
- git.trustedfirmware.org/TF-M/trusted-firmware-m.git/ (Product)
- trustedfirmware-m.readthedocs.io/en/latest/security/security_advisories/debug_l… (Mitigation, Vendor Advisory)
Frequently asked questions
- What is CVE-2023-51712?
- CVE-2023-51712 is a medium-severity vulnerability in Trustedfirmware Trusted Firmware-M. CVSS score: 4.7/10. Published 2024-09-05.
- How severe is CVE-2023-51712?
- Medium severity. CVSS v3 base score is 4.7 out of 10.
- Is CVE-2023-51712 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.