CVE-2019-10240

CVE-2019-10240 is a high-severity security vulnerability in org.eclipse.hawkbit:hawkbit-autoconfigure (maven), affecting versions <= 0.3.0M1. It is fixed in 0.3.0M2.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

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

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.

Impact

CVE-2019-10240 has a CVSS score of 8.1 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.3.0M2); upgrading removes the vulnerable code path.

Affected versions

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

Security releases

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 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.eclipse.hawkbit:hawkbit-autoconfigure to 0.3.0M2 or later; org.eclipse.hawkbit:hawkbit-ui to 0.3.0M2 or later; org.eclipse.hawkbit:hawkbit-parent to 0.3.0M2 or later; org.eclipse.hawkbit:hawkbit-starters to 0.3.0M2 or later; org.eclipse.hawkbit:hawkbit-boot-starter to 0.3.0M2 or later; org.eclipse.hawkbit:hawkbit-update-server to 0.3.0M2 or later; org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-ui to 0.3.0M2 or later; org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-api to 0.3.0M2 or later; org.eclipse.hawkbit:hawkbit-boot-starter-dmf-api to 0.3.0M2 or later; org.eclipse.hawkbit:hawkbit-boot-starter-ddi-api to 0.3.0M2 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2019-10240? CVE-2019-10240 is a high-severity security vulnerability in org.eclipse.hawkbit:hawkbit-autoconfigure (maven), affecting versions <= 0.3.0M1. It is fixed in 0.3.0M2.
  2. How severe is CVE-2019-10240? CVE-2019-10240 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which packages are affected by CVE-2019-10240?
    • org.eclipse.hawkbit:hawkbit-autoconfigure (maven) (versions <= 0.3.0M1)
    • org.eclipse.hawkbit:hawkbit-ui (maven) (versions <= 0.3.0M1)
    • org.eclipse.hawkbit:hawkbit-parent (maven) (versions <= 0.3.0M1)
    • org.eclipse.hawkbit:hawkbit-starters (maven) (versions <= 0.3.0M1)
    • org.eclipse.hawkbit:hawkbit-boot-starter (maven) (versions <= 0.3.0M1)
    • org.eclipse.hawkbit:hawkbit-update-server (maven) (versions <= 0.3.0M1)
    • org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-ui (maven) (versions <= 0.3.0M1)
    • org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-api (maven) (versions <= 0.3.0M1)
    • org.eclipse.hawkbit:hawkbit-boot-starter-dmf-api (maven) (versions <= 0.3.0M1)
    • org.eclipse.hawkbit:hawkbit-boot-starter-ddi-api (maven) (versions <= 0.3.0M1)
  4. Is there a fix for CVE-2019-10240? Yes. CVE-2019-10240 is fixed in 0.3.0M2. Upgrade to this version or later.
  5. Is CVE-2019-10240 exploitable, and should I be worried? Whether CVE-2019-10240 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2019-10240 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2019-10240?
    • Upgrade org.eclipse.hawkbit:hawkbit-autoconfigure to 0.3.0M2 or later
    • Upgrade org.eclipse.hawkbit:hawkbit-ui to 0.3.0M2 or later
    • Upgrade org.eclipse.hawkbit:hawkbit-parent to 0.3.0M2 or later
    • Upgrade org.eclipse.hawkbit:hawkbit-starters to 0.3.0M2 or later
    • Upgrade org.eclipse.hawkbit:hawkbit-boot-starter to 0.3.0M2 or later
    • Upgrade org.eclipse.hawkbit:hawkbit-update-server to 0.3.0M2 or later
    • Upgrade org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-ui to 0.3.0M2 or later
    • Upgrade org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-api to 0.3.0M2 or later
    • Upgrade org.eclipse.hawkbit:hawkbit-boot-starter-dmf-api to 0.3.0M2 or later
    • Upgrade org.eclipse.hawkbit:hawkbit-boot-starter-ddi-api to 0.3.0M2 or later

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo