Bug 2170763 (CVE-2023-20032) - CVE-2023-20032 clamav: HFS+ Partition Scanning Buffer Overflow Vulnerability
Summary: CVE-2023-20032 clamav: HFS+ Partition Scanning Buffer Overflow Vulnerability
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2023-20032
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2170765 2170767
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-17 08:23 UTC by TEJ RATHI
Modified: 2023-02-17 15:00 UTC (History)
2 users (show)

Fixed In Version: clamav 0.103.8, clamav 0.105.2, clamav 1.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-02-17 13:45:31 UTC
Embargoed:

Attachments (Terms of Use)

Description TEJ RATHI 2023-02-17 08:23:58 UTC 
CVE-2023-20032: Ppossible remote code execution vulnerability in the HFS+ file parser. 

The issue affects versions 1.0.0 and earlier, 0.105.1 and earlier, and 0.103.7 and earlier. 

This vulnerability is due to a missing buffer size check that may result in a heap buffer overflow write. An attacker could exploit this vulnerability by submitting a crafted HFS+ partition file to be scanned by ClamAV on an affected device. A successful exploit could allow the attacker to execute arbitrary code with the privileges of the ClamAV scanning process, or else crash the process, resulting in a denial of service (DoS) condition.

https://blog.clamav.net/2023/02/clamav-01038-01052-and-101-patch.html
Comment 1 TEJ RATHI 2023-02-17 08:24:30 UTC 
Created clamav tracking bugs for this issue:

Affects: epel-all [bug 2170767]
Affects: fedora-all [bug 2170765]
Comment 2 Product Security DevOps Team 2023-02-17 13:45:30 UTC 
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.
Note You need to log in before you can comment on or make changes to this bug.