Skip to content

Denial of service via HAMT Decoding Panics

Moderate severity GitHub Reviewed Published Feb 9, 2023 in ipfs/go-unixfs • Updated May 20, 2024

Package

gomod github.com/ipfs/go-unixfs (Go)

Affected versions

< 0.4.3

Patched versions

0.4.3

Description

Impact

Trying to read malformed HAMT sharded directories can cause panics and virtual memory leaks.
If you are reading untrusted user input, an attacker can then trigger a panic.

This is caused by bogus fanout parameter in the HAMT directory nodes.
This include checks returned in ipfs/go-bitfield GHSA-2h6c-j3gf-xp9r, as well as limiting the fanout to <= 1024 (to avoid attempts of arbitrary sized allocations).

Patches

Workarounds

Do not feed untrusted user data to the decoding functions.

References

References

@Jorropo Jorropo published to ipfs/go-unixfs Feb 9, 2023
Published by the National Vulnerability Database Feb 9, 2023
Published to the GitHub Advisory Database Feb 10, 2023
Reviewed Feb 10, 2023
Last updated May 20, 2024

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
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
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:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.101%
(43rd percentile)

Weaknesses

CVE ID

CVE-2023-23625

GHSA ID

GHSA-q264-w97q-q778

Source code

Credits

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