# CVE-2021-41527: 2FA bypass on the RISC Platform

> Attackers can bypass two-factor authentication on the RISC Platform if the 2FA setup is incomplete, allowing unauthorized access.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA: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:** 7 Feb 2025
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-vjph-w72m-276x

## What is CVE-2021-41527?

CVE-2021-41527 is a low-severity authentication bypass vulnerability in Flexera RISC Platform, published on 7 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An error related to the 2-factor authorization (2FA) on the RISC Platform prior to the saas-2021-12-29 release can potentially be exploited to bypass the 2FA. The vulnerability requires that the 2FA setup hasn’t been completed.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2021-41527 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-41527 is a low-severity authentication bypass vulnerability in Flexera RISC Platform, published on 7 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-41527 exists.

Affected product: Flexera RISC Platform. 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-41527/ (Markdown: https://insights.sbomify.com/CVE-2021-41527/index.md)
```

## Sources

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

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