GHSA-36gq-35j3-p9r9
Vulnerability from github
Published
2025-01-21 20:24
Modified
2025-04-28 14:09
Severity ?
5.9 (Medium) - CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:N/I:N/A:H
Summary
Excessive Platform Resource Consumption within a Loop when unmarshalling Compose file having recursive loop
Details

Impact

The compose-go library component in versions v2.10-v2.4.0 allows an authorized user who sends malicious YAML payloads to cause the compose-go to consume excessive amount of Memory and CPU cycles while parsing YAML, such as used by Docker Compose from versions v2.27.0 to v2.29.7 included

Patches

compose-go v2.24.1 fixed the issue

Workarounds

There isn't any known workaround.

References

  • https://github.com/docker/compose/issues/12235

  • https://github.com/compose-spec/compose-go/pull/703

  • https://github.com/compose-spec/compose-go/pull/618

  • https://github.com/docker/compose/commit/d239f0f3187a2ed5404c61f83bd5e995c81600ff#diff-33ef32bf6c23acb95f5902d7097b7a1d5128ca061167ec0716715b0b9eeaa5f6R10
Show details on source website

To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/compose-spec/compose-go/v2"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.1.0"
            },
            {
              "fixed": "2.4.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2024-10846"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-20",
      "CWE-400"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-01-21T20:24:02Z",
    "nvd_published_at": "2025-01-23T16:15:33Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\nThe `compose-go` library component in versions `v2.10-v2.4.0` allows an authorized user who sends malicious YAML payloads to cause the `compose-go` to consume excessive amount of Memory and CPU cycles while parsing YAML, such as used by Docker Compose from versions ` v2.27.0` to `v2.29.7` included\n\n### Patches\ncompose-go `v2.24.1` fixed the issue\n\n### Workarounds\nThere isn\u0027t any known workaround.\n\n### References\n* https://github.com/docker/compose/issues/12235\n* https://github.com/compose-spec/compose-go/pull/703\n\n* https://github.com/compose-spec/compose-go/pull/618\n* https://github.com/docker/compose/commit/d239f0f3187a2ed5404c61f83bd5e995c81600ff#diff-33ef32bf6c23acb95f5902d7097b7a1d5128ca061167ec0716715b0b9eeaa5f6R10",
  "id": "GHSA-36gq-35j3-p9r9",
  "modified": "2025-04-28T14:09:27Z",
  "published": "2025-01-21T20:24:02Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/compose-spec/compose-go/security/advisories/GHSA-36gq-35j3-p9r9"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-10846"
    },
    {
      "type": "WEB",
      "url": "https://github.com/docker/compose/issues/12235"
    },
    {
      "type": "WEB",
      "url": "https://github.com/compose-spec/compose-go/pull/618"
    },
    {
      "type": "WEB",
      "url": "https://github.com/compose-spec/compose-go/pull/703"
    },
    {
      "type": "WEB",
      "url": "https://github.com/docker/compose/commit/d239f0f3187a2ed5404c61f83bd5e995c81600ff#diff-33ef32bf6c23acb95f5902d7097b7a1d5128ca061167ec0716715b0b9eeaa5f6R10"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/compose-spec/compose-go"
    },
    {
      "type": "WEB",
      "url": "https://security.netapp.com/advisory/ntap-20250425-0008"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Excessive Platform Resource Consumption within a Loop when unmarshalling Compose file having recursive loop"
}


Log in or create an account to share your comment.




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.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • 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.