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

> Attackers can exploit a race condition in GForge configuration file updates to bypass access restrictions or modify data.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 May 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-1577-1, GHSA-w8p2-vhrj-74p5

## What is CVE-2008-0167?

CVE-2008-0167 is a medium-severity vulnerability in n/a, published on 18 May 2008. It can be exploited over the network, with no action from the victim.

### Official description

The write_array_file function in utils/include.pl in GForge 4.5.14 updates configuration files by truncating them to zero length and then writing new data, which might allow attackers to bypass intended access restrictions or have unspecified other impact in opportunistic circumstances.

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

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

It affects 1 product.


Products: Gforge Gforge.

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

Apply the vendor's patch.

## Is CVE-2008-0167 being exploited?

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

Public exploit code:

- phpQLAdmin 2.2.7 - Multiple Remote File Inclusions (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-4070](https://insights.sbomify.com/CVE-2009-4070/): SQL injection in n/a (high 7.5)
- [CVE-2008-6187](https://insights.sbomify.com/CVE-2008-6187/): SQL injection in n/a (high 7.5)
- [CVE-2008-6188](https://insights.sbomify.com/CVE-2008-6188/): SQL injection in n/a (high 7.5)
- [CVE-2008-6189](https://insights.sbomify.com/CVE-2008-6189/): SQL injection in n/a (high 7.5)
- [CVE-2008-2381](https://insights.sbomify.com/CVE-2008-2381/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-0167 is a medium-severity vulnerability in n/a, published on 18 May 2008. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-0167 exists.

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

## Sources

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

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