# CVE-2011-3571: Information disclosure in n/a

> Remote authenticated users can compromise confidentiality and integrity in Oracle Virtualization VDI via unspecified session vectors.

- **Severity:** Low 3.6 (`AV:N/AC:H/Au:S/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Jan 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fjgc-8pc6-5qr3

## What is CVE-2011-3571?

CVE-2011-3571 is a low-severity vulnerability in n/a, published on 18 Jan 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the Virtual Desktop Infrastructure (VDI) component in Oracle Virtualization 3.2 allows remote authenticated users to affect confidentiality and integrity via unknown vectors related to Session.  NOTE: this CVE identifier was accidentally used for a Concurrency issue in Java Runtime Environment, but that issue has been reassigned to CVE-2012-0507.

## Which versions are affected by CVE-2011-3571?

It affects 1 product.


Products: Oracle Virtualization.

## How do I fix CVE-2011-3571?

Apply the vendor's patch.

## Is CVE-2011-3571 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-3779](https://insights.sbomify.com/CVE-2013-3779/): Other in n/a (high 7.5)
- [CVE-2011-3538](https://insights.sbomify.com/CVE-2011-3538/): Auth bypass in n/a (medium 6.8)
- [CVE-2015-2581](https://insights.sbomify.com/CVE-2015-2581/): Other in n/a (medium 6.4)
- [CVE-2014-2439](https://insights.sbomify.com/CVE-2014-2439/): Other in n/a (medium 6.4)
- [CVE-2021-20191](https://insights.sbomify.com/CVE-2021-20191/): Insertion of Sensitive Information into Log File in ansible (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-3571 and fix it if it is affected.

What it is: CVE-2011-3571 is a low-severity vulnerability in n/a, published on 18 Jan 2012. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-3571 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-2011-3571/ (Markdown: https://insights.sbomify.com/CVE-2011-3571/index.md)
```

## Sources

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

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