# CVE-2015-3411: Path traversal in n/a

> Remote attackers can read or write arbitrary files by exploiting null byte injection in PHP file handling functions, bypassing intended file type restrictions.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 May 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4gf4-5fpq-6cwc, UBUNTU-CVE-2015-3411

## What is CVE-2015-3411?

CVE-2015-3411 is a medium-severity path traversal vulnerability in Php Php, published on 16 May 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHP before 5.4.40, 5.5.x before 5.5.24, and 5.6.x before 5.6.8 does not ensure that pathnames lack %00 sequences, which might allow remote attackers to read or write to arbitrary files via crafted input to an application that calls (1) a DOMDocument load method, (2) the xmlwriter_open_uri function, (3) the finfo_file function, or (4) the hash_hmac_file function, as demonstrated by a filename\0.xml attack that bypasses an intended configuration in which client users may read only .xml files.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2015-3411?

It affects 8 products.


Products: Php Php, Redhat Enterprise Linux, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Hpc Node, Redhat Enterprise Linux Hpc Node Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Eus, Redhat Enterprise Linux Workstation.

## How do I fix CVE-2015-3411?

Upgrade to a fixed version.

## Is CVE-2015-3411 being exploited?

There is no known exploitation of CVE-2015-3411 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-2015-3411 and fix it if it is affected.

What it is: CVE-2015-3411 is a medium-severity path traversal vulnerability in Php Php, published on 16 May 2016. 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-2015-3411 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-2015-3411/ (Markdown: https://insights.sbomify.com/CVE-2015-3411/index.md)
```

## Sources

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

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