CVE-2024-6163

5.3 MEDIUM

📋 TL;DR

This authentication bypass vulnerability in Checkmk allows remote attackers to access HTTP endpoints without proper credentials, potentially exposing sensitive monitoring data. It affects Checkmk versions before specific patch releases across multiple major versions.

💻 Affected Systems

Products:
  • Checkmk
Versions: Checkmk < 2.3.0p10, < 2.2.0p31, < 2.1.0p46, <= 2.0.0p39
Operating Systems: Linux, Windows
Default Config Vulnerable: ⚠️ Yes
Notes: All default installations of affected versions are vulnerable. The vulnerability affects specific HTTP endpoints.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Unauthenticated attackers could access all monitoring data, configuration files, and potentially execute administrative functions, leading to complete system compromise.

🟠

Likely Case

Attackers access monitoring dashboards, view system metrics, and potentially extract sensitive infrastructure information.

🟢

If Mitigated

With proper network segmentation and access controls, impact is limited to unauthorized viewing of monitoring data.

🌐 Internet-Facing: HIGH - Directly exposed Checkmk instances can be exploited without authentication from anywhere on the internet.
🏢 Internal Only: MEDIUM - Internal attackers or compromised internal systems could exploit this to escalate privileges or access sensitive monitoring data.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

The vulnerability allows authentication bypass, making exploitation straightforward once the vulnerable endpoint is identified.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.3.0p10, 2.2.0p31, 2.1.0p46, 2.0.0p40

Vendor Advisory: https://checkmk.com/werk/17011

Restart Required: Yes

Instructions:

1. Backup your Checkmk configuration. 2. Update to the patched version using your distribution's package manager. 3. Restart Checkmk services. 4. Verify the update was successful.

🔧 Temporary Workarounds

Network Access Restriction

linux

Restrict access to Checkmk HTTP endpoints using firewall rules or network segmentation.

iptables -A INPUT -p tcp --dport 80 -s trusted_network -j ACCEPT
iptables -A INPUT -p tcp --dport 443 -s trusted_network -j ACCEPT
iptables -A INPUT -p tcp --dport 80 -j DROP
iptables -A INPUT -p tcp --dport 443 -j DROP

Reverse Proxy Authentication

all

Place Checkmk behind a reverse proxy with additional authentication layer.

🧯 If You Can't Patch

  • Implement strict network access controls to limit Checkmk HTTP endpoint exposure
  • Monitor authentication logs for suspicious access patterns and failed login attempts

🔍 How to Verify

Check if Vulnerable:

Check Checkmk version: omd version. If version matches affected range and specific HTTP endpoints are accessible without authentication, system is vulnerable.

Check Version:

omd version

Verify Fix Applied:

Verify updated version: omd version. Test previously vulnerable endpoints require authentication.

📡 Detection & Monitoring

Log Indicators:

  • Unauthenticated access to sensitive endpoints
  • HTTP requests to Checkmk endpoints without authentication headers

Network Indicators:

  • Unusual traffic patterns to Checkmk HTTP endpoints from unauthorized sources

SIEM Query:

source="checkmk.log" AND (http_status=200 OR http_status=302) AND NOT (user!="" OR auth_success="true")

🔗 References

📤 Share & Export