CVE-2022-3570: Buffer Overflow

Published Oct 21, 2022
·
Updated

Multiple heap buffer overflows in tiffcrop.c utility in libtiff library Version 4.4.0 allows attacker to trigger unsafe or out of bounds memory access via crafted TIFF image file which could result into application crash, potential information disclosure or any other context-dependent impact

Affected Software

4 affected componentsFixes available
debian/tiff<=4.1.0+git191117-2~deb10u4
4.1.0+git191117-2~deb10u84.2.0-1+deb11u44.2.0-1+deb11u54.5.0-6+deb12u14.5.1+git230720-3
LibTIFF libtiff>=3.9.0<=4.4.0
Debian Debian Linux=10.0
Debian Debian Linux=11.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/tiff to a version that resolves this vulnerability.

    Fixed in 4.1.0+git191117-2~deb10u8Fixed in 4.2.0-1+deb11u4Fixed in 4.2.0-1+deb11u5Fixed in 4.5.0-6+deb12u1Fixed in 4.5.1+git230720-3

Event History

Oct 21, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Nov 15, 2022
Data Sourced
via Red Hat·06:19 AM
DescriptionSeverityAffected Software
Jan 30, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2022-3570?

CVE-2022-3570 is a vulnerability in the libtiff library that allows an attacker to trigger heap buffer overflows via a crafted TIFF image file, potentially leading to application crashes or other impacts.

2

How severe is CVE-2022-3570?

CVE-2022-3570 has a severity rating of 5.5, which is considered high.

3

Which versions of the libtiff library are affected?

Versions 4.1.0+git191117-2~deb10u8, 4.2.0-1+deb11u4, 4.5.0-6, and 4.5.1+git230720-1 of the libtiff library are affected.

4

How can I fix CVE-2022-3570?

To fix CVE-2022-3570, update the libtiff library to a version that is not affected, such as 4.1.0+git191117-2~deb10u8, 4.2.0-1+deb11u4, 4.5.0-6, or 4.5.1+git230720-1.

5

Are there any references for CVE-2022-3570?

Yes, you can find references for CVE-2022-3570 at the following URLs: [Reference 1](https://gitlab.com/libtiff/libtiff/-/commit/cfbb883bf6ea7bedcb04177cc4e52d304522fdff), [Reference 2](https://gitlab.com/libtiff/libtiff/-/issues/381), [Reference 3](https://gitlab.com/libtiff/libtiff/-/issues/386).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203