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

> Local attackers can execute arbitrary code by placing a malicious configuration file in the current working directory of the MAAS import script.

- **Severity:** Medium 4.4 (`AV:L/AC:M/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:** 15 Nov 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-hvgm-p4gp-w6qm

## What is CVE-2013-1057?

CVE-2013-1057 is a medium-severity path traversal vulnerability in Canonical Ubuntu Linux, published on 15 Nov 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Untrusted search path vulnerability in maas-import-pxe-files in MAAS before 13.10 allows local users to execute arbitrary code via a Trojan horse import_pxe_files configuration file in the current working directory.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Canonical Maas, Canonical Ubuntu Linux.

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

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

## Is CVE-2013-1057 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2025-7044](https://insights.sbomify.com/CVE-2025-7044/): Privilege Escalation in MAAS via Websocket Request Manipulation (high 7.7)
- [CVE-2013-1058](https://insights.sbomify.com/CVE-2013-1058/): Security feature bypass in n/a (medium 5.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-1057 and fix it if it is affected.

What it is: CVE-2013-1057 is a medium-severity path traversal vulnerability in Canonical Ubuntu Linux, published on 15 Nov 2013. 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-1057 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. 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-1057/ (Markdown: https://insights.sbomify.com/CVE-2013-1057/index.md)
```

## Sources

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

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