dbcve.org
CiliumApplication

CVE-2022-29178

HIGH · 8.2 CVSS v3.1 Published 2022-05-20
Fix available
A fix is available. Upgrade to 1.9.16 / 1.10.11 or later.
See remediation →
84/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cilium is open source software for providing and securing network connectivity and loadbalancing between application workloads. Cilium prior to versions 1.9.16, 1.10.11, and 1.11.15 contains an incorrect default permissions vulnerability. Operating Systems with users belonging to the group ID 1000 can access the API of Cilium via Unix domain socket available on the host where Cilium is running. This could allow malicious users to compromise integrity as well as system availability on that host. The problem has been fixed and the patch is available in versions 1.9.16, 1.10.11, and 1.11.5. A potential workaround is to modify Cilium's DaemonSet to run with a certain command, which can be found in the GitHub Security Advisory for this vulnerability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cilium prior to versions 1.9.16, 1.10.11, and 1.11.5 contains incorrect default permissions on its Unix domain socket, allowing users belonging to group ID 1000 to access the Cilium API. This unauthorized API access enables malicious users to compromise system integrity and availability on the host.

MitigationUpgrade Cilium to versions 1.9.16, 1.10.11, or 1.11.5 or later, or apply the DaemonSet workaround documented in the GitHub Security Advisory to restrict socket access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CiliumApplication
Affected:< 1.9.16>= 1.10.0, < 1.10.11>= 1.11.0, < 1.11.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Cilium version
    Run 'cilium version' or check the container/daemon image version to obtain the exact version number
    Affected if The version is less than 1.9.16, or is 1.10.x below 1.10.11, or is 1.11.x below 1.11.5
  2. Identify the Cilium Unix domain socket
    Locate the Cilium socket file by examining the Cilium DaemonSet configuration or running 'find /var/run -name *cilium* -type s 2>/dev/null' in the container
    Affected if A Unix domain socket exists in the Cilium runtime environment and is accessible
  3. Inspect socket file permissions
    Run 'ls -la' on the identified socket file to view owner, group, and permission bits
    Affected if The socket grants read or write access to the group (g+r or g+rw), allowing group members to communicate with the Cilium API daemon
  4. Verify if group ID 1000 exists
    Check if group 1000 is defined on the host or in the container by running 'getent group 1000' or 'grep 1000 /etc/group'
    Affected if Group ID 1000 is present on the system and the socket permissions allow group access, creating the unauthorized access condition

A system is affected if it runs a vulnerable Cilium version (below 1.9.16, 1.10.x below 1.10.11, or 1.11.x below 1.11.5) AND the Cilium Unix domain socket grants group permissions that include group ID 1000.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.9.16 / 1.10.11 / 1.11.5 or later
Fixed in 1.9.161.10.111.11.5
Interim mitigation

Upgrade Cilium to versions 1.9.16, 1.10.11, or 1.11.5 or later, or apply the DaemonSet workaround documented in the GitHub Security Advisory to restrict socket access.

Recommended fix High confidence

Cilium 1.9.16, 1.10.11, or 1.11.5 (or later stable releases)

  1. Upgrade to Cilium version 1.9.16 or later if running a 1.9.x release
  2. Upgrade to Cilium version 1.10.11 or later if running a 1.10.x release
  3. Upgrade to Cilium version 1.11.5 or later if running a 1.11.x release
  4. After upgrade, verify that the Unix domain socket permissions have been corrected and users in group 1000 can no longer access the Cilium API

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cilium Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-29178 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-29178 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data