# CVE-2017-3255: Information disclosure in JDeveloper

> Unauthenticated attackers can read sensitive data from Oracle JDeveloper via HTTP, requiring immediate patching by users of the affected versions.

- **Severity:** Medium 5.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/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:** 27 Jan 2017
- **Updated:** 9 Oct 2024
- **Also known as:** GHSA-g3mq-97x4-gmv9

## What is CVE-2017-3255?

CVE-2017-3255 is a medium-severity vulnerability in Oracle JDeveloper, published on 27 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Oracle JDeveloper component of Oracle Fusion Middleware (subcomponent: ADF Faces). Supported versions that are affected are 11.1.1.7.0, 11.1.1.9.0, 11.1.2.4.0, 12.1.3.0.0, 12.2.1.0.0, 12.2.1.1.0 and 12.2.1.2.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle JDeveloper. While the vulnerability is in Oracle JDeveloper, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle JDeveloper accessible data. CVSS v3.0 Base Score 5.8 (Confidentiality impacts).

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-3255?

It affects 1 product.


Products: Oracle Jdeveloper.

## How do I fix CVE-2017-3255?

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

## Is CVE-2017-3255 being exploited?

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

## Other vulnerabilities in Oracle JDeveloper

- [CVE-2016-3504](https://insights.sbomify.com/CVE-2016-3504/): Other in n/a (critical 9.8)
- [CVE-2018-2711](https://insights.sbomify.com/CVE-2018-2711/): Information disclosure in JDeveloper (high 8.2)
- [CVE-2026-60622](https://insights.sbomify.com/CVE-2026-60622/): Missing authorization in Oracle JDeveloper (high 7.5)
- [CVE-2026-60629](https://insights.sbomify.com/CVE-2026-60629/): Missing authorization in Oracle JDeveloper (high 7.5)
- [CVE-2026-60345](https://insights.sbomify.com/CVE-2026-60345/): Auth bypass in Oracle JDeveloper (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3255 and fix it if it is affected.

What it is: CVE-2017-3255 is a medium-severity vulnerability in Oracle JDeveloper, published on 27 Jan 2017. 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-2017-3255 in the wild and no public exploit code.

Affected product: Oracle JDeveloper. 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-2017-3255/ (Markdown: https://insights.sbomify.com/CVE-2017-3255/index.md)
```

## Sources

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

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