# CVE-2003-1123: Security feature bypass in n/a

> Untrusted Java applets can access trusted applet data, bypassing security restrictions and potentially exposing sensitive information.

- **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:** 12 Mar 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-wm8w-8q3h-xpmg

## What is CVE-2003-1123?

CVE-2003-1123 is a high-severity vulnerability in Sun Jdk, published on 12 Mar 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

Sun Java Runtime Environment (JRE) and SDK 1.4.0_01 and earlier allows untrusted applets to access certain information within trusted applets, which allows attackers to bypass the restrictions of the Java security model.

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

It affects 2 products.


Products: Sun Jdk, Sun Jre.

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

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

## Is CVE-2003-1123 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-1123 exists.

Public exploit code:

- Sun JRE/SDK 1.x - Untrusted Applet Java Security Model Violation (exploitdb)

## Other vulnerabilities in Sun Jdk

- [CVE-2011-3521](https://insights.sbomify.com/CVE-2011-3521/): Deserialization in n/a (critical 10.0)
- [CVE-2011-3548](https://insights.sbomify.com/CVE-2011-3548/): Other in n/a (critical 10.0)
- [CVE-2011-3549](https://insights.sbomify.com/CVE-2011-3549/): Other in n/a (critical 10.0)
- [CVE-2011-3554](https://insights.sbomify.com/CVE-2011-3554/): Other in n/a (critical 10.0)
- [CVE-2011-0802](https://insights.sbomify.com/CVE-2011-0802/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-1123 is a high-severity vulnerability in Sun Jdk, published on 12 Mar 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-1123 exists.

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-2003-1123/ (Markdown: https://insights.sbomify.com/CVE-2003-1123/index.md)
```

## Sources

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

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