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