# CVE-2013-6501: Path traversal in n/a

> Local attackers can exploit predictable WSDL cache filenames in /tmp to inject malicious data, potentially leading to code execution or data modification.

- **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:** 30 Mar 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-x247-pp49-3c7r, UBUNTU-CVE-2013-6501

## What is CVE-2013-6501?

CVE-2013-6501 is a medium-severity path traversal vulnerability in Php Php, published on 30 Mar 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The default soap.wsdl_cache_dir setting in (1) php.ini-production and (2) php.ini-development in PHP through 5.6.7 specifies the /tmp directory, which makes it easier for local users to conduct WSDL injection attacks by creating a file under /tmp with a predictable filename that is used by the get_sdl function in ext/soap/php_sdl.c.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2013-6501?

It affects 2 products.


Products: Php Php, Suse Linux Enterprise Server.

## How do I fix CVE-2013-6501?

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

## Is CVE-2013-6501 being exploited?

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

What it is: CVE-2013-6501 is a medium-severity path traversal vulnerability in Php Php, published on 30 Mar 2015. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-6501 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-2013-6501/ (Markdown: https://insights.sbomify.com/CVE-2013-6501/index.md)
```

## Sources

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

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