# CVE-2001-1480: Information disclosure in n/a

> Untrusted Java applets can access the system clipboard, potentially exposing sensitive data copied by the user.

- **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:** 21 Jun 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-3p5q-mj37-8frf

## What is CVE-2001-1480?

CVE-2001-1480 is a high-severity vulnerability in Sun Jdk, published on 21 Jun 2005. 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) and SDK 1.2 through 1.3.0_04 allows untrusted applets to access the system clipboard.

## Which versions are affected by CVE-2001-1480?

It affects 4 products.


Products: Apple Mac Os Runtime for Java, Sun Jdk, Sun Jre, Sun Sdk.

## How do I fix CVE-2001-1480?

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

## Is CVE-2001-1480 being exploited?

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

## Other vulnerabilities in Sun Jdk

- [CVE-2000-0563](https://insights.sbomify.com/CVE-2000-0563/): Server-side request forgery in n/a (critical 10.0)
- [CVE-2001-0068](https://insights.sbomify.com/CVE-2001-0068/): Path traversal in n/a (low 2.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-1480 and fix it if it is affected.

What it is: CVE-2001-1480 is a high-severity vulnerability in Sun Jdk, published on 21 Jun 2005. 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-2001-1480 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-2001-1480/ (Markdown: https://insights.sbomify.com/CVE-2001-1480/index.md)
```

## Sources

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

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