CVE-2015-5293
First published: Wed Sep 30 2015(Updated: )
It is reported that when a bridge device is set up with "None" for the boot protocol on a network with working IPv6 stateless configuration the host will receieve a valid SLAAC IPv6 address. This could result in a system being reachable via IPv6 when it is not intended to be.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Red Hat Enterprise Virtualization Manager | <=3.6.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2015-5293?
CVE-2015-5293 has been classified as a moderate severity vulnerability.
How do I fix CVE-2015-5293?
To address CVE-2015-5293, ensure the bridge device is configured correctly and avoid using 'None' for the boot protocol.
What systems are affected by CVE-2015-5293?
CVE-2015-5293 affects Red Hat Enterprise Virtualization Manager versions up to and including 3.6.0.
What is the impact of CVE-2015-5293?
The impact of CVE-2015-5293 is that it may unintentionally expose a system to IPv6 traffic.
When was CVE-2015-5293 reported?
CVE-2015-5293 was reported in 2015.
- agent/type
- agent/softwarecombine
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/author
- agent/last-modified-date
- agent/weakness
- agent/references
- agent/event
- agent/description
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2015-5293
- agent/trending
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/redhat
- canonical/red hat enterprise virtualization manager
- version/red hat enterprise virtualization manager/3.6.0