Skip to content
Fencer Intel
high 8.1

CVE-2019-10240 json

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

published 7y ago modified 4mo ago also GHSA-jwqm-c9f2-2cq3 , EUVD-2019-0424

cvss
8.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 38%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.eclipse.hawkbit:hawkbit-autoconfigure 0.3.0M2
  • maven org.eclipse.hawkbit:hawkbit-ui 0.3.0M2
  • maven org.eclipse.hawkbit:hawkbit-parent 0.3.0M2
  • maven org.eclipse.hawkbit:hawkbit-starters 0.3.0M2
  • maven org.eclipse.hawkbit:hawkbit-boot-starter 0.3.0M2
  • maven org.eclipse.hawkbit:hawkbit-update-server 0.3.0M2
  • maven org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-ui 0.3.0M2
  • maven org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-api 0.3.0M2
  • maven org.eclipse.hawkbit:hawkbit-boot-starter-dmf-api 0.3.0M2
  • maven org.eclipse.hawkbit:hawkbit-boot-starter-ddi-api 0.3.0M2
  • The Eclipse Foundation Eclipse hawkBit 0.3.0M2

Is CVE-2019-10240 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • bugs.eclipse.org https://bugs.eclipse.org/bugs/show_bug.cgi?id=546053 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.eclipse.hawkbit:hawkbit-autoconfigure
<0.3.0M2
0.3.0M2
maven org.eclipse.hawkbit:hawkbit-ui
<0.3.0M2
0.3.0M2
maven org.eclipse.hawkbit:hawkbit-parent
<0.3.0M2
0.3.0M2
maven org.eclipse.hawkbit:hawkbit-starters
<0.3.0M2
0.3.0M2
maven org.eclipse.hawkbit:hawkbit-boot-starter
<0.3.0M2
0.3.0M2
maven org.eclipse.hawkbit:hawkbit-update-server
<0.3.0M2
0.3.0M2
maven org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-ui
<0.3.0M2
0.3.0M2
maven org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-api
<0.3.0M2
0.3.0M2
maven org.eclipse.hawkbit:hawkbit-boot-starter-dmf-api
<0.3.0M2
0.3.0M2
maven org.eclipse.hawkbit:hawkbit-boot-starter-ddi-api
<0.3.0M2
0.3.0M2

Affected products

  • The Eclipse Foundation Eclipse hawkBit

Classification

Weakness
  • CWE-829 Inclusion of Functionality from Untrusted Control Sphere
  • CWE-494 Download of Code Without Integrity Check
  • CWE-319 Cleartext Transmission of Sensitive Information

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.