# CVE-2014-2439: Other in n/a

> Remote attackers can compromise confidentiality and integrity of the Workspace Web Application in Oracle Secure Global Desktop.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 16 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-79m6-q5h9-fv2f

## What is CVE-2014-2439?

CVE-2014-2439 is a medium-severity vulnerability in n/a, published on 16 Apr 2014. It can be exploited over the network.

### Official description

Unspecified vulnerability in the Oracle Secure Global Desktop (SGD) component in Oracle Virtualization 5.0 and 5.1 allows remote attackers to affect confidentiality and integrity via unknown vectors related to Workspace Web Application.

## Which versions are affected by CVE-2014-2439?

It affects 1 product.


Products: Oracle Virtualization.

## How do I fix CVE-2014-2439?

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

## Is CVE-2014-2439 being exploited?

There is no known exploitation of CVE-2014-2439 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-2021-20191](https://insights.sbomify.com/CVE-2021-20191/): Insertion of Sensitive Information into Log File in ansible (medium 5.5)
- [CVE-2020-10775](https://insights.sbomify.com/CVE-2020-10775/): Open redirect in ovirt-engine (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2439 and fix it if it is affected.

What it is: CVE-2014-2439 is a medium-severity vulnerability in n/a, published on 16 Apr 2014. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2014-2439 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-2014-2439/ (Markdown: https://insights.sbomify.com/CVE-2014-2439/index.md)
```

## Sources

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

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