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

> Remote attackers can execute arbitrary commands on the server via shell metacharacters in the gitweb search functionality.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Jan 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-932q-24j4-3r46

## What is CVE-2008-5516?

CVE-2008-5516 is a high-severity command injection vulnerability in n/a, published on 20 Jan 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The web interface in git (gitweb) 1.5.x before 1.5.5 allows remote attackers to execute arbitrary commands via shell metacharacters related to git_search.

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

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

It affects 2 products.


Products: Git-Scm Git, Git Git.

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

Upgrade to a fixed version.

## Is CVE-2008-5516 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-23521](https://insights.sbomify.com/CVE-2022-23521/): gitattributes parsing integer overflow in git (critical 9.8)
- [CVE-2022-41903](https://insights.sbomify.com/CVE-2022-41903/): Integer overflow in `git archive`, `git log --format` leading to RCE in git (critical 9.8)
- [CVE-2019-1353](https://insights.sbomify.com/CVE-2019-1353/): Security feature bypass in Git (critical 9.8)
- [CVE-2016-2315](https://insights.sbomify.com/CVE-2016-2315/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-2324](https://insights.sbomify.com/CVE-2016-2324/): Integer overflow in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-5516 is a high-severity command injection vulnerability in n/a, published on 20 Jan 2009. 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-5516 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-5516/ (Markdown: https://insights.sbomify.com/CVE-2008-5516/index.md)
```

## Sources

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

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