CVE-2024-45615: Libopensc: pkcs15init: usage of uninitialized values in libopensc and pkcs15init
A vulnerability was found in OpenSC, OpenSC tools, PKCS#11 module, minidriver, and CTK. The problem is missing initialization of variables expected to be initialized (as arguments to other functions, etc.).
Other sources
The reported issues are part of the libopensc library, which makes them accessible from OpenSC tools, PKCS#11 module, minidriver, or CTK. One is only relevant to handling the card enrollment using the pkcs15-init tool. The attack requires a crafted USB device or smart card that would present the system with specially crafted responses to the APDUs, so they are considered high complexity and low severity.
The problem is missing initialization of variables expected to be initialized (as arguments to other functions, etc.). The uninitialized variables were reflected in the following functions:
- cacreadfile - pivgetchallenge - scasn1decodeobjectid - scpkcs15emuschsmdecodecvc - doinitapp, scpkcs15initcreatepin
Originally reported by Matteo Marini (Sapienza University of Rome)
— Red Hat
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/openscto a version that resolves this vulnerability.Fixed in 0.21.0-1+deb11u1Fixed in 0.23.0-0.3+deb12u2Fixed in 0.26.1-1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-45615?
CVE-2024-45615 has been classified with a critical severity due to its potential impact on system security.
How do I fix CVE-2024-45615?
To resolve CVE-2024-45615, it is recommended to upgrade to the latest version of OpenSC or apply security patches provided by Red Hat.
Which software is affected by CVE-2024-45615?
CVE-2024-45615 impacts various versions of Red Hat Enterprise Linux (7.0, 8.0, and 9.0) as well as OpenSC versions prior to 0.26.0.
What are the implications of CVE-2024-45615?
The implications of CVE-2024-45615 include potential unauthorized access or manipulation of cryptographic operations due to uninitialized variable usage.
Is CVE-2024-45615 being actively exploited?
As of the latest information, there is no direct evidence indicating active exploitation of CVE-2024-45615 in the wild.