CVE-2024-49369: Icinga 2 has a TLS Certificate Validation Bypass for JSON-RPC and HTTP API Connections
Icinga is a monitoring system which checks the availability of network resources, notifies users of outages, and generates performance data for reporting. The TLS certificate validation in all Icinga 2 versions starting from 2.4.0 was flawed, allowing an attacker to impersonate both trusted cluster nodes as well as any API users that use TLS client certificates for authentication (ApiUser objects with the clientcn attribute set). This vulnerability has been fixed in v2.14.3, v2.13.10, v2.12.11, and v2.11.12.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/icinga2to a version that resolves this vulnerability.Fixed in 2.13.6-2+deb12u2 - Upgrade
Upgrade
debian/icinga2to a version that resolves this vulnerability.Fixed in 2.14.3-1 - Upgrade
Upgrade
debian/icinga2to a version that resolves this vulnerability.Fixed in 2.13.6-2+deb12u2Fixed in 2.14.6-1Fixed in 2.14.6-1+deb13u1Fixed in 2.16.6-1 - Upgrade
Upgrade
Icinga 2to a version that resolves this vulnerability.Fixed in 2.14.3
Event History
Frequently Asked Questions
What is the severity of CVE-2024-49369?
CVE-2024-49369 is considered a medium severity vulnerability due to its potential for exploitation by attackers.
How do I fix CVE-2024-49369?
To fix CVE-2024-49369, upgrade Icinga 2 to the latest version that addresses the TLS certificate validation flaw.
What versions are affected by CVE-2024-49369?
CVE-2024-49369 affects all versions of Icinga 2 starting from 2.4.0.
What type of vulnerability is CVE-2024-49369?
CVE-2024-49369 is a security vulnerability related to flawed TLS certificate validation.
Can CVE-2024-49369 allow for man-in-the-middle attacks?
Yes, CVE-2024-49369 could potentially allow attackers to perform man-in-the-middle attacks by impersonating Icinga 2 services.