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,505

Total vulnerabilities in the database

Vulnerabilities for products matching "exchange_server"

Found 1 matching product.

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

microsoft / exchange_server

1403 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2020-16969	High	October 16, 2020 10/16/20	== 2013-cumulative_update_23 == 2019-cumulative_update_6 == 2016-cumulative_update_17 == 2019-cumulative_update_7 == 2016-cumulative_update_18
CVE-2020-16875	High	September 11, 2020 9/11/20	== 2019-cumulative_update_6 == 2019-cumulative_update_5 == 2016-cumulative_update_17 == 2016-cumulative_update_16
CVE-2020-0903	Medium	March 12, 2020 3/12/20	== 2016-cumulative_update_14 == 2019-cumulative_update_3 == 2019-cumulative_update_4 == 2016-cumulative_update_15
CVE-2020-0692	High	February 11, 2020 2/11/20	== 2013-cumulative_update_23 == 2016-cumulative_update_14 == 2019-cumulative_update_3 == 2019-cumulative_update_4 == 2016-cumulative_update_15
CVE-2020-0688	High	February 11, 2020 2/11/20	== 2013-cumulative_update_23 == 2016-cumulative_update_14 == 2019-cumulative_update_3 == 2019-cumulative_update_4 == 2016-cumulative_update_15 == 2010-sp3_rollup_30
CVE-2019-1373	Critical	November 12, 2019 11/12/19	== 2013-cumulative_update_23 == 2016-cumulative_update_13 == 2019-cumulative_update_2 == 2016-cumulative_update_14 == 2019-cumulative_update_3
CVE-2019-1266	Medium	September 11, 2019 9/11/19	== 2016-cumulative_update_12 == 2019-cumulative_update_1 == 2016-cumulative_update_13 == 2019-cumulative_update_2
CVE-2019-1233	High	September 11, 2019 9/11/19	== 2016-cumulative_update_12 == 2019-cumulative_update_1 == 2016-cumulative_update_13 == 2019-cumulative_update_2
CVE-2019-1136	Medium	July 15, 2019 7/15/19	== 2010-sp3 == 2013-cumulative_update_13 == 2013-cumulative_update_12 == 2013-cumulative_update_23
CVE-2019-1137	Medium	July 15, 2019 7/15/19	== 2013-cumulative_update_7 == 2013-cumulative_update_3 == 2013-cumulative_update_17 == 2013-cumulative_update_13 == 2013-cumulative_update_8 == 2013-sp1 == 2013-cumulative_update_12 == 2013-cumulative_update_16 == 2013-cumulative_update_2 == 2013-cumulative_update_10 == 2013-cumulative_update_11 == 2013-cumulative_update_9 == 2013-cumulative_update_14 == 2013-cumulative_update_6 == 2013-cumulative_update_18 == 2013-cumulative_update_19 == 2013-cumulative_update_20 == 2013-cumulative_update_21 == 2013-cumulative_update_22 == 2013-cumulative_update_23 == 2013-cumulative_update_1 == 2013-cumulative_update_15 == 2013-cumulative_update_5 == 2013 == 2016-cumulative_update_6 == 2016-cumulative_update_1 == 2016-cumulative_update_5 == 2016-cumulative_update_2 == 2016-cumulative_update_7 == 2016-cumulative_update_8 == 2016-cumulative_update_9 == 2016-cumulative_update_10 == 2016-cumulative_update_11 == 2016-cumulative_update_12 == 2016-cumulative_update_13 == 2016 == 2016-cumulative_update_3 == 2016-cumulative_update_4 == 2019-cumulative_update_1 == 2019-cumulative_update_2 == 2019
CVE-2019-1084	Low	July 15, 2019 7/15/19	== 2016-cumulative_update_1 == 2016-cumulative_update_2 == 2010-sp2 == 2016-cumulative_update_12 == 2013-cumulative_update_23 == 2016-cumulative_update_13
CVE-2019-0858	Medium	April 9, 2019 4/9/19	== 2016-cumulative_update_11 == 2013-cumulative_update_22 == 2016-cumulative_update_12 == 2019-cumulative_update_1 == 2019
CVE-2019-0817	Medium	April 9, 2019 4/9/19	== 2010-sp3 == 2016-cumulative_update_11 == 2013-cumulative_update_22 == 2016-cumulative_update_12 == 2019-cumulative_update_1 == 2019
CVE-2019-0686	Medium	March 5, 2019 3/5/19	== 2010-sp3_rollup26 == 2013-cumulative_update_22 == 2016-cumulative_update_12 == 2019-cumulative_update_1
CVE-2019-0724	High	March 5, 2019 3/5/19	== 2013-cumulative_update_22 == 2016-cumulative_update_12 == 2019-cumulative_update_1 == 2010-sp3_rollup_26
CVE-2019-0586	Critical	January 8, 2019 1/8/19	== 2016-cumulative_update_10 == 2016-cumulative_update_11 == 2019
CVE-2019-0588	Medium	January 8, 2019 1/8/19	== 2013-cumulative_update_21 == 2016-cumulative_update_10 == 2016-cumulative_update_11 == 2010-sp3_rollup25 == 2019
CVE-2018-8604	Low	December 12, 2018 12/12/18	== 2016-cumulative_update_10 == 2016-cumulative_update_11
CVE-2018-8581	High	November 14, 2018 11/14/18	== 2016 == 2019 == 2013 == 2010
CVE-2018-8448	Medium	October 10, 2018 10/10/18	== 2013-cumulative_update_21 == 2016-cumulative_update_10
CVE-2018-8265	High	October 10, 2018 10/10/18	== 2013-cumulative_update_21 == 2016-cumulative_update_10
CVE-2018-16793	Medium	September 21, 2018 9/21/18	== 2010-sp3_rollup1 == 2010-sp3_rollup2 == 2010-sp3_rollup3 == 2010-sp3_rollup4 == 2010-sp3_rollup5 == 2010-sp3_rollup6 == 2010-sp3_rollup7 == 2010-sp3_rollup8 == 2010-sp3_rollup9 == 2010-sp3_rollup10 == 2010-sp3_rollup11 == 2010-sp3_rollup12 == 2010-sp3_rollup13 == 2010-sp3_rollup14 == 2010-sp3_rollup15 == 2010-sp3_rollup16 == 2010-sp3_rollup17 == 2010-sp3_rollup18
CVE-2018-8374	Low	August 15, 2018 8/15/18	== 2016-cumulative_update_9 == 2016-cumulative_update_10
CVE-2018-8302	High	August 15, 2018 8/15/18	== 2010-sp3 == 2016-cumulative_update_9 == 2013-cumulative_update_20 == 2013-cumulative_update_21 == 2016-cumulative_update_10
CVE-2018-8151	Low	May 9, 2018 5/9/18	== 2010-sp3 == 2013-sp1 == 2016-cumulative_update_8 == 2013-cumulative_update_19 == 2016-cumulative_update_9 == 2013-cumulative_update_20
CVE-2018-8152	Medium	May 9, 2018 5/9/18	== 2016-cumulative_update_8 == 2016-cumulative_update_9
CVE-2018-8153	Medium	May 9, 2018 5/9/18	== 2016-cumulative_update_8 == 2016-cumulative_update_9
CVE-2018-8154	High	May 9, 2018 5/9/18	== 2010-sp3 == 2013-sp1 == 2016-cumulative_update_8 == 2013-cumulative_update_19 == 2016-cumulative_update_9 == 2013-cumulative_update_20
CVE-2018-8159	Medium	May 9, 2018 5/9/18	== 2016-cumulative_update_8 == 2013-cumulative_update_19 == 2016-cumulative_update_9 == 2013-cumulative_update_20
CVE-2018-0986	High	April 4, 2018 4/4/18	== 2016 == 2013
CVE-2018-0924	Low	March 14, 2018 3/14/18	== 2013-sp1 == 2016-cumulative_update_7 == 2016-cumulative_update_8 == 2013-cumulative_update_18 == 2013-cumulative_update_19 == 2010-sp3_rollup20
CVE-2018-0940	Low	March 14, 2018 3/14/18	== 2013-sp1 == 2016-cumulative_update_7 == 2016-cumulative_update_8 == 2013-cumulative_update_18 == 2013-cumulative_update_19 == 2010-sp3_rollup20
CVE-2018-0941	Low	March 14, 2018 3/14/18	== 2016-cumulative_update_7 == 2016-cumulative_update_8
CVE-2017-11932	Medium	December 12, 2017 12/12/17	== 2016-cumulative_update_6 == 2016-cumulative_update_7
CVE-2017-8758	Medium	September 13, 2017 9/13/17	== 2016
CVE-2017-11761	Medium	September 13, 2017 9/13/17	== 2013-cumulative_update_17 == 2016-cumulative_update_6 == 2013-sp1 == 2013-cumulative_update_16 == 2016-cumulative_update_5
CVE-2017-8621	Medium	July 11, 2017 7/11/17	== 2010-sp3 == 2013-sp1 == 2013-cumulative_update_16 == 2016-cumulative_update_5
CVE-2017-8559	Low	July 11, 2017 7/11/17	== 2013-sp1 == 2013-cumulative_update_16 == 2016-cumulative_update_5
CVE-2017-8560	Low	July 11, 2017 7/11/17	== 2013-sp1 == 2013-cumulative_update_16 == 2016-cumulative_update_5
CVE-2017-8535	Medium	May 26, 2017 5/26/17	== 2016 == 2013
CVE-2017-8536	Medium	May 26, 2017 5/26/17	== 2016 == 2013
CVE-2017-8537	Medium	May 26, 2017 5/26/17	== 2016 == 2013
CVE-2017-8540	High	May 26, 2017 5/26/17	== 2016 == 2013
CVE-2017-0110	Low	March 17, 2017 3/17/17	== 2013-cumulative_update_3 == 2013-sp1 == 2013-cumulative_update_14
CVE-2016-3379	Low	September 14, 2016 9/14/16	== 2016-cumulative_update_1 == 2016-cumulative_update_2
CVE-2016-3378	Medium	September 14, 2016 9/14/16	== 2013-cumulative_update_13 == 2016-cumulative_update_1 == 2013-sp1 == 2013-cumulative_update_12 == 2016-cumulative_update_2
CVE-2016-0138	Low	September 14, 2016 9/14/16	== 2010-sp3 == 2013-cumulative_update_13 == 2016-cumulative_update_1 == 2007-sp3 == 2013-sp1 == 2013-cumulative_update_12 == 2016-cumulative_update_2
CVE-2016-0032	Medium	January 13, 2016 1/13/16	== 2013-sp1 == 2013-cumulative_update_10 == 2013-cumulative_update_11 == 2016
CVE-2016-0031	Medium	January 13, 2016 1/13/16	== 2016
CVE-2016-0030	Medium	January 13, 2016 1/13/16	== 2013-sp1 == 2013-cumulative_update_10 == 2016

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.