CVE-2013-6795 json
The Updater in Rackspace Openstack Windows Guest Agent for XenServer before 1.2.6.0 allows remote attackers to execute arbitrary code via a…
published 2013-12-24 12 y ago modified 2026-06-17 4 mo ago also EUVD-2013-6597
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.3%
- EPSS 5.3% chance of exploitation in 30 days, percentile 92%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Exploit prediction
5.34% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/rackerlabs/openstack-guest-agents-windows-xenserver/commit/ef16f88f20254b8083e361f11707da25f8482401 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
github.com
/rackerlabs/openstack-guest-agents-windows-xenserver/commit/ef16f88f20254b8083e361f11707da25f8482401
exploit, patch
-
blog.cloudpassage.com
/2013/11/18/cve-2013-6795-vulnerability-rackspace-windows-agent-updater/
url-repurposed
- packetstormsecurity.com /files/124153/Rackspace-Windows-Agent-Updater-Arbitrary-Code-Execution.html
-
archives.neohapsis.com
/archives/bugtraq/2013-11/0122.html
mailing-list
-
osvdb.org
/100191
vdb-entry
-
secunia.com
/advisories/55775
third-party-advisory
- github.com /rackerlabs/openstack-guest-agents-windows-xenserver/releases/tag/1.2.6.0
Sources
- CVE List CVE-2013-6795
- NVD CVE-2013-6795
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.