GHSA-jwqm-c9f2-2cq3
HIGHGHSA-jwqm-c9f2-2cq3 is a high-severity (CVSS 8.1) CWE-494 vulnerability in org.eclipse.hawkbit:hawkbit-autoconfigure. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-jwqm-c9f2-2cq3 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Cleartext Transmission of Sensitive Information, Inclusion of Functionality from Untrusted Control Sphere , and Download of Code Without Integrity Check in Eclipse hawkBit
Real-World Exposure
org.eclipse.hawkbit:hawkbit-autoconfigure☕org.eclipse.hawkbit:hawkbit-ui☕org.eclipse.hawkbit:hawkbit-parent☕org.eclipse.hawkbit:hawkbit-starters☕org.eclipse.hawkbit:hawkbit-boot-starter☕org.eclipse.hawkbit:hawkbit-update-server☕org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-ui☕org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-api+2 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.eclipse.hawkbit:hawkbit-autoconfigure | all versions | 0.3.0M2 |
| ☕Maven | org.eclipse.hawkbit:hawkbit-ui | all versions | 0.3.0M2 |
| ☕Maven | org.eclipse.hawkbit:hawkbit-parent | all versions | 0.3.0M2 |
| ☕Maven | org.eclipse.hawkbit:hawkbit-starters | all versions | 0.3.0M2 |
| ☕Maven | org.eclipse.hawkbit:hawkbit-boot-starter | all versions | 0.3.0M2 |
| ☕Maven | org.eclipse.hawkbit:hawkbit-update-server | all versions | 0.3.0M2 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.hawkbit:hawkbit-autoconfigure. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.eclipse.hawkbit:hawkbit-autoconfigure to 0.3.0M2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jwqm-c9f2-2cq3 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-jwqm-c9f2-2cq3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-jwqm-c9f2-2cq3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-jwqm-c9f2-2cq3 in your dependencies?
O3 detects GHSA-jwqm-c9f2-2cq3 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.