# CVE-2014-4266: Other in n/a

> Remote attackers can compromise integrity in Oracle Java SE via unspecified Serviceability vectors, requiring users to upgrade to patched versions.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 17 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-g7wm-p554-cmgm, UBUNTU-CVE-2014-4266

## What is CVE-2014-4266?

CVE-2014-4266 is a medium-severity vulnerability in Oracle Jdk, published on 17 Jul 2014. An attacker can exploit it over the internet without logging in.

### Official description

Unspecified vulnerability in Oracle Java SE 7u60 and 8u5 allows remote attackers to affect integrity via unknown vectors related to Serviceability.

## Which versions are affected by CVE-2014-4266?

It affects 2 products.


Products: Oracle Jdk, Oracle Jre.

## How do I fix CVE-2014-4266?

Upgrade to a fixed version.

## Is CVE-2014-4266 being exploited?

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

## Other vulnerabilities in Oracle Jdk

- [CVE-2012-4681](https://insights.sbomify.com/CVE-2012-4681/): Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2012-1723](https://insights.sbomify.com/CVE-2012-1723/): Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-4805](https://insights.sbomify.com/CVE-2015-4805/): Deserialization in n/a (critical 10.0)
- [CVE-2015-4835](https://insights.sbomify.com/CVE-2015-4835/): Other in n/a (critical 10.0)
- [CVE-2015-4843](https://insights.sbomify.com/CVE-2015-4843/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-4266 and fix it if it is affected.

What it is: CVE-2014-4266 is a medium-severity vulnerability in Oracle Jdk, published on 17 Jul 2014. An attacker can exploit it over the internet without logging in.
Exploitation: There is no known exploitation of CVE-2014-4266 in the wild and no public exploit code.

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

## Sources

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

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