# CVE-2006-3118: Race condition in n/a

> Local attackers can cause denial of service in Spread by exploiting a race condition involving static temporary filenames.

- **Severity:** Low 1.2 (`AV:L/AC:H/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fq89-8h82-8cxg

## What is CVE-2006-3118?

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

### Official description

spread uses a temporary file with a static filename based on the port number, which allows local users to cause a denial of service by creating the file during a race condition between unlink and bind function calls.  NOTE: spread deletes this temporary file before use, which could cause conflicts with other programs that use the same filename, but this is not a distinct issue.

## Which versions are affected by CVE-2006-3118?

It affects 1 product.


Products: Canonical Spread.

## How do I fix CVE-2006-3118?

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

## Is CVE-2006-3118 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-3118 and fix it if it is affected.

What it is: CVE-2006-3118 is a low-severity vulnerability in n/a, published on 30 Jun 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-2006-3118 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-2006-3118/ (Markdown: https://insights.sbomify.com/CVE-2006-3118/index.md)
```

## Sources

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

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