Bug 1903232 (CVE-2020-29367) - CVE-2020-29367 blosc: heap-based buffer overflow when there is a lack of space to write compressed data
Summary: CVE-2020-29367 blosc: heap-based buffer overflow when there is a lack of spac...
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2020-29367
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1903233 1903234 1903235 1903871 1903872
Blocks: 1903237
TreeView+ depends on / blocked
 
Reported: 2020-12-01 16:53 UTC by Guilherme de Almeida Suckevicz
Modified: 2021-06-07 17:04 UTC (History)
23 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-02-09 22:09:41 UTC
Embargoed:

Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2020-12-01 16:53:51 UTC 
blosc2.c in Blosc C-Blosc2 through 2.0.0.beta.5 has a heap-based buffer overflow when there is a lack of space to write compressed data.

Reference:
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26442

Upstream patch:
https://github.com/Blosc/c-blosc2/commit/c4c6470e88210afc95262c8b9fcc27e30ca043ee
Comment 1 Guilherme de Almeida Suckevicz 2020-12-01 16:54:17 UTC 
Created blosc tracking bugs for this issue:

Affects: epel-all [bug 1903234]
Affects: fedora-all [bug 1903233]
Affects: openstack-rdo [bug 1903235]
Comment 5 Summer Long 2021-02-09 05:36:06 UTC 
Statement:

OpenShift Container Platform (OCP) 4 temporarily shipped one version of the blosc package in OCP 4.3.0. Updates to the blosc package, which is used in the ironic-hardware-inventory-recorder-image container are consumed from OpenStack Platform 16 repositories.

In Red Hat OpenStack Platform, because the flaw has a lower impact and the fix would require a substantial amount of development, no update will be provided at this time for the RHOSP blosc package.
Comment 6 Product Security DevOps Team 2021-02-09 22:09:41 UTC 
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2020-29367
Note You need to log in before you can comment on or make changes to this bug.