CVE-2017-6414: Medium severity Libcacard Project Libcacard vulnerability

Published Mar 1, 2017
·
Updated

Memory leak in the vcardapdunew function in card7816.c in libcacard before 2.5.3 allows local guest OS users to cause a denial of service (host memory consumption) via vectors related to allocating a new APDU object.

Other sources

The CAC(Common Access Card) library, used by Quick Emulator(Qemu) to implement smartcard support, is vulnerable to a host memory leakage issue. It could occur while allocating a new APDU object using guest supplied raw byte stream in 'vcardapdunew'.

A guest user/process could use this flaw to leak host memory resulting in DoS.

Upstream patch: --------------- -> https://cgit.freedesktop.org/spice/libcacard/commit/?id=9113dc6a303604a2d9812ac70c17d076ef11886c

Reference: ---------- -> http://www.openwall.com/lists/oss-security/2017/03/01/11

— Red Hat

Affected Software

1 affected component
Libcacard Project Libcacard<2.5.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade libcacard to a version that resolves this vulnerability.

    Fixed in 2.5.3
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch 9113dc6a303604a2d9812ac70c17d076ef11886c
  3. Compensating control

    Mitigate potential DoS from host memory consumption by restricting or isolating untrusted guest OS users/processes that may be able to trigger vcard_apdu_new allocations via Qemu smartcard/CAC functionality.

Event History

Mar 1, 2017
Data Sourced
via Red Hat·11:05 AM
DescriptionSeverityAffected Software
Mar 15, 2017
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
Data Sourced
via NVD·02:59 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Who can exploit this issue?

A local user or process inside a guest OS can exploit it. The affected component is libcacard as used by QEMU to provide smartcard support, and successful exploitation consumes memory on the host.

2

What access does an attacker need?

The attacker needs local, low-privileged access in a guest OS and does not need user interaction. Exploitation involves supplying a crafted raw byte stream during allocation of a new APDU object.

3

What is the impact on the host?

The issue causes a host-memory leak that can be repeatedly triggered, potentially exhausting host memory and causing a denial of service. The provided impact information indicates availability impact, not confidentiality or integrity impact.

4

Which versions are affected?

libcacard versions before 2.5.3 are affected.

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