Skip to content

Denial of service via HAMT Decoding Bug #421

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
scacaca opened this issue Feb 28, 2025 · 0 comments
Open

Denial of service via HAMT Decoding Bug #421

scacaca opened this issue Feb 28, 2025 · 0 comments
Labels
need/triage Needs initial labeling and prioritization

Comments

@scacaca
Copy link

scacaca commented Feb 28, 2025

Summary

Trying to read malformed HAMT sharded directories can cause memory leaks.

Description

If you are reading untrusted user input, an attacker can then trigger a memory leaks. Because there is no size limit for the child nodes of the HAMT bucket here.
there is a similar vulnerablity
The fix can be something like this.
In js-hamt-sharding,. there is similarly no corresponding logic for size limits on child nodes

@scacaca scacaca added the need/triage Needs initial labeling and prioritization label Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/triage Needs initial labeling and prioritization
Projects
None yet
Development

No branches or pull requests

1 participant