# CVE-2024-49369: Icinga 2 has a TLS Certificate Validation Bypass for JSON-RPC and HTTP API Connections

> Attackers can bypass TLS certificate validation to impersonate trusted nodes or API users, leading to unauthorized access in Icinga 2.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Nov 2024
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2024-49369, GHSA-j7wq-r9mg-9wpv, UBUNTU-CVE-2024-49369, openSUSE-SU-2024:0371-1, openSUSE-SU-2024:0372-1, openSUSE-SU-2024:14493-1

## What is CVE-2024-49369?

CVE-2024-49369 is a critical vulnerability in Debian Debian Linux, published on 12 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 client_cn attribute set). This vulnerability has been fixed in v2.14.3, v2.13.10, v2.12.11, and v2.11.12.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2024-49369?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `icinga2` | SUSE:Package Hub 15 SP5 | All versions | 2.13.10-bp155.3.3.1 |
| `icinga2` | SUSE:Package Hub 15 SP6 | All versions | 2.13.10-bp156.4.3.1 |
| `icinga2` | openSUSE:Leap 15.5 | All versions | 2.13.10-bp155.3.3.1 |
| `icinga2` | openSUSE:Leap 15.6 | All versions | 2.13.10-bp156.4.3.1 |
| `icinga2` | openSUSE:Tumbleweed | All versions | 2.14.3-1.1 |

Products: Debian Debian Linux, Icinga Icinga.

## How do I fix CVE-2024-49369?

Upgrade to a fixed version.

## Is CVE-2024-49369 being exploited?

There is no known exploitation of CVE-2024-49369 in the wild and no public exploit code.

Public exploit code:

- https://github.com/Quantum-Sicarius/CVE-2024-49369 (github_poc): https://github.com/Quantum-Sicarius/CVE-2024-49369

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-49369 and fix it if it is affected.

What it is: CVE-2024-49369 is a critical vulnerability in Debian Debian Linux, published on 12 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-49369 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-49369/ (Markdown: https://insights.sbomify.com/CVE-2024-49369/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-49369
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-49369
- OSV: https://osv.dev/vulnerability/CVE-2024-49369

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-49369/
Summaries are generated and may contain mistakes; the official description above is the record.