Duplicate Advisory: Privilege Escalation in Eclipse hawkBit DDI allows Tenant-Isolated Firmware Exfiltration

Severity: medium · CVSS 4.3 · Published 2026-07-21

### Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-92r3-p8c2-3fpx. This link is maintained to preserve external references.

### Original Description 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.

Vendors: Maven.

Quick answers

Is This vulnerability exploited in the wild?
No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?
Medium severity, with a CVSS score of 4.3, published 21 July 2026.
Which products and versions are affected?
org.eclipse.hawkbit:hawkbit-ddi-resource (Maven) < 1.0.4, ECOSYSTEM:introduced=0,fixed=1.0.4.
Is there a fix for This vulnerability?
Yes. org.eclipse.hawkbit:hawkbit-ddi-resource (Maven): upgrade to 1.0.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected?
Check whether you run org.eclipse.hawkbit:hawkbit-ddi-resource (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.eclipse.hawkbit:hawkbit-ddi-resource (Maven): upgrade to 1.0.4 or later
    # set org.eclipse.hawkbit:hawkbit-ddi-resource to 1.0.4 in your pom.xml or build.gradle

Affected products

  • org.eclipse.hawkbit:hawkbit-ddi-resource (Maven) < 1.0.4, ECOSYSTEM:introduced=0,fixed=1.0.4

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.