# CVE-2014-9767: Path traversal in n/a

> Remote attackers can create arbitrary empty directories via a crafted ZIP archive due to a path traversal flaw in the PHP zip extension.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 May 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4gmr-f4gg-2jhp, UBUNTU-CVE-2014-9767

## What is CVE-2014-9767?

CVE-2014-9767 is a medium-severity path traversal vulnerability in Php Php, published on 22 May 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Directory traversal vulnerability in the ZipArchive::extractTo function in ext/zip/php_zip.c in PHP before 5.4.45, 5.5.x before 5.5.29, and 5.6.x before 5.6.13 and ext/zip/ext_zip.cpp in HHVM before 3.12.1 allows remote attackers to create arbitrary empty directories via a crafted ZIP archive.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2014-9767?

It affects 2 products.


Products: Hiphop Virtual Machine for Php Project Hiphop Virtual Machine for Php, Php Php.

## How do I fix CVE-2014-9767?

Upgrade to a fixed version.

## Is CVE-2014-9767 being exploited?

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

## Other vulnerabilities in Php Php

- [CVE-2014-1439](https://insights.sbomify.com/CVE-2014-1439/): XML external entity in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-9767 and fix it if it is affected.

What it is: CVE-2014-9767 is a medium-severity path traversal vulnerability in Php Php, published on 22 May 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-9767 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-2014-9767/ (Markdown: https://insights.sbomify.com/CVE-2014-9767/index.md)
```

## Sources

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

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