# CVE-2008-5186: Path traversal in n/a

> Remote attackers might exploit file inclusion in GeSHi library via crafted inputs, though the vendor disputes this vulnerability.

- **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:** 21 Nov 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-5186, GHSA-rhpx-cf93-fp5q

## What is CVE-2008-5186?

CVE-2008-5186 is a high-severity path traversal vulnerability in n/a, published on 21 Nov 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The set_language_path function in geshi.php in Generic Syntax Highlighter (GeSHi) before 1.0.8.1 might allow remote attackers to conduct file inclusion attacks via crafted inputs that influence the default language path ($path variable).  NOTE: this issue has been disputed by a vendor, stating that only a static value is used, so this is not a vulnerability in GeSHi. Separate CVE identifiers would be created for web applications that integrate GeSHi in a way that allows control of the default language path

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Geshi Geshi.

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

Upgrade to a fixed version.

## Is CVE-2008-5186 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-5185](https://insights.sbomify.com/CVE-2008-5185/): Denial of service in n/a (medium 5.0)
- [CVE-2005-3080](https://insights.sbomify.com/CVE-2005-3080/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-5186 is a high-severity path traversal vulnerability in n/a, published on 21 Nov 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-5186 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-5186/ (Markdown: https://insights.sbomify.com/CVE-2008-5186/index.md)
```

## Sources

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

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