# CVE-2013-4236: Denial of service in n/a

> Privileged guest users can cause host unavailability via invalid XML characters in guest agent responses, impacting virtualization management.

- **Severity:** Low 2.7 (`AV:A/AC:L/Au:S/C:N/I:N/A:P`)
- **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:** 19 Aug 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-jhj6-xfqh-j93v, RHSA-2013:1155

## What is CVE-2013-4236?

CVE-2013-4236 is a low-severity denial of service vulnerability in n/a, published on 19 Aug 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

VDSM in Red Hat Enterprise Virtualization 3 and 3.2 allows privileged guest users to cause the host to become "unavailable to the managment server" via invalid XML characters in a guest agent response.  NOTE: this issue is due to an incomplete fix for CVE-2013-0167.

## Which versions are affected by CVE-2013-4236?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vdsm` | Red Hat:enterprise_linux:6::hypervisor | All versions | 0:4.10.2-24.0.el6ev |
| `vdsm-cli` | Red Hat:enterprise_linux:6::hypervisor | All versions | 0:4.10.2-24.0.el6ev |
| `vdsm-debuginfo` | Red Hat:enterprise_linux:6::hypervisor | All versions | 0:4.10.2-24.0.el6ev |
| `vdsm-hook-vhostmd` | Red Hat:enterprise_linux:6::hypervisor | All versions | 0:4.10.2-24.0.el6ev |
| `vdsm-python` | Red Hat:enterprise_linux:6::hypervisor | All versions | 0:4.10.2-24.0.el6ev |
| `vdsm-reg` | Red Hat:enterprise_linux:6::hypervisor | All versions | 0:4.10.2-24.0.el6ev |
| `vdsm-xmlrpc` | Red Hat:enterprise_linux:6::hypervisor | All versions | 0:4.10.2-24.0.el6ev |
| `vdsm` | Red Hat:rhev_manager:3 | All versions | 0:4.10.2-24.0.el6ev |
| `vdsm-bootstrap` | Red Hat:rhev_manager:3 | All versions | 0:4.10.2-24.0.el6ev |
| `vdsm-debuginfo` | Red Hat:rhev_manager:3 | All versions | 0:4.10.2-24.0.el6ev |

Products: Redhat Enterprise Virtualization.

## How do I fix CVE-2013-4236?

Apply the vendor's patch.

## Is CVE-2013-4236 being exploited?

There is no known exploitation of CVE-2013-4236 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2015-5201](https://insights.sbomify.com/CVE-2015-5201/): Auth bypass in Enterprise Virtualization Hypervisor (aka RHEV-H) (high 7.5)
- [CVE-2013-2151](https://insights.sbomify.com/CVE-2013-2151/): Privilege escalation in n/a (high 7.2)
- [CVE-2013-2152](https://insights.sbomify.com/CVE-2013-2152/): Privilege escalation in n/a (high 7.2)
- [CVE-2013-2176](https://insights.sbomify.com/CVE-2013-2176/): Privilege escalation in n/a (high 7.2)
- [CVE-2017-2614](https://insights.sbomify.com/CVE-2017-2614/): Auth bypass in ovirt-engine-extension-aaa-jdbc (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4236 and fix it if it is affected.

What it is: CVE-2013-4236 is a low-severity denial of service vulnerability in n/a, published on 19 Aug 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-4236 in the wild and no public exploit code.

Affected product: n/a. 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-4236/ (Markdown: https://insights.sbomify.com/CVE-2013-4236/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-4236
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-4236
- OSV: https://osv.dev/vulnerability/CVE-2013-4236

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-4236/
Summaries are generated and may contain mistakes; the official description above is the record.