GHSA-jwqm-c9f2-2cq3 Cleartext Transmission of Sensitive Information, Inclusion of Functionality from Untrusted Control Sphere , and Download of Code Without Integrity Check in Eclipse hawkBit

• Maven org.eclipse.hawkbit:hawkbit-autoconfigure: < 0.3.0M2 → fixed in 0.3.0M2 • Maven org.eclipse.hawkbit:hawkbit-ui: < 0.3.0M2 → fixed in 0.3.0M2 • Maven org.eclipse.hawkbit:hawkbit-parent: < 0.3.0M2 → fixed in 0.3.0M2 • Maven org.eclipse.hawkbit:hawkbit-starters: < 0.3.0M2 → fixed in 0.3.0M2 • Maven org.eclipse.hawkbit:hawkbit-boot-starter: < 0.3.0M2 → fixed in 0.3.0M2 • Maven org.eclipse.hawkbit:hawkbit-update-server: < 0.3.0M2 → fixed in 0.3.0M2 • Maven org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-ui: < 0.3.0M2 → fixed in 0.3.0M2 • Maven org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-api: < 0.3.0M2 → fixed in 0.3.0M2 • Maven org.eclipse.hawkbit:hawkbit-boot-starter-dmf-api: < 0.3.0M2 → fixed in 0.3.0M2 • Maven org.eclipse.hawkbit:hawkbit-boot-starter-ddi-api: < 0.3.0M2 → fixed in 0.3.0M2

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.