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

> Remote authenticated users can access sensitive information in Oracle Retail MICROS ARS POS, requiring a security patch.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2016
- **Updated:** 15 Oct 2024
- **Also known as:** GHSA-88w2-wmp4-jh84

## What is CVE-2016-0684?

CVE-2016-0684 is a medium-severity vulnerability in n/a, published on 21 Apr 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the Oracle Retail MICROS ARS POS component in Oracle Retail Applications 1.5 allows remote authenticated users to affect confidentiality via vectors related to POS.

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

It affects 1 product.


Products: Oracle Micros Arspos.

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

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

## Is CVE-2016-0684 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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