# CVE-2003-1572: Memory corruption in n/a

> Unsigned applets can crash the JVM and read unauthorized memory via the ReadEnv class in Sun Java Media Framework.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 1 Jun 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-34cp-xmwv-8pxg

## What is CVE-2003-1572?

CVE-2003-1572 is a critical memory corruption vulnerability in n/a, published on 1 Jun 2009. 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

Sun Java Media Framework (JMF) 2.1.1 through 2.1.1c allows unsigned applets to cause a denial of service (JVM crash) and read or write unauthorized memory locations via the ReadEnv class, as demonstrated by reading environment variables using modified .data and .size fields.

## Which versions are affected by CVE-2003-1572?

It affects 1 product.


Products: Sun Jmf.

## How do I fix CVE-2003-1572?

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

## Is CVE-2003-1572 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-1572 and fix it if it is affected.

What it is: CVE-2003-1572 is a critical memory corruption vulnerability in n/a, published on 1 Jun 2009. 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-2003-1572 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-2003-1572/ (Markdown: https://insights.sbomify.com/CVE-2003-1572/index.md)
```

## Sources

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

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