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

> Remote attackers can compromise confidentiality and integrity in Oracle Field Service via unspecified wireless vectors.

- **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:** 21 Apr 2016
- **Updated:** 15 Oct 2024
- **Also known as:** GHSA-8rfq-cjfm-rp46

## What is CVE-2016-3466?

CVE-2016-3466 is a critical vulnerability in n/a, published on 21 Apr 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 Field Service component in Oracle E-Business Suite 12.1.1, 12.1.2, and 12.1.3 allows remote attackers to affect confidentiality and integrity via vectors related to Wireless.

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

It affects 1 product.


Products: Oracle Field Service.

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

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

## Is CVE-2016-3466 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-2828](https://insights.sbomify.com/CVE-2019-2828/): Cross-site scripting in Field Service (critical 9.6)
- [CVE-2017-10170](https://insights.sbomify.com/CVE-2017-10170/): Information disclosure in Field Service (high 8.2)
- [CVE-2021-2362](https://insights.sbomify.com/CVE-2021-2362/): Missing authorization in Field Service (high 8.1)
- [CVE-2026-60739](https://insights.sbomify.com/CVE-2026-60739/): Missing authorization in Oracle Field Service (high 7.1)
- [CVE-2020-2603](https://insights.sbomify.com/CVE-2020-2603/): Cross-site scripting in Field Service (medium 6.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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