CVE-2013-4355: Infoleak
First published: Tue Oct 01 2013(Updated: )
Xen 4.3.x and earlier does not properly handle certain errors, which allows local HVM guests to obtain hypervisor stack memory via a (1) port or (2) memory mapped I/O write or (3) other unspecified operations related to addresses without associated memory.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Xen XAPI | <=4.3.0 | |
| Xen XAPI | =3.0.2 | |
| Xen XAPI | =3.0.3 | |
| Xen XAPI | =3.0.4 | |
| Xen XAPI | =3.1.3 | |
| Xen XAPI | =3.1.4 | |
| Xen XAPI | =3.2.0 | |
| Xen XAPI | =3.2.1 | |
| Xen XAPI | =3.2.2 | |
| Xen XAPI | =3.2.3 | |
| Xen XAPI | =3.3.0 | |
| Xen XAPI | =3.3.1 | |
| Xen XAPI | =3.3.2 | |
| Xen XAPI | =3.4.0 | |
| Xen XAPI | =3.4.1 | |
| Xen XAPI | =3.4.2 | |
| Xen XAPI | =3.4.3 | |
| Xen XAPI | =3.4.4 | |
| Xen XAPI | =4.0.0 | |
| Xen XAPI | =4.0.1 | |
| Xen XAPI | =4.0.2 | |
| Xen XAPI | =4.0.3 | |
| Xen XAPI | =4.0.4 | |
| Xen XAPI | =4.1.0 | |
| Xen XAPI | =4.1.1 | |
| Xen XAPI | =4.1.2 | |
| Xen XAPI | =4.1.3 | |
| Xen XAPI | =4.1.4 | |
| Xen XAPI | =4.1.5 | |
| Xen XAPI | =4.2.0 | |
| Xen XAPI | =4.2.1 | |
| Xen XAPI | =4.2.2 | |
| Xen XAPI | =4.2.3 |
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
- http://lists.opensuse.org/opensuse-security-announce/2014-03/msg00015.html
- http://lists.opensuse.org/opensuse-security-announce/2014-03/msg00021.html
- http://lists.opensuse.org/opensuse-security-announce/2014-04/msg00000.html
- http://lists.opensuse.org/opensuse-updates/2013-11/msg00009.html
- http://rhn.redhat.com/errata/RHSA-2013-1790.html
- http://security.gentoo.org/glsa/glsa-201407-03.xml
- http://www.debian.org/security/2014/dsa-3006
- http://www.openwall.com/lists/oss-security/2013/09/30/1
Frequently Asked Questions
What is the severity of CVE-2013-4355?
CVE-2013-4355 has been classified as a medium severity vulnerability due to its potential to allow local HVM guests to access hypervisor stack memory.
How do I fix CVE-2013-4355?
The recommended fix for CVE-2013-4355 is to upgrade to a patched version of Xen that addresses this vulnerability.
Who is affected by CVE-2013-4355?
CVE-2013-4355 affects users running Xen versions 4.3.x and earlier, as well as specific older versions down to 3.0.2.
What are the potential impacts of CVE-2013-4355?
The impacts of CVE-2013-4355 include unauthorized access to sensitive hypervisor memory, which may lead to further exploitation.
Is CVE-2013-4355 exploitable remotely?
CVE-2013-4355 is not remotely exploitable as it requires local access to the hypervisor environment.
- agent/references
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/weakness
- agent/severity
- agent/author
- agent/event
- agent/description
- agent/first-publish-date
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/xen
- canonical/xen xapi
- version/xen xapi/4.3.0
- version/xen xapi/3.0.2
- version/xen xapi/3.0.3
- version/xen xapi/3.0.4
- version/xen xapi/3.1.3
- version/xen xapi/3.1.4
- version/xen xapi/3.2.0
- version/xen xapi/3.2.1
- version/xen xapi/3.2.2
- version/xen xapi/3.2.3
- version/xen xapi/3.3.0
- version/xen xapi/3.3.1
- version/xen xapi/3.3.2
- version/xen xapi/3.4.0
- version/xen xapi/3.4.1
- version/xen xapi/3.4.2
- version/xen xapi/3.4.3
- version/xen xapi/3.4.4
- version/xen xapi/4.0.0
- version/xen xapi/4.0.1
- version/xen xapi/4.0.2
- version/xen xapi/4.0.3
- version/xen xapi/4.0.4
- version/xen xapi/4.1.0
- version/xen xapi/4.1.1
- version/xen xapi/4.1.2
- version/xen xapi/4.1.3
- version/xen xapi/4.1.4
- version/xen xapi/4.1.5
- version/xen xapi/4.2.0
- version/xen xapi/4.2.1
- version/xen xapi/4.2.2
- version/xen xapi/4.2.3