# CVE-2016-3613: Other in n/a

> Remote attackers can compromise confidentiality, integrity, and availability of Oracle Secure Global Desktop via OpenSSL-related vectors.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2016
- **Updated:** 11 Oct 2024
- **Also known as:** GHSA-43xw-grf3-j6mj

## What is CVE-2016-3613?

CVE-2016-3613 is a critical vulnerability in n/a, published on 21 Jul 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in the Oracle Secure Global Desktop component in Oracle Virtualization 4.63, 4.71, and 5.2 allows remote attackers to affect confidentiality, integrity, and availability via vectors related to OpenSSL.

## Which versions are affected by CVE-2016-3613?

It affects 1 product.


Products: Oracle Secure Global Desktop.

## How do I fix CVE-2016-3613?

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

## Is CVE-2016-3613 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-2177](https://insights.sbomify.com/CVE-2021-2177/): Auth bypass in Secure Global Desktop (critical 10.0)
- [CVE-2021-2248](https://insights.sbomify.com/CVE-2021-2248/): Auth bypass in Secure Global Desktop (critical 10.0)
- [CVE-2021-2447](https://insights.sbomify.com/CVE-2021-2447/): Auth bypass in Secure Global Desktop (critical 9.9)
- [CVE-2021-2446](https://insights.sbomify.com/CVE-2021-2446/): Other in Secure Global Desktop (critical 9.6)
- [CVE-2021-2221](https://insights.sbomify.com/CVE-2021-2221/): Other in Secure Global Desktop (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-3613 and fix it if it is affected.

What it is: CVE-2016-3613 is a critical vulnerability in n/a, published on 21 Jul 2016. 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-2016-3613 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-2016-3613/ (Markdown: https://insights.sbomify.com/CVE-2016-3613/index.md)
```

## Sources

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

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