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

> An attacker can traverse the file system to access unauthorized files via the downloadDocServer function in TEMENOS Channels.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-ch35-w937-rw95

## What is CVE-2019-14251?

CVE-2019-14251 is a high-severity path traversal vulnerability in n/a, published on 9 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in T24 in TEMENOS Channels R15.01. The login page presents JavaScript functions to access a document on the server once successfully authenticated. However, an attacker can leverage downloadDocServer() to traverse the file system and access files or directories that are outside of the restricted directory because WealthT24/GetImage is used with the docDownloadPath and uploadLocation parameters.

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

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

It affects 1 product.


Products: Temenos T24.

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

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

## Is CVE-2019-14251 being exploited?

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

Public exploit code:

- T24 Web Server - Local File Inclusion (nuclei): http/cves/2019/CVE-2019-14251.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2019-14251 is a high-severity path traversal vulnerability in n/a, published on 9 Dec 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-14251 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-14251/ (Markdown: https://insights.sbomify.com/CVE-2019-14251/index.md)
```

## Sources

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

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