CVE-2023-51712: Medium severity TrustedFirmware Trusted Firmware-m vulnerability
Published Sep 5, 2024
·Updated
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.
Affected Software
1 affected component
TrustedFirmware Trusted Firmware-m<=2.0.0
Event History
Sep 5, 2024
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·04:15 PM
DescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2023-51712?
CVE-2023-51712 is considered a significant vulnerability due to the potential exposure of sensitive data.
2
How do I fix CVE-2023-51712?
To fix CVE-2023-51712, update Trusted Firmware-M to version 2.0.1 or later where the argument verification has been implemented.
3
What type of attack does CVE-2023-51712 allow?
CVE-2023-51712 allows attackers to read sensitive data through the logging subsystem due to insufficient argument verification.
4
Which versions of Trusted Firmware-M are affected by CVE-2023-51712?
CVE-2023-51712 affects Trusted Firmware-M versions up to and including 2.0.0.
5
Is CVE-2023-51712 a common vulnerability?
CVE-2023-51712 is a noteworthy vulnerability, particularly for applications utilizing the logging feature of Trusted Firmware-M.