Allocation of Resources Without Limits or Throttling Affecting hubble-ui package, versions <0.13.1-r10


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.04% (12th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CHAINGUARDLATEST-HUBBLEUI-8660812
  • published24 Jan 2025
  • disclosed22 Jan 2025

Introduced: 22 Jan 2025

NewCVE-2025-23028  (opens in a new tab)
CWE-770  (opens in a new tab)

How to fix?

Upgrade Chainguard hubble-ui to version 0.13.1-r10 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream hubble-ui package and not the hubble-ui package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

Cilium is a networking, observability, and security solution with an eBPF-based dataplane. A denial of service vulnerability affects versions 1.14.0 through 1.14.7, 1.15.0 through 1.15.11, and 1.16.0 through 1.16.4. In a Kubernetes cluster where Cilium is configured to proxy DNS traffic, an attacker can crash Cilium agents by sending a crafted DNS response to workloads from outside the cluster. For traffic that is allowed but without using DNS-based policy, the dataplane will continue to pass traffic as configured at the time of the DoS. For workloads that have DNS-based policy configured, existing connections may continue to operate, and new connections made without relying on DNS resolution may continue to be established, but new connections which rely on DNS resolution may be disrupted. Any configuration changes that affect the impacted agent may not be applied until the agent is able to restart. This issue is fixed in Cilium v1.14.18, v1.15.12, and v1.16.5. No known workarounds are available.