# CVE-2003-0863: Security feature bypass in n/a

> PHP fails to enforce safe_mode_include_dir restrictions when unconfigured, allowing remote attackers to bypass file inclusion security controls.

- **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:** No
- **Published:** 15 Oct 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-m77h-43fp-5x4g

## What is CVE-2003-0863?

CVE-2003-0863 is a high-severity vulnerability in Php Php, published on 15 Oct 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The php_check_safe_mode_include_dir function in fopen_wrappers.c of PHP 4.3.x returns a success value (0) when the safe_mode_include_dir variable is not specified in configuration, which differs from the previous failure value and may allow remote attackers to exploit file include vulnerabilities in PHP applications.

## Which versions are affected by CVE-2003-0863?

It affects 1 product.


Products: Php Php.

## How do I fix CVE-2003-0863?

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

## Is CVE-2003-0863 being exploited?

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

Public exploit code:

- PHP 4.3.x - Undefined Safe_Mode_Include_Dir Safemode 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-2003-0863 and fix it if it is affected.

What it is: CVE-2003-0863 is a high-severity vulnerability in Php Php, published on 15 Oct 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-0863 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-2003-0863/ (Markdown: https://insights.sbomify.com/CVE-2003-0863/index.md)
```

## Sources

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

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