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.
eclipse-hawkbit/hawkbithawkbit-ddi/hawkbit-ddi-resource, as well as the compiled binaries and Docker images that contain this component.1.0.3 and prior versions.1.0.4Upgrade 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.
Eclipse would like to thank Santosh Kumar Puppala (GitHub: Santoshkumarpuppala, Email: santhoshkumar7794@gmail.com) for discovering and reporting this vulnerability through coordinated disclosure.
{
"cwe_ids": [
"CWE-284",
"CWE-862"
],
"github_reviewed": true,
"github_reviewed_at": "2026-11-06T18:09:45Z",
"nvd_published_at": null,
"severity": "MODERATE"
}