Advisory

GHSA-36gq-35j3-p9r9

Also known as: CVE-2024-10846, GO-2025-3412

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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2025-01-21 20:24 UTC
Modified
2025-04-28 14:09 UTC

Affected packages and fixes

github.com/compose-spec/compose-go/v2

Go · All systems

Affected

  • introduced 2.1.0, fixed 2.4.1 (semver)

Fixed versions

2.4.1

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences