# CVE-2012-4991: Path traversal in n/a

> Authenticated attackers can read, delete, or create files and list directories via path traversal in Axway SecureTransport.

- **Severity:** High 8.5 (`AV:N/AC:L/Au:S/C:C/I:C/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Dec 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qr4m-qxp9-h6pg

## What is CVE-2012-4991?

CVE-2012-4991 is a high-severity path traversal vulnerability in n/a, published on 13 Dec 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in Axway SecureTransport 5.1 SP2 and earlier allow remote authenticated users to (1) read, (2) delete, or (3) create files, or (4) list directories, via a ..%5C (encoded dot dot backslash) in a URI.

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

## Which versions are affected by CVE-2012-4991?

It affects 1 product.


Products: Axway Securetransport.

## How do I fix CVE-2012-4991?

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

## Is CVE-2012-4991 being exploited?

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

Public exploit code:

- Axway Secure Transport 5.1 SP2 - Directory Traversal (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2019-14277](https://insights.sbomify.com/CVE-2019-14277/): XML external entity in n/a (critical 9.8)
- [CVE-2013-7057](https://insights.sbomify.com/CVE-2013-7057/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-4991 and fix it if it is affected.

What it is: CVE-2012-4991 is a high-severity path traversal vulnerability in n/a, published on 13 Dec 2012. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-4991 in the wild and no public exploit code.

Affected product: n/a. 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-2012-4991/ (Markdown: https://insights.sbomify.com/CVE-2012-4991/index.md)
```

## Sources

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

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