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

> Remote attackers can compromise confidentiality, integrity, and availability of Oracle Database and Retail systems via unspecified JDBC vectors.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/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-5www-hr54-473v

## What is CVE-2016-3506?

CVE-2016-3506 is a high-severity 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 JDBC component in Oracle Database Server 11.2.0.4, 12.1.0.1, and 12.1.0.2; the Oracle Retail Xstore Point of Service 5.5, 6.0, 6.5, 7.0, 7.1, 15.0, and 16.0; the Oracle Retail Warehouse Management System 14.04, 14.1.3, and 15.0.1; the Oracle Retail Workforce Management 1.60.7, and 1.64.0; the Oracle Retail Clearance Optimization Engine 13.4; the Oracle Retail Markdown Optimization 13.4 and 14.0; and Oracle Retail Merchandising System 16.0 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors.

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

It affects 1 product.


Products: Oracle Jdbc.

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

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

## Is CVE-2016-3506 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-3506 is a high-severity 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-3506 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-3506/ (Markdown: https://insights.sbomify.com/CVE-2016-3506/index.md)
```

## Sources

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

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