# CVE-2013-6795: Deserialization in n/a

> Remote attackers can execute arbitrary code on Windows guests by sending a crafted serialized object to the Updater service.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** CVE-2013-6764, GHSA-x7rq-j53w-9x9x

## What is CVE-2013-6795?

CVE-2013-6795 is a critical unsafe deserialization vulnerability in n/a, published on 24 Dec 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Updater in Rackspace Openstack Windows Guest Agent for XenServer before 1.2.6.0 allows remote attackers to execute arbitrary code via a crafted serialized .NET object to TCP port 1984, which triggers the download and extraction of a ZIP file that overwrites the Agent service binary.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Rackspace Openstack Windows Guest Agent.

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

No fix has been published for CVE-2013-6795 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-6795 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-6795 is a critical unsafe deserialization vulnerability in n/a, published on 24 Dec 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-6795 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-6795/ (Markdown: https://insights.sbomify.com/CVE-2013-6795/index.md)
```

## Sources

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

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