# CVE-2021-42917: Memory corruption in n/a

> Attackers can cause a denial of service in Kodi media center via a buffer overflow in the istream component.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 Nov 2021
- **Updated:** 18 Nov 2024
- **Also known as:** DEBIAN-CVE-2021-42917, GHSA-9856-v5xm-mr4c, UBUNTU-CVE-2021-42917

## What is CVE-2021-42917?

CVE-2021-42917 is a medium-severity memory corruption vulnerability in n/a, published on 1 Nov 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Buffer overflow vulnerability in Kodi xbmc up to 19.0, allows attackers to cause a denial of service due to improper length of values passed to istream.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Kodi Kodi.

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

Upgrade to a fixed version.

## Is CVE-2021-42917 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-5982](https://insights.sbomify.com/CVE-2017-5982/): Path traversal in n/a (high 7.5)
- [CVE-2018-8831](https://insights.sbomify.com/CVE-2018-8831/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2023-30207](https://insights.sbomify.com/CVE-2023-30207/): Denial of service in n/a (medium 5.5)
- [CVE-2023-23082](https://insights.sbomify.com/CVE-2023-23082/): Memory corruption in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-42917 is a medium-severity memory corruption vulnerability in n/a, published on 1 Nov 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-42917 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-42917/ (Markdown: https://insights.sbomify.com/CVE-2021-42917/index.md)
```

## Sources

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

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