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

Found 4 matching products. Filters apply to all results.

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

lotus / domino

12 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2002-2191	Medium	December 31, 2002 12/31/02	== 5.0.9 == 5.0.9a == 5.0.8
CVE-2002-0407	Medium	July 26, 2002 7/26/02	<= 5.0.9a
CVE-2002-0408	Medium	July 26, 2002 7/26/02	<= 5.0.9a
CVE-2002-0245	High	May 29, 2002 5/29/02	== 5.0.6a == 5.0.6 == 5.0.4 == 5.0.9 == 5.0.7a == 5.0.1 == 5.0.4a == 5.0.3 == 5.0.2 == 5.0.5 == 5.0.7 == 5.0 == 5.0.8
CVE-2002-0087	Low	March 15, 2002 3/15/02	== 5.0.7
CVE-2001-0954	Medium	December 7, 2001 12/7/01	== 5.0.5 == 5.0.8
CVE-2001-0846	High	December 6, 2001 12/6/01	== 5.0.6a == 5.0.6 == 5.0.4 == 5.0.7a == 5.0.1 == 5.0.2c == 5.0.4a == 5.0.3 == 5.0.2 == 5.0.2a == 5.0.5 == 5.0.7 == 5.0 == 5.0.8
CVE-2001-0939	Medium	November 30, 2001 11/30/01	== 5.0.6 == 5.0.4 == 5.0.1 == 5.0.3 == 5.0.2 == 5.0.5 == 5.0.7 == 5.0 == 5.0.8
CVE-2001-1018	Medium	September 20, 2001 9/20/01	== 5.0.8
CVE-2000-1203	Medium	August 20, 2001 8/20/01	== 4.6.1 == 5.0.6 == 5.0.4 == 4.6.4 == 5.0.1 == 5.0.3 == 4.6.3 == 5.0.2 == 5.0.5 == 5.0.7 == 5.0.8
CVE-2000-1046	High	December 11, 2000 12/11/00	== 5.0.2c == 5.0.2a
CVE-1999-1012	Medium	May 4, 1999 5/4/99	== 4.6.1

ibm / domino

27 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2012-6277	High	February 21, 2020 2/21/20	>= 8.5.0 <= 8.5.3.6
CVE-2018-1771	High	December 20, 2018 12/20/18	== 9.0.0.0-if1 == 9.0.0.0-if2 == 9.0.0.0-if3 == 9.0.0.0-if4 == 9.0.1.10-if2 == 9.0.1.10-if3 == 9.0.1.10-if4 == 9.0.1.10-if1 >= 9.0.1.0 <= 9.0.1.10
CVE-2016-6087	Critical	June 7, 2017 6/7/17	== 8.5.1.4 == 8.5.3.6 == 9.0.1.1 == 8.5.3.0 == 9.0.1.2 == 8.5.3.5 == 8.5.1.1 == 8.5.3.1 == 9.0.1.5 == 8.5.1.2 == 8.5.3.4 == 9.0.1.7 == 8.5.2.4 == 9.0.0.0 == 8.5.1.3 == 9.0.1.4 == 8.5.2.2 == 9.0.1.0 == 8.5.2.0 == 8.5.3.2 == 8.5.2.3 == 9.0.1.6 == 9.0.1.3 == 8.5.2.1 == 8.5.1.5 == 8.5.1.0 == 8.5.3.3
CVE-2017-1274	Medium	April 25, 2017 4/25/17	== 8.5.3.6 == 9.0.1 == 9.0.1.8 == 9.0.0.0 == 8.5.3
CVE-2016-0270	Low	February 8, 2017 2/8/17	== 9.0.1.5 == 9.0.1.4 == 9.0.1.3
CVE-2016-6113	Low	February 1, 2017 2/1/17	== 8.5.1.0 == 8.5.1.1 == 8.5.1.2 == 8.5.1.3 == 8.5.1.4 == 8.5.1.5 == 8.5.2.0 == 8.5.2.1 == 8.5.2.2 == 8.5.2.3 == 8.5.2.4 == 8.5.3.0 == 8.5.3.1 == 8.5.3.2 == 8.5.3.3 == 8.5.3.4 == 8.5.3.5 == 8.5.3.6 == 9.0.0.0 == 9.0.1.0 == 9.0.1.1 == 9.0.1.2 == 9.0.1.3 == 9.0.1.4 == 9.0.1.5 == 9.0.1.6
CVE-2016-2938	Low	February 1, 2017 2/1/17	== 8.5.1.0 == 8.5.1.1 == 8.5.1.2 == 8.5.1.3 == 8.5.1.4 == 8.5.1.5 == 8.5.2.0 == 8.5.2.1 == 8.5.2.2 == 8.5.2.3 == 8.5.2.4 == 8.5.3.0 == 8.5.3.1 == 8.5.3.2 == 8.5.3.3 == 8.5.3.4 == 8.5.3.5 == 8.5.3.6 == 9.0.0.0 == 9.0.1.0 == 9.0.1.1 == 9.0.1.2 == 9.0.1.3 == 9.0.1.4 == 9.0.1.5 == 9.0.1.6
CVE-2016-2939	Low	February 1, 2017 2/1/17	== 8.5.1.0 == 8.5.1.1 == 8.5.1.2 == 8.5.1.3 == 8.5.1.4 == 8.5.1.5 == 8.5.2.0 == 8.5.2.1 == 8.5.2.2 == 8.5.2.3 == 8.5.2.4 == 8.5.3.0 == 8.5.3.1 == 8.5.3.2 == 8.5.3.3 == 8.5.3.4 == 8.5.3.5 == 8.5.3.6 == 9.0.0.0 == 9.0.1.0 == 9.0.1.1 == 9.0.1.2 == 9.0.1.3 == 9.0.1.4 == 9.0.1.5 == 9.0.1.6
CVE-2016-5880	Low	February 1, 2017 2/1/17	== 8.5.1.0 == 8.5.1.1 == 8.5.1.2 == 8.5.1.3 == 8.5.1.4 == 8.5.1.5 == 8.5.2.0 == 8.5.2.1 == 8.5.2.2 == 8.5.2.3 == 8.5.2.4 == 8.5.3.0 == 8.5.3.1 == 8.5.3.2 == 8.5.3.3 == 8.5.3.4 == 8.5.3.5 == 8.5.3.6 == 9.0.0.0 == 9.0.1.0 == 9.0.1.1 == 9.0.1.2 == 9.0.1.3 == 9.0.1.4 == 9.0.1.5 == 9.0.1.6
CVE-2016-5882	Low	February 1, 2017 2/1/17	== 8.5.1.0 == 8.5.1.1 == 8.5.1.2 == 8.5.1.3 == 8.5.1.4 == 8.5.1.5 == 8.5.2.0 == 8.5.2.1 == 8.5.2.2 == 8.5.2.3 == 8.5.2.4 == 8.5.3.0 == 8.5.3.1 == 8.5.3.2 == 8.5.3.3 == 8.5.3.4 == 8.5.3.5 == 8.5.3.6 == 9.0.0.0 == 9.0.1.0 == 9.0.1.1 == 9.0.1.2 == 9.0.1.3 == 9.0.1.4 == 9.0.1.5 == 9.0.1.6
CVE-2016-5884	Low	February 1, 2017 2/1/17	== 8.5.1.0 == 8.5.1.1 == 8.5.1.2 == 8.5.1.3 == 8.5.1.4 == 8.5.1.5 == 8.5.2.0 == 8.5.2.1 == 8.5.2.2 == 8.5.2.3 == 8.5.2.4 == 8.5.3.0 == 8.5.3.1 == 8.5.3.2 == 8.5.3.3 == 8.5.3.4 == 8.5.3.5 == 8.5.3.6 == 9.0.0.0 == 9.0.1.0 == 9.0.1.1 == 9.0.1.2 == 9.0.1.3 == 9.0.1.4 == 9.0.1.5 == 9.0.1.6
CVE-2016-0304	Medium	June 29, 2016 6/29/16	== 8.5.3.6 == 8.5.3.5 == 8.5.3.1 == 8.5.3.4 == 8.5.3 == 8.5.3.2 == 8.5.3.3 == 8.5.2.4 == 8.5.2.2 == 8.5.2.3 == 8.5.2.1 == 8.5.2 == 8.5.1.4 == 8.5.1.1 == 8.5.1.2 == 8.5.1 == 8.5.1.3 == 8.5.1.5 == 8.5.0 == 9.0.1.1 == 9.0.1.2 == 9.0.1 == 9.0.1.5 == 9.0.1.4 == 9.0.1.3
CVE-2016-0301	Medium	June 26, 2016 6/26/16	== 8.5.0 == 8.5.1 == 8.5.1.1 == 8.5.1.2 == 8.5.1.3 == 8.5.1.4 == 8.5.2 == 8.5.2.1 == 8.5.2.2 == 8.5.2.3 == 8.5.3 == 8.5.3.1 == 8.5.3.2 == 8.5.3.3 == 8.5.3.4 == 8.5.3.5 == 9.0.1 == 9.0.1.1 == 9.0.1.2 == 9.0.1.3 == 9.0.1.4 == 9.0.1.5
CVE-2016-0279	Medium	June 26, 2016 6/26/16	== 8.5.0 == 8.5.1 == 8.5.1.1 == 8.5.1.2 == 8.5.1.3 == 8.5.1.4 == 8.5.2 == 8.5.2.1 == 8.5.2.2 == 8.5.2.3 == 8.5.3 == 8.5.3.1 == 8.5.3.2 == 8.5.3.3 == 8.5.3.4 == 8.5.3.5 == 9.0.1 == 9.0.1.1 == 9.0.1.2 == 9.0.1.3 == 9.0.1.4 == 9.0.1.5
CVE-2016-0278	Medium	June 26, 2016 6/26/16	== 8.5.0 == 8.5.1 == 8.5.1.1 == 8.5.1.2 == 8.5.1.3 == 8.5.1.4 == 8.5.2 == 8.5.2.1 == 8.5.2.2 == 8.5.2.3 == 8.5.3 == 8.5.3.1 == 8.5.3.2 == 8.5.3.3 == 8.5.3.4 == 8.5.3.5 == 9.0.1 == 9.0.1.1 == 9.0.1.2 == 9.0.1.3 == 9.0.1.4 == 9.0.1.5
CVE-2016-0277	Medium	June 26, 2016 6/26/16	== 8.5.0 == 8.5.1 == 8.5.1.1 == 8.5.1.2 == 8.5.1.3 == 8.5.1.4 == 8.5.2 == 8.5.2.1 == 8.5.2.2 == 8.5.2.3 == 8.5.3 == 8.5.3.1 == 8.5.3.2 == 8.5.3.3 == 8.5.3.4 == 8.5.3.5 == 9.0.1 == 9.0.1.1 == 9.0.1.2 == 9.0.1.3 == 9.0.1.4 == 9.0.1.5
CVE-2015-5040	High	October 29, 2015 10/29/15	== 8.5.1.4 == 8.5.3.6 == 9.0.1.1 == 8.5.0.1 == 9.0.1.2 == 8.5.3.5 == 9.0.1 == 8.5.1.1 == 8.5.3.1 == 8.5.0 == 8.5.1.2 == 8.5.3.4 == 8.5.2.4 == 8.5.1 == 8.5.1.3 == 9.0.1.4 == 8.5.2.2 == 8.5.3 == 8.5.3.2 == 8.5.2.3 == 9.0.1.3 == 8.5.2.1 == 8.5.1.5 == 8.5.2 == 8.5.3.3
CVE-2015-4994	High	October 29, 2015 10/29/15	== 9.0.1 == 8.5.0 == 8.5.1 == 8.5.3 == 8.5.2
CVE-2015-2015	Low	August 23, 2015 8/23/15	<= 8.5.3
CVE-2015-2014	Medium	August 23, 2015 8/23/15	== 9.0.1 == 8.5.0 == 8.5.1 == 8.5.3 == 8.5.2
CVE-2015-1981	Low	June 28, 2015 6/28/15	== 9.0.1 == 8.5.0 == 8.5.1 == 8.5.3 == 8.5.2
CVE-2015-1903	High	May 20, 2015 5/20/15	== 9.0.1 == 8.5.0 == 8.5.1 == 8.5.3 == 8.5.2
CVE-2015-1902	High	May 20, 2015 5/20/15	== 9.0.1 == 8.5.0 == 8.5.1 == 8.5.3 == 8.5.2
CVE-2015-0135	High	April 21, 2015 4/21/15	== 9.0.1 == 8.5.0 == 8.5.1 == 8.5.2
CVE-2015-0179	High	April 6, 2015 4/6/15	== 9.0.1 == 8.5.0 == 8.5.1 == 8.5.3 == 8.5.2
CVE-2015-0134	High	April 6, 2015 4/6/15	== 9.0.1 == 8.5.0 == 8.5.1 == 8.5.3 == 8.5.2
CVE-2015-0117	High	April 6, 2015 4/6/15	== 9.0.1 == 8.5.0 == 8.5.1 == 8.5.3 == 8.5.2

hcltech / domino

22 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2024-23562	Medium	July 8, 2024 7/8/24	== 11.0 == 12.0 == 14.0
CVE-2023-37539	High	June 6, 2024 6/6/24	== 11.0 == 12.0 == 14.0
CVE-2023-37495	Medium	February 29, 2024 2/29/24	>= 9.0 < 14.0
CVE-2023-28010	Low	September 8, 2023 9/8/23	== 12.0.2 == 12.0.2-fixpack_1
CVE-2022-44754	Critical	December 19, 2022 12/19/22	== 9.0.1 == 9.0.1-feature_pack_10_interim_fix_3 == 9.0.1-feature_pack_10_interim_fix_4 == 9.0.1-feature_pack_8 == 9.0.1-feature_pack_8_interim_fix_1 == 9.0.1-feature_pack_8_interim_fix_2 == 9.0.1-feature_pack_8_interim_fix_3 == 9.0.1-feature_pack_10_interim_fix_5 == 9.0 == 9.0.1-fixpack_10 == 9.0.1-fixpack_3 == 9.0.1-fixpack_4 == 9.0.1-fixpack_5 == 9.0.1-fixpack_6 == 9.0.1-fixpack_7 == 9.0.1-fixpack_8 == 9.0.1-fixpack_9
CVE-2022-44750	Critical	December 19, 2022 12/19/22	== 9.0.1 == 9.0.1-feature_pack_10_interim_fix_3 == 9.0.1-feature_pack_10_interim_fix_4 == 9.0.1-feature_pack_8 == 9.0.1-feature_pack_8_interim_fix_1 == 9.0.1-feature_pack_8_interim_fix_2 == 9.0.1-feature_pack_8_interim_fix_3 == 9.0.1-feature_pack_10_interim_fix_5 == 9.0 == 9.0.1-fixpack_10 == 9.0.1-fixpack_3 == 9.0.1-fixpack_4 == 9.0.1-fixpack_5 == 9.0.1-fixpack_6 == 9.0.1-fixpack_7 == 9.0.1-fixpack_8 == 9.0.1-fixpack_9
CVE-2022-44752	Critical	December 19, 2022 12/19/22	== 9.0.1 == 9.0.1-feature_pack_10_interim_fix_3 == 9.0.1-feature_pack_10_interim_fix_4 == 9.0.1-feature_pack_8 == 9.0.1-feature_pack_8_interim_fix_1 == 9.0.1-feature_pack_8_interim_fix_2 == 9.0.1-feature_pack_8_interim_fix_3 == 9.0.1-feature_pack_10_interim_fix_5 == 9.0 == 9.0.1-fixpack_10 == 9.0.1-fixpack_3 == 9.0.1-fixpack_4 == 9.0.1-fixpack_5 == 9.0.1-fixpack_6 == 9.0.1-fixpack_7 == 9.0.1-fixpack_8 == 9.0.1-fixpack_9
CVE-2022-38654	Medium	November 4, 2022 11/4/22	== 10.0.1 == 9.0.1 == 9.0.1-feature_pack_10_interim_fix_3 == 9.0.1-feature_pack_10_interim_fix_4 == 9.0.1-feature_pack_8 == 9.0.1-feature_pack_8_interim_fix_1 == 9.0.1-feature_pack_8_interim_fix_2 == 9.0.1-feature_pack_8_interim_fix_3 == 9.0.1-feature_pack_10_interim_fix_5 == 11.0.1 == 10.0.0 == 9.0.1-fixpack_3 == 9.0.1-fixpack_4 == 9.0.1-fixpack_5 == 9.0.1-fixpack_6 == 9.0.1-fixpack_7 == 9.0.1-fixpack_8 == 9.0.1-fixpack_9 == 10.0.1-fixpack_1 == 10.0.1-fixpack_2 == 10.0.1-fixpack_3 == 10.0.1-fixpack_4 == 10.0.1-fixpack_5 == 10.0.1-fixpack_6 == 10.0.1-fixpack_7 == 11.0.1-fixpack_1 == 11.0.1-fixpack_2 == 11.0.1-fixpack_3 == 11.0.1-fixpack_4 == 11.0.1-fixpack_5 == 12.0
CVE-2022-38660	High	November 4, 2022 11/4/22	< 9.0.1 == 9.0.1-feature_pack_10_interim_fix_3 == 9.0.1-feature_pack_10_interim_fix_4 == 9.0.1-feature_pack_8 == 9.0.1-feature_pack_8_interim_fix_1 == 9.0.1-feature_pack_8_interim_fix_2 == 9.0.1-feature_pack_8_interim_fix_3 == 9.0.1-feature_pack_10_interim_fix_5
CVE-2022-27546	High	August 29, 2022 8/29/22	== 10.0.1 == 9.0.1 == 11.0 == 11.0.1 == 9.0 == 10.0 == 9.0.1-fixpack_10 == 9.0.1-fixpack_3 == 9.0.1-fixpack_4 == 9.0.1-fixpack_5 == 9.0.1-fixpack_6 == 9.0.1-fixpack_7 == 9.0.1-fixpack_8 == 9.0.1-fixpack_9 == 10.0.1-fixpack_1 == 10.0.1-fixpack_2 == 10.0.1-fixpack_3 == 10.0.1-fixpack_4 == 10.0.1-fixpack_5 == 10.0.1-fixpack_6 == 10.0.1-fixpack_7 == 10.0.1-fixpack_8 == 11.0.1-fixpack_1 == 11.0.1-fixpack_2 == 11.0.1-fixpack_3 == 11.0.1-fixpack_4 == 11.0.1-fixpack_5 == 12.0 == 12.0.1 == 12.0.1-fixpack_1
CVE-2022-27547	Medium	August 29, 2022 8/29/22	== 10.0.1 == 9.0.1 == 11.0 == 11.0.1 == 9.0 == 10.0 == 9.0.1-fixpack_10 == 9.0.1-fixpack_3 == 9.0.1-fixpack_4 == 9.0.1-fixpack_5 == 9.0.1-fixpack_6 == 9.0.1-fixpack_7 == 9.0.1-fixpack_8 == 9.0.1-fixpack_9 == 10.0.1-fixpack_1 == 10.0.1-fixpack_2 == 10.0.1-fixpack_3 == 10.0.1-fixpack_4 == 10.0.1-fixpack_5 == 10.0.1-fixpack_6 == 10.0.1-fixpack_7 == 10.0.1-fixpack_8 == 11.0.1-fixpack_1 == 11.0.1-fixpack_2 == 11.0.1-fixpack_3 == 11.0.1-fixpack_4 == 11.0.1-fixpack_5 == 12.0 == 12.0.1 == 12.0.1-fixpack_1
CVE-2022-27558	Medium	August 29, 2022 8/29/22	== 12.0.1 == 12.0.1-fixpack_1
CVE-2020-4107	High	May 19, 2022 5/19/22	== 11.0 == 9.0 == 10.0
CVE-2020-14273	High	December 28, 2020 12/28/20	== 10.0.1-fix_pack_1 == 10.0.1-fix_pack_2 == 10.0.1-fix_pack_3 == 10.0.1-fix_pack_4 == 10.0.1 == 11.0.1 == 10.0.1-fix_pack_5 == 11.0.1-fix_pack_1 == 11.0.0
CVE-2020-14270	Medium	December 22, 2020 12/22/20	== 10.0.1-fix_pack_1 == 10.0.1-fix_pack_2 == 10.0.1-fix_pack_3 == 10.0.1-fix_pack_4 == 10.0.1 >= 9.0.0 <= 10.0.0 == 11.0.1 == 11.0.0
CVE-2020-4080	Medium	December 18, 2020 12/18/20	== 10.0.1-fix_pack_1 == 10.0.1-fix_pack_2 == 10.0.1-fix_pack_3 == 10.0.1-fix_pack_4 == 10.0.1 == 11.0 == 11.0.1 == 10.0.1-fix_pack_5 == 11.0.1-fix_pack_1 == 10.0.0
CVE-2020-14244	Critical	December 14, 2020 12/14/20	== 10.0.1-fix_pack_1 == 10.0.1-fix_pack_2 == 10.0.1-fix_pack_3 >= 9.0.0 < 10.0.1
CVE-2020-14260	Critical	December 2, 2020 12/2/20	>= 11.0.0 <= 11.0.1 >= 10.0.0 <= 10.0.1 >= 9.0.0 <= 9.0.1
CVE-2020-4128	Medium	December 1, 2020 12/1/20	== 10.0.1-fix_pack_1 == 10.0.1-fix_pack_2 == 10.0.1-fix_pack_3 == 10.0.1-fix_pack_4 == 10.0.1 >= 11.0.0 <= 11.0.1 >= 10.0.0 <= 10.0.1 >= 9.0.0 <= 9.0.1
CVE-2020-14230	High	November 21, 2020 11/21/20	< 9.0.1 == 10.0.1-fix_pack_1 == 10.0.1-fix_pack_2 == 10.0.1-fix_pack_3 == 10.0.1-fix_pack_4 == 10.0.1 >= 10.0.0 < 10.0.1 == 9.0.1 == 9.0.1-feature_pack_10_interim_fix_3 == 9.0.1-feature_pack_10_interim_fix_4 == 9.0.1-feature_pack_8 == 9.0.1-feature_pack_8_interim_fix_1 == 9.0.1-feature_pack_8_interim_fix_2 == 9.0.1-feature_pack_8_interim_fix_3 >= 11.0.0 < 11.0.1
CVE-2020-14234	High	November 21, 2020 11/21/20	< 9.0.1 >= 10.0.0 < 10.0.1 == 9.0.1 == 9.0.1-feature_pack_10_interim_fix_3 == 9.0.1-feature_pack_10_interim_fix_4 == 9.0.1-feature_pack_8 == 9.0.1-feature_pack_8_interim_fix_1 == 9.0.1-feature_pack_8_interim_fix_2 == 9.0.1-feature_pack_8_interim_fix_3 == 9.0.1-feature_pack_10_interim_fix_5
CVE-2017-1712	Medium	July 1, 2020 7/1/20	< 9.0.1

domino_project / domino

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2015-10039	Medium		January 11, 2023 1/11/23	< 0.1.5524.38553

Showing vulnerabilities for 4 products matching "domino". 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.