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

> Remote attackers can read arbitrary files via path traversal in Infoware MapSuite MapAPI, requiring an upgrade to secure the application.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-77r3-2xp4-rrj3

## What is CVE-2014-2232?

CVE-2014-2232 is a medium-severity path traversal vulnerability in n/a, published on 1 Dec 2014. It can be exploited over the network, with no action from the victim.

### Official description

Absolute path traversal vulnerability in the MapAPI in Infoware MapSuite before 1.0.36 and 1.1.x before 1.1.49 allows remote attackers to read arbitrary files via unspecified vectors.

Weakness: CWE-21

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

It affects 1 product.


Products: Infoware Mapsuite.

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

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

## Is CVE-2014-2232 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-2843](https://insights.sbomify.com/CVE-2014-2843/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2014-2233](https://insights.sbomify.com/CVE-2014-2233/): Server-side request forgery in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2232 is a medium-severity path traversal vulnerability in n/a, published on 1 Dec 2014. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-2232 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-2014-2232/ (Markdown: https://insights.sbomify.com/CVE-2014-2232/index.md)
```

## Sources

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

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