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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2019-10240: 0.43% estimated exploitation activity in the next 30 days; percentile 37.84 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

15 Apr 2019, 16:19 UTC

Last modified by the source

9 Jan 2023, 05:05 UTC

Source last checked

26 Oct 2026, 15:53 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jwqm-c9f2-2cq3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2019-10240

Advisory: Cleartext Transmission of Sensitive Information, Inclusion of Functionality from Untrusted Control Sphere , and Download of Code Without Integrity Check in Eclipse hawkBit
IDs: CVE-2019-10240, GHSA-jwqm-c9f2-2cq3
Record: https://patchnext.com/advisories/cve-2019-10240 (revision 1, source checked 26 Oct 2026, 15:53 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.eclipse.hawkbit:hawkbit-boot-starter-ddi-api 0.3.0M2; org.eclipse.hawkbit:hawkbit-parent 0.3.0M2; org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-ui 0.3.0M2; org.eclipse.hawkbit:hawkbit-autoconfigure 0.3.0M2; org.eclipse.hawkbit:hawkbit-update-server 0.3.0M2; org.eclipse.hawkbit:hawkbit-starters 0.3.0M2; org.eclipse.hawkbit:hawkbit-boot-starter-dmf-api 0.3.0M2; org.eclipse.hawkbit:hawkbit-boot-starter 0.3.0M2; org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-api 0.3.0M2; org.eclipse.hawkbit:hawkbit-ui 0.3.0M2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.eclipse.hawkbit:hawkbit-boot-starter-ddi-api: affected <= 0.3.0M1; fixed in 0.3.0M2
- Maven org.eclipse.hawkbit:hawkbit-parent: affected <= 0.3.0M1; fixed in 0.3.0M2
- Maven org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-ui: affected <= 0.3.0M1; fixed in 0.3.0M2
- Maven org.eclipse.hawkbit:hawkbit-autoconfigure: affected <= 0.3.0M1; fixed in 0.3.0M2
- Maven org.eclipse.hawkbit:hawkbit-update-server: affected <= 0.3.0M1; fixed in 0.3.0M2
- Maven org.eclipse.hawkbit:hawkbit-starters: affected <= 0.3.0M1; fixed in 0.3.0M2
- Maven org.eclipse.hawkbit:hawkbit-boot-starter-dmf-api: affected <= 0.3.0M1; fixed in 0.3.0M2
- Maven org.eclipse.hawkbit:hawkbit-boot-starter: affected <= 0.3.0M1; fixed in 0.3.0M2
- Maven org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-api: affected <= 0.3.0M1; fixed in 0.3.0M2
- Maven org.eclipse.hawkbit:hawkbit-ui: affected <= 0.3.0M1; fixed in 0.3.0M2

## Suggested inspection (read-only)
- Maven org.eclipse.hawkbit:hawkbit-boot-starter-ddi-api: check the installed version with your package manager.
- Maven org.eclipse.hawkbit:hawkbit-parent: check the installed version with your package manager.
- Maven org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-ui: check the installed version with your package manager.
- Maven org.eclipse.hawkbit:hawkbit-autoconfigure: check the installed version with your package manager.
- Maven org.eclipse.hawkbit:hawkbit-update-server: check the installed version with your package manager.
- Maven org.eclipse.hawkbit:hawkbit-starters: check the installed version with your package manager.
- Maven org.eclipse.hawkbit:hawkbit-boot-starter-dmf-api: check the installed version with your package manager.
- Maven org.eclipse.hawkbit:hawkbit-boot-starter: check the installed version with your package manager.
- Maven org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-api: check the installed version with your package manager.
- Maven org.eclipse.hawkbit:hawkbit-ui: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.eclipse.hawkbit:hawkbit-boot-starter-ddi-api, org.eclipse.hawkbit:hawkbit-parent, org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-ui, org.eclipse.hawkbit:hawkbit-autoconfigure, org.eclipse.hawkbit:hawkbit-update-server, org.eclipse.hawkbit:hawkbit-starters, org.eclipse.hawkbit:hawkbit-boot-starter-dmf-api, org.eclipse.hawkbit:hawkbit-boot-starter, org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-api, org.eclipse.hawkbit:hawkbit-ui.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jwqm-c9f2-2cq3 (GitHub-reviewed advisory GHSA-jwqm-c9f2-2cq3 lists affected ranges: Maven org.eclipse.hawkbit:hawkbit-autoconfigure >=0 =0 =0 =0 =0 =0 =0 <=0.3.0M1; Maven…)

Commands are suggestions: review each one before running it.