# CVE-2021-41528: Improper authorization related to Import / Export interfaces on RISC Platform

> Low-privilege attackers can access import and export interfaces on the Flexera RISC Platform due to improper authorization checks.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/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:** 7 Feb 2025
- **Also known as:** GHSA-9m9p-ggvx-5qpm

## What is CVE-2021-41528?

CVE-2021-41528 is a medium-severity missing authorization 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 when handling authorization related to the import / export interfaces on the RISC Platform prior to the saas-2021-12-29 release can potentially be exploited to access the import / export functionality with low privileges.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2021-41528 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-41528 is a medium-severity missing authorization 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: There is no known exploitation of CVE-2021-41528 in the wild and no public exploit code.

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-41528/ (Markdown: https://insights.sbomify.com/CVE-2021-41528/index.md)
```

## Sources

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

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