Skip to content

Excessive Platform Resource Consumption within a Loop when unmarshalling Compose file having recursive loop

Moderate severity GitHub Reviewed Published Jan 21, 2025 in compose-spec/compose-go

Package

gomod github.com/compose-spec/compose-go/v2 (Go)

Affected versions

>= 2.1.0, < 2.4.1

Patched versions

2.4.1

Description

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

References

@glours glours published to compose-spec/compose-go Jan 21, 2025
Published to the GitHub Advisory Database Jan 21, 2025
Reviewed Jan 21, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:N/I:N/A:H

Weaknesses

CVE ID

CVE-2024-10846

GHSA ID

GHSA-36gq-35j3-p9r9

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.