Vulnerability Database

328,411

Total vulnerabilities in the database

Vulnerabilities for products matching "nagios"

Found 1 matching product.

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

nagios / nagios

35 vulnerabilities found
Title Severity Exploit Date Affected Version
CVE-2020-13977
Low June 9, 2020 6/9/20
== 4.4.5
CVE-2020-6584
Medium March 16, 2020 3/16/20
== 2.1.3
CVE-2020-6585
High March 16, 2020 3/16/20
== 2.1.3
CVE-2020-6586
Medium March 16, 2020 3/16/20
== 2.1.3
CVE-2019-3698
Medium February 28, 2020 2/28/20
< 3.5.1
< 3.0.6
CVE-2016-8641
High August 1, 2018 8/1/18
== 4.2.3
== 4.2.2
== 4.2.1
== 4.2.0
CVE-2018-13441
Low July 12, 2018 7/12/18
<= 4.4.1
CVE-2017-12847
Medium August 23, 2017 8/23/17
<= 4.3.2
CVE-2008-7313
High March 31, 2017 3/31/17
<= 4.2.3
CVE-2014-5009
High March 31, 2017 3/31/17
<= 4.2.3
CVE-2016-10089
High February 15, 2017 2/15/17
<= 4.2.4
CVE-2016-9565
High December 15, 2016 12/15/16
<= 4.2.1
CVE-2016-9566
High December 15, 2016 12/15/16
<= 4.2.3
CVE-2014-4703
Low December 5, 2014 12/5/14
== 2.0.2
CVE-2014-4702
Low December 5, 2014 12/5/14
<= 2.0.1
CVE-2014-4701
Low December 5, 2014 12/5/14
<= 2.0.1
CVE-2014-1878
Medium February 28, 2014 2/28/14
== 4.0.0-beta4
== 4.0.2
== 4.0.0-beta1
== 4.0.0-beta3
<= 4.0.3
== 4.0.0-beta2
CVE-2013-2214
Low February 10, 2014 2/10/14
== 3.0-alpha3
== 3.1.2
== 3.0-rc3
== 3.0-beta4
== 3.0-alpha5
== 3.5.0
== 3.2.2
== 3.2.0
== 3.1.1
== 3.0.6
== 3.0-alpha2
== 3.0.1
== 3.4.4
== 3.0-beta5
== 3.4.1
== 3.0-rc1
== 3.0.2
== 3.1.0
== 3.0-beta2
== 3.0-beta7
== 3.0-rc2
== 4.0.0-beta1
== 3.4.2
== 3.0
== 3.4.3
== 4.0.0-beta3
== 3.0.4
== 3.0-alpha1
== 3.0-beta6
== 3.0-alpha4
== 3.2.1
== 3.0-beta1
== 3.0-beta3
== 3.0.3
== 3.2.3
== 4.0.0-beta2
== 3.3.1
== 3.0.5
== 3.4.0
CVE-2013-7108
Medium January 15, 2014 1/15/14
<= 4.0.2
== 3.0
== 3.0-alpha1
== 3.0-alpha2
== 3.0-alpha3
== 3.0-alpha4
== 3.0-alpha5
== 3.0-beta1
== 3.0-beta2
== 3.0-beta3
== 3.0-beta4
== 3.0-beta5
== 3.0-beta6
== 3.0-beta7
== 3.0-rc1
== 3.0-rc2
== 3.0-rc3
== 3.0.1
== 3.0.2
== 3.0.3
== 3.0.4
== 3.0.5
== 3.0.6
== 3.1.0
== 3.1.1
== 3.1.2
== 3.2.0
== 3.2.1
== 3.2.2
== 3.2.3
== 3.3.1
== 3.4.0
== 3.4.1
== 3.4.2
== 3.4.3
== 3.5.1
CVE-2013-7205
Medium January 15, 2014 1/15/14
== 3.0-alpha3
== 3.1.2
== 3.0-rc3
== 3.0-beta4
== 3.0-alpha5
== 3.2.2
== 3.2.0
== 3.1.1
== 3.0.6
== 3.0-alpha2
== 3.0.1
== 3.0-beta5
== 3.4.1
== 3.0-rc1
== 3.0.2
== 3.1.0
== 3.0-beta2
== 3.0-beta7
== 3.0-rc2
<= 4.0.2
== 3.4.2
== 3.0
== 3.4.3
== 3.5.1
== 3.0.4
== 3.0-alpha1
== 3.0-beta6
== 3.0-alpha4
== 3.2.1
== 3.0-beta1
== 3.0-beta3
== 3.0.3
== 3.2.3
== 3.3.1
== 3.0.5
== 3.4.0
CVE-2013-4214
Medium November 23, 2013 11/23/13
== 3.4.4
<= 3.5.1
CVE-2012-6096
High January 22, 2013 1/22/13
== 3.0-alpha3
== 3.1.2
== 3.0-rc3
== 3.0-beta4
== 3.0-alpha5
== 3.2.2
== 3.2.0
== 3.1.1
== 3.0.6
== 3.0-alpha2
== 3.0.1
== 3.0-beta5
== 3.4.1
== 3.0-rc1
== 3.0.2
== 3.1.0
== 3.0-beta2
== 3.0-beta7
== 3.0-rc2
== 3.4.2
== 3.0
== 3.0.4
== 3.0-alpha1
== 3.0-beta6
== 3.0-alpha4
== 3.2.1
<= 3.4.3
== 3.0-beta1
== 3.0-beta3
== 3.0.3
== 3.2.3
== 3.3.1
== 3.0.5
== 3.4.0
CVE-2011-2179
Low June 14, 2011 6/14/11
== 3.2.3
CVE-2011-1523
Low May 3, 2011 5/3/11
== 3.0-alpha3
== 2.0b5
== 2.7
== 3.1.2
== 2.4
== 3.0-rc3
== 3.0-beta4
== 2.0b6
== 3.2.2
== 3.2.0
== 3.1.1
== 3.0.6
== 1.0b3
== 1.1
== 3.0-alpha2
== 2.1
== 1.0b6
== 3.0.1
== 1.0
== 2.3.1
== 3.0-beta5
== 2.2
== 3.0-rc1
== 2.0b2
<= 3.2.3
== 1.0b4
== 3.0.2
== 2.5
== 2.0b4
== 2.8
== 3.1.0
== 3.0-beta2
== 2.10
== 1.2
== 3.0-beta7
== 3.0-rc2
== 1.0b5
== 1.0_b3
== 2.0b1
== 3.0
== 2.0
== 3.0.4
== 1.4
== 3.0-alpha1
== 1.4.1
== 3.0-beta6
== 2.0b3
== 1.3
== 2.11
== 3.0-alpha4
== 3.2.1
== 2.0rc1
== 3.0-beta1
== 1.0_b1
== 2.3
== 1.0b1
== 3.0-beta3
== 3.0.3
== 1.0b2
== 3.0.5
== 2.9
== 1.0_b2
== 2.0rc2
CVE-2009-2288
High July 1, 2009 7/1/09
== 3.0-alpha3
== 2.7
== 3.0-rc3
== 3.0-beta4
== 3.0.6
== 1.1
== 3.0-alpha2
== 3.0.1
== 1.0
== 3.0-beta5
== 3.0-rc1
<= 3.1.0
== 1.0b4
== 3.0.2
== 2.0b4
== 3.0-beta2
== 2.10
== 3.0-beta7
== 3.0-rc2
== 3.0
== 2.0
== 3.0.4
== 3.0-alpha1
== 1.4.1
== 3.0-beta6
== 3.0-alpha4
== 3.0-beta1
== 1.0b1
== 3.0-beta3
== 3.0.3
== 1.0b2
== 3.0.5
CVE-2008-6373
Medium March 2, 2009 3/2/09
== 3.0-alpha3
== 2.0b5
== 2.7
== 2.4
<= 3.0.5
== 3.0-rc3
== 3.0-beta4
== 2.0b6
== 1.0b3
== 1.1
== 3.0-alpha2
== 2.1
== 1.0b6
== 3.0.1
== 1.0
== 2.3.1
== 3.0-beta5
== 2.2
== 3.0-rc1
== 2.0b2
== 1.0b4
== 3.0.2
== 2.5
== 2.0b4
== 2.8
== 3.0-beta2
== 2.10
== 1.2
== 3.0-beta7
== 3.0-rc2
== 1.0b5
== 1.0_b3
== 2.0b1
== 3.0
== 2.0
== 3.0.4
== 1.4
== 3.0-alpha1
== 1.4.1
== 3.0-beta6
== 2.0b3
== 1.3
== 2.11
== 3.0-alpha4
== 2.0rc1
== 3.0-beta1
== 1.0_b1
== 2.3
== 1.0b1
== 3.0-beta3
== 3.0.3
== 1.0b2
== 2.9
== 1.0_b2
== 2.0rc2
CVE-2008-5027
Medium November 10, 2008 11/10/08
== 3.0-alpha3
== 2.0b5
== 2.7
== 2.4
== 3.0-rc3
== 3.0-beta4
== 2.0b6
== 1.0b3
== 1.1
== 3.0-alpha2
== 2.1
== 1.0b6
== 3.0.1
== 1.0
== 2.3.1
== 3.0-beta5
== 2.2
== 3.0-rc1
== 2.0b2
== 1.0b4
== 3.0.2
== 2.5
== 2.0b4
== 2.8
<= 3.0.4
== 3.0-beta2
== 2.10
== 1.2
== 3.0-beta7
== 3.0-rc2
== 1.0b5
== 1.0_b3
== 2.0b1
== 3.0
== 2.0
== 1.4
== 3.0-alpha1
== 1.4.1
== 3.0-beta6
== 2.0b3
== 1.3
== 2.11
== 3.0-alpha4
== 2.0rc1
== 3.0-beta1
== 1.0_b1
== 2.3
== 1.0b1
== 3.0-beta3
== 3.0.3
== 1.0b2
== 2.9
== 1.0_b2
== 2.0rc2
CVE-2008-5028
Medium November 10, 2008 11/10/08
== 3.0-alpha3
== 2.0b5
== 2.7
== 2.4
== 3.0-rc3
== 3.0-beta4
== 2.0b6
== 1.0b3
== 1.1
== 3.0-alpha2
== 2.1
== 1.0b6
== 3.0.1
== 1.0
== 2.3.1
== 3.0-beta5
== 2.2
== 3.0-rc1
== 2.0b2
== 1.0b4
== 3.0.2
== 2.5
== 2.0b4
== 2.8
<= 3.0.4
== 3.0-beta2
== 2.10
== 1.2
== 3.0-beta7
== 3.0-rc2
== 1.0b5
== 1.0_b3
== 2.0b1
== 3.0
== 2.0
== 1.4
== 3.0-alpha1
== 1.4.1
== 3.0-beta6
== 2.0b3
== 1.3
== 2.11
== 3.0-alpha4
== 2.0rc1
== 3.0-beta1
== 1.0_b1
== 2.3
== 1.0b1
== 3.0-beta3
== 3.0.3
== 1.0b2
== 2.9
== 1.0_b2
== 2.0rc2
CVE-2008-4796
High October 30, 2008 10/30/08
< 4.2.2
CVE-2007-5803
Low May 13, 2008 5/13/08
== 2.0b5
== 2.7
== 2.4
== 2.0b6
== 1.0b3
== 1.1
== 2.1
== 1.0b6
== 2.3.1
== 2.2
== 2.0b2
== 1.0b4
== 2.5
== 2.0b4
== 2.8
== 2.10
== 1.2
== 1.0b5
== 2.0b1
== 2.0
== 1.4
== 1.4.1
== 2.0b3
== 1.3
== 2.11
== 2.0rc1
== 2.3
== 1.0b1
== 1.0b2
== 2.9
== 2.0rc2
CVE-2008-1360
Low March 17, 2008 3/17/08
== 2.7
== 2.3.1
== 2.2
== 2.8
== 2.10
== 2.3
== 2.9
CVE-2007-5624
Low October 23, 2007 10/23/07
<= 2.9
CVE-2006-2489
High May 19, 2006 5/19/06
== 2.0b5
== 2.0b6
== 1.0b3
== 1.1
== 2.1
== 1.0b6
== 1.0
== 2.2
== 2.0b2
== 1.0b4
== 2.0b4
== 1.2
== 1.0b5
== 2.0b1
== 2.0
== 1.4
== 2.0b3
== 1.3
== 2.0rc1
== 2.3
== 1.0b1
== 1.0b2
== 2.0rc2
CVE-2006-2162
Medium May 3, 2006 5/3/06
<= 1.3
<= 2.2
CVE-2002-1959
High December 31, 2002 12/31/02
== 1.0_b3
== 1.0_b1
== 1.0_b2

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.