Ovirt EngineApplication · Redhat
CVE-2016-3077
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 · uneditedThe VersionMapper.fromKernelVersionString method in oVirt Engine allows remote authenticated users to cause a denial of service (process crash) for all VMs.
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 confidenceThe VersionMapper.fromKernelVersionString method in oVirt Engine contains a vulnerability where malformed kernel version strings can cause a process crash. Authenticated remote users can trigger this DoS condition, affecting all VMs managed by the engine.
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
all versionsCVSS 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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
-
Confirm oVirt Engine is installedCheck for oVirt Engine installation by looking for the 'engine' service or process: run 'systemctl status ovirt-engine' or 'ps aux | grep ovirt-engine'Affected if The oVirt Engine service or process is found running on the system
-
Identify the installed oVirt Engine versionRun 'rpm -q ovirt-engine' to query the RPM package version, or use 'engine- --version' if the command is availableAffected if The command returns a version string indicating oVirt Engine is installed (all versions are affected)
-
Verify remote access to oVirt Engine is enabledCheck if the engine service is listening on its management port (usually 443 or 8443) by running 'ss -tlnp | grep -E "(443|8443)"' or checking the firewall configurationAffected if The oVirt Engine web interface port is accessible, allowing authenticated remote users to send requests
-
Confirm kernel version data can be submitted to the engineVerify that the engine accepts VM configuration or kernel version data from authenticated users through the API or web interfaceAffected if Authenticated users can interact with the VersionMapper.fromKernelVersionString method via VM or host configuration features
If oVirt Engine is running and accessible to authenticated remote users, the environment is affected because all versions contain the vulnerable VersionMapper.fromKernelVersionString method.
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 dataApply the vendor patch for CVE-2016-3077 to fix the VersionMapper.fromKernelVersionString method to properly handle malformed input without crashing. Consider implementing input validation and error handling as a defense-in-depth measure.
Fix this in Ovirt Engine
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-3077 — 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-2016-3077 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