# CVE-2016-5517: Information disclosure in n/a

> Local users can access sensitive information in Oracle E-Business Suite via AD Utilities, requiring a security patch.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 25 Oct 2016
- **Updated:** 10 Oct 2024
- **Also known as:** GHSA-w857-vvv6-q3c8

## What is CVE-2016-5517?

CVE-2016-5517 is a medium-severity vulnerability in n/a, published on 25 Oct 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unspecified vulnerability in the Oracle Applications DBA component in Oracle E-Business Suite 12.1.3 allows local users to affect confidentiality via vectors related to AD Utilities.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Applications Dba.

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

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

## Is CVE-2016-5517 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-61110](https://insights.sbomify.com/CVE-2026-61110/): Auth bypass in Oracle Applications DBA (high 8.8)
- [CVE-2026-22011](https://insights.sbomify.com/CVE-2026-22011/): Privilege escalation in Oracle Applications DBA (high 7.6)
- [CVE-2026-70681](https://insights.sbomify.com/CVE-2026-70681/): Auth bypass in Oracle Applications DBA (high 7.5)
- [CVE-2026-61107](https://insights.sbomify.com/CVE-2026-61107/): Privilege escalation in Oracle Applications DBA (high 7.2)
- [CVE-2026-70680](https://insights.sbomify.com/CVE-2026-70680/): Missing authorization in Oracle Applications DBA (high 7.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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