# CVE-2007-0014: Security feature bypass in n/a

> Attackers can bypass ChainKey Java Code Protection to decompile class files by using a modified class loader, exposing proprietary source code.

- **Severity:** Medium 4.4 (`AV:L/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3fh8-vxv8-v699

## What is CVE-2007-0014?

CVE-2007-0014 is a medium-severity vulnerability in n/a, published on 17 Jan 2007. 

### Official description

ChainKey Java Code Protection allows attackers to decompile Java class files via a Java class loader with a modified defineClass method that saves the bytecode to a file before it is passed to the JVM.

Weakness: CWE-310

## Which versions are affected by CVE-2007-0014?

It affects 1 product.


Products: Sun Chainkey Java Code Protection.

## How do I fix CVE-2007-0014?

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

## Is CVE-2007-0014 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-0014 and fix it if it is affected.

What it is: CVE-2007-0014 is a medium-severity vulnerability in n/a, published on 17 Jan 2007. 
Exploitation: There is no known exploitation of CVE-2007-0014 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-2007-0014/ (Markdown: https://insights.sbomify.com/CVE-2007-0014/index.md)
```

## Sources

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

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