# CVE-2002-0076: Code injection in n/a

> Remote attackers can execute arbitrary commands and escape the Java sandbox by tricking users into visiting a malicious applet.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-x79p-2mvq-597f

## What is CVE-2002-0076?

CVE-2002-0076 is a high-severity code injection vulnerability in Sun Jdk, published on 2 Apr 2003. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Java Runtime Environment (JRE) Bytecode Verifier allows remote attackers to escape the Java sandbox and execute commands via an applet containing an illegal cast operation, as seen in (1) Microsoft VM build 3802 and earlier as used in Internet Explorer 4.x and 5.x, (2) Netscape 6.2.1 and earlier, and possibly other implementations that use vulnerable versions of SDK or JDK, aka a variant of the "Virtual Machine Verifier" vulnerability.

## Which versions are affected by CVE-2002-0076?

It affects 5 products.


Products: Hp Java Jre-Jdk, Microsoft Virtual Machine, Sun Jdk, Sun Jre, Sun Sdk.

## How do I fix CVE-2002-0076?

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

## Is CVE-2002-0076 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0076 and fix it if it is affected.

What it is: CVE-2002-0076 is a high-severity code injection vulnerability in Sun Jdk, published on 2 Apr 2003. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2002-0076 in the wild and no public exploit code.

Affected product: Sun 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-2002-0076/ (Markdown: https://insights.sbomify.com/CVE-2002-0076/index.md)
```

## Sources

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

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