# CVE-2005-2530: Privilege escalation in n/a

> An untrusted Java applet can gain elevated privileges on Mac OS X due to a vulnerability in specific OS extensions.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** 5 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4x6g-wvjv-qm6c

## What is CVE-2005-2530?

CVE-2005-2530 is a critical vulnerability in n/a, published on 5 Aug 2006. 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

Unspecified vulnerability in Java 1.3.1 before 1.3.1_16 on Apple Mac OS X allows an untrusted applet to gain privileges, related to "Mac OS X specific extensions."

## Which versions are affected by CVE-2005-2530?

It affects 1 product.


Products: Sun Java.

## How do I fix CVE-2005-2530?

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

## Is CVE-2005-2530 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-0887](https://insights.sbomify.com/CVE-2010-0887/): Other in n/a (critical 10.0)
- [CVE-2005-2529](https://insights.sbomify.com/CVE-2005-2529/): Privilege escalation in n/a (critical 10.0)
- [CVE-2009-1105](https://insights.sbomify.com/CVE-2009-1105/): Security feature bypass in n/a (high 7.5)
- [CVE-2008-3440](https://insights.sbomify.com/CVE-2008-3440/): Code injection in n/a (high 7.5)
- [CVE-2009-1102](https://insights.sbomify.com/CVE-2009-1102/): Code injection in n/a (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2530 and fix it if it is affected.

What it is: CVE-2005-2530 is a critical vulnerability in n/a, published on 5 Aug 2006. 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-2005-2530 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-2005-2530/ (Markdown: https://insights.sbomify.com/CVE-2005-2530/index.md)
```

## Sources

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

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