# CVE-2019-20150: Information disclosure in n/a

> A logged-in user can expose saved SSH/SFTP credentials by manipulating the SFTP host setting and triggering a connectivity check to a malicious server.

- **Severity:** Medium 6.5 (`CVSS:3.1/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:** 20 Aug 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gxq8-qw7q-mh32

## What is CVE-2019-20150?

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

### Official description

In TreasuryXpress 19191105, a logged-in user can discover saved credentials, even though the UI hides them. Using functionality within the application and a malicious host, it is possible to force the application to expose saved SSH/SFTP credentials. This can be done by using the application's editor to change the expected SFTP Host IP to a malicious host, and then using the Check Connectivity option. The application then sends these saved credentials to the malicious host.

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

It affects 1 product.


Products: Treasuryxpress Treasuryxpress.

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

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

## Is CVE-2019-20150 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-20151](https://insights.sbomify.com/CVE-2019-20151/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2019-20152](https://insights.sbomify.com/CVE-2019-20152/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-20150 is a medium-severity vulnerability in n/a, published on 20 Aug 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-20150 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-2019-20150/ (Markdown: https://insights.sbomify.com/CVE-2019-20150/index.md)
```

## Sources

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

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