OSV-2018-104
Heap-buffer-overflow in git__strntol64
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11382
Crash type: Heap-buffer-overflow READ 1
Crash state:
git__strntol64
git__strntol32
parse_mode
What each source reports
OSV No score
Heap-buffer-overflow in git__strntol64
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11382
Crash type: Heap-buffer-overflow READ 1
Crash state:
git__strntol64
git__strntol32
parse_mode
- Record
OSV-2018-104- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
libgit2OSS-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-2018-104 is a vulnerability with no CVSS score yet in libgit2, published January 13, 2021. No source lists public exploit code. A source reports a fix.