Eclipse hawkBit DDI has Privilege Escalation that allows Tenant-Isolated Firmware ExfiltrationGHSA-92r3-p8c2-3fpx
MEDIUMFix: eclipse-hawkbit/hawkbit#3156GHSA-92r3-p8c2-3fpx is a medium-severity (CVSS 4.3) CWE-284 vulnerability in org.eclipse.hawkbit:hawkbit-ddi-resource. A fix is available for org.eclipse.hawkbit:hawkbit-ddi-resource — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-92r3-p8c2-3fpx.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.eclipse.hawkbit:hawkbit-ddi-resourceReal-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
Description
A privilege escalation vulnerability has been identified in the Direct Device Integration (DDI) Controller of Eclipse hawkBit (versions 1.0.3 and prior).
This vulnerability allows an authenticated device to escalate its permissions and bypass the strict boundaries of its assigned updates. Under normal operation, a device should be restricted strictly to the specific firmware artifacts explicitly assigned to it. However, this flaw enables any authenticated device to bypass this restriction and download any firmware artifact within the same tenant.
This is not an authentication bypass; the requesting device must possess valid credentials for its respective tenant. Instead, the issue stems from a flaw in object-level authorization validation.
A related, lower-severity helper issue exists in the listing software modules artifacts metadata endpoint. This endpoint does not enforce assignment checks, enabling an authenticated device to list and enumerate available firmware artifacts, which can facilitate targeted exfiltration using the main download authorization bypass.
Impact
- Severity: Moderate
- Scope: Tenant-isolated. An attacker must be an authenticated device within the target tenant to exploit this vulnerability.
- Confidentiality Impact: Low. While firmware binaries can be retrieved, the impact is mitigated because access is restricted strictly to the scope of the pre-authenticated tenant, and no administrative or cross-tenant data is exposed. Additionally, production firmware binaries are by design not expected to contain highly sensitive or confidential data (such as hardcoded credentials or private keys), further supporting the Low confidentiality rating.
Affected Products and Versions
- Product:
eclipse-hawkbit/hawkbit - Affected Component:
hawkbit-ddi/hawkbit-ddi-resource, as well as the compiled binaries and Docker images that contain this component. - Affected Versions:
1.0.3and prior versions. - Patched Version:
1.0.4
Remediation
Upgrade to version 1.0.4 or later.
Fix details: The download authorization logic has been corrected to ensure that assignment-based verification is executed on every artifact download request. Additionally, the software module metadata endpoint has been updated to enforce proper authorization, restricting access exclusively to software modules and artifacts that are explicitly assigned to or already installed on the requesting device.
Credits
Eclipse would like to thank Santosh Kumar Puppala (GitHub: Santoshkumarpuppala, Email: [email protected]) for discovering and reporting this vulnerability through coordinated disclosure.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.eclipse.hawkbit:hawkbit-ddi-resource | all versions | 1.0.4org.eclipse.hawkbit:hawkbit-ddi-resource:1.0.4 |
Affected Products
hawkbiteclipseDetection & 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-ddi-resource, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.eclipse.hawkbit:hawkbit-ddi-resource to 1.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-92r3-p8c2-3fpx is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is GHSA-92r3-p8c2-3fpx in your dependencies?
Find it across Maven, including transitive dependencies.