Skip to content

Cleartext Transmission of Sensitive Information, Inclusion of Functionality from Untrusted Control Sphere , and Download of Code Without Integrity Check in Eclipse hawkBit

High severity GitHub Reviewed Published Apr 15, 2019 to the GitHub Advisory Database • Updated Jan 9, 2023

Package

maven org.eclipse.hawkbit:hawkbit-autoconfigure (Maven)

Affected versions

<= 0.3.0M1

Patched versions

0.3.0M2
maven org.eclipse.hawkbit:hawkbit-boot-starter (Maven)
<= 0.3.0M1
0.3.0M2
maven org.eclipse.hawkbit:hawkbit-boot-starter-ddi-api (Maven)
<= 0.3.0M1
0.3.0M2
maven org.eclipse.hawkbit:hawkbit-boot-starter-dmf-api (Maven)
<= 0.3.0M1
0.3.0M2
maven org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-api (Maven)
<= 0.3.0M1
0.3.0M2
maven org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-ui (Maven)
<= 0.3.0M1
0.3.0M2
maven org.eclipse.hawkbit:hawkbit-parent (Maven)
<= 0.3.0M1
0.3.0M2
maven org.eclipse.hawkbit:hawkbit-starters (Maven)
<= 0.3.0M1
0.3.0M2
maven org.eclipse.hawkbit:hawkbit-ui (Maven)
<= 0.3.0M1
0.3.0M2
maven org.eclipse.hawkbit:hawkbit-update-server (Maven)
<= 0.3.0M1
0.3.0M2

Description

Eclipse hawkBit versions prior to 0.3.0M2 resolved Maven build artifacts for the Vaadin based UI over HTTP instead of HTTPS. Any of these dependent artifacts could have been maliciously compromised by a MITM attack. Hence produced build artifacts of hawkBit might be infected.

References

Published to the GitHub Advisory Database Apr 15, 2019
Reviewed Dec 3, 2021
Last updated Jan 9, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(25th percentile)

Weaknesses

Cleartext Transmission of Sensitive Information

The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors. Learn more on MITRE.

Download of Code Without Integrity Check

The product downloads source code or an executable from a remote location and executes the code without sufficiently verifying the origin and integrity of the code. Learn more on MITRE.

Inclusion of Functionality from Untrusted Control Sphere

The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere. Learn more on MITRE.

CVE ID

CVE-2019-10240

GHSA ID

GHSA-jwqm-c9f2-2cq3

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.