CVE-2020-27219
Summary
| CVE | CVE-2020-27219 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2021-01-14 23:15:00 UTC |
| Updated | 2021-01-21 16:37:00 UTC |
| 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. |
Risk And Classification
Problem Types: CWE-79
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Eclipse | Hawkbit | 0.3.0 | m1 | All | All |
| Application | Eclipse | Hawkbit | 0.3.0 | m2 | All | All |
| Application | Eclipse | Hawkbit | 0.3.0 | m3 | All | All |
| Application | Eclipse | Hawkbit | 0.3.0 | m4 | All | All |
| Application | Eclipse | Hawkbit | 0.3.0 | m5 | All | All |
| Application | Eclipse | Hawkbit | 0.3.0 | m6 | All | All |
| Application | Eclipse | Hawkbit | All | All | All | All |
| Application | Eclipse | Hawkbit | 0.3.0 | m1 | All | All |
| Application | Eclipse | Hawkbit | 0.3.0 | m2 | All | All |
| Application | Eclipse | Hawkbit | 0.3.0 | m3 | All | All |
| Application | Eclipse | Hawkbit | 0.3.0 | m4 | All | All |
| Application | Eclipse | Hawkbit | 0.3.0 | m5 | All | All |
| Application | Eclipse | Hawkbit | 0.3.0 | m6 | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Mgmt API error page vulnerable to cross-site scripting attack · Issue #1067 · eclipse/hawkbit · GitHub | CONFIRM | github.com | Third Party Advisory |
| 570289 – (CVE-2020-27219) Eclipse hawkBit CVE request: Improper escaping of JSON response field | CONFIRM | bugs.eclipse.org | Vendor Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.