Graphicsmagick 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.

Version

1.3.2654
1.3.2516
1.3.814
1.3.914
1.3.1614

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 Fix93
Temporary Fix0
Workaround0
Unavailable0
Not Defined22

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

High0
Functional0
Proof-of-Concept4
Unproven0
Not Defined111

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
Local7
Adjacent0
Network108

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
Low1
None114

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
Required67
None48

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.

CVSSv3 Base

≤10
≤20
≤30
≤41
≤55
≤637
≤722
≤836
≤910
≤104

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
≤41
≤57
≤635
≤723
≤835
≤910
≤104

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
≤45
≤530
≤623
≤731
≤821
≤90
≤105

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
≤613
≤732
≤813
≤930
≤1015

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
≤50
≤60
≤70
≤80
≤90
≤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

<1k19
<2k74
<5k22
<10k0
<25k0
<50k0
<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

<1k111
<2k3
<5k1
<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.

🔴 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 (78): 1.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.1, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.1.8, 1.1.9, 1.1.11, 1.1.12, 1.1.13, 1.1.14, 1.2, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.2.6, 1.2.7, 1.2.18, 1.3, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.3.6, 1.3.7, 1.3.8, 1.3.9, 1.3.11, 1.3.12, 1.3.13, 1.3.14, 1.3.15, 1.3.16, 1.3.17, 1.3.18, 1.3.19, 1.3.21, 1.3.22, 1.3.23, 1.3.24, 1.3.25, 1.3.26, 1.3.27, 1.3.27a, 1.3.28, 1.3.29, 1.3.31, 1.3.32, 1.3.33, 1.3.34, 1.3.35, 1.4, 1.4 snapshot-20171217 Q8, 1.4 snapshot-20181209 Q8, 1.4 snapshot-20190322 Q8, 1.4 snapshot-20190403 Q8, 1.4 snapshot-20190423 Q8, 1.4 snapshot-20191208 Q8, 6.9, 6.9.1, 6.9.2, 6.9.3, 7.0.3, 7.0.3.1, 7.0.3.2

Software Type: Image Processing Software

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
08/23/20234.94.9GraphicsMagick PCX Image File pcx.c WritePCXImage denial of service$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2020-21679
09/29/20227.07.0GraphicsMagick MIFF Parser heap-based overflow$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2022-1270
05/06/20207.47.4GraphicsMagick png.c ReadMNGImage out-of-bounds write$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2020-12672
03/24/20208.58.2GraphicsMagick compress.c HuffmanDecodeImage integer overflow$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-10938
03/18/20205.95.6GraphicsMagick Text Filename information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2019-12921
12/24/20197.77.7GraphicsMagick pict.c EncodeImage out-of-bounds$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2019-19953
12/24/20198.08.0GraphicsMagick miff.c ImportRLEPixels out-of-bounds write$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2019-19951
12/24/20198.08.0GraphicsMagick error.c ThrowLoggedException use after free$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2019-19950
04/24/20197.57.5GraphicsMagick mat.c WriteMATLABImage memory corruption$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2019-11506
04/24/20197.57.5GraphicsMagick pdb.c WritePDBImage memory corruption$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2019-11505
04/23/20195.45.4GraphicsMagick XWD Image File xwd.c Floating Point input validation$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2019-11474
04/23/20195.45.4GraphicsMagick XWD Image File xwd.c out-of-bounds$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2019-11473
04/08/20195.45.4GraphicsMagick mpc.c ReadMPCImage resource management$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2019-11010
04/08/20197.27.2GraphicsMagick xwd.c ReadXWDImage out-of-bounds$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2019-11009
04/08/20198.08.0GraphicsMagick xwd.c WriteXWDImage memory corruption$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2019-11008
04/08/20197.27.2GraphicsMagick Image Colormap png.c ReadMNGImage memory corruption$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2019-11007
04/08/20198.28.2GraphicsMagick miff.c ReadMIFFImage memory corruption$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2019-11006
04/08/20198.58.5GraphicsMagick svg.c SVGStartElement memory corruption$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2019-11005
12/17/20185.45.3GraphicsMagick dib File dib.c ReadDIBImage input validation$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2018-20189
12/17/20185.15.0GraphicsMagick bmp.c ReadBMPImage out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2018-20185
12/17/20186.46.2GraphicsMagick tga.c WriteTGAImage memory corruption$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2018-20184
03/25/20185.95.8GraphicsMagick MNG File png.c ReadMNGImage divide by zero$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2018-9018
03/14/20185.45.3GraphicsMagick emf.c ReadEnhMetaFile null pointer dereference$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2017-18231
03/14/20185.45.3GraphicsMagick cineon.c ReadCINEONImage null pointer dereference$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2017-18230
03/14/20185.45.3GraphicsMagick tiff.c ReadTIFFImage resource management$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2017-18229

90 more entries are not shown

Might our Artificial Intelligence support you?

Check our Alexa App!