| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in LibTIFF 4.4.0 and classified as critical. This issue affects the function _TIFFmemcpy of the file libtiff/tif_unix.c. This manipulation causes out-of-bounds write.
This vulnerability appears as CVE-2022-3597. The attack may be initiated remotely. There is no available exploit.
To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability has been found in LibTIFF 4.4.0 (Image Processing Software) and classified as critical. Affected by this vulnerability is the function _TIFFmemcpy of the file libtiff/tif_unix.c. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. The CWE definition for the vulnerability is CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
LibTIFF 4.4.0 has an out-of-bounds write in _TIFFmemcpy in libtiff/tif_unix.c:346 when called from extractImageSection, tools/tiffcrop.c:6826, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 236b7191.
The weakness was presented 10/21/2022 as 413. It is possible to read the advisory at gitlab.com. This vulnerability is known as CVE-2022-3597 since 10/19/2022. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability scanner Nessus provides a plugin with the ID 240052 (TencentOS Server 4: libtiff (TSSA-2024:0785)), which helps to determine the existence of the flaw in a target environment.
Applying the patch 236b7191f04c60d09ee836ae13b50f812c841047 is able to eliminate this problem. The bugfix is ready for download at gitlab.com.
The vulnerability is also documented in the vulnerability database at Tenable (240052). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
License
Website
- Product: http://www.libtiff.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.1VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CNA Base Score: 5.5
CNA Vector (GitLab Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Out-of-bounds writeCWE: CWE-787 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 240052
Nessus Name: TencentOS Server 4: libtiff (TSSA-2024:0785)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 236b7191f04c60d09ee836ae13b50f812c841047
Timeline
10/19/2022 🔍10/21/2022 🔍
10/21/2022 🔍
06/17/2025 🔍
Sources
Product: libtiff.orgAdvisory: 413
Status: Confirmed
CVE: CVE-2022-3597 (🔍)
GCVE (CVE): GCVE-0-2022-3597
GCVE (VulDB): GCVE-100-211963
Entry
Created: 10/21/2022 21:10Updated: 06/17/2025 14:15
Changes: 10/21/2022 21:10 (53), 11/19/2022 10:03 (11), 05/08/2025 00:18 (15), 06/17/2025 14:15 (2)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.