# CVE-2021-28117: Open redirect in n/a

> KDE Discover automatically creates links to dangerous URLs from store.kde.org, potentially bypassing security controls.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Mar 2021
- **Updated:** 15 Oct 2024
- **Also known as:** CLEANSTART-2024-WS30553, DEBIAN-CVE-2021-28117, GHSA-vr8p-gg49-j8hx, MGASA-2021-0146, UBUNTU-CVE-2021-28117

## What is CVE-2021-28117?

CVE-2021-28117 is a high-severity vulnerability in n/a, published on 20 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

libdiscover/backends/KNSBackend/KNSResource.cpp in KDE Discover before 5.21.3 automatically creates links to potentially dangerous URLs (that are neither https:// nor http://) based on the content of the store.kde.org web site. (5.18.7 is also a fixed version.)

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

It affects 1 product.


Products: Kde Discover.

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

Upgrade to a fixed version.

## Is CVE-2021-28117 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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