CVE-2024-47825 Affecting cilium-fips-1.14 package, versions <1.14.16-r0


Severity

Recommended
0.0
high
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.09% (41st 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 IDSNYK-CHAINGUARDLATEST-CILIUMFIPS114-8346767
  • published6 Nov 2024
  • disclosed21 Oct 2024

Introduced: 21 Oct 2024

CVE-2024-47825  (opens in a new tab)

How to fix?

Upgrade Chainguard cilium-fips-1.14 to version 1.14.16-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream cilium-fips-1.14 package and not the cilium-fips-1.14 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. Starting in version 1.14.0 and prior to versions 1.14.16 and 1.15.10, a policy rule denying a prefix that is broader than /32 may be ignored if there is a policy rule referencing a more narrow prefix (CIDRSet or toFQDN) and this narrower policy rule specifies either enableDefaultDeny: false or - toEntities: all. Note that a rule specifying toEntities: world or toEntities: 0.0.0.0/0 is insufficient, it must be to entity all.This issue has been patched in Cilium v1.14.16 and v1.15.10. As this issue only affects policies using enableDefaultDeny: false or that set toEntities to all, some workarounds are available. For users with policies using enableDefaultDeny: false, remove this configuration option and explicitly define any allow rules required. For users with egress policies that explicitly specify toEntities: all, use toEntities: world.

CVSS Scores

version 3.1