Bug 2235265 (CVE-2023-40745) - CVE-2023-40745 libtiff: integer overflow in tiffcp.c
Summary: CVE-2023-40745 libtiff: integer overflow in tiffcp.c
Keywords:
Status: NEW
Alias: CVE-2023-40745
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
: 2224974 (view as bug list)
Depends On: 2237199 2237200 2237195 2237196 2237197 2237198
Blocks: 2222912
TreeView+ depends on / blocked
 
Reported: 2023-08-28 08:46 UTC by Dhananjay Arunesh
Modified: 2024-04-30 10:01 UTC (History)
11 users (show)

Fixed In Version: libtiff 4.6.0
Doc Type: If docs needed, set a value
Doc Text:
LibTIFF is vulnerable to an integer overflow. This flaw allows remote attackers to cause a denial of service (application crash) or possibly execute an arbitrary code via a crafted tiff image, which triggers a heap-based buffer overflow.
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2024:2289 0 None None None 2024-04-30 10:01:40 UTC

Description Dhananjay Arunesh 2023-08-28 08:46:51 UTC
Multiple potential integer overflow in tiffcp.c in libtiff <= 4.5.1 can allow remote attackers to cause a denial of service (application crash) or possibly execute an arbitrary code via a crafted tiff image which triggers a heap-based buffer overflow.

Comment 2 Dhananjay Arunesh 2023-08-28 08:55:23 UTC
*** Bug 2224974 has been marked as a duplicate of this bug. ***

Comment 10 Dhananjay Arunesh 2023-09-04 05:49:15 UTC
Created libtiff tracking bugs for this issue:

Affects: fedora-all [bug 2237199]


Created mingw-libtiff tracking bugs for this issue:

Affects: fedora-all [bug 2237200]

Comment 11 errata-xmlrpc 2024-04-30 10:01:39 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2024:2289 https://access.redhat.com/errata/RHSA-2024:2289


Note You need to log in before you can comment on or make changes to this bug.