# CVE-2016-5599: Missing authorization in n/a

> Remote attackers can compromise confidentiality and integrity in Oracle Advanced Supply Chain Planning via the MscObieeSrvlt component.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Oct 2016
- **Updated:** 10 Oct 2024
- **Also known as:** GHSA-487v-49wh-p479

## What is CVE-2016-5599?

CVE-2016-5599 is a critical missing authorization vulnerability in n/a, published on 25 Oct 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 Advanced Supply Chain Planning component in Oracle Supply Chain Products Suite 12.2.3 through 12.2.5 allows remote attackers to affect confidentiality and integrity via vectors related to MscObieeSrvlt.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Advanced Supply Chain Planning.

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

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

## Is CVE-2016-5599 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-2253](https://insights.sbomify.com/CVE-2021-2253/): Missing authorization in Advanced Supply Chain Planning (critical 9.1)
- [CVE-2026-61039](https://insights.sbomify.com/CVE-2026-61039/): Auth bypass in Oracle Advanced Supply Chain Planning (high 7.2)

## Fix prompt for AI coding agents

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

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

## Sources

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

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