# CVE-2008-4304: Command injection in n/a

> Remote attackers can execute arbitrary commands via shell metacharacters in the SSL_CLIENT_CERT environment variable in phpCollab.

- **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:** Not needed
- **Fix available:** No
- **Published:** 23 Dec 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qg8m-qgmv-g29c

## What is CVE-2008-4304?

CVE-2008-4304 is a critical command injection vulnerability in n/a, published on 23 Dec 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

general/login.php in phpCollab 2.5 rc3 and earlier allows remote attackers to execute arbitrary commands via shell metacharacters in unspecified input related to the SSL_CLIENT_CERT environment variable. NOTE: in some environments, SSL_CLIENT_CERT always has a base64-encoded string value, which may impose constraints on injection for typical shells.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Phpcollab Phpcollab.

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

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

## Is CVE-2008-4304 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-15907](https://insights.sbomify.com/CVE-2017-15907/): SQL injection in n/a (critical 9.8)
- [CVE-2017-6089](https://insights.sbomify.com/CVE-2017-6089/): SQL injection in n/a (critical 9.8)
- [CVE-2017-6090](https://insights.sbomify.com/CVE-2017-6090/): File upload in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-4304 is a critical command injection vulnerability in n/a, published on 23 Dec 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-4304 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-4304/ (Markdown: https://insights.sbomify.com/CVE-2008-4304/index.md)
```

## Sources

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

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