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.

383,304

Total vulnerabilities in the database

Vulnerabilities for products matching "epolicy_orchestrator"

Found 1 matching product.

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

mcafee / epolicy_orchestrator

86 vulnerabilities found

Title	Severity	Date	Affected versions
CVE-2023-5445	Medium	November 17, 2023 11/17/23	`< 5.10.0` `= 5.10.0-service_pack_1_update` `= 5.10.0-service_pack_1_update_1` `= 5.10.0-update_1` `= 5.10.0-update_10` `= 5.10.0-update_11` `= 5.10.0-update_11_hotfix_1` `= 5.10.0-update_11_hotfix_2` `= 5.10.0-update_12` `= 5.10.0-update_13` `= 5.10.0-update_14` `= 5.10.0-update_15` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2023-5444	High	November 17, 2023 11/17/23	`< 5.10.0` `= 5.10.0-service_pack_1_update` `= 5.10.0-service_pack_1_update_1` `= 5.10.0-update_1` `= 5.10.0-update_10` `= 5.10.0-update_11` `= 5.10.0-update_11_hotfix_1` `= 5.10.0-update_11_hotfix_2` `= 5.10.0-update_12` `= 5.10.0-update_13` `= 5.10.0-update_14` `= 5.10.0-update_15` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2023-3946	Medium	July 26, 2023 7/26/23	`< 5.10.0` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_10` `= 5.10.0-update_11` `= 5.10.0-update_11_hotfix_1` `= 5.10.0-update_11_hotfix_2` `= 5.10.0-update_12` `= 5.10.0-update_13` `= 5.10.0-update_14` `= 5.10.0-update_15` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2022-3338	Medium	October 18, 2022 10/18/22	`< 5.10.0` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_10` `= 5.10.0-update_11` `= 5.10.0-update_12` `= 5.10.0-update_13` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2022-3339	Medium	October 18, 2022 10/18/22	`< 5.10.0` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_10` `= 5.10.0-update_11` `= 5.10.0-update_12` `= 5.10.0-update_13` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2022-0857	Medium	March 23, 2022 3/23/22	`< 5.10.0` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_10` `= 5.10.0-update_11` `= 5.10.0-update_12` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2022-0858	Medium	March 23, 2022 3/23/22	`< 5.10.0` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_10` `= 5.10.0-update_11` `= 5.10.0-update_12` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2022-0859	Medium	March 23, 2022 3/23/22	`< 5.10.0` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_10` `= 5.10.0-update_11` `= 5.10.0-update_12` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2022-0861	Low	March 23, 2022 3/23/22	`< 5.10.0` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_10` `= 5.10.0-update_11` `= 5.10.0-update_12` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2022-0862	Low	March 23, 2022 3/23/22	`< 5.10.0` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_10` `= 5.10.0-update_11` `= 5.10.0-update_12` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2022-0842	Medium	March 23, 2022 3/23/22	`< 5.10.0` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_10` `= 5.10.0-update_11` `= 5.10.0-update_12` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2021-31834	Medium	October 22, 2021 10/22/21	`< 5.10.0` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_10` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2021-31835	Medium	October 22, 2021 10/22/21	`< 5.10.0` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_10` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2021-3712	High	August 24, 2021 8/24/21	`< 5.10.0` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_10` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2021-2432	Low	July 21, 2021 7/21/21	`< 5.10.0` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_10` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2021-30639	High	July 12, 2021 7/12/21	`< 5.10.0` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_10` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2021-33037	Medium	July 12, 2021 7/12/21	`< 5.10.0` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_10` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2020-13938	Medium	June 10, 2021 6/10/21	`< 5.10.0` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_10` `= 5.10.0-update_11` `= 5.10.0-update_12` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2021-2161	Medium	April 22, 2021 4/22/21	`< 5.10.0` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_10` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2021-23889	Low	March 26, 2021 3/26/21	`< 5.10.0` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2021-23890	Medium	March 26, 2021 3/26/21	`< 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2021-23888	Medium	March 26, 2021 3/26/21	`< 5.10.0` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2021-23840	High	February 16, 2021 2/16/21	`< 5.10.0` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_10` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8` `= 5.10.0-update_9`
CVE-2020-14792	Medium	October 21, 2020 10/21/20	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6`
CVE-2020-14782	Low	October 21, 2020 10/21/20	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6`
CVE-2020-7317	Medium	October 14, 2020 10/14/20	`<= 5.9.1` `>= 5.10.0, <= 5.10.9`
CVE-2020-7318	Medium	October 14, 2020 10/14/20	`>= 5.10.0, <= 5.10.9`
CVE-2020-14621	Medium	July 15, 2020 7/15/20	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8`
CVE-2020-14581	Low	July 15, 2020 7/15/20	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8`
CVE-2020-14578	Low	July 15, 2020 7/15/20	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8`
CVE-2020-14579	Low	July 15, 2020 7/15/20	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8`
CVE-2020-13935	High	July 14, 2020 7/14/20	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8`
CVE-2020-9484	High	May 20, 2020 5/20/20	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3`
CVE-2020-2773	Low	April 15, 2020 4/15/20	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8`
CVE-2020-2754	Low	April 15, 2020 4/15/20	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8`
CVE-2020-2755	Low	April 15, 2020 4/15/20	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8`
CVE-2020-2756	Low	April 15, 2020 4/15/20	`>= 5.9.0, < 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8`
CVE-2020-2757	Low	April 15, 2020 4/15/20	`>= 5.9.0, < 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6` `= 5.10.0-update_7` `= 5.10.0-update_8`
CVE-2020-2654	Low	January 15, 2020 1/15/20	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6`
CVE-2020-2604	High	January 15, 2020 1/15/20	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6`
CVE-2020-2583	Low	January 15, 2020 1/15/20	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6`
CVE-2020-2590	Low	January 15, 2020 1/15/20	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6`
CVE-2020-2593	Medium	January 15, 2020 1/15/20	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6`
CVE-2019-2975	Medium	October 16, 2019 10/16/19	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6`
CVE-2019-2949	Medium	October 16, 2019 10/16/19	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6`
CVE-2019-2933	Low	October 16, 2019 10/16/19	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6`
CVE-2019-2894	Low	October 16, 2019 10/16/19	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4` `= 5.10.0-update_5` `= 5.10.0-update_6`
CVE-2019-2842	Low	July 23, 2019 7/23/19	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4`
CVE-2019-2816	Medium	July 23, 2019 7/23/19	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4`
CVE-2019-2766	Low	July 23, 2019 7/23/19	`= 5.9.0` `= 5.9.1` `= 5.10.0` `= 5.10.0-update_1` `= 5.10.0-update_2` `= 5.10.0-update_3` `= 5.10.0-update_4`

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.