| Package | Affected versions | Patched versions |
|---|---|---|
| org.eclipse.hawkbit:hawkbit-autoconfigure | < 0.3.0M2 | 0.3.0M2 |
| org.eclipse.hawkbit:hawkbit-boot-starter | < 0.3.0M2 | 0.3.0M2 |
| org.eclipse.hawkbit:hawkbit-boot-starter-ddi-api | < 0.3.0M2 | 0.3.0M2 |
| org.eclipse.hawkbit:hawkbit-boot-starter-dmf-api | < 0.3.0M2 | 0.3.0M2 |
| org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-api | < 0.3.0M2 | 0.3.0M2 |
| org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-ui | < 0.3.0M2 | 0.3.0M2 |
| org.eclipse.hawkbit:hawkbit-parent | < 0.3.0M2 | 0.3.0M2 |
| org.eclipse.hawkbit:hawkbit-starters | < 0.3.0M2 | 0.3.0M2 |
| org.eclipse.hawkbit:hawkbit-ui | < 0.3.0M2 | 0.3.0M2 |
| org.eclipse.hawkbit:hawkbit-update-server | < 0.3.0M2 | 0.3.0M2 |
| hawkbit | = 0.3.0≤ 0.2.5 |
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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free