OSV-2020-958
Heap-buffer-overflow in hts_log
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18152
Crash type: Heap-buffer-overflow READ {*}
Crash state:
hts_log
bam_read1
sam_read1
What each source reports
OSV No score
Heap-buffer-overflow in hts_log
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18152
Crash type: Heap-buffer-overflow READ {*}
Crash state:
hts_log
bam_read1
sam_read1
- Record
OSV-2020-958- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
htslibOSS-Fuzz |
Commit ranges | Not evaluated |
Not evaluated means the source gave git commits or a range we can't read, so we can't tell which releases are affected. A fixed version beside it is the source’s own claim.
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
OSV-2020-958 is a vulnerability with no CVSS score yet in htslib, published July 22, 2020. No source lists public exploit code. A source reports a fix.