Enterprise LinuxOperating system · Redhat
CVE-2011-4111
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBuffer overflow in the ccid_card_vscard_handle_message function in hw/ccid-card-passthru.c in QEMU before 0.15.2 and 1.x before 1.0-rc4 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted VSC_ATR message.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceBuffer overflow in the ccid_card_vscard_handle_message function in QEMU's CCID card passthrough device (hw/ccid-card-passthru.c) allows remote attackers to send crafted VSC_ATR messages, potentially causing denial of service or arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Enterprise LinuxOperating system
= 6.0
Enterprise Linux Server SupplementaryOperating system
= 6.1.z<= 0.15.1= 0.15.0= 1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- High
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:A/AC:H/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed QEMU versionRun `qemu-system-x86_64 --version` or `qemu --version` and compare the output to the affected ranges: versions <= 0.15.1, 0.15.0, or 1.0Affected if The installed QEMU version is 0.15.0, 0.15.1, 1.0, or any version <= 0.15.1 (including older versions)
-
Identify if CCID passthrough device is configuredCheck VM configuration files or libvirt domain XML for a hardware entry resembling `card` with `passthru` or a CCID device using the passthrough driverAffected if A virtual machine is configured to use the CCID card passthrough device (hw/ccid-card-passthru.c)
-
Verify the vulnerable source file is presentLocate `hw/ccid-card-passthru.c` in the QEMU source tree and check if it contains the function `ccid_card_vscard_handle_message`Affected if The QEMU installation includes the CCID passthrough source file with the vulnerable function
-
Check for active CCID passthrough device usageInspect running VM configurations or libvirt domains for emulated smart card readers using the passthrough mechanismAffected if A VM is actively using or has an active instance of the CCID passthrough device
You are affected if your QEMU version is 0.15.0, 0.15.1, 1.0, or any version <= 0.15.1 AND you have a virtual machine configured to use the CCID card passthrough device.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade QEMU to version 0.15.2 or later (for 0.15.x) or 1.0-rc4 or later (for 1.x) to patch the vulnerability. If upgrade is not possible, disable the CCID card passthrough feature.
Fix this in Enterprise Linux
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4111 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-4111 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data