CVE-2024-4467
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 · uneditedA flaw was found in the QEMU disk image utility (qemu-img) 'info' command. A specially crafted image file containing a `json:{}` value describing block devices in QMP could cause the qemu-img process on the host to consume large amounts of memory or CPU time, leading to denial of service or read/write to an existing external file.
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 confidenceA flaw in qemu-img's 'info' command allows specially crafted image files with json:{} block device descriptions to cause excessive memory/CPU consumption (denial of service) and potentially read/write to external files on the host system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Locate qemu-img executableRun 'which qemu-img' or 'find /usr -name qemu-img 2>/dev/null' to find the qemu-img binaryAffected if qemu-img is not found on the system, the system is not affected by this vulnerability
-
Determine qemu-img versionRun 'qemu-img --version' and compare the version number to the fixed version (qemu-img 9.0.0 and later are patched; check your distribution's security advisories for specific patched versions)Affected if The installed version is older than the patched version for your qemu-img package
-
Identify qemu-img usage patternsSearch for scripts, cron jobs, or automated processes that invoke 'qemu-img info' on image files, especially those from untrusted or external sources: grep -r 'qemu-img info' /path/to/searchAffected if qemu-img info is run against image files from untrusted or external sources without prior validation
-
Check for untrusted image filesLocate qemu image files (.qcow2, .img, etc.) that may have originated from untrusted sources or the internet: find / -name '*.qcow2' -o -name '*.img' 2>/dev/null and review their provenanceAffected if Untrusted or externally-sourced image files exist on the system and are processed by qemu-img info
-
Audit recent qemu-img info executionReview system logs, bash history, or audit logs for recent 'qemu-img info' command execution: history | grep 'qemu-img info' or check /var/log/audit/audit.log if auditd is enabledAffected if qemu-img info has been recently executed, particularly on untrusted images
The environment is affected if qemu-img is installed with a vulnerable version AND processes image files (especially untrusted or externally-sourced ones) using the 'info' command.
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 dataUpdate qemu-img to the patched version. If immediate patching is not possible, restrict qemu-img access and validate image sources before running 'info' commands.
- Consultation2.0 h
- Implementation1.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4467 — 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-2024-4467 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