CVE-2024-45616: Libopensc: uninitialized values after incorrect check or usage of apdu response values in libopensc

Published Sep 2, 2024
·
Updated

A vulnerability was found in OpenSC, OpenSC tools, PKCS#11 module, minidriver, and CTK. An attacker could use a crafted USB Device or Smart Card, which would present the system with a specially crafted response to APDUs.

The following problems were caused by insufficient control of the response APDU buffer and its length when communicating with the card.

Other sources

The reported issues are part of the libopensc library, which makes them accessible from OpenSC tools, PKCS#11 module, minidriver, or CTK. 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 following problems were caused by insufficient control of the response APDU buffer and its length when communicating with the card. The uninitialized variables were reflected in these functions:

- cardosmatchcard - itoaword, called from schexdump - scbintohex - strcmp, called from scasn1readtag - asn1decode - processfcp - dnieprocessfci - iso7816processfci - scpkcs15initparseinfo, mscextractrsapublickey - scbintohex - gidsreadmasterfile - scbintohex

Originally reported by Matteo Marini (Sapienza University of Rome)

Red Hat

Affected Software

5 affected componentsFixes available
redhat Enterprise Linux=7.0
redhat Enterprise Linux=8.0
redhat Enterprise Linux=9.0
Opensc Project Opensc<0.26.0
debian/opensc<=0.21.0-1
0.21.0-1+deb11u10.23.0-0.3+deb12u20.26.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/opensc to 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

Sep 2, 2024
Data Sourced
via Red Hat·06:38 PM
DescriptionSeverityAffected Software
Sep 3, 2024
CVE Published
via MITRE·09:20 PM
Data Sourced
via MITRE·09:20 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:15 PM
DescriptionSeverityWeaknessAffected Software
Apr 10, 2025
Data Sourced
via Ubuntu·03:08 AM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-45616?

CVE-2024-45616 is considered a high severity vulnerability due to potential exploitation via crafted USB devices or Smart Cards.

2

How do I fix CVE-2024-45616?

To fix CVE-2024-45616, update to the latest versions of the affected software that have addressed this vulnerability.

3

What systems are affected by CVE-2024-45616?

CVE-2024-45616 affects Red Hat Enterprise Linux 7.0, 8.0, 9.0, and OpenSC versions below 0.26.0.

4

What type of attacks can exploit CVE-2024-45616?

CVE-2024-45616 can be exploited by attackers using a specially crafted USB device or Smart Card that presents malicious APDU responses.

5

Is there a workaround for CVE-2024-45616?

Currently, the recommended action for CVE-2024-45616 is to apply vendor patches rather than relying on workarounds.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203