Ovirt EngineApplication · Redhat
CVE-2018-1062
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 vulnerability was discovered in oVirt 4.1.x before 4.1.9, where the combination of Enable Discard and Wipe After Delete flags for VM disks managed by oVirt, could cause a disk to be incompletely zeroed when removed from a VM. If the same storage blocks happen to be later allocated to a new disk attached to another VM, potentially sensitive data could be revealed to privileged users of that VM.
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 · moderate confidenceIn oVirt 4.1.x before 4.1.9, the interaction between Enable Discard and Wipe After Delete flags on VM disks can result in incomplete zeroing of storage blocks when a disk is removed. When the same storage blocks are later allocated to a new disk attached to a different VM, residual sensitive data from the previous VM may be accessible to privileged users of the new VM.
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
Ovirt EngineApplication
>= 4.1.0, < 4.1.9CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
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 installed oVirt Engine versionRun 'engine-version' or check /etc/ovirt-engine/engine.conf for the version string, or use the administration portal under Administration > System > GeneralAffected if Version is 4.1.0 through 4.1.8 (versions before 4.1.9)
-
Locate VM disks with Enable Discard flag enabledIn oVirt administration portal, navigate to Storage > Disks and inspect the 'Discard' column for each disk, or query via API: GET /api/disks and check for discard_with_delete=true in disk configurationAffected if Any VM disk has Enable Discard option enabled
-
Locate VM disks with Wipe After Delete flag enabledIn oVirt administration portal, navigate to Storage > Disks and inspect the 'Wipe After Delete' column, or query via API: GET /api/disks and check for wipe_after_delete=true in disk configurationAffected if Any VM disk has Wipe After Delete option enabled
-
Identify disks with both flags simultaneously enabledCross-reference results from steps 2 and 3 - check if any single disk has both Enable Discard AND Wipe After Delete set to true, or use API filter: search for disks where both discard_with_delete=true AND wipe_after_delete=trueAffected if Any disk has BOTH Enable Discard and Wipe After Delete enabled simultaneously
You are affected if your oVirt Engine version is 4.1.0-4.1.8 and any VM disk has both the Enable Discard and Wipe After Delete flags enabled at the same time.
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 data4.1.9
Upgrade to oVirt 4.1.9 or later which addresses the improper handling of these disk flags; alternatively, audit disk configurations to avoid the problematic flag combination until patching is feasible.
Fix this in Ovirt Engine
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1062 — 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-2018-1062 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