Bug 2251319

Summary: libtiff: OOM in TIFFReadFromUserBuffer
Product: [Other] Security Response Reporter: Rohit Keshri <rkeshri>
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: bdettelb, caswilli, hhorak, hkataria, jsherril, kaycoth, kshier
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
An out-of-memory problem was found in libtiff that could be triggered by passing a craft tiff file to TIFFReadFromUserBuffer() API. In this flaw a remote attacker could utilize this bug to perform arbitrary size allocation and cause deny-of-services.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2024-03-04 07:46:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2251321, 2251322, 2251323, 2251324    
Bug Blocks: 2251312    

Description Rohit Keshri 2023-11-24 09:38:07 UTC 
An out-of-memory problem was found in libtiff that could be triggered by passing a craft tiff file to TIFFReadFromUserBuffer() API. In this flaw a remote attacker could could utilize this bug to perform arbitrary size allocation and cause deny-of-services.

Reference:
https://gitlab.com/libtiff/libtiff/-/issues/619

Fixed at:
https://gitlab.com/libtiff/libtiff/-/merge_requests/553
Comment 2 Rohit Keshri 2023-11-24 09:43:04 UTC 
Created iv tracking bugs for this issue:

Affects: fedora-all [bug 2251323]


Created libtiff tracking bugs for this issue:

Affects: fedora-all [bug 2251321]


Created mingw-libtiff tracking bugs for this issue:

Affects: fedora-all [bug 2251322]


Created tkimg tracking bugs for this issue:

Affects: fedora-all [bug 2251324]
Comment 8 Dhananjay Arunesh 2024-03-04 07:46:50 UTC 

*** This bug has been marked as a duplicate of bug 2251311 ***