# CVE-2005-2527: Race condition in n/a

> Local attackers can corrupt or create arbitrary files via a race condition in Java temporary directory handling on Mac OS X.

- **Severity:** Low 1.2 (`AV:L/AC:H/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7fqm-4mw8-jrhj

## What is CVE-2005-2527?

CVE-2005-2527 is a low-severity vulnerability in n/a, published on 5 Aug 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Race condition in Java 1.4.2 before 1.4.2 Release 2 on Apple Mac OS X allows local users to corrupt files or create arbitrary files via unspecified attack vectors related to a temporary directory, possibly due to a symlink attack.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

It affects 1 product.


Products: Sun Java.

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

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

## Is CVE-2005-2527 being exploited?

There is no known exploitation of CVE-2005-2527 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-2005-2530](https://insights.sbomify.com/CVE-2005-2530/): 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)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2527 is a low-severity vulnerability in n/a, published on 5 Aug 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-2527 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-2527/ (Markdown: https://insights.sbomify.com/CVE-2005-2527/index.md)
```

## Sources

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

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