# GHSA-9cc5-2pq7-hfj8: Potential out-of-bounds read with a malformed ELF file and the HashTable API.

> A malformed ELF file can cause out-of-bounds reads in the xmas-elf library, potentially leading to information disclosure or crashes.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Mar 2025
- **Also known as:** RUSTSEC-2025-0018

## What is GHSA-9cc5-2pq7-hfj8?

GHSA-9cc5-2pq7-hfj8 is a memory corruption vulnerability in xmas-elf, published on 26 Mar 2025. 

### Official description

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.

## Which versions are affected by GHSA-9cc5-2pq7-hfj8?

3 open source packages ship an affected version, including xmas-elf.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `xmas-elf` | crates.io | All versions | 0.10 |
| `xmas-elf` | crates.io | All versions | 0.10 |
| `xmas-elf` | crates.io | From 0.0.0-0 | 0.10.0 |

## How do I fix GHSA-9cc5-2pq7-hfj8?

Upgrade xmas-elf to a fixed version for your release line: 0.10 or 0.10.0.

## Is GHSA-9cc5-2pq7-hfj8 being exploited?

There is no known exploitation of GHSA-9cc5-2pq7-hfj8 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-9cc5-2pq7-hfj8 and fix it if it is affected.

What it is: GHSA-9cc5-2pq7-hfj8 is a memory corruption vulnerability in xmas-elf, published on 26 Mar 2025. 
Exploitation: There is no known exploitation of GHSA-9cc5-2pq7-hfj8 in the wild and no public exploit code.

Affected packages and fixed versions:
- xmas-elf (crates.io): affected all versions; fixed in 0.10
- xmas-elf (crates.io): affected all versions; fixed in 0.10
- xmas-elf (crates.io): affected from 0.0.0-0; fixed in 0.10.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-9cc5-2pq7-hfj8/ (Markdown: https://insights.sbomify.com/GHSA-9cc5-2pq7-hfj8/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-9cc5-2pq7-hfj8

---
From sbomify Insights: https://insights.sbomify.com/GHSA-9cc5-2pq7-hfj8/
Summaries are generated and may contain mistakes; the official description above is the record.