# CVE-2017-10273: Path traversal in JDeveloper

> A path traversal vulnerability in Oracle JDeveloper allows high-privileged attackers to read, modify, or disrupt data via local access.

- **Severity:** Medium 4.7 (`CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Jan 2018
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-4qr8-xvfr-96r5

## What is CVE-2017-10273?

CVE-2017-10273 is a medium-severity path traversal vulnerability in Oracle Corporation JDeveloper, published on 18 Jan 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Oracle JDeveloper component of Oracle Fusion Middleware (subcomponent: Deployment). Supported versions that are affected are 11.1.1.7.0, 11.1.1.7.1, 11.1.1.9.0, 11.1.2.4.0, 12.1.3.0.0 and 12.2.1.2.0. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where Oracle JDeveloper executes to compromise Oracle JDeveloper. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle JDeveloper, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle JDeveloper accessible data as well as unauthorized read access to a subset of Oracle JDeveloper accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle JDeveloper. CVSS 3.0 Base Score 4.7 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:L).

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Oracle Jdeveloper.

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

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

## Is CVE-2017-10273 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-10273 exists.

Public exploit code:

- Oracle JDeveloper 11.1.x/12.x - Directory Traversal (exploitdb)

## Other vulnerabilities in Oracle Corporation 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-10273 and fix it if it is affected.

What it is: CVE-2017-10273 is a medium-severity path traversal vulnerability in Oracle Corporation JDeveloper, published on 18 Jan 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-10273 exists.

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

## Sources

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

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