# CVE-2015-0475: Information disclosure in n/a

> Remote authenticated users can compromise confidentiality in Oracle JD Edwards EnterpriseOne Technology component via Web Runtime Security vectors.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/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:** 16 Apr 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xf49-x3pq-cfv4

## What is CVE-2015-0475?

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

### Official description

Unspecified vulnerability in the JD Edwards EnterpriseOne Technology component in Oracle JD Edwards Products 9.1 allows remote authenticated users to affect confidentiality via unknown vectors related to Web Runtime Security.

## Which versions are affected by CVE-2015-0475?

It affects 1 product.


Products: Oracle Jd Edwards Products.

## How do I fix CVE-2015-0475?

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

## Is CVE-2015-0475 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-0420](https://insights.sbomify.com/CVE-2016-0420/): Denial of service in n/a (high 7.8)
- [CVE-2016-0423](https://insights.sbomify.com/CVE-2016-0423/): Other in n/a (high 7.3)
- [CVE-2016-0422](https://insights.sbomify.com/CVE-2016-0422/): Denial of service in n/a (high 7.1)
- [CVE-2016-0424](https://insights.sbomify.com/CVE-2016-0424/): Denial of service in n/a (high 7.1)
- [CVE-2015-4919](https://insights.sbomify.com/CVE-2015-4919/): Other in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-0475 and fix it if it is affected.

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

## Sources

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

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