# CVE-2013-4355: Information disclosure in n/a > Local HVM guests can read hypervisor stack memory via improper error handling in I/O operations, exposing sensitive data. - **Severity:** Low 1.5 (`AV:L/AC:M/Au:S/C:P/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 1 Oct 2013 - **Updated:** 6 Aug 2024 - **Also known as:** DEBIAN-CVE-2013-4355, GHSA-85vh-p875-9rm4, RHSA-2013:1790 ## What is CVE-2013-4355? CVE-2013-4355 is a low-severity vulnerability in Xen Xen, published on 1 Oct 2013. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2013-4355? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `kernel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-PAE` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-PAE-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-PAE-devel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-debug` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-debug-devel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-debuginfo-common` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-devel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-doc` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-headers` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-xen` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-xen-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-xen-devel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-371.3.1.el5 | | `kernel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-PAE` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-PAE-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-PAE-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-debug` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-debug-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-debuginfo-common` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-doc` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-headers` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-kdump` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-kdump-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-kdump-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-xen` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-xen-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-371.3.1.el5 | | `kernel-xen-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-371.3.1.el5 | Products: Xen Xen. ## How do I fix CVE-2013-4355? Apply the vendor's patch. ## Is CVE-2013-4355 being exploited? There is no known exploitation of CVE-2013-4355 in the wild and no public exploit code. ## Other vulnerabilities in Xen Xen - [CVE-2017-10912](https://insights.sbomify.com/CVE-2017-10912/): Privilege escalation in n/a (critical 10.0) - [CVE-2017-10918](https://insights.sbomify.com/CVE-2017-10918/): Memory corruption in n/a (critical 10.0) - [CVE-2017-10920](https://insights.sbomify.com/CVE-2017-10920/): Memory corruption in n/a (critical 10.0) - [CVE-2017-10921](https://insights.sbomify.com/CVE-2017-10921/): Memory corruption in n/a (critical 10.0) - [CVE-2025-27466](https://insights.sbomify.com/CVE-2025-27466/): Mutiple vulnerabilities in the Viridian interface (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2013-4355 and fix it if it is affected. What it is: CVE-2013-4355 is a low-severity vulnerability in Xen Xen, published on 1 Oct 2013. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2013-4355 in the wild and no public exploit code. Affected product: Xen Xen. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2013-4355/ (Markdown: https://insights.sbomify.com/CVE-2013-4355/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2013-4355 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-4355 - OSV: https://osv.dev/vulnerability/CVE-2013-4355 --- From sbomify Insights: https://insights.sbomify.com/CVE-2013-4355/ Summaries are generated and may contain mistakes; the official description above is the record.