# CVE-2021-45096: XML external entity in n/a

> An attacker can exploit XXE in KNIME Analytics Platform via crafted workflow files to read sensitive data or execute code.

- **Severity:** Medium 4.7 (`CVSS:3.1/AC:L/AV:N/A:N/C:L/I:N/PR:N/S:C/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fgh6-7vq6-4p7f

## What is CVE-2021-45096?

CVE-2021-45096 is a medium-severity vulnerability in n/a, published on 16 Dec 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

KNIME Analytics Platform before 4.5.0 is vulnerable to XXE (external XML entity injection) via a crafted workflow file (.knwf), aka AP-17730.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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

It affects 1 product.


Products: Knime Knime Analytics Platform.

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

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

## Is CVE-2021-45096 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-31500](https://insights.sbomify.com/CVE-2022-31500/): Misconfiguration in n/a (high 7.8)
- [CVE-2023-5562](https://insights.sbomify.com/CVE-2023-5562/): Unsafe default allows for cross-site scripting attacks in KNIME Server and KNIME Business Hub (medium 6.1)
- [CVE-2022-44749](https://insights.sbomify.com/CVE-2022-44749/): Opening workflows from untrusted resources may override arbitrary file system contents (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-45096 is a medium-severity vulnerability in n/a, published on 16 Dec 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-45096 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-45096/ (Markdown: https://insights.sbomify.com/CVE-2021-45096/index.md)
```

## Sources

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

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