CVE-2019-10240GHSA-JWQM-C9F2-2CQ3
Eclipse hawkBit versions prior to 0.3.0M2 resolved Maven build artifacts for the Vaadin based UI over HTTP instead of HTTPS.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.3.0M2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- The Eclipse Foundation Eclipse hawkBit
fixed in 0.3.0M2
- org.eclipse.hawkbit:hawkbit-autoconfigureMaven
fixed in 0.3.0M2
- org.eclipse.hawkbit:hawkbit-uiMaven
fixed in 0.3.0M2
- org.eclipse.hawkbit:hawkbit-parentMaven
fixed in 0.3.0M2
- org.eclipse.hawkbit:hawkbit-startersMaven
fixed in 0.3.0M2
- org.eclipse.hawkbit:hawkbit-boot-starterMaven
fixed in 0.3.0M2
- org.eclipse.hawkbit:hawkbit-update-serverMaven
fixed in 0.3.0M2
- org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-uiMaven
fixed in 0.3.0M2
- org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-apiMaven
fixed in 0.3.0M2
- org.eclipse.hawkbit:hawkbit-boot-starter-dmf-apiMaven
fixed in 0.3.0M2
- org.eclipse.hawkbit:hawkbit-boot-starter-ddi-apiMaven
fixed in 0.3.0M2