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

> Remote attackers can read internal server files via path traversal in the source code viewer of Aptana Jaxer.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 9 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q3ph-369r-jjmm

## What is CVE-2019-14312?

CVE-2019-14312 is a medium-severity path traversal vulnerability in n/a, published on 9 Aug 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Aptana Jaxer 1.0.3.4547 is vulnerable to a local file inclusion vulnerability in the wikilite source code viewer. This vulnerability allows a remote attacker to read internal files on the server via a tools/sourceViewer/index.html?filename=../ URI.

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

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

It affects 1 product.


Products: Aptana Jaxer.

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

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

## Is CVE-2019-14312 being exploited?

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

Public exploit code:

- Aptana Jaxer 1.0.3.4547 - Local File inclusion (exploitdb)
- Aptana Jaxer 1.0.3.4547 - Local File inclusion (nuclei): http/cves/2019/CVE-2019-14312.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2019-14312 is a medium-severity path traversal vulnerability in n/a, published on 9 Aug 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-14312 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-14312/ (Markdown: https://insights.sbomify.com/CVE-2019-14312/index.md)
```

## Sources

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

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