ghsa-9m5p-c77c-f9j7
Vulnerability from github
Published
2025-01-22 18:08
Modified
2025-01-22 18:44
Severity ?
5.3 (Medium) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Summary
DoS in Cilium agent DNS proxy from crafted DNS responses
Details

Impact

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.

Patches

This issue affects:

  • Cilium v1.14 between v1.14.0 and v1.14.17 inclusive
  • Cilium v1.15 between v1.15.0 and v1.15.11 inclusive
  • Cilium v1.16 between v1.16.0 and v1.16.4 inclusive

This issue is fixed in:

  • Cilium v1.14.18
  • Cilium v1.15.12
  • Cilium v1.16.5

Workarounds

There are no known workarounds to this issue.

Acknowledgements

The Cilium community has worked together with members of Isovalent and the Cisco Advanced Security Initiatives Group (ASIG) to prepare these mitigations. Special thanks to @kokelley-cisco for reporting this issue and @bimmlerd for the fix.

For more information

If you have any questions or comments about this advisory, please reach out on Slack.

If you think you have found a vulnerability affecting Cilium, we strongly encourage you to report it to our security mailing list at security@cilium.io. This is a private mailing list for the Cilium security team, and your report will be treated as top priority.

Show details on source website

To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "Go",
            name: "github.com/cilium/cilium",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "1.14.0",
                  },
                  {
                     fixed: "1.14.18",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         package: {
            ecosystem: "Go",
            name: "github.com/cilium/cilium",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "1.15.0",
                  },
                  {
                     fixed: "1.15.12",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         package: {
            ecosystem: "Go",
            name: "github.com/cilium/cilium",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "1.16.0",
                  },
                  {
                     fixed: "1.16.5",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2025-23028",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-770",
      ],
      github_reviewed: true,
      github_reviewed_at: "2025-01-22T18:08:13Z",
      nvd_published_at: "2025-01-22T17:15:13Z",
      severity: "MODERATE",
   },
   details: "### Impact\n\nIn 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.\n\nFor 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.\n\n### Patches\n\nThis issue affects:\n\n- Cilium v1.14 between v1.14.0 and v1.14.17 inclusive\n- Cilium v1.15 between v1.15.0 and v1.15.11 inclusive\n- Cilium v1.16 between v1.16.0 and v1.16.4 inclusive\n\nThis issue is fixed in:\n\n- Cilium v1.14.18\n- Cilium v1.15.12\n- Cilium v1.16.5\n\n### Workarounds\n\nThere are no known workarounds to this issue.\n\n### Acknowledgements\n\nThe Cilium community has worked together with members of Isovalent and the Cisco Advanced Security Initiatives Group (ASIG) to prepare these mitigations. Special thanks to @kokelley-cisco for reporting this issue and @bimmlerd for the fix.\n\n### For more information\n\nIf you have any questions or comments about this advisory, please reach out on [Slack](https://docs.cilium.io/en/latest/community/community/#slack).\n\nIf you think you have found a vulnerability affecting Cilium, we strongly encourage you to report it to our security mailing list at [security@cilium.io](mailto:security@cilium.io). This is a private mailing list for the Cilium security team, and your report will be treated as top priority.",
   id: "GHSA-9m5p-c77c-f9j7",
   modified: "2025-01-22T18:44:35Z",
   published: "2025-01-22T18:08:13Z",
   references: [
      {
         type: "WEB",
         url: "https://github.com/cilium/cilium/security/advisories/GHSA-9m5p-c77c-f9j7",
      },
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2025-23028",
      },
      {
         type: "WEB",
         url: "https://github.com/cilium/cilium/pull/36252",
      },
      {
         type: "WEB",
         url: "https://github.com/cilium/cilium/commit/1971bc684b6b36703ebae0dd7539c623f988a257",
      },
      {
         type: "WEB",
         url: "https://github.com/cilium/cilium/commit/b1948e217a4212b81175d8bf763d0ef350fcc96c",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/cilium/cilium",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
         type: "CVSS_V3",
      },
   ],
   summary: "DoS in Cilium agent DNS proxy from crafted DNS responses",
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.