Skip to content
Fencer Intel
medium —

GHSA-9cc5-2pq7-hfj8 json

xmas-elf potential out-of-bounds read with a malformed ELF file and the HashTable API.

published last yr. modified 2mo ago also RUSTSEC-2025-0018

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

Affected versions of this crate only validated the `index` argument of `HashTable::get_bucket` and `HashTable::get_chain` against the input-controlled `bucket_count` and `chain_count` fields, but not against the size of the ELF section. As a result, a malformed ELF file could trigger out-of-bounds reads in a consumer of the HashTable API by setting these fields to inappropriately large values that would fall outside the relevant hash table section, and by introducing correspondingly out-of-bounds hash table indexes elsewhere in the ELF file.

Patch / fix

  • crates.io xmas-elf 0.10, 0.10.0

Is GHSA-9cc5-2pq7-hfj8 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io xmas-elf
<0.10
>=0.0.0-0, <0.10.0
0.10
0.10.0

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.