# CVE-2008-1570: Race condition in n/a

> Local attackers can exploit a race condition in policyd-weight to modify or delete arbitrary files, potentially leading to privilege escalation.

- **Severity:** Medium 6.9 (`AV:L/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** Yes
- **Published:** 31 Mar 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-1570, GHSA-72h5-35jc-jq88

## What is CVE-2008-1570?

CVE-2008-1570 is a medium-severity vulnerability in n/a, published on 31 Mar 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Race condition in the create_lockpath function in policyd-weight 0.1.14 beta-16 allows local users to modify or delete arbitrary files by creating the LOCKPATH directory, then modifying it after the symbolic link check occurs.  NOTE: this is due to an incomplete fix for CVE-2008-1569.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2008-1570?

It affects 1 product.


Products: Policyd-Weight Policyd-Weight.

## How do I fix CVE-2008-1570?

Apply the vendor's patch.

## Is CVE-2008-1570 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-1569](https://insights.sbomify.com/CVE-2008-1569/): Path traversal in n/a (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1570 and fix it if it is affected.

What it is: CVE-2008-1570 is a medium-severity vulnerability in n/a, published on 31 Mar 2008. 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-2008-1570 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-2008-1570/ (Markdown: https://insights.sbomify.com/CVE-2008-1570/index.md)
```

## Sources

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

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