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 "samba"

Found 2 matching products. Filters apply to all results.

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

samba / samba

4403 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2011-1678	Low	April 10, 2011 4/10/11	<= 3.5.8
CVE-2011-0719	Medium	March 1, 2011 3/1/11	== 3.0.19 == 3.0.23-c == 3.0.14a == 3.0.27 == 3.0.31 == 3.0.3 == 3.0.8 == 3.2.15 == 3.3.3 == 3.0.23-b == 3.0.29 == 3.0.25-pre2 == 3.0.25b == 3.2.5 == 3.2.3 == 3.0.2a == 3.0.36 == 3.0.28-a == 3.2.4 == 3.0.5 == 3.0.26-a == 3.3.9 == 3.0.21-a == 3.0.28 == 3.0.32 == 3.0.26a == 3.2.13 == 3.0.6 == 3.0.21a == 3.0.34 == 3.0.25-rc1 == 3.0.23 == 3.2.1 == 3.0.4-rc1 == 3.3.4 == 3.0.33 == 3.0.25-b == 3.0.21-b == 3.0.20a == 3.3.12 == 3.0.21b == 3.0.20-a == 3.3.7 == 3.0.0 == 3.0.9 == 3.2.9 == 3.0.11 == 3.0.7 == 3.0.13 == 3.3.1 == 3.2.2 == 3.2.7 == 3.0.14-a == 3.0.20b == 3.0.21-c == 3.0.16 == 3.2.10 == 3.0.17 == 3.0.21 == 3.0.26 == 3.0.14 == 3.0.25-pre1 == 3.0.30 == 3.0.21c == 3.3.11 == 3.0.20-b == 3.3.0 == 3.0.23b == 3.3.6 == 3.0.25-rc3 == 3.3.14 == 3.0.23-a == 3.0.2 == 3.0.12 == 3.2.12 == 3.0.37 == 3.0.20 == 3.2.8 == 3.0.35 == 3.0.18 == 3.0.23-d == 3.0.2-a == 3.0.25a == 3.0.25c == 3.3.2 == 3.0.24 == 3.0.10 == 3.2.11 == 3.1.0 == 3.0.27-a == 3.3.8 == 3.3.13 == 3.2.14 == 3.0.23d == 3.0.25-rc2 == 3.2.0 == 3.3.5 == 3.0.25-a == 3.0.23c == 3.0.15 == 3.2.6 == 3.0.23a == 3.0.25-c == 3.0.4 == 3.3.10 == 3.0.25 == 3.0.1 == 3.0.22 == 3.4.2 == 3.4.11 == 3.4.0 == 3.4.7 == 3.4.8 == 3.4.5 == 3.4.6 == 3.4.1 == 3.4.10 == 3.4.4 == 3.4.3 == 3.4.9 == 3.5.1 == 3.5.6 == 3.5.2 == 3.5.5 == 3.5.0 == 3.5.4 == 3.5.3
CVE-2010-3069	High	September 15, 2010 9/15/10	>= 3.0.0 <= 3.3.14 >= 3.4.0 < 3.4.9 >= 3.5.0 < 3.5.5
CVE-2010-1635	Medium	June 17, 2010 6/17/10	== 3.0.19 == 3.0.14a == 3.0.27 == 3.0.31 == 3.0.3 == 3.0.8 == 3.2.15 == 3.3.3 == 3.5.1 == 3.0.29 == 3.0.25-pre2 == 3.0.25b == 3.2.5 == 3.4.2 == 3.2.3 == 3.3 == 3.0.2a == 3.0.36 == 3.4.0 == 3.2.4 == 3.0.5 == 3.3.9 == 3.0.28 == 3.4.5 == 3.0.32 == 3.0.26a == 3.2.13 == 3.0.6 == 3.4.6 == 3.0.21a == 3.0.34 == 3.0.25-rc1 == 3.0.23 == 3.2.1 == 3.0.4-rc1 == 3.3.4 == 3.0.33 == 3.0.20a == 3.4 == 3.0.21b == 3.0.27a == 3.3.7 == 3.4.1 == 3.0.0 == 3.0.9 == 3.2.9 == 3.0.11 == 3.0.7 == 3.0.13 == 3.3.1 == 3.2.2 == 3.2.7 == 3.0.20b == 3.0.16 == 3.2.10 == 3.0.17 == 3.2 == 3.5 == 3.0.21 == 3.0.26 == 3.0.14 == 3.0.25-pre1 == 3.0.30 == 3.0.21c == 3.3.11 == 3.3.0 == 3.0.23b == 3.3.6 == 3.0.25-rc3 == 3.5.0 == 3.0.2 == 3.0.12 == 3.2.12 == 3.0.37 == 3.0.20 == 3.2.8 == 3.0.35 == 3.0.18 == 3.0.25a == 3.0.25c <= 3.4.7 == 3.3.2 == 3.0.24 == 3.0.10 == 3.2.11 == 3.4.4 == 3.1.0 == 3.4.3 == 3.3.8 == 3.2.14 == 3.0.23d == 3.0.25-rc2 == 3.2.0 == 3.3.5 == 3.0.23c == 3.0.15 == 3.2.6 == 3.0.23a == 3.0.28a == 3.0.4 == 3.3.10 == 3.0.25 == 3.0.1 == 3.0.22
CVE-2010-1642	Medium	June 17, 2010 6/17/10	== 3.0.19 == 3.0.14a == 3.0.27 == 3.0.31 == 3.0.3 == 3.0.8 == 3.2.15 == 3.3.3 == 3.5.1 == 3.0.29 == 3.0.25-pre2 == 3.0.25b == 3.2.5 == 3.4.2 == 3.2.3 == 3.3 == 3.0.2a == 3.0.36 == 3.4.0 == 3.2.4 == 3.0.5 == 3.3.9 == 3.0.28 == 3.4.5 == 3.0.32 == 3.0.26a == 3.2.13 == 3.0.6 == 3.4.6 == 3.0.21a == 3.0.34 == 3.0.25-rc1 == 3.0.23 == 3.2.1 == 3.0.4-rc1 == 3.3.4 == 3.0.33 == 3.0.20a == 3.4 == 3.0.21b == 3.0.27a == 3.3.7 == 3.4.1 == 3.0.0 == 3.0.9 == 3.2.9 == 3.0.11 == 3.0.7 == 3.0.13 == 3.3.1 == 3.2.2 == 3.2.7 == 3.0.20b == 3.0.16 == 3.2.10 == 3.0.17 == 3.2 == 3.5 == 3.0.21 == 3.0.26 == 3.0.14 == 3.0.25-pre1 == 3.0.30 == 3.0.21c == 3.3.11 == 3.3.0 == 3.0.23b == 3.3.6 == 3.0.25-rc3 == 3.5.0 == 3.0.2 == 3.0.12 == 3.2.12 == 3.0.37 == 3.0.20 == 3.2.8 == 3.0.35 == 3.0.18 == 3.0.25a == 3.0.25c <= 3.4.7 == 3.3.2 == 3.0.24 == 3.0.10 == 3.2.11 == 3.4.4 == 3.1.0 == 3.4.3 == 3.3.8 == 3.2.14 == 3.0.23d == 3.0.25-rc2 == 3.2.0 == 3.3.5 == 3.0.23c == 3.0.15 == 3.2.6 == 3.0.23a == 3.0.28a == 3.0.4 == 3.3.10 == 3.0.25 == 3.0.1 == 3.0.22
CVE-2010-2063	High	June 17, 2010 6/17/10	>= 3.0.0 <= 3.3.12
CVE-2010-0926	Low	March 10, 2010 3/10/10	== 3.3.3 == 3.4.2 == 3.4.0 == 3.3.9 == 3.4.5 == 3.3.4 == 3.3.7 == 3.4.1 == 3.3.1 == 3.3.0 == 3.3.6 == 3.5.0 == 3.3.2 == 3.4.4 == 3.4.3 == 3.3.8 == 3.3.5 == 3.3.10
CVE-2010-0728	High	March 10, 2010 3/10/10	== 3.4.6 == 3.3.11 == 3.5.0
CVE-2010-0787	Low	March 2, 2010 3/2/10	== 3.2.3 == 3.4.0 == 3.4.5 == 3.0.28a == 3.0.22
CVE-2010-0547	Low	February 4, 2010 2/4/10	== 3.0.14a == 2.2.1a == 3.0.27 == 3.0.31 == 3.0.3 == 2.2.12 == 3.0.8 == 3.2.15 == 3.3.3 == 3.0.29 == 3.0.25-pre2 == 3.0.25b == 3.2.5 == 3.4.2 == 2.2.3a == 3.2.3 == 1.9.18-p2 == 3.0.2a == 3.0.36 == 3.4.0 == 3.2.4 == 3.0.5 == 1.9.17-p5 == 1.9.18-p1 == 3.3.9 == 2.2.8a == 3.0.28 == 3.0.32 == 3.0.26a == 3.2.13 == 3.0.6 == 1.9.18-p4 == 3.0.21a == 3.0.34 == 3.0.25-rc1 == 1.9.17-p1 == 1.9.18-p10 == 3.0.23 == 3.2.1 == 3.0.4-rc1 == 3.3.4 == 3.0.33 == 1.9.17 == 3.0.20a == 2.2.9 == 2.2.3 == 3.0.21b == 3.0.27a == 3.3.7 == 3.4.1 == 3.0.0 == 2.2.11 == 1.9.18-p3 == 3.0.9 == 3.2.9 == 3.0.11 == 2.2.1 == 3.0.13 == 3.3.1 == 3.2.2 == 1.9.18-p8 == 3.2.7 == 3.0.20b == 2.2.7a == 1.9.17-p2 == 3.2.10 == 2.2.4 == 3.0.21 == 3.0.26 == 3.0.14 == 1.9.18-p6 == 3.0.25-pre1 == 1.9.18-p7 == 3.0.30 == 3.0.21c == 3.3.0 == 2.2a == 3.0.23b == 3.3.6 == 3.0.25-rc3 == 2.2.6 == 2.2.8 == 3.0.2 == 3.0.12 == 3.2.12 == 3.0.37 == 1.9.18 == 3.0.20 == 2.2.0a == 3.2.8 == 3.0.35 <= 3.4.5 == 3.0.25a == 3.0.25c == 1.9.17-p3 == 3.3.2 == 3.0.24 == 3.0.10 == 3.2.11 == 3.4.4 == 2.2.2 == 2.2.10 == 3.4.3 == 3.3.8 == 3.2.14 == 3.0.23d == 3.0.25-rc2 == 2.2.0 == 3.2.0 == 2.2.5 == 3.3.5 == 3.0.23c == 3.2.6 == 1.9.18-p5 == 1.9.17-p4 == 2.2.7 == 3.0.23a == 3.0.28a == 3.0.4 == 3.3.10 == 3.0.25 == 3.0.1 == 3.0.22
CVE-2009-2906	Low	October 7, 2009 10/7/09	== 3.4.0 == 3.4.1 < 3.0.37 >= 3.3.0 < 3.3.8 >= 3.2.0 < 3.2.15
CVE-2009-2948	Low	October 7, 2009 10/7/09	>= 3.4.0 < 3.4.2 >= 3.3.0 < 3.3.8 >= 3.2.0 < 3.2.15 >= 3.0.0 < 3.0.37
CVE-2009-2813	Medium	September 14, 2009 9/14/09	== 3.0.12 == 3.0.13 == 3.0.14 == 3.0.14a == 3.0.15 == 3.0.16 == 3.0.17 == 3.0.18 == 3.0.19 == 3.0.20 == 3.0.20a == 3.0.20b == 3.0.21 == 3.0.21a == 3.0.21b == 3.0.21c == 3.0.22 == 3.0.23 == 3.0.23a == 3.0.23b == 3.0.23c == 3.0.23d == 3.0.24 == 3.0.25-rc2 == 3.0.25-rc3 == 3.0.25-pre1 == 3.0.25-rc1 == 3.0.25-pre2 == 3.0.25 == 3.0.25a == 3.0.25b == 3.0.25c == 3.0.26 == 3.0.26a == 3.0.27 == 3.0.27a == 3.0.28 == 3.0.28a == 3.0.29 == 3.0.30 == 3.0.31 == 3.0.32 == 3.0.33 == 3.0.34 == 3.0.35 == 3.0.36 == 3.2 == 3.2.0 == 3.2.1 == 3.2.2 == 3.2.3 == 3.2.4 == 3.2.5 == 3.2.6 == 3.2.7 == 3.2.8 == 3.2.9 == 3.2.10 == 3.2.11 == 3.2.12 == 3.2.13 == 3.2.14 == 3.2.15 == 3.3 == 3.3.0 == 3.3.1 == 3.3.2 == 3.3.3 == 3.3.4 == 3.3.5 == 3.3.6 == 3.3.7 == 3.4 == 3.4.0 == 3.4.1
CVE-2009-1886	High	June 25, 2009 6/25/09	== 3.2.5 == 3.2.3 == 3.2.4 == 3.2.1 == 3.2.9 == 3.2.2 == 3.2.7 == 3.2.10 == 3.2.12 == 3.2.8 == 3.2.11 == 3.2.0 == 3.2.6
CVE-2009-1888	Medium	June 25, 2009 6/25/09	>= 3.2.0 < 3.2.13 >= 3.3.0 < 3.3.6 >= 3.0.31 <= 3.0.35
CVE-2009-0022	Medium	January 5, 2009 1/5/09	== 3.2.5 == 3.2.3 == 3.2.4 == 3.2.1 == 3.2.2 == 3.2.0 == 3.2.6
CVE-2008-4314	High	December 1, 2008 12/1/08	== 3.0.31 == 3.0.29 == 3.2.3 == 3.2.4 == 3.0.32 == 3.2.1 == 3.0.33 == 3.2.2 == 3.0.30 == 3.2.0
CVE-2008-3789	Low	August 27, 2008 8/27/08	>= 3.2.0 < 3.2.3
CVE-2008-1105	High	May 29, 2008 5/29/08	>= 3.0.0 <= 3.0.29
CVE-2007-6015	High	December 13, 2007 12/13/07	== 3.0.14a == 2.2.1a == 3.0.27 == 2.0.10 == 2.2.12 == 3.0.25-pre2 == 2.0.1 == 3.0.25b == 2.2.3a == 2.0.2 == 3.0.2a == 2.2.8a == 3.0.26a == 3.0.21a == 3.0.25-rc1 == 3.0.20a == 2.2.9 == 2.2.3 == 3.0.21b == 2.0.6 == 3.0.0 == 2.2.11 == 3.0.11 == 2.0.4 == 3.0.13 == 3.0.20b == 2.2.7a == 2.2.4 == 2.0.9 == 3.0.21 == 3.0.26 == 3.0.14 == 3.0.25-pre1 == 2.0.3 == 3.0.21c == 3.0.23b == 3.0.25-rc3 == 2.2.6 == 2.2.8 == 3.0.2 == 3.0.12 == 3.0.20 == 2.2.0a == 2.0.7 == 2.0.8 == 3.0.25a == 3.0.25c == 3.0.24 == 3.0.10 == 2.2.2 == 2.0.5 == 3.0.23d == 3.0.25-rc2 == 2.2.0 == 2.2.5 == 3.0.23c == 2.2.7 == 3.0.23a == 3.0.25 == 3.0.1 == 3.0.22
CVE-2007-4572	High	November 16, 2007 11/16/07	== 3.0.19 == 3.0.14a == 3.0.3 == 3.0.8 == 3.0.25-pre2 == 3.0.25b == 3.0.2a == 3.0.5 == 3.0.26a == 3.0.6 == 3.0.21a == 3.0.25-rc1 == 3.0.23 == 3.0.4-rc1 == 3.0.20a == 3.0.21b == 3.0.0 == 3.0.9 == 3.0.11 == 3.0.7 == 3.0.13 == 3.0.20b == 3.0.16 == 3.0.17 == 3.0.21 == 3.0.26 == 3.0.14 == 3.0.25-pre1 == 3.0.21c == 3.0.23b == 3.0.25-rc3 == 3.0.2 == 3.0.12 == 3.0.20 == 3.0.18 == 3.0.25a == 3.0.25c == 3.0.24 == 3.0.10 == 3.0.23d == 3.0.25-rc2 == 3.0.23c == 3.0.15 == 3.0.23a == 3.0.4 == 3.0.25 == 3.0.1 == 3.0.22
CVE-2007-5398	High	November 16, 2007 11/16/07	== 3.0.19 == 3.0.14a == 3.0.3 == 3.0.8 == 3.0.25-pre2 == 3.0.25b == 3.0.2a == 3.0.5 == 3.0.26a == 3.0.6 == 3.0.21a == 3.0.25-rc1 == 3.0.23 == 3.0.4-rc1 == 3.0.20a == 3.0.21b == 3.0.0 == 3.0.9 == 3.0.11 == 3.0.7 == 3.0.13 == 3.0.20b == 3.0.16 == 3.0.17 == 3.0.21 == 3.0.26 == 3.0.14 == 3.0.25-pre1 == 3.0.21c == 3.0.23b == 3.0.25-rc3 == 3.0.2 == 3.0.12 == 3.0.20 == 3.0.18 == 3.0.25a == 3.0.25c == 3.0.24 == 3.0.10 == 3.0.23d == 3.0.25-rc2 == 3.0.23c == 3.0.15 == 3.0.23a == 3.0.4 == 3.0.25 == 3.0.1 == 3.0.22
CVE-2007-4138	Medium	September 14, 2007 9/14/07	== 3.0.25b == 3.0.25a == 3.0.25c == 3.0.25
CVE-2007-2444	High	May 14, 2007 5/14/07	== 3.0.25-pre2 == 3.0.24 == 3.0.23d
CVE-2007-2446	High	May 14, 2007 5/14/07	== 3.0.19 == 3.0.14a == 3.0.25-pre2 == 3.0.2a == 3.0.21a == 3.0.25-rc1 == 3.0.23 == 3.0.20a == 3.0.21b == 3.0.0 == 3.0.11 == 3.0.13 == 3.0.20b == 3.0.16 == 3.0.17 == 3.0.21 == 3.0.14 == 3.0.25-pre1 == 3.0.21c == 3.0.23b == 3.0.25-rc3 == 3.0.2 == 3.0.12 == 3.0.20 == 3.0.18 == 3.0.24 == 3.0.10 == 3.0.23d == 3.0.25-rc2 == 3.0.23c == 3.0.15 == 3.0.23a == 3.0.1 == 3.0.22
CVE-2007-2447	Medium	May 14, 2007 5/14/07	== 3.0.19 == 3.0.14a == 3.0.3 == 3.0.8 == 3.0.25-pre2 == 3.0.2a == 3.0.5 == 3.0.6 == 3.0.21a == 3.0.25-rc1 == 3.0.23 == 3.0.4-rc1 == 3.0.20a == 3.0.21b == 3.0.0 == 3.0.9 == 3.0.11 == 3.0.7 == 3.0.13 == 3.0.20b == 3.0.16 == 3.0.17 == 3.0.21 == 3.0.14 == 3.0.25-pre1 == 3.0.21c == 3.0.23b == 3.0.25-rc3 == 3.0.2 == 3.0.12 == 3.0.20 == 3.0.18 == 3.0.24 == 3.0.10 == 3.0.23d == 3.0.25-rc2 == 3.0.23c == 3.0.15 == 3.0.23a == 3.0.4 == 3.0.1 == 3.0.22
CVE-2007-0452	Medium	February 6, 2007 2/6/07	== 3.0.14a == 3.0.8 == 3.0.6 == 3.0.21a == 3.0.23 == 3.0.20a == 3.0.21b == 3.0.9 == 3.0.11 == 3.0.7 == 3.0.13 == 3.0.20b == 3.0.21 == 3.0.21c == 3.0.23b == 3.0.12 == 3.0.20 == 3.0.10 == 3.0.23d == 3.0.23c == 3.0.23a == 3.0.22
CVE-2007-0453	Low	February 6, 2007 2/6/07	== 3.0.21a == 3.0.23 == 3.0.21b == 3.0.21 == 3.0.21c == 3.0.23b == 3.0.23d == 3.0.23c == 3.0.23a == 3.0.22
CVE-2007-0454	High	February 6, 2007 2/6/07	== 3.0.14a == 3.0.8 == 3.0.6 == 3.0.21a == 3.0.20a == 3.0.21b == 3.0.9 == 3.0.11 == 3.0.7 == 3.0.13 == 3.0.20b == 3.0.21 == 3.0.14 == 3.0.21c == 3.0.12 == 3.0.20 == 3.0.10 == 3.0.23d == 3.0.22
CVE-2006-3403	Medium	July 12, 2006 7/12/06	== 3.0.19 == 3.0.14a == 3.0.3 == 3.0.8 == 3.0.5 == 3.0.6 == 3.0.21a == 3.0.20a == 3.0.21b == 3.0.9 == 3.0.11 == 3.0.7 == 3.0.13 == 3.0.20b == 3.0.16 == 3.0.17 == 3.0.21 == 3.0.14 == 3.0.21c == 3.0.2 == 3.0.12 == 3.0.18 == 3.0.10 == 3.0.15 == 3.0.4 == 3.0.1 == 3.0.22
CVE-2006-1059	Low	March 30, 2006 3/30/06	== 3.0.21a == 3.0.21b == 3.0.21 == 3.0.21c
CVE-2004-0882	High	January 27, 2005 1/27/05	== 3.0.3 == 3.0.2a == 3.0.5 == 3.0.6 == 3.0.4-rc1 == 3.0.0 == 3.0.7 == 3.0.2 == 3.0.4 == 3.0.1
CVE-2004-0930	Medium	January 27, 2005 1/27/05	== 3.0.3 == 3.0.5 == 3.0.6 == 3.0.0 == 3.0.7 == 3.0.4
CVE-2004-1154	High	January 10, 2005 1/10/05	== 2.2.1a == 3.0.3 == 2.0.10 == 2.2.12 == 3.0.8 == 2.0.1 == 2.2.3a == 2.0.2 == 3.0.2a == 3.0.5 == 2.2.8a == 3.0.6 == 3.0.4-rc1 == 2.2.9 == 2.2.3 == 2.0.6 == 3.0.0 == 2.2.11 == 3.0.9 == 2.0.4 == 3.0.7 == 2.2.7a == 2.2.4 == 2.0.9 == 2.0.3 == 2.2a == 2.2.6 == 2.2.8 == 3.0.2 == 2.2.0a == 2.0.7 == 2.0.8 == 2.2.2 == 2.0.5 == 2.2.0 == 2.0.0 == 2.2.5 == 2.2.7 == 3.0.4 == 3.0.1
CVE-2004-0808	Medium	December 31, 2004 12/31/04	== 3.0.3 == 3.0.2a == 3.0.5 == 3.0.6 == 3.0.4-rc1 == 3.0.0 == 3.0.2 == 3.0.4 == 3.0.1
CVE-2004-0829	Medium	December 31, 2004 12/31/04	== 2.0.1 == 2.2.3a == 1.9.18-p2 == 2.0.2 == 1.9.17-p5 == 1.9.18-p1 == 2.2.8a == 1.9.18-p4 == 1.9.17-p1 == 1.9.18-p10 == 1.9.17 == 2.2.9 == 2.2.3 == 2.0.6 == 1.9.18-p3 == 2.0.4 == 2.2.1 == 1.9.18-p8 == 2.2.7a == 1.9.17-p2 == 2.2.4 == 1.9.18-p6 == 1.9.18-p7 == 2.0.3 == 2.2.6 == 2.2.8 == 1.9.18 == 2.0.7 == 1.9.17-p3 == 2.0.5a == 2.2.2 == 2.0.5 == 2.2.10 == 2.2.0 == 2.0.0 == 2.2.5 == 1.9.18-p5 == 1.9.17-p4 == 2.2.7
CVE-2004-2546	Medium	December 31, 2004 12/31/04	== 2.2.1a == 3.0.3 == 2.2.12 == 2.2.3a == 1.9.18-p2 == 3.0.2a == 3.0.5 == 1.9.17-p5 == 1.9.18-p1 == 2.2.8a == 1.9.18-p4 == 1.9.17-p1 == 1.9.18-p10 == 3.0.4-rc1 == 1.9.17 == 2.2.9 == 3.0.0 == 2.2.11 == 1.9.18-p3 == 2.2.1 == 1.9.18-p8 == 2.2.7a == 2.0 == 1.9.18-p6 == 1.9.18-p7 == 2.2a == 3.0.2 == 1.9.17-p3 == 2.0.5a == 2.2.10 == 2.0.0 == 1.9.18-p5 == 1.9.17-p4 == 3.0.4 == 3.0.1
CVE-2004-2687	High	December 31, 2004 12/31/04	<= 2.18.3
CVE-2004-0815	High	November 3, 2004 11/3/04	== 2.2.1a == 2.2.3a == 3.0.2a == 2.2.8a == 2.2.9 == 2.2.3 == 3.0.0 == 2.2.11 == 2.2.7a == 2.2.4 == 2.2a == 2.2.6 == 2.2.8 == 3.0.2 == 2.2.0a == 2.2.2 == 2.2.0 == 2.2.5 == 2.2.7 == 3.0.1
CVE-2004-0807	Medium	September 13, 2004 9/13/04	== 3.0.3 == 3.0.2a == 3.0.5 == 3.0.6 == 3.0.4-rc1 == 3.0.0 == 3.0.2 == 3.0.4 == 3.0.1
CVE-2004-0600	High	July 27, 2004 7/27/04	== 3.0.3 == 3.0.2a == 3.0.2 == 3.0.4
CVE-2004-0686	Medium	July 27, 2004 7/27/04	>= 2.2.0 < 2.2.10 >= 3.0.0 < 3.0.5
CVE-2004-0186	High	March 15, 2004 3/15/04	== 3.0.0 == 2.0
CVE-2004-0082	High	March 3, 2004 3/3/04	== 3.0.0 == 3.0.1
CVE-2003-1332	High	December 31, 2003 12/31/03	<= 2.2.7a
CVE-2003-0196	High	May 5, 2003 5/5/03	== 2.2.1a == 2.0.10 == 2.0.1 == 2.2.3a == 2.0.2 == 2.2.3 == 2.0.6 == 2.0.4 == 2.0.5 == 2.0.0 == 2.0.7 == 2.0.8 == 2.0.9 == 2.2.4 == 2.2.5 == 2.2.0 == 2.2.0a == 2.2.6 == 2.2.7 == 2.0.3 == 2.2.2 == 2.2.7a == 2.2.8
CVE-2003-0201	High	May 5, 2003 5/5/03	== 2.2.1a == 2.0.10 == 2.0.1 == 2.2.3a == 2.0.2 == 2.0.6 == 2.0.4 == 2.2.7a == 2.0.3 == 2.2.0 == 2.2.0a == 2.2.8 == 2.0.5 == 2.0.7 == 2.2.4 == 2.2.5 == 2.0.0 == 2.0.8 == 2.0.9 == 2.2.6 == 2.2.7
CVE-2003-0085	High	March 31, 2003 3/31/03	== 2.2.1a == 2.0.10 == 2.0.1 == 2.2.3a == 2.0.2 == 2.2.3 == 2.0.6 == 2.0.4 == 2.2.7a == 2.0.8 == 2.0.9 == 2.2.4 == 2.2.5 == 2.0.3 == 2.2.0 == 2.2.0a == 2.2.6 == 2.2.7 == 2.0.0 == 2.0.7 == 2.0.5 == 2.2.2
CVE-2003-0086	Low	March 31, 2003 3/31/03	== 2.2.1a == 2.0.10 == 2.0.1 == 2.2.3a == 2.0.2 == 2.2.3 == 2.0.6 == 2.0.4 == 2.2.7a == 2.0.5 == 2.2.2 == 2.0.3 == 2.2.0 == 2.2.0a == 2.2.7 == 2.0.8 == 2.0.9 == 2.2.5 == 2.2.6 == 2.0.0 == 2.0.7 == 2.2.4
CVE-2002-2196	High	December 31, 2002 12/31/02	== 2.2.1a == 2.2.3a == 1.9.18-p2 == 1.9.17-p5 == 1.9.18-p1 == 1.9.18-p4 == 1.9.17-p1 == 1.9.18-p10 == 1.9.17 == 1.9.18-p3 == 2.2.1 == 1.9.18-p8 == 1.9.18-p6 == 1.9.18-p7 == 2.2a == 1.9.17-p3 == 2.0.5a <= 2.2.4 == 2.0.0 == 1.9.18-p5 == 1.9.17-p4

Showing vulnerabilities for 2 products matching "samba". 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.