What is the severity of CVE-2020-27219?

CVE-2020-27219 has a moderate severity rating due to the potential for unsafe characters in the error responses.

How do I fix CVE-2020-27219?

To fix CVE-2020-27219, upgrade Eclipse Hawkbit to version 0.3.0M7 or later.

What kind of attack does CVE-2020-27219 allow?

CVE-2020-27219 allows an attacker to potentially retrieve unsafe or sensitive path information through unescaped JSON responses.

Which versions of Eclipse Hawkbit are affected by CVE-2020-27219?

CVE-2020-27219 affects all versions of Eclipse Hawkbit prior to 0.3.0M7.

Is there a workaround for CVE-2020-27219?

There is no official workaround for CVE-2020-27219, and updating to the fixed version is recommended.

Vulnerability/
CVE-2020-27219

medium

6.1

CWE

14/1/2021

4/8/2024

CVE-2020-27219: XSS

First published: Thu Jan 14 2021(Updated: )

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.

Credit: emo@eclipse.org

Affected Software	Affected Version	How to fix
Eclipse Hawkbit	<=0.2.5
Eclipse Hawkbit	=0.3.0-m1
Eclipse Hawkbit	=0.3.0-m2
Eclipse Hawkbit	=0.3.0-m3
Eclipse Hawkbit	=0.3.0-m4
Eclipse Hawkbit	=0.3.0-m5
Eclipse Hawkbit	=0.3.0-m6

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-27219?
CVE-2020-27219 has a moderate severity rating due to the potential for unsafe characters in the error responses.
How do I fix CVE-2020-27219?
To fix CVE-2020-27219, upgrade Eclipse Hawkbit to version 0.3.0M7 or later.
What kind of attack does CVE-2020-27219 allow?
CVE-2020-27219 allows an attacker to potentially retrieve unsafe or sensitive path information through unescaped JSON responses.
Which versions of Eclipse Hawkbit are affected by CVE-2020-27219?
CVE-2020-27219 affects all versions of Eclipse Hawkbit prior to 0.3.0M7.
Is there a workaround for CVE-2020-27219?
There is no official workaround for CVE-2020-27219, and updating to the fixed version is recommended.

collector/nvd-index
agent/type
agent/references
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/author
agent/weakness
agent/severity
agent/tags
agent/event
agent/description
agent/first-publish-date
agent/source
vendor/eclipse
canonical/eclipse hawkbit
version/eclipse hawkbit/0.2.5
version/eclipse hawkbit/0.3.0-m1
version/eclipse hawkbit/0.3.0-m2
version/eclipse hawkbit/0.3.0-m3
version/eclipse hawkbit/0.3.0-m4
version/eclipse hawkbit/0.3.0-m5
version/eclipse hawkbit/0.3.0-m6

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.