Vulnerability Database

326,895

Total vulnerabilities in the database

Vulnerabilities for products matching "surgemail"

Found 1 matching product.

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

netwin / surgemail

17 vulnerabilities found
Title Severity Exploit Date Affected Version
Low September 17, 2012 9/17/12
== 6.0-a4
Low January 7, 2011 1/7/11
== 4.2d3-3
== 3.6f7
== 1.3d
== 1.1a
== 3.9g2
== 3.8s
== 3.0c2
== beta_3.9a
== 2.2a6
== 1.8e
== 3.7b
== 3.8d
== 3.9a
== 1.6e2
== 1.3i
== 1.3c
== 2.0g2
== 1.3b
== 3.8b
== 3.7b8
== 3.8i3
== 2.0e
== 3.8a
== 3.5b3
== 1.1d
== 3.8k3
== 1.3l
== 3.7b6
== 4.2a3-3
== 1.7b3
== 1.8f
== 3.9c
== 2.1a
== 1.5f
== 1.6e
== 2.0c
== 2.2g2
== 3.8f2
== 3.8m
== 3.8q
== 4.2d2-2
== 1.6d
== 3.7b3
== 3.8u
== 3.8f
== 1.4c
== 4.0k
== 1.3k
== 1.3a_rc1
== 1.5d2
== 4.0a
== 1.2a
== 3.2e
== 3.8k4
== 1.6a
== 3.8o
== 1.5a
== 1.3g
== 1.5c
== 1.0d
== 1.3f
== 1.3h
== 1.1c
== 1.2b
== 3.9g
== 1.5b
== 1.4b
== 4.0u3
== 1.1b
== 1.0c
== 2.2c10
== 4.2a2-3
== 4.0u4
== 3.6d
== 2.2g3
== 1.8d
<= 4.2d4-4
== 1.8b3
== 2.2c9
== 4.2d-1
== 1.7a
== 1.3a
== 3.7b7
== 1.4a
== 1.8g3
== 3.8i2
== 3.6f5
== 1.8a
== 1.9
== 2.0a2
== 3.8i
== 1.3j
== 3.7b5
== 3.8k
== 4.2a2-2
== 4.0v-8
== 2.1c7
== 3.8f3
== 3.1s
== 3.9e
== 1.6b
== 3.8k2
== 1.3e
== 3.5a
== 1.9b2
== 3.0a
== 1.5d
== 3.6f3
== 1.2c
Low September 8, 2009 9/8/09
== 3.9e
Medium June 25, 2008 6/25/08
== 3.8s
== 3.8d
== 3.9a
== 3.8b
== 3.8i3
== 3.8a
== 3.8k3
== 3.9c
<= 3.9g
== 3.8f2
== 3.8m
== 3.8q
== 3.8u
== 3.8f
== 3.8k4
== 3.8o
== 3.8i2
== 3.8i
== 3.8k
== 3.8f3
== 3.9e
== 3.8k2
High March 25, 2008 3/25/08
== 3.6f7
== 3.0c2
== 2.2a6
== 3.7b
== 3.8d
== 2.0g2
== 3.8b
== 3.7b8
== 3.8i3
== 2.0e
== 3.8a
== 3.5b3
== 3.8k3
== 3.7b6
== 2.0c
== 2.2g2
== 3.8f2
== 3.8m
== 3.7b3
== 3.8f
== 3.2e
== 2.2c10
== 3.6d
== 2.2g3
== 3.7b7
== 1.8g3
== 3.8i2
== 3.6f5
== 2.0a2
== 3.8i
== 3.7b5
== 3.8k
== 2.1c7
== 3.8f3
== 3.8k2
== 3.5a
== 1.9b2
== 3.0a
== 3.6f3
High March 25, 2008 3/25/08
<= 3.8k4
Medium February 27, 2008 2/27/08
== 3.0c2
== 2.2a6
== 1.8e
== 2.0g2
== 3.8i3
== 2.0e
== 2.1a
== 2.0c
== 2.2g2
== 38k
== 2.2c10
== 2.2g3
== 1.8d
== 38k4
== 1.8b3
== 2.2c9
== 1.8g3
== 3.8i2
== 1.8a
== 1.9
== 2.0a2
== 3.8i
== 2.1c7
== 3.8f3
== 3.1s
== 1.9b2
== 3.0a
High February 27, 2008 2/27/08
== 3.0c2
== 2.2a6
== 1.8e
== 39a
== 2.0g2
== 2.0e
== 2.1a
== beta_39a
== 2.0c
== 2.2g2
<= 38k4
== 2.2c10
== 2.2g3
== 1.8d
== 1.8b3
== 2.2c9
== 1.8g3
== 1.8a
== 1.9
== 2.0a2
== 2.1c7
== 3.8f3
== 1.9b2
== 3.0a
Medium December 20, 2007 12/20/07
== 38k4
High August 16, 2007 8/16/07
== 38k
Medium August 16, 2007 8/16/07
== 38k
High May 14, 2007 5/14/07
== 3.8i2
== 3.8i
== 3.8f3
Low May 24, 2005 5/24/05
== 3.0c2
Low May 2, 2005 5/2/05
== 2.2g3
High December 31, 2004 12/31/04
== 2.2a6
== 2.0g2
== 2.0e
== 1.8f
== 2.1a
== 2.0c
== 1.8d
== 1.8b3
== 1.8g3
== 1.8a
== 1.9
== 2.0a2
== 2.1c7
== 1.9b2
Low December 31, 2004 12/31/04
== 1.3d
== 1.1a
== 1.8e
== 1.6e2
== 1.3i
== 1.3c
== 1.3b
== 1.1d
== 1.3l
== 1.7b3
== 1.5f
== 1.6e
== 1.6d
== 1.4c
== 1.3k
== 1.3a_rc1
== 1.5d2
== 1.2a
== 1.6a
== 1.5a
== 1.3g
== 1.5c
== 1.0d
== 1.3f
== 1.3h
== 1.1c
== 1.2b
== 1.5b
== 1.4b
== 1.1b
== 1.0c
== 1.8d
== 1.8b3
== 1.7a
== 1.3a
== 1.4a
== 1.8g3
== 1.8a
== 2.0a2
== 1.3j
== 1.6b
== 1.3e
== 1.9b2
== 1.5d
== 1.2c
Low December 31, 2004 12/31/04
<= 2.0a2
== 1.8f
== 1.8d
== 1.8b3
== 1.8g3
== 1.8a
== 1.9
== 1.9b2

Frequently Asked Questions

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.