# CVE-2020-14930: Information disclosure in n/a

> Attackers can take over accounts because the password-reset feature leaks verification tokens to unauthenticated HTTP clients.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 19 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pvp3-4g5m-35pm

## What is CVE-2020-14930?

CVE-2020-14930 is a high-severity vulnerability in n/a, published on 19 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in BT CTROMS Terminal OS Port Portal CT-464. Account takeover can occur because the password-reset feature discloses the verification token. Upon a getverificationcode.jsp request, this token is transmitted not only to the registered phone number of the user account, but is also transmitted to the unauthenticated HTTP client.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2020-14930?

It affects 1 product.


Products: Bt Ctroms Terminal Project Bt Ctroms Terminal.

## How do I fix CVE-2020-14930?

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

## Is CVE-2020-14930 being exploited?

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

Public exploit code:

- CTROMS Terminal OS Port Portal - 'Password Reset' Authentication Bypass (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-14930 and fix it if it is affected.

What it is: CVE-2020-14930 is a high-severity vulnerability in n/a, published on 19 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-14930 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-2020-14930/ (Markdown: https://insights.sbomify.com/CVE-2020-14930/index.md)
```

## Sources

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

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