OSV-2020-104
Heap-buffer-overflow in void arrow::util::internal::ByteStreamSlitDecodeSSE2<double>
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21420
Crash type: Heap-buffer-overflow READ 1
Crash state:
void arrow::util::internal::ByteStreamSlitDecodeSSE2<double>
virtual thunk to parquet::ByteStreamSplitDecoder<parquet::PhysicalType<
parquet::TypedDecoder<parquet::PhysicalType<
What each source reports
OSV No score
Heap-buffer-overflow in void arrow::util::internal::ByteStreamSlitDecodeSSE2<double>
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21420
Crash type: Heap-buffer-overflow READ 1
Crash state:
void arrow::util::internal::ByteStreamSlitDecodeSSE2<double>
virtual thunk to parquet::ByteStreamSplitDecoder<parquet::PhysicalType<
parquet::TypedDecoder<parquet::PhysicalType<
- Record
OSV-2020-104- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
arrowOSS-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-104 is a vulnerability with no CVSS score yet in arrow, published June 24, 2020. No source lists public exploit code. A source reports a fix.