Is CVE-2016-5321 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2016-5321 being exploited in the wild.

How severe is CVE-2016-5321?

Medium severity, with a CVSS score of 6.5, published 20 January 2017.

Which products and versions are affected?

LibTIFF libtiff 4.0.6 and earlier.

Is there a fix for CVE-2016-5321?

A patch was published on 2017-01-09: Gentoo and Debian released updates addressing the issue in libtiff 4.0.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2016-5321 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2016-5321?

Check whether you run Libtiff or Opensuse. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2016-5321: LibTIFF denial of service in DumpModeDecode

CVE-2016-5321 · Severity: medium · CVSS 6.5 · Published 2017-01-20

A vulnerability exists in libtiff, a widely used library for processing TIFF image files. An attacker can provide a specially crafted image that, when opened by an application using this library, causes the application to crash. This results in a denial of service, potentially disrupting business operations or software that relies on image processing.

Technologies: Libtiff, Opensuse. Vendors: Libtiff, Opensuse.

Quick answers

Is CVE-2016-5321 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-5321 being exploited in the wild.
How severe is CVE-2016-5321?: Medium severity, with a CVSS score of 6.5, published 20 January 2017.
Which products and versions are affected?: LibTIFF libtiff 4.0.6 and earlier.
Is there a fix for CVE-2016-5321?: A patch was published on 2017-01-09: Gentoo and Debian released updates addressing the issue in libtiff 4.0.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2016-5321 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2016-5321?: Check whether you run Libtiff or Opensuse. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A memory corruption vulnerability exists in libtiff versions 4.0.6 and earlier within the DumpModeDecode function. The flaw is categorized as an improper restriction of operations within the bounds of a memory buffer (CWE-119), leading to an invalid memory read. An unauthenticated remote attacker can exploit this by enticing a user or automated system to process a maliciously crafted TIFF image. Successful exploitation results in an application crash (denial of service). The issue is addressed in libtiff version 4.0.7.

Affected products

LibTIFF libtiff 4.0.6 and earlier

Timeline

2017-01-09: patched: Gentoo and Debian released updates addressing the issue in libtiff 4.0.7.
2017-01-20: disclosed: NVD publication date.

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.