# CVE-2020-14945: Privilege escalation in n/a

> Authenticated low-privileged users can escalate to administrator rights by modifying SaveUser data in Global RADAR BSA Radar.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 22 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hmf8-53x4-w3jj

## What is CVE-2020-14945?

CVE-2020-14945 is a high-severity vulnerability in n/a, published on 22 Jun 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A privilege escalation vulnerability exists within Global RADAR BSA Radar 1.6.7234.24750 and earlier that allows an authenticated, low-privileged user to escalate their privileges to administrator rights (i.e., the BankAdmin role) via modified SaveUser data.

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

It affects 1 product.


Products: Globalradar Bsa Radar.

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

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

## Is CVE-2020-14945 being exploited?

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

Public exploit code:

- BSA Radar 1.6.7234.24750 - Authenticated Privilege Escalation (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2020-14944](https://insights.sbomify.com/CVE-2020-14944/): Missing authorization in n/a (critical 9.8)
- [CVE-2020-14943](https://insights.sbomify.com/CVE-2020-14943/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2020-14946](https://insights.sbomify.com/CVE-2020-14946/): Path traversal in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-14945 is a high-severity vulnerability in n/a, published on 22 Jun 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-2020-14945 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-14945/ (Markdown: https://insights.sbomify.com/CVE-2020-14945/index.md)
```

## Sources

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

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