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.

328,409

Total vulnerabilities in the database

Vulnerabilities for products matching "unbound"

Found 3 matching products. Filters apply to all results.

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

nlnetlabs / unbound

30 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2024-8508	Medium	October 3, 2024 10/3/24	< 1.21.1
CVE-2024-1931	High	March 7, 2024 3/7/24	>= 1.18.0 < 1.19.2
CVE-2023-50387	High	February 14, 2024 2/14/24	< 1.19.1
CVE-2022-3204	High	September 26, 2022 9/26/22	<= 1.16.2
CVE-2022-30698	Medium	August 1, 2022 8/1/22	< 1.16.2
CVE-2022-30699	Medium	August 1, 2022 8/1/22	< 1.16.2
CVE-2019-25031	Medium	April 27, 2021 4/27/21	< 1.9.5
CVE-2019-25032	Critical	April 27, 2021 4/27/21	< 1.9.5
CVE-2019-25033	Critical	April 27, 2021 4/27/21	< 1.9.5
CVE-2019-25034	Critical	April 27, 2021 4/27/21	< 1.9.5
CVE-2019-25035	Critical	April 27, 2021 4/27/21	< 1.9.5
CVE-2019-25036	High	April 27, 2021 4/27/21	< 1.9.5
CVE-2019-25037	High	April 27, 2021 4/27/21	< 1.9.5
CVE-2019-25038	Critical	April 27, 2021 4/27/21	< 1.9.5
CVE-2019-25039	Critical	April 27, 2021 4/27/21	< 1.9.5
CVE-2019-25040	High	April 27, 2021 4/27/21	< 1.9.5
CVE-2019-25041	High	April 27, 2021 4/27/21	< 1.9.5
CVE-2019-25042	Critical	April 27, 2021 4/27/21	< 1.9.5
CVE-2020-28935	Medium	December 7, 2020 12/7/20	< 1.13.0
CVE-2020-10772	High	November 27, 2020 11/27/20	== 1.6.6-5
CVE-2020-12662	High	May 19, 2020 5/19/20	< 1.10.1
CVE-2020-12663	High	May 19, 2020 5/19/20	< 1.10.1
CVE-2019-18934	High	November 19, 2019 11/19/19	>= 1.6.4 <= 1.9.4
CVE-2019-16866	High	October 3, 2019 10/3/19	< 1.9.4
CVE-2017-15105	Medium	January 23, 2018 1/23/18	< 1.6.8
CVE-2014-8602	Low	December 11, 2014 12/11/14	<= 1.5.0
CVE-2009-4008	Medium	June 2, 2011 6/2/11	== 1.3.4 == 0.8 == 1.2.1 == 1.3.3 == 1.0.1 == 1.1.0 == 0.0 == 0.10 == 1.3.0 == 0.09 == 1.4.2 == 1.0.0 == 0.7.2 == 1.4.0 == 1.1.1 == 0.11 == 1.4.1 == 1.3.2 == 1.3.1 == 0.4 == 0.7 == 0.2 == 0.1 == 0.7.1 == 1.2.0 == 1.0.2 == 0.5 == 0.6 == 0.3 <= 1.4.3
CVE-2011-1922	Low	May 31, 2011 5/31/11	== 1.3.4 == 1.4.9 == 1.2.1 == 1.3.3 == 1.4.3 == 1.0.1 == 1.4.7 == 1.4.5 == 1.1.0 == 1.3.0 == 1.4.2 == 1.0.0 == 1.4.0 == 1.1.1 == 1.4.1 == 1.3.2 == 1.4.8 == 1.3.1 == 1.4.6 == 1.2.0 == 1.0.2 == 1.4.4
CVE-2010-0969	Medium	March 16, 2010 3/16/10	== 1.3.4 == 0.8 == 1.2.1 == 1.3.3 == 1.0.1 == 1.1.0 == 0.0 == 0.10 == 1.3.0 == 0.09 == 1.0.0 == 0.7.2 == 1.4.0 == 1.1.1 == 0.11 == 1.4.1 == 1.3.2 == 1.3.1 == 0.4 == 0.7 == 0.2 == 0.1 == 0.7.1 == 1.2.0 == 1.0.2 == 0.5 == 0.6 <= 1.4.2 == 0.3
CVE-2009-3602	High	October 13, 2009 10/13/09	== 0.8 == 1.2.1 == 1.0.1 == 1.1.0 == 0.0 == 0.10 == 1.3.0 == 0.09 == 1.0.0 == 0.7.2 == 1.1.1 == 0.11 <= 1.3.3 == 1.3.2 == 1.3.1 == 0.4 == 0.7 == 0.2 == 0.1 == 0.7.1 == 1.2.0 == 1.0.2 == 0.5 == 0.6 == 0.3

unbound / unbound

3 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2012-1192	Medium	February 17, 2012 2/17/12	== 1.3.3 == 0.7 == 0.0 == 0.6 == 0.4 == 0.2 == 1.3.1 == 0.11 == 1.3.4 == 1.0.0 == 1.4.7 == 1.2.0 == 1.3.2 == 1.3.0 == 1.4.4 == 1.4.1 == 0.1 == 1.1.0 == 1.4.6 <= 1.4.10 == 0.3 == 0.7.2 == 1.4.8 == 1.0.1 == 1.0.2 == 0.9 == 0.7.1 == 1.2.1 == 0.8 == 1.4.3 == 1.4.2 == 0.10 == 1.4.0 == 1.4.5 == 1.1.1 == 1.4.9 == 0.5
CVE-2011-4869	High	December 20, 2011 12/20/11	== 1.3.3 == 0.7 == 0.0 == 0.6 == 0.4 == 0.2 == 1.3.1 == 0.11 == 1.3.4 <= 1.4.12 == 1.0.0 == 1.4.7 == 1.2.0 == 1.3.2 == 1.3.0 == 1.4.4 == 1.4.1 == 0.1 == 1.1.0 == 1.4.6 == 0.3 == 1.4.10 == 0.7.2 == 1.4.8 == 1.0.1 == 1.0.2 == 0.7.1 == 1.2.1 == 1.4.11 == 0.8 == 1.4.3 == 1.4.2 == 0.10 == 1.4.0 == 0.09 == 1.4.5 == 1.1.1 == 1.4.9 == 0.5
CVE-2011-4528	Medium	December 20, 2011 12/20/11	== 1.3.3 <= 1.4.13 == 0.7 == 0.0 == 0.6 == 0.4 == 0.2 == 1.3.1 == 0.11 == 1.3.4 == 1.0.0 == 1.4.7 == 1.2.0 == 1.3.2 == 1.3.0 == 1.4.4 == 1.4.1 == 0.1 == 1.1.0 == 1.4.6 == 0.3 == 1.4.10 == 0.7.2 == 1.4.8 == 1.0.1 == 1.0.2 == 1.4.12 == 1.4.14-rc1 == 0.7.1 == 1.2.1 == 1.4.11 == 0.8 == 1.4.3 == 1.4.2 == 0.10 == 1.4.0 == 0.09 == 1.4.5 == 1.1.1 == 1.4.9 == 0.5

fedoraproject / unbound

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2024-1488	High		February 15, 2024 2/15/24	< 1.19.1-2.fc40

Showing vulnerabilities for 3 products matching "unbound". Each product has independent pagination.

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.