# CVE-2012-6314: Security feature bypass in n/a

> Authenticated users can retain USB device access after policy changes due to failed propagation in Citrix XenDesktop VDA.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** No
- **Published:** 26 Dec 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5ggg-wqqw-9v43

## What is CVE-2012-6314?

CVE-2012-6314 is a medium-severity vulnerability in n/a, published on 26 Dec 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Citrix XenDesktop Virtual Desktop Agent (VDA) 5.6.x before 5.6.200, when making changes to the server-side policy that control USB redirection, does not propagate changes to the VDA, which allows authenticated users to retain access to the USB device.

## Which versions are affected by CVE-2012-6314?

It affects 1 product.


Products: Citrix Xendesktop.

## How do I fix CVE-2012-6314?

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

## Is CVE-2012-6314 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-6077](https://insights.sbomify.com/CVE-2013-6077/): Missing authorization in n/a (medium 5.8)
- [CVE-2014-4700](https://insights.sbomify.com/CVE-2014-4700/): Missing authorization in n/a (medium 4.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-6314 and fix it if it is affected.

What it is: CVE-2012-6314 is a medium-severity vulnerability in n/a, published on 26 Dec 2012. 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-2012-6314 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-2012-6314/ (Markdown: https://insights.sbomify.com/CVE-2012-6314/index.md)
```

## Sources

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

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