How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

346,508

Total vulnerabilities in the database

Vulnerabilities for products matching "imagemagick"

Found 1 matching product.

You can search for specific versions with /product/imagemagick/1.2.3

imagemagick / imagemagick

3244 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2018-8804	Medium	March 20, 2018 3/20/18	== 7.0.7-25q16
CVE-2017-18209	Medium	March 1, 2018 3/1/18	== 7.0.7-1 == 7.0.7-0 == 7.0.7-4 == 7.0.7-3 == 7.0.7-2 == 7.0.7-6 == 7.0.7-9 == 7.0.7-12 == 7.0.7-16 == 7.0.7-17 == 7.0.7-22 == 7.0.7-5 == 7.0.7.7 == 7.0.7-8 == 7.0.7-10 == 7.0.7-11 == 7.0.7-13 == 7.0.7-14 == 7.0.7-15 == 7.0.7-18 == 7.0.7-19 == 7.0.7-20 == 7.0.7-21 == 7.0.7-23 == 7.0.7-24 == 7.0.7-25
CVE-2017-18210	High	March 1, 2018 3/1/18	== 7.0.7-1 == 7.0.7-0 == 7.0.7-4 == 7.0.7-3 == 7.0.7-2 == 7.0.7-6 == 7.0.7-9 == 7.0.7-12 == 7.0.7-16 == 7.0.7-17 == 7.0.7-22 == 7.0.7-5 == 7.0.7.7 == 7.0.7-8 == 7.0.7-10 == 7.0.7-11 == 7.0.7-13 == 7.0.7-14 == 7.0.7-15 == 7.0.7-18 == 7.0.7-19 == 7.0.7-20 == 7.0.7-21 == 7.0.7-23 == 7.0.7-24 == 7.0.7-25
CVE-2017-18211	High	March 1, 2018 3/1/18	== 7.0.7-1 == 7.0.7-0 == 7.0.7-4 == 7.0.7-3 == 7.0.7-2 == 7.0.7-6 == 7.0.7-9 == 7.0.7-12 == 7.0.7-16 == 7.0.7-17 == 7.0.7-22 == 7.0.7-5 == 7.0.7.7 == 7.0.7-8 == 7.0.7-10 == 7.0.7-11 == 7.0.7-13 == 7.0.7-14 == 7.0.7-15 == 7.0.7-18 == 7.0.7-19 == 7.0.7-20 == 7.0.7-21 == 7.0.7-23 == 7.0.7-24 == 7.0.7-25
CVE-2018-7470	Low	February 25, 2018 2/25/18	== 7.0.7-22-q16
CVE-2018-7443	Low	February 23, 2018 2/23/18	== 7.0.7-23-q16
CVE-2018-6930	Low	February 13, 2018 2/13/18	== 7.0.7-22
CVE-2018-6876	Low	February 9, 2018 2/9/18	== 7.0.7-22-q16
CVE-2018-6405	Medium	January 30, 2018 1/30/18	< 6.9.9-35 >= 7.0.0-0 < 7.0.7-23
CVE-2017-18027	Low	January 12, 2018 1/12/18	== 7.0.7-1-q16
CVE-2017-18028	High	January 12, 2018 1/12/18	== 7.0.7-1-q16
CVE-2017-18029	Low	January 12, 2018 1/12/18	== 7.0.6-10-q16
CVE-2018-5357	Low	January 12, 2018 1/12/18	== 7.0.7-22-q16
CVE-2018-5358	Low	January 12, 2018 1/12/18	== 7.0.7-22-q16
CVE-2017-18022	Low	January 5, 2018 1/5/18	== 7.0.7-12
CVE-2018-5246	Low	January 5, 2018 1/5/18	== 7.0.7-17
CVE-2018-5247	Low	January 5, 2018 1/5/18	== 7.0.7-17
CVE-2018-5248	Medium	January 5, 2018 1/5/18	== 7.0.7-17
CVE-2017-1000476	High	January 3, 2018 1/3/18	== 7.0.7-12-q16
CVE-2017-1000445	Medium	January 2, 2018 1/2/18	< 6.9.9-15 >= 7.0.0-0 <= 7.0.7-1
CVE-2017-18008	Low	January 1, 2018 1/1/18	== 7.0.7-17
CVE-2017-17914	High	December 27, 2017 12/27/17	== 7.0.7-16
CVE-2017-17934	Low	December 27, 2017 12/27/17	== 7.0.7-17
CVE-2017-17879	Medium	December 27, 2017 12/27/17	== 7.0.7-16
CVE-2017-17880	Medium	December 27, 2017 12/27/17	== 7.0.7-16
CVE-2017-17881	Low	December 27, 2017 12/27/17	== 7.0.7-12
CVE-2017-17882	Low	December 27, 2017 12/27/17	== 7.0.7-12
CVE-2017-17883	Low	December 27, 2017 12/27/17	== 7.0.7-12
CVE-2017-17884	Low	December 27, 2017 12/27/17	== 7.0.7-16
CVE-2017-17885	Low	December 27, 2017 12/27/17	== 7.0.7-12
CVE-2017-17886	Low	December 27, 2017 12/27/17	== 7.0.7-12
CVE-2017-17887	Low	December 27, 2017 12/27/17	== 7.0.7-16
CVE-2017-17680	Low	December 14, 2017 12/14/17	== 7.0.7-12-q16
CVE-2017-17681	High	December 14, 2017 12/14/17	== 7.0.7-12-q16
CVE-2017-17682	High	December 14, 2017 12/14/17	== 7.0.7-12-q16
CVE-2017-17499	Critical	December 11, 2017 12/11/17	>= 7.0.0-0 < 7.0.7-12 < 6.9.9-24
CVE-2017-17504	Medium	December 11, 2017 12/11/17	>= 7.0.0-0 < 7.0.7-12 < 6.9.9-24
CVE-2017-16546	High	November 5, 2017 11/5/17	== 7.0.7-9
CVE-2017-15277	Low	October 12, 2017 10/12/17	== 7.0.6-1
CVE-2017-15281	Medium	October 12, 2017 10/12/17	== 7.0.7-6
CVE-2017-15217	Low	October 10, 2017 10/10/17	== 7.0.7-2
CVE-2017-15218	Low	October 10, 2017 10/10/17	== 7.0.7-2
CVE-2017-15032	High	October 5, 2017 10/5/17	== 7.0.7-2
CVE-2017-15033	Medium	October 5, 2017 10/5/17	== 7.0.7-2
CVE-2017-15017	Medium	October 5, 2017 10/5/17	== 7.0.7-0
CVE-2017-15015	Medium	October 5, 2017 10/5/17	== 7.0.7-0
CVE-2017-15016	Medium	October 5, 2017 10/5/17	== 7.0.7-0
CVE-2017-14989	Low	October 3, 2017 10/3/17	== 7.0.7-4
CVE-2017-14739	Medium	September 26, 2017 9/26/17	== 7.0.7-4
CVE-2017-14741	Low	September 26, 2017 9/26/17	== 7.0.7-3

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.