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.

325,773

Total vulnerabilities in the database

Vulnerabilities for products matching "mail_security"

Found 2 matching products. Filters apply to all results.

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

symantec / mail_security

19 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2012-6277	High	February 21, 2020 2/21/20	<= 8.1.0 <= 6.5.7 == 6.5.7
CVE-2019-12759	High	November 15, 2019 11/15/19	< 7.5
CVE-2011-0548	High	July 18, 2011 7/18/11	== 8.0 == 6.0.0 == 7.5
CVE-2010-0131	High	August 17, 2010 8/17/10	*
CVE-2009-3032	High	March 5, 2010 3/5/10	== 8.0.2 == 6.0.7 == 7.5.7 == 6.0.6 == 5.0.13 == 8.0.1 == 7.5.6 == 5.0.1.181 == 7.5.3.25 == 5.0.11 == 6.0.8 == 5.0.12 == 5.0.1.182 == 7.5.5.32 == 7.5.8 == 5.0.1.189 == 7.5.4.29 == 8.0 == 5.0.0
CVE-2009-3037	High	September 1, 2009 9/1/09	== 5.0 == 5.0.0 == 5.0.1 == 5.0.1.181 == 5.0.1.182 == 5.0.1.189 == 5.0.1.200 == 5.0.10 == 5.0.11 == 5.0.12 == 6.0.6 == 6.0.7 == 6.0.8 == 7.5.3.25 == 7.5.4.29 == 7.5.5.32 == 7.5.6 == 8.0
CVE-2008-4564	High	March 18, 2009 3/18/09	== 5.0 == 5.0.0 == 5.0.0.24 == 5.0.1 == 5.0.1.181 == 5.0.1.182 == 5.0.1.189 == 5.0.1.200 == 5.0.10 == 5.0.11 == 6.0.6-microsoft_exchange == 6.0.7-microsoft_exchange == 7.5..4.29 == 7.5.3.25 == 7.5.5.32
CVE-2007-5405	High	April 10, 2008 4/10/08	== 5.0.1 == 7.5 == 5.0 == 5.0.0
CVE-2007-5406	High	April 10, 2008 4/10/08	<= 7.5 == 5.0 == 5.0.0 == 5.0.1
CVE-2007-6020	High	April 10, 2008 4/10/08	== 5.0.1 == 7.5 == 5.0 == 5.0.0
CVE-2007-5909	High	November 10, 2007 11/10/07	== 5.0.1 == 5.0.0.24 == 7.5 == 5.0 == 5.0.0
CVE-2007-5910	High	November 10, 2007 11/10/07	== 5.0.1 == 5.0.0.24 == 7.5 == 5.0 == 5.0.0
CVE-2007-0447	High	October 5, 2007 10/5/07	== 4.0 == 4.0-build456 == 4.0-build463 == 4.0-build465 == 4.0-build736 == 4.0-build741 == 4.0-build743 == 4.0.1 == 4.1-build458 == 4.1-build459 == 4.1-build461 == 4.5 == 4.5_build_719 == 4.5_build_736 == 4.5_build_741 == 4.5.4.743 == 4.6_build_97 == 4.6.1.107 == 4.6.3 == 5.0 == 5.0.0.204 == 5.0.1 == 5.1.0 == 6.0.0
CVE-2007-3699	High	October 5, 2007 10/5/07	== 4.0 == 4.0-build456 == 4.0-build463 == 4.0-build465 == 4.0-build736 == 4.0-build741 == 4.0-build743 == 4.0.1 == 4.1-build458 == 4.1-build459 == 4.1-build461 == 4.5 == 4.5_build_719 == 4.5_build_736 == 4.5_build_741 == 4.5.4.743 == 4.6_build_97 == 4.6.1.107 == 4.6.3 == 5.0 == 5.0.0.204 == 5.0.1 == 5.1.0 == 6.0.0
CVE-2007-1792	High	June 27, 2007 6/27/07	== 5.0.0 == 5.0.1
CVE-2007-1252	High	March 3, 2007 3/3/07	== 5.0
CVE-2006-5545	Medium	October 26, 2006 10/26/06	== 5.1.0
CVE-2005-1346	Low	May 2, 2005 5/2/05	== 4.5.4.743 == 4.0.5.66
CVE-2005-0249	High	February 8, 2005 2/8/05	== 4.1-build_461 == 4.1-build_458 == 4.0 == 4.1-build_459 == 4.5_build_719

eset / mail_security

7 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2024-3779	Medium	July 16, 2024 7/16/24	<= 11.0.10008.0
CVE-2024-0353	High	February 15, 2024 2/15/24	>= 10.0 < 10.0.14007.0 >= 9.0 < 9.0.14008.0 >= 8.0 < 8.0.14014.0 < 7.3.14006.0 >= 10.1 < 10.1.10014.0 >= 10.0 < 10.0.10018.0 >= 9.0 < 9.0.10012.0 >= 8.0 < 8.0.10024.0 < 7.3.10018.0
CVE-2023-7043	Low	January 31, 2024 1/31/24	== 10.1.10012.0
CVE-2021-37851	High	May 11, 2022 5/11/22	>= 6.0 < 8.0.14011.0 >= 6.0 < 8.0.10020.0
CVE-2022-27167	High	May 10, 2022 5/10/22	>= 6.0 < 8.0.14011.0 >= 6.0 < 8.0.10020.0
CVE-2021-37852	High	February 9, 2022 2/9/22	>= 8.0 < 8.0.14006.0 >= 7.0.14008.0 < 7.3.14003.0 >= 8.0.10012.0 < 8.0.10018.0 >= 7.0.10019 < 7.3.10014.0
CVE-2020-26941	Medium	January 26, 2021 1/26/21	<= 7.2

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