# CVE-2025-2310: HDF5 Metadata Attribute Decoder H5MM_strndup heap-based overflow

> A heap-based buffer overflow in the HDF5 library's metadata decoder allows local attackers to execute arbitrary code or cause denial of service.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Mar 2025
- **Updated:** 8 May 2025
- **Also known as:** AZL-58806, AZL-58825, DEBIAN-CVE-2025-2310, ECHO-ccd1-8584-5447, GHSA-qxwf-xj2v-qm83, JLSEC-2026-328, UBUNTU-CVE-2025-2310

## What is CVE-2025-2310?

CVE-2025-2310 is a medium-severity memory corruption vulnerability in Hdfgroup Hdf5, published on 14 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in HDF5 1.14.6 and classified as critical. This issue affects the function H5MM_strndup of the component Metadata Attribute Decoder. The manipulation leads to heap-based buffer overflow. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. The vendor plans to fix this issue in an upcoming release.

Weakness: CWE-122 (Heap-based Buffer Overflow), CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-2310?

It affects 1 product.


Products: Hdfgroup Hdf5.

## How do I fix CVE-2025-2310?

No fix published yet.

## Is CVE-2025-2310 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2310 exists.

## Other vulnerabilities in Hdfgroup Hdf5

- [CVE-2024-32608](https://insights.sbomify.com/CVE-2024-32608/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-29157](https://insights.sbomify.com/CVE-2024-29157/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-29159](https://insights.sbomify.com/CVE-2024-29159/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-29164](https://insights.sbomify.com/CVE-2024-29164/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-32611](https://insights.sbomify.com/CVE-2024-32611/): Other in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2310 and fix it if it is affected.

What it is: CVE-2025-2310 is a medium-severity memory corruption vulnerability in Hdfgroup Hdf5, published on 14 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2310 exists.

Affected product: Hdfgroup Hdf5. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2025-2310/ (Markdown: https://insights.sbomify.com/CVE-2025-2310/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-2310
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-2310
- OSV: https://osv.dev/vulnerability/CVE-2025-2310

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-2310/
Summaries are generated and may contain mistakes; the official description above is the record.