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.

328,409

Total vulnerabilities in the database

Vulnerabilities for products matching "lotus_domino"

Found 1 matching product.

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

ibm / lotus_domino

86 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2014-3086	High	August 12, 2014 8/12/14	== 8.5.3.0 == 9.0.1.0
CVE-2014-0913	Low	May 9, 2014 5/9/14	== 8.5.3.6 == 9.0.1.0
CVE-2014-0892	Medium	April 23, 2014 4/23/14	== 8.5.0 == 8.5.0.1 == 8.5.1 == 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
CVE-2014-0822	High	February 6, 2014 2/6/14	== 8.5.2.4 == 8.5.3.5 == 8.5.1.1 == 8.5.1.4 == 8.5.2.2 == 9.0.0.0 == 8.5.2.1 == 8.5.1 == 8.5.0.1 == 8.5.3.0 == 8.5.3.4 == 8.5.0 == 8.5.1.2 == 8.5.3.1 == 8.5.2.3 == 9.0.1.0 == 8.5.3.3 == 8.5.2.0 == 8.5.3.2 == 8.5.1.5 == 8.5.1.3
CVE-2013-4063	Low	December 21, 2013 12/21/13	== 8.5.3.5 == 9.0.0.0 == 8.5.3.0 == 8.5.3.4 == 8.5.3.1 == 8.5.3.3 == 8.5.3.2
CVE-2013-4064	Low	December 21, 2013 12/21/13	== 8.5.3.5 == 9.0.0.0 == 8.5.3.0 == 8.5.3.4 == 8.5.3.1 == 8.5.3.3 == 8.5.3.2
CVE-2013-4065	Low	December 21, 2013 12/21/13	== 8.5.3.5 == 9.0.0.0 == 8.5.3.0 == 8.5.3.4 == 8.5.3.1 == 8.5.3.3 == 8.5.3.2
CVE-2013-4050	Medium	November 8, 2013 11/8/13	== 9.0.0.0 == 8.5.0
CVE-2013-4051	Low	November 8, 2013 11/8/13	== 9.0.0.0 == 8.5.0
CVE-2013-4055	Low	November 8, 2013 11/8/13	== 9.0.0.0 == 8.5.0
CVE-2013-5388	Low	October 22, 2013 10/22/13	== 9.0.0.0 == 8.5.3.0
CVE-2013-5389	Low	October 22, 2013 10/22/13	== 9.0.0.0 == 8.5.3.0
CVE-2013-4068	High	September 20, 2013 9/20/13	== 9.0.0.0 == 8.5.3.0 == 8.5.3.4 == 8.5.3.1 == 8.5.3.3 == 8.5.3.2
CVE-2013-0595	Low	August 27, 2013 8/27/13	== 8.5.0 == 8.5.0.1 == 8.5.1 == 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
CVE-2013-0590	Low	August 27, 2013 8/27/13	== 8.5.0 == 8.5.0.1 == 8.5.1 == 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
CVE-2013-0591	Low	August 27, 2013 8/27/13	== 8.5.0 == 8.5.0.1 == 8.5.1 == 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
CVE-2013-3990	Low	August 9, 2013 8/9/13	== 8.5.2.4 == 8.5.1.1 == 8.5.1.4 == 8.5.2.2 == 9.0.0.0 == 8.5.2.1 == 8.5.1 == 8.5.0.1 == 8.5.3.0 == 8.5.3.4 == 8.5.0 == 8.5.1.2 == 8.5.3.1 == 8.5.2.3 == 8.5.3.3 == 8.5.2.0 == 8.5.3.2 == 8.5.1.5 == 8.5.1.3
CVE-2013-3027	High	August 9, 2013 8/9/13	== 9.0.0.0
CVE-2013-3032	Low	August 9, 2013 8/9/13	== 8.5.2.4 == 8.5.1.1 == 8.5.1.4 == 8.5.2.2 == 9.0.0.0 == 8.5.2.1 == 8.5.1 == 8.5.0.1 == 8.5.3.0 == 8.5.0 == 8.5.1.2 == 8.5.3.1 == 8.5.2.3 == 8.5.2.0 == 8.5.3.2 == 8.5.1.5 == 8.5.1.3
CVE-2013-0486	Low	March 27, 2013 3/27/13	== 8.5.2.4 == 8.5.1.1 == 8.5.1.4 == 8.5.2.2 == 8.5.2.1 == 8.5.1 == 8.5.0.1 == 8.5.3.0 == 8.5.0 == 8.5.1.2 == 8.5.3.1 == 8.5.2.3 == 8.5.2.0 == 8.5.3.2 == 8.5.1.5 == 8.5.1.3
CVE-2013-0487	High	March 27, 2013 3/27/13	== 8.5.2.4 == 8.5.1.1 == 8.5.1.4 == 8.5.2.2 == 8.5.2.1 == 8.5.1 == 8.5.0.1 == 8.5.3.0 == 8.5.0 == 8.5.1.2 == 8.5.3.1 == 8.5.2.3 == 8.5.2.0 == 8.5.3.2 == 8.5.1.5 == 8.5.1.3
CVE-2013-0488	Low	March 27, 2013 3/27/13	== 8.5.2.4 == 8.5.1.1 == 8.5.1.4 == 8.5.2.2 == 8.5.2.1 == 8.5.1 == 8.5.0.1 == 8.5.3.0 == 8.5.0 == 8.5.1.2 == 8.5.3.1 == 8.5.2.3 == 8.5.2.0 == 8.5.3.2 == 8.5.1.5 == 8.5.1.3
CVE-2013-0489	Medium	March 27, 2013 3/27/13	== 8.5.2.4 == 8.5.1.1 == 8.5.1.4 == 8.5.2.2 == 8.5.2.1 == 8.5.1 == 8.5.0.1 == 8.5.3.0 == 8.5.0 == 8.5.1.2 == 8.5.3.1 == 8.5.2.3 == 8.5.2.0 == 8.5.3.2 == 8.5.1.5 == 8.5.1.3
CVE-2012-4842	Medium	February 27, 2013 2/27/13	== 8.5.2.4 == 8.5.1.1 == 8.5.1.4 == 8.5.2.2 == 8.5.2.1 == 8.5.1 == 8.5.0.1 == 8.5.3.0 == 8.5.0 == 8.5.1.2 == 8.5.2.3 == 8.5.2.0 == 8.5.1.5 == 8.5.1.3
CVE-2012-4844	Low	February 27, 2013 2/27/13	== 8.5.2.4 == 8.5.1.1 == 8.5.1.4 == 8.5.2.2 == 8.5.2.1 == 8.5.1 == 8.5.0.1 == 8.5.3.0 == 8.5.0 == 8.5.1.2 == 8.5.2.3 == 8.5.2.0 == 8.5.1.5 == 8.5.1.3
CVE-2012-4821	High	January 11, 2013 1/11/13	== 8.0 == 8.0.1 == 8.0.2 == 8.0.2.1 == 8.0.2.2 == 8.0.2.3 == 8.0.2.4 == 8.5.0 == 8.5.0.1 == 8.5.1 == 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
CVE-2012-4822	High	January 11, 2013 1/11/13	== 8.0 == 8.0.1 == 8.0.2 == 8.0.2.1 == 8.0.2.2 == 8.0.2.3 == 8.0.2.4 == 8.5.0 == 8.5.0.1 == 8.5.1 == 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
CVE-2012-4823	High	January 11, 2013 1/11/13	== 8.0 == 8.0.1 == 8.0.2 == 8.0.2.1 == 8.0.2.2 == 8.0.2.3 == 8.0.2.4 == 8.5.0 == 8.5.0.1 == 8.5.1 == 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
CVE-2012-4820	High	January 11, 2013 1/11/13	== 8.0 == 8.0.1 == 8.0.2 == 8.0.2.1 == 8.0.2.2 == 8.0.2.3 == 8.0.2.4 == 8.5.0 == 8.5.0.1 == 8.5.1 == 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
CVE-2012-3301	Low	August 21, 2012 8/21/12	== 8.5.2.4 == 8.5.1.1 == 8.5.1.4 == 8.5.2.2 == 8.5.2.1 == 8.5.0.1 == 8.5.3.0 == 8.5.0 == 8.5.1.2 == 8.5.3.1 == 8.5.2.3 == 8.5.2.0 == 8.5.3.2 == 8.5.1.5 == 8.5.1.3
CVE-2012-3302	Low	August 21, 2012 8/21/12	== 7.0.2.2 == 7.0.4.0 == 7.0.4.2 == 7.0.1.1 == 7.0.3.0 == 7.0.4.1 == 7.0.2 == 7.0.1 == 7.0.3.1 == 8.5.2.4 == 8.5.1.1 == 8.5.1.4 == 8.5.2.2 == 8.5.2.1 == 8.5.0.1 == 8.5.3.0 == 8.5.0 == 8.5.1.2 == 8.5.3.1 == 8.5.2.3 == 8.5.2.0 == 8.5.3.2 == 8.5.1.5 == 8.5.1.3
CVE-2011-1393	High	December 27, 2011 12/27/11	== 8.0.2.4 == 8.5.1.1 == 8.5.1.4 == 8.0.2 == 8.0.2.3 == 8.5.1 == 8.5.0 <= 8.5.2 == 8.0.2.1 == 8.0.2.6 == 8.5.1.2 == 8.0.5 == 8.0.2.5 == 8.0.2.2 == 8.0 == 8.5.1.5 == 8.0.1 == 8.5.1.3
CVE-2011-3575	High	September 19, 2011 9/19/11	== 8.5.2
CVE-2011-3576	Low	September 19, 2011 9/19/11	== 8.5.2
CVE-2011-1520	High	March 25, 2011 3/25/11	*
CVE-2011-1519	High	March 25, 2011 3/25/11	== 7.0.2.2 == 7.0.4 == 7.0.4.2 == 7.0.1.1 == 7.0.2.1 == 7.0.2.3 == 7.0.4.1 == 7.0.3 == 7.0 == 7.0.2 == 7.0.1 == 7.0.3.1 == 8.0.2.4 == 8.5.1.1 == 8.5.1.4 == 8.0.2 == 8.5.2.2 == 8.0.2.3 == 8.5.2.1 == 8.5.1 == 8.5.0.1 == 8.5.0 == 8.5.3 == 8.0.2.1 == 8.0.2.6 == 8.5.1.2 == 8.0.2.5 == 8.5.2 == 8.0.2.2 == 8.0 == 8.5.1.5 == 8.0.1 == 8.5.1.3
CVE-2011-0913	High	February 8, 2011 2/8/11	== 8.0.2.4 == 7.0.2.2 == 6.0.5 == 5.0.4 == 5.0.2 == 7.0.4 == 6.5.2 == 6.5.4.1 == 8.5.1.1 == 6.0 == 8.5.1.4 == 8.0.2 == 7.0.4.2 == 7.0.1.1 == 4.6.4 == 6.0.4 == 6.0.2 == 5.0.1 == 5.0.8a == 5.0.3 == 6.5.4 == 7.0.2.1 == 6.0.2_cf2 == 5.0.9 == 6.0.2.2 == 8.0.2.3 == 8.5.2.1 == 6.0.1.1 == 7.0.2.3 == 7.0.4.1 <= 8.5.2.2 == 6.5 == 6.5.2.1 == 8.5.1 == 6.5.4.3 == 4.6.1 == 5.0.4a == 6.5.3.1 == 7.0.3 == 6.5.1 == 6.0.1.2 == 5.0.11 == 5.0.7 == 7.0 == 8.0.2.1 == 8.0.2.6 == 8.5.1.2 == 6.5.0 == 6.5.6 == 6.0.2.1 == 5.0.6 == 5.0.6a == 5.0 == 4.6.3 == 6.0.1 == 6.5.4.2 == 6.5.3 == 8.0.2.5 == 6.0.3 == 6.0.1.3 == 8.5.2 == 8.0.2.2 == 7.0.2 == 6.5.5 == 5.0.9a == 5.0.5 == 8.5.1.5 == 7.0.1 == 5.0.8 == 7.0.3.1 == 8.0.1 == 5.0.7a == 5.0.10 == 8.5.1.3
CVE-2011-0914	High	February 8, 2011 2/8/11	== 8.0.2.4 == 7.0.2.2 == 6.0.5 == 5.0.4 == 5.0.2 == 7.0.4 == 6.5.2 == 6.5.4.1 == 8.5.1.1 == 6.0 == 8.5.1.4 == 8.0.2 == 7.0.4.2 == 7.0.1.1 == 4.6.4 == 6.0.4 == 6.0.2 == 5.0.1 == 5.0.8a == 5.0.3 == 6.5.4 == 7.0.2.1 == 6.0.2_cf2 == 5.0.9 == 6.0.2.2 == 8.0.2.3 == 8.5.2.1 == 6.0.1.1 == 7.0.2.3 == 7.0.4.1 <= 8.5.2.2 == 6.5 == 6.5.2.1 == 8.5.1 == 6.5.4.3 == 4.6.1 == 5.0.4a == 6.5.3.1 == 7.0.3 == 6.5.1 == 6.0.1.2 == 5.0.11 == 5.0.7 == 7.0 == 8.0.2.1 == 8.0.2.6 == 8.5.1.2 == 6.5.0 == 6.5.6 == 6.0.2.1 == 5.0.6 == 5.0.6a == 5.0 == 4.6.3 == 6.0.1 == 6.5.4.2 == 6.5.3 == 8.0.2.5 == 6.0.3 == 6.0.1.3 == 8.5.2 == 8.0.2.2 == 7.0.2 == 6.5.5 == 5.0.9a == 5.0.5 == 8.5.1.5 == 7.0.1 == 5.0.8 == 7.0.3.1 == 8.0.1 == 5.0.7a == 5.0.10 == 8.5.1.3
CVE-2011-0915	High	February 8, 2011 2/8/11	== 8.0.2.4 == 7.0.2.2 == 6.0.5 == 5.0.4 == 5.0.2 == 7.0.4 == 6.5.2 == 6.5.4.1 == 8.5.1.1 == 6.0 == 8.5.1.4 == 8.0.2 == 7.0.4.2 == 7.0.1.1 == 4.6.4 == 6.0.4 == 6.0.2 == 5.0.1 == 5.0.8a == 5.0.3 == 6.5.4 == 7.0.2.1 == 6.0.2_cf2 == 5.0.9 == 6.0.2.2 == 8.0.2.3 == 8.5.2.1 == 6.0.1.1 == 7.0.2.3 == 7.0.4.1 <= 8.5.2.2 == 6.5 == 6.5.2.1 == 8.5.1 == 6.5.4.3 == 4.6.1 == 5.0.4a == 6.5.3.1 == 7.0.3 == 6.5.1 == 6.0.1.2 == 5.0.11 == 5.0.7 == 7.0 == 8.0.2.1 == 8.0.2.6 == 8.5.1.2 == 6.5.0 == 6.5.6 == 6.0.2.1 == 5.0.6 == 5.0.6a == 5.0 == 4.6.3 == 6.0.1 == 6.5.4.2 == 6.5.3 == 8.0.2.5 == 6.0.3 == 6.0.1.3 == 8.5.2 == 8.0.2.2 == 7.0.2 == 6.5.5 == 5.0.9a == 5.0.5 == 8.5.1.5 == 7.0.1 == 5.0.8 == 7.0.3.1 == 8.0.1 == 5.0.7a == 5.0.10 == 8.5.1.3
CVE-2011-0916	High	February 8, 2011 2/8/11	*
CVE-2011-0917	High	February 8, 2011 2/8/11	*
CVE-2011-0918	High	February 8, 2011 2/8/11	*
CVE-2011-0919	High	February 8, 2011 2/8/11	*
CVE-2011-0920	High	February 8, 2011 2/8/11	*
CVE-2010-3407	High	September 16, 2010 9/16/10	== 8.0.2.4 == 8.5.1.1 == 8.0.2 == 8.0.2.3 == 8.5.1 == 8.5.0.1 == 8.5.0 == 8.0.2.1 == 8.0.2.2 == 8.0 == 8.0.1
CVE-2010-0927	Low	March 5, 2010 3/5/10	== 7.0.2.2 == 7.0.1.1 == 7.0.2.1 == 7.0.2.3 == 7.0.3 == 7.0 == 7.0.2 == 8.0 == 7.0.1 == 7.0.3.1 == 8.0.1
CVE-2010-0358	High	January 20, 2010 1/20/10	== 8.5.0.1 == 7.0
CVE-2010-0276	High	January 9, 2010 1/9/10	== 8.0.2.3
CVE-2009-3087	Medium	September 8, 2009 9/8/09	== 8.0
CVE-2009-1286	Medium	April 13, 2009 4/13/09	== 8.0.2 == 8.0.2.1 == 8.0 == 8.0.1

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.