cve.bz

CVE-2019-10240 eclipse hawkbit: Download of Code Without Integrity Check

8.1 highExploit referenceEPSS 0.4%Fix available

High (8.1) in eclipse hawkbit. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in org.eclipse.hawkbit:hawkbit-autoconfigure 0.3.0M2.

On this page
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.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 39th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-319 Cleartext Transmission of Sensitive Information
CWE-494 Download of Code Without Integrity Check
CWE-829 Inclusion of Functionality from Untrusted Control Sphere
OWASP Top 10
A04:2025 Cryptographic Failures, A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • org.eclipse.hawkbit:hawkbit-autoconfigure (Maven): fixed in 0.3.0M2
  • org.eclipse.hawkbit:hawkbit-ui (Maven): fixed in 0.3.0M2
  • org.eclipse.hawkbit:hawkbit-parent (Maven): fixed in 0.3.0M2
  • org.eclipse.hawkbit:hawkbit-starters (Maven): fixed in 0.3.0M2
  • org.eclipse.hawkbit:hawkbit-boot-starter (Maven): fixed in 0.3.0M2
  • org.eclipse.hawkbit:hawkbit-update-server (Maven): fixed in 0.3.0M2
  • org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-ui (Maven): fixed in 0.3.0M2
  • org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-api (Maven): fixed in 0.3.0M2
  • Vendor advisory: https://bugs.eclipse.org/bugs/show_bug.cgi?id=546053

Ask an AI about this CVE

Show the promptExplain CVE-2019-10240 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2019-10240?via=ask-ai-copy and https://cve.bz/cve/CVE-2019-10240?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2019-10240 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
The Eclipse Foundation Eclipse hawkBitbefore 0.3.0M2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jwqm-c9f2-2cq3Mavenorg.eclipse.hawkbit:hawkbit-autoconfigure<0.3.0M20.3.0M2
GHSA-jwqm-c9f2-2cq3Mavenorg.eclipse.hawkbit:hawkbit-ui<0.3.0M20.3.0M2
GHSA-jwqm-c9f2-2cq3Mavenorg.eclipse.hawkbit:hawkbit-parent<0.3.0M20.3.0M2
GHSA-jwqm-c9f2-2cq3Mavenorg.eclipse.hawkbit:hawkbit-starters<0.3.0M20.3.0M2
GHSA-jwqm-c9f2-2cq3Mavenorg.eclipse.hawkbit:hawkbit-boot-starter<0.3.0M20.3.0M2
GHSA-jwqm-c9f2-2cq3Mavenorg.eclipse.hawkbit:hawkbit-update-server<0.3.0M20.3.0M2
GHSA-jwqm-c9f2-2cq3Mavenorg.eclipse.hawkbit:hawkbit-boot-starter-mgmt-ui<0.3.0M20.3.0M2
GHSA-jwqm-c9f2-2cq3Mavenorg.eclipse.hawkbit:hawkbit-boot-starter-mgmt-api<0.3.0M20.3.0M2
GHSA-jwqm-c9f2-2cq3Mavenorg.eclipse.hawkbit:hawkbit-boot-starter-dmf-api<0.3.0M20.3.0M2
GHSA-jwqm-c9f2-2cq3Mavenorg.eclipse.hawkbit:hawkbit-boot-starter-ddi-api<0.3.0M20.3.0M2

Attack patterns (CAPEC)

  • CAPEC-65 Sniff Application Code Likelihood: Low · Severity: High
  • CAPEC-102 Session Sidejacking Likelihood: High · Severity: High
  • CAPEC-117 Interception Likelihood: Low · Severity: Medium
  • CAPEC-383 Harvesting Information via API Event Monitoring Severity: Low
  • CAPEC-477 Signature Spoofing by Mixing Signed and Unsigned Content Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-494 (12), CWE-829 (13).

References

Check your stackJSON