Libtiff Vulnerabilities

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Last Year

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Version

4.0.645
4.0.344
4.0.140
4.0.238
4.0.733

Grouping all affected versions of a specific product helps to determine existing issues. This makes it possible to determine vendors and products which need attention when it comes to remediations.

Remediation

Official Fix187
Temporary Fix0
Workaround0
Unavailable2
Not Defined39

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability

High1
Functional0
Proof-of-Concept33
Unproven5
Not Defined189

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector

Not Defined0
Physical0
Local28
Adjacent3
Network197

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication

Not Defined0
High0
Low12
None216

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction

Not Defined0
Required94
None134

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Last Year

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base

≤10
≤20
≤30
≤44
≤519
≤663
≤749
≤859
≤98
≤1026

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp

≤10
≤20
≤30
≤45
≤523
≤666
≤763
≤841
≤98
≤1022

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB

≤10
≤20
≤30
≤48
≤539
≤652
≤737
≤861
≤91
≤1030

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD

≤10
≤20
≤30
≤40
≤50
≤620
≤755
≤837
≤924
≤1014

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

CNA

≤10
≤20
≤30
≤40
≤51
≤619
≤71
≤82
≤91
≤100

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day

<1k66
<2k40
<5k121
<10k0
<25k0
<50k1
<100k0
≥100k0

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today

<1k212
<2k11
<5k5
<10k0
<25k0
<50k0
<100k0
≥100k0

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Last Year

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Versions (45): 3.0, 3.1, 3.4, 3.5.1, 3.5.2, 3.5.3, 3.5.4, 3.5.5, 3.5.6, 3.5.7, 3.6, 3.6.1, 3.7, 3.7.1, 3.7.2, 3.7.3, 3.7.4, 3.8, 3.8.1, 3.8.2, 3.9, 3.9.1, 3.9.2, 3.9.2-5.2.1, 3.9.3, 3.9.4, 3.9.5, 4, 4.0, 4.0.1, 4.0.2, 4.0.3, 4.0.3-35.amzn2.0.1, 4.0.4, 4.0.5, 4.0.6, 4.0.7, 4.0.8, 4.0.9, 4.1, 4.2, 4.3, 4.4, 4.4.0rc1, libtiff5.tif

Link to Product Website: http://www.libtiff.org/

Software Type: Image Processing Software

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
11/13/20226.35.7LibTIFF tif_getimage.c TIFFReadRGBATileExt integer overflow$0-$5k$0-$5kProof-of-ConceptOfficial Fix0.94CVE-2022-3970
10/21/20228.38.2LibTIFF TIFF File tiffcrop.c out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-3570
10/21/20225.45.4LibTIFF TIFF File tif_unix.c _TIFFmemcpy out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2022-3627
10/21/20226.16.0LibTIFF TIFF File tif_unix.c _TIFFmemset out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-3626
10/21/20225.45.4LibTIFF TIFF File tiffcrop.c writeSingleSection out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.08CVE-2022-3599
10/21/20226.16.0LibTIFF TIFF File tiffcrop.c extractContigSamplesShifted24bits out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-3598
10/21/20226.16.0LibTIFF tif_unix.c _TIFFmemcpy out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.21CVE-2022-3597
09/01/20226.46.2libtiff tiffcrop.c rotateImage buffer size$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2022-2520
09/01/20226.46.2libtiff tiffcrop.c rotateImage double free$0-$5k$0-$5kNot DefinedOfficial Fix0.07CVE-2022-2519
08/31/20225.45.3libtiff tif_close.c TIFFClose release of reference$0-$5k$0-$5kNot DefinedOfficial Fix0.06CVE-2022-2521
08/29/20224.94.8LibTIFF TIFF File tiffcrop.c extractImageSection out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-2953
08/18/20227.57.4LibTIFF tiffcrop extractContigSamples8bits out-of-bounds write$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2022-2869
08/18/20226.26.1LibTIFF tiffcrop out-of-bounds$0-$5k$0-$5kNot DefinedNot Defined0.03CVE-2022-2868
08/18/20227.57.5LibTIFF tiffcrop out-of-bounds write$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2022-2867
07/20/20224.94.9LibTIFF TIFF File tif_dirread.c TIFFFetchStripThing uninitialized resource$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2022-34266
07/01/20225.45.4LibTIFF tiffcrop divide by zero$0-$5k$0-$5kNot DefinedOfficial Fix0.57CVE-2022-2058
07/01/20225.45.4LibTIFF tiffcrop divide by zero$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-2057
07/01/20225.45.4LibTIFF tiffcrop divide by zero$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-2056
05/11/20224.94.8LibTIFF tif_lzw.c LZWDecode out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-1623
05/11/20224.94.8LibTIFF TIFF File tif_lzw.c LZWDecode out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2022-1622
04/03/20224.34.2LibTIFF tiff2ps resource consumption$0-$5k$0-$5kProof-of-ConceptNot Defined0.02CVE-2022-1210
03/28/20224.94.8LibTIFF TIFF File out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2022-1056
03/11/20226.05.9LibTIFF TIFF File tif_dirread.c TIFFFetchNormalTag null pointer dereference$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-0908
03/11/20224.94.8LibTIFF tiff out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-0924
03/11/20224.94.8LibTIFF tiffcrop divide by zero$0-$5k$0-$5kNot DefinedOfficial Fix0.07CVE-2022-0909

203 more entries are not shown

Do you want to use VulDB in your project?

Use the official API to access entries easily!