Enterprise Virtualization ManagerApplication · Redhat
CVE-2015-5293
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 3.6 and earlier gives valid SLAAC IPv6 addresses to interfaces when "boot protocol" is set to None, which might allow remote attackers to communicate with a system designated to be unreachable.
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 confidenceRed Hat Enterprise Virtualization Manager 3.6 and earlier incorrectly assigns valid SLAAC IPv6 addresses to network interfaces when the boot protocol is set to None. This causes systems intended to be isolated or unreachable to become reachable via IPv6, bypassing network segmentation controls.
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.6.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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/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.
-
Check Red Hat Enterprise Virtualization Manager versionRun 'rhsm-manager --version' or check /etc/redhat-release on the RHEV Manager host to determine the installed versionAffected if Version is 3.6.0 or earlier
-
Identify network interfaces with boot protocol set to NoneUse the RHEV administrative interface or ovirt-shell command 'list vms' followed by 'list nics' for each VM to identify network interfaces where the boot protocol is configured as None (or static:none)Affected if Any network interface on a managed VM has boot protocol set to None and is connected to a network that has IPv6 enabled
-
Check for SLAAC IPv6 address assignment on None-protocol interfacesFrom within the guest operating system of affected VMs, run 'ip -6 addr show' or check the network interface configuration to see if an IPv6 address was auto-assigned via SLAACAffected if An IPv6 address appears on a network interface that was configured with boot protocol None, indicating SLAAC auto-assignment occurred despite the None setting
You are affected if your RHEV Manager version is 3.6.0 or earlier and you have virtual machines with network interfaces set to boot protocol None that have obtained IPv6 addresses via SLAAC, bypassing intended network isolation.
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 dataConfigure sysctl settings to disable IPv6 or use router advertisements to prevent SLAAC address assignment on interfaces designated as unreachable, or ensure proper network isolation at the layer 3 level.
Fix this in Enterprise Virtualization Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5293 — 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-2015-5293 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