# CVE-2021-31932: Auth bypass in n/a

> Unauthenticated attackers can bypass authentication in the Nokia BTS TRS web console via URL encoding, gaining full administrative access to the device.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/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:** 11 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-623f-xv48-w9h8

## What is CVE-2021-31932?

CVE-2021-31932 is a critical authentication bypass vulnerability in n/a, published on 11 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Nokia BTS TRS web console FTM_W20_FP2_2019.08.16_0010 allows Authentication Bypass. A malicious unauthenticated user can get access to all the functionalities exposed via the web panel, circumventing the authentication process, by using URL encoding for the . (dot) character.

## Which versions are affected by CVE-2021-31932?

It affects 1 product.


Products: Nokia Bts Trs Web Console.

## How do I fix CVE-2021-31932?

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

## Is CVE-2021-31932 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-31932 and fix it if it is affected.

What it is: CVE-2021-31932 is a critical authentication bypass vulnerability in n/a, published on 11 Feb 2022. 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-2021-31932 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-2021-31932/ (Markdown: https://insights.sbomify.com/CVE-2021-31932/index.md)
```

## Sources

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

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