# CVE-2006-6383: Security feature bypass in n/a

> Local attackers can bypass PHP safe_mode and open_basedir restrictions by exploiting a null byte parsing inconsistency in session_save_path.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vfqf-7vvp-5w4j

## What is CVE-2006-6383?

CVE-2006-6383 is a medium-severity vulnerability in Php Php, published on 10 Dec 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

PHP 5.2.0 and 4.4 allows local users to bypass safe_mode and open_basedir restrictions via a malicious path and a null byte before a ";" in a session_save_path argument, followed by an allowed path, which causes a parsing inconsistency in which PHP validates the allowed path but sets session.save_path to the malicious path.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2006-6383?

It affects 1 product.


Products: Php Php.

## How do I fix CVE-2006-6383?

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

## Is CVE-2006-6383 being exploited?

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

Public exploit code:

- PHP 5.2 - Session.Save_Path() 'Safe_mode' / 'open_basedir' Restriction Bypass (exploitdb)

## 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-2006-6383 and fix it if it is affected.

What it is: CVE-2006-6383 is a medium-severity vulnerability in Php Php, published on 10 Dec 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-6383 exists.

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

## Sources

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

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