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

> A regression in PHP's glob function allows bypassing open_basedir restrictions, potentially exposing files outside the intended directory.

- **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 stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 8 Jan 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vh95-55pv-84h2

## What is CVE-2008-0145?

CVE-2008-0145 is a high-severity path traversal vulnerability in Php Php, published on 8 Jan 2008. 

### Official description

Unspecified vulnerability in glob in PHP before 4.4.8, when open_basedir is enabled, has unknown impact and attack vectors.  NOTE: this issue reportedly exists because of a regression related to CVE-2007-4663.

Weakness: CWE-264

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

It affects 1 product.


Products: Php Php.

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

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

## Is CVE-2008-0145 being exploited?

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

## Other vulnerabilities in Php Php

- [CVE-2012-2688](https://insights.sbomify.com/CVE-2012-2688/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-2376](https://insights.sbomify.com/CVE-2012-2376/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-3268](https://insights.sbomify.com/CVE-2011-3268/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-4143](https://insights.sbomify.com/CVE-2009-4143/): Other in n/a (critical 10.0)
- [CVE-2008-5557](https://insights.sbomify.com/CVE-2008-5557/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-0145 is a high-severity path traversal vulnerability in Php Php, published on 8 Jan 2008. 
Exploitation: There is no known exploitation of CVE-2008-0145 in the wild and no public exploit code.

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

## Sources

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

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