# CVE-2020-27219: Cross-site Scripting in Eclipse Hawkbit

> An attacker can inject malicious scripts via unescaped path attributes in 404 error responses, potentially leading to code execution in the browser context.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **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:** Yes
- **Published:** 14 Jan 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rcvx-rmvf-mxch

## What is CVE-2020-27219?

CVE-2020-27219 is a medium-severity cross-site scripting vulnerability in The Eclipse Foundation Eclipse Hawkbit, published on 14 Jan 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

In all version of Eclipse Hawkbit prior to 0.3.0M7, the HTTP 404 (Not Found) JSON response body returned by the REST API may contain unsafe characters within the path attribute. Sending a POST request to a non existing resource will return the full path from the given URL unescaped to the client.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2020-27219?

2 open source packages ship an affected version, including org.eclipse.hawkbit:hawkbit-parent. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.eclipse.hawkbit:hawkbit-parent` | Maven | All versions | 0.3.0M7 |
| `org.eclipse.hawkbit:hawkbit-parent` | Maven | All versions | 0.3.0M7 |

Products: Eclipse Hawkbit.

## How do I fix CVE-2020-27219?

Upgrade org.eclipse.hawkbit:hawkbit-parent to 0.3.0M7 or later.

## Is CVE-2020-27219 being exploited?

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

Public exploit code:

- https://github.com/shoucheng3/eclipse__hawkbit_CVE-2020-27219_0-3-0M6 (github_poc): https://github.com/shoucheng3/eclipse__hawkbit_CVE-2020-27219_0-3-0M6

## Other vulnerabilities in The Eclipse Foundation Eclipse Hawkbit

- [CVE-2019-10240](https://insights.sbomify.com/CVE-2019-10240/): Cleartext Transmission of Sensitive Information, Inclusion of Functionality from Untrusted Control Sphere , and Download of Code Without Integrity Check in Eclipse hawkBit (high 8.1)
- [CVE-2026-16454](https://insights.sbomify.com/CVE-2026-16454/): Privilege Escalation in Eclipse hawkBit DDI allows Tenant-Isolated Firmware Exfiltration (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-27219 and fix it if it is affected.

What it is: CVE-2020-27219 is a medium-severity cross-site scripting vulnerability in The Eclipse Foundation Eclipse Hawkbit, published on 14 Jan 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-2020-27219 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.eclipse.hawkbit:hawkbit-parent (Maven): affected all versions; fixed in 0.3.0M7
- org.eclipse.hawkbit:hawkbit-parent (Maven): affected all versions; fixed in 0.3.0M7

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

## Sources

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

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