# CVE-2019-12314: Path traversal in n/a

> Attackers can read arbitrary local files via path traversal in the WS.macx1.W_MCS endpoint of Deltek Maconomy.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m2jw-qr8p-cx48

## What is CVE-2019-12314?

CVE-2019-12314 is a critical path traversal vulnerability in n/a, published on 24 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Deltek Maconomy 2.2.5 is prone to local file inclusion via absolute path traversal in the WS.macx1.W_MCS/ PATH_INFO, as demonstrated by a cgi-bin/Maconomy/MaconomyWS.macx1.W_MCS/etc/passwd URI.

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

## Which versions are affected by CVE-2019-12314?

It affects 1 product.


Products: Deltek Maconomy.

## How do I fix CVE-2019-12314?

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

## Is CVE-2019-12314 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-12314 exists.

Public exploit code:

- Deltek Maconomy 2.2.5 - Local File Inclusion (exploitdb)
- Optional Mitigation Steps (github_poc): https://github.com/ras313/CVE-2019-12314
- Deltek Maconomy 2.2.5 - Local File Inclusion (nuclei): http/cves/2019/CVE-2019-12314.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12314 and fix it if it is affected.

What it is: CVE-2019-12314 is a critical path traversal vulnerability in n/a, published on 24 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-12314 exists.

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-2019-12314/ (Markdown: https://insights.sbomify.com/CVE-2019-12314/index.md)
```

## Sources

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

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