Enterprise Virtualization ManagerApplication · Redhat
CVE-2013-2144
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 · uneditedRed Hat Enterprise Virtualization Manager (RHEVM) before 3.2 does not properly check permissions for the target storage domain, which allows attackers to cause a denial of service (disk space consumption) by cloning a VM from a snapshot.
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 confidenceRHEVM before 3.2 lacks proper authorization checks when cloning a VM from a snapshot, specifically failing to validate permissions on the target storage domain. This allows any authenticated user to trigger VM cloning operations that consume disk space on any storage domain, leading to denial of service.
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 Virtualization ManagerApplication
<= 3.1= 2.1= 2.2= 2.2.3= 3.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
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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.
-
Identify the installed RHEVM versionCheck the RHEVM version by accessing the administration portal's About section, or by running 'rpm -q rhevm' on the RHEVM serverAffected if The installed version is 3.1 or earlier, or matches 2.1, 2.2, 2.2.3, or 3.0 exactly
-
Verify VM cloning from snapshots functionalityConfirm that the VM cloning from snapshot feature is available and accessible in the RHEVM environmentAffected if The feature is enabled and users with standard authentication can access VM cloning operations
-
Review storage domain permissions configurationExamine the RHEVM storage domain access control settings to determine whether target storage domain permissions are being validated during clone operationsAffected if Storage domain permissions are not enforced or can be bypassed for authenticated users performing clone operations
-
Audit recent VM clone operationsReview RHEVM audit logs for VM cloning operations, focusing on the storage domains targeted and the users performing the operationsAffected if Clone operations exist that targeted storage domains the initiating user should not have had permission to access
A user is affected if the RHEVM version is 3.1 or earlier, or exactly 2.1, 2.2, 2.2.3, or 3.0, and authenticated users can clone VMs to storage domains without proper permission validation.
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 RHEVM to version 3.2 or later, which includes proper permission checks for target storage domains during VM cloning operations.
Fix this in Enterprise Virtualization Manager
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2144 — 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-2013-2144 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