OSV-2023-392 Negative-size-param in H5MM_memcpy
Not scored
Published
Check this codebase for OSV-2023-392 and fix it if it is affected.
What it is: OSV-2023-392 is a vulnerability in hdf5, published on 13 May 2023.
Exploitation: There is no known exploitation of OSV-2023-392 in the wild and no public exploit code.
Affected packages and fixed versions:
- hdf5 (OSS-Fuzz): affected all versions; no fix listed
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/OSV-2023-392/ (Markdown: https://insights.sbomify.com/OSV-2023-392/index.md)
A negative size parameter in H5MM_memcpy can cause a crash, leading to denial of service in applications using the HDF5 library.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2023-392?
OSV-2023-392 is a vulnerability in hdf5, published on 13 May 2023.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=58892
Crash type: Negative-size-param
Crash state:
H5MM_memcpy
H5O__link_decode
H5O__msg_iterate_real
Which versions are affected by OSV-2023-392?
1 open source package ship an affected version, including hdf5.
| Package | Affected | Fixed in |
|---|---|---|
hdf5 OSS-Fuzz | All versions | None |
How do I fix OSV-2023-392?
No fix has been published for OSV-2023-392 yet. Limit exposure of the affected software until one is available.
Is OSV-2023-392 being exploited?
There is no known exploitation of OSV-2023-392 in the wild and no public exploit code.