ORG.ECLIPSE.HAWKBIT:HAWKBIT-DDI-RESOURCE · GHSA-f3j8-8ggq-f9x2 · Package
FIX → 1.0.4
This advisory is withdrawn as a duplicate of GHSA-92r3-p8c2-3fpx; the original text says that in hawkBit 1.0.3 and earlier, an authenticated device can bypass object-level checks in the DDI controller and download any firmware artifact in its tenant. A related lower-severity flaw lets such a device list artifact metadata without assignment checks.
first public Jul 21, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams that run Eclipse hawkBit as a software update server for devices and use the DDI controller API, where each device has its own tenant credentials. The flaw lets a device that is authenticated in a tenant download firmware meant for other devices in that tenant. Deployments that do not expose DDI to devices, or that run 1.0.4 or later, are not affected by this flaw.
Not affected if fixed-1.0.4-or-later, no-ddi-exposure
Who cares cwe-284, ddi, firmware-update, hawkbit, java, maven
org.eclipse.hawkbit:hawkbit-ddi-resource in your Maven dependencies, for example with mvn dependency:treeUpgrade to 1.0.4
org.eclipse.hawkbit:hawkbit-ddi-resource (affected below )This advisory has been withdrawn because it is a duplicate of GHSA-92r3-p8c2-3fpx. This link is maintained to preserve external references.
In Eclipse hawkBit versions 1.0.3 and prior, a privilege escalation vulnerability (CWE-284 / CWE-862) has been identified in the Direct Device Integration (DDI) Controller.
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.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
1.0.41.0.4GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.