Nagios Nagios

Do you want an email whenever new security vulnerabilities are reported in Nagios?

By the Year

In 2024 there have been 0 vulnerabilities in Nagios . Nagios did not have any published security vulnerabilities last year.

Year Vulnerabilities Average Score
2024 0 0.00
2023 0 0.00
2022 0 0.00
2021 0 0.00
2020 3 6.90
2019 0 0.00
2018 2 6.65

It may take a day or so for new Nagios vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.

Recent Nagios Security Vulnerabilities

Nagios Log Server 2.1.3 has Incorrect Access Control.

CVE-2020-6584 6.5 - Medium - March 16, 2020

Nagios Log Server 2.1.3 has Incorrect Access Control.

Improper Privilege Management

Nagios Log Server 2.1.3 has CSRF.

CVE-2020-6585 8.8 - High - March 16, 2020

Nagios Log Server 2.1.3 has CSRF.

Session Riding

Nagios Log Server 2.1.3 allows XSS by visiting /profile and entering a crafted name field that is mishandled on the /admin/users page

CVE-2020-6586 5.4 - Medium - March 16, 2020

Nagios Log Server 2.1.3 allows XSS by visiting /profile and entering a crafted name field that is mishandled on the /admin/users page. Any malicious user with limited access can store an XSS payload in his Name. When any admin views this, the XSS is triggered.

XSS

A privilege escalation vulnerability was found in nagios 4.2.x

CVE-2016-8641 7.8 - High - August 01, 2018

A privilege escalation vulnerability was found in nagios 4.2.x that occurs in daemon-init.in when creating necessary files and insecurely changing the ownership afterwards. It's possible for the local attacker to create symbolic links before the files are to be created and possibly escalating the privileges with the ownership change.

insecure temporary file

qh_help in Nagios Core version 4.4.1 and earlier is prone to a NULL pointer dereference vulnerability, which

CVE-2018-13441 5.5 - Medium - July 12, 2018

qh_help in Nagios Core version 4.4.1 and earlier is prone to a NULL pointer dereference vulnerability, which allows attacker to cause a local denial-of-service condition by sending a crafted payload to the listening UNIX socket.

NULL Pointer Dereference

status.cgi in Nagios 4.0 before 4.0 beta4 and 3.x before 3.5.1 does not properly restrict access to certain users

CVE-2013-2214 - February 10, 2014

status.cgi in Nagios 4.0 before 4.0 beta4 and 3.x before 3.5.1 does not properly restrict access to certain users that are a contact for a service, which allows remote authenticated users to obtain sensitive information about hostnames via the servicegroup (1) overview, (2) summary, or (3) grid style in status.cgi. NOTE: this behavior is by design in most 3.x versions, but the upstream vendor "decided to change it for Nagios 4" and 3.5.1.

Permissions, Privileges, and Access Controls

rss-newsfeed.php in Nagios Core 3.4.4, 3.5.1, and earlier, when MAGPIE_CACHE_ON is set to 1

CVE-2013-4214 - November 23, 2013

rss-newsfeed.php in Nagios Core 3.4.4, 3.5.1, and earlier, when MAGPIE_CACHE_ON is set to 1, allows local users to overwrite arbitrary files via a symlink attack on /tmp/magpie_cache.

insecure temporary file

The _httpsrequest function (Snoopy/Snoopy.class.php) in Snoopy 1.2.3 and earlier, as used in (1) ampache, (2) libphp-snoopy, (3) mahara, (4) mediamate, (5) opendb, (6) pixelpost, and possibly other products

CVE-2008-4796 - October 30, 2008

The _httpsrequest function (Snoopy/Snoopy.class.php) in Snoopy 1.2.3 and earlier, as used in (1) ampache, (2) libphp-snoopy, (3) mahara, (4) mediamate, (5) opendb, (6) pixelpost, and possibly other products, allows remote attackers to execute arbitrary commands via shell metacharacters in https URLs.

Shell injection

Stay on top of Security Vulnerabilities

Want an email whenever new vulnerabilities are published for WordPress or by Nagios? Click the Watch button to subscribe.

Nagios
Vendor

Nagios
Product

subscribe