Vulnerabilities (CVE)

Filtered by vendor Icinga Subscribe
Filtered by product Icinga
Total 26 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2020-14004 2 Icinga, Opensuse 3 Icinga, Backports Sle, Leap 2024-11-21 4.6 MEDIUM 7.8 HIGH
An issue was discovered in Icinga2 before v2.12.0-rc1. The prepare-dirs script (run as part of the icinga2 systemd service) executes chmod 2750 /run/icinga2/cmd. /run/icinga2 is under control of an unprivileged user by default. If /run/icinga2/cmd is a symlink, then it will by followed and arbitrary files can be changed to mode 2750 by the unprivileged icinga2 user.
CVE-2018-6536 1 Icinga 1 Icinga 2024-11-21 4.9 MEDIUM 5.5 MEDIUM
An issue was discovered in Icinga 2.x through 2.8.1. The daemon creates an icinga2.pid file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for icinga2.pid modification before a root script executes a "kill `cat /pathname/icinga2.pid`" command, as demonstrated by icinga2.init.d.cmake.
CVE-2018-6535 1 Icinga 1 Icinga 2024-11-21 4.3 MEDIUM 8.1 HIGH
An issue was discovered in Icinga 2.x through 2.8.1. The lack of a constant-time password comparison function can disclose the password to an attacker.
CVE-2018-6534 1 Icinga 1 Icinga 2024-11-21 4.3 MEDIUM 6.5 MEDIUM
An issue was discovered in Icinga 2.x through 2.8.1. By sending specially crafted messages, an attacker can cause a NULL pointer dereference, which can cause the product to crash.
CVE-2018-6533 1 Icinga 1 Icinga 2024-11-21 7.2 HIGH 7.8 HIGH
An issue was discovered in Icinga 2.x through 2.8.1. By editing the init.conf file, Icinga 2 can be run as root. Following this the program can be used to run arbitrary code as root. This was fixed by no longer using init.conf to determine account information for any root-executed code (a larger issue than CVE-2017-16933).
CVE-2018-6532 1 Icinga 1 Icinga 2024-11-21 5.0 MEDIUM 7.5 HIGH
An issue was discovered in Icinga 2.x through 2.8.1. By sending specially crafted (authenticated and unauthenticated) requests, an attacker can exhaust a lot of memory on the server side, triggering the OOM killer.