CVE-2025-64997
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-18

Last updated on: 2025-12-23

Assigner: Checkmk GmbH

Description
Insufficient permission validation in Checkmk versions prior to 2.4.0p17 and 2.3.0p42 allow low-privileged users to view agent information via the REST API, which could lead to information disclosure.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-18
Last Modified
2025-12-23
Generated
2026-05-07
AI Q&A
2025-12-18
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 72 associated CPEs
Vendor Product Version / Range
checkmk checkmk 2.2.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.3.0
checkmk checkmk 2.4.0
checkmk checkmk 2.4.0
checkmk checkmk 2.4.0
checkmk checkmk 2.4.0
checkmk checkmk 2.4.0
checkmk checkmk 2.4.0
checkmk checkmk 2.4.0
checkmk checkmk 2.4.0
checkmk checkmk 2.4.0
checkmk checkmk 2.4.0
checkmk checkmk 2.4.0
checkmk checkmk 2.4.0
checkmk checkmk 2.4.0
checkmk checkmk 2.4.0
checkmk checkmk 2.4.0
checkmk checkmk 2.4.0
checkmk checkmk 2.4.0
checkmk checkmk 2.4.0
checkmk checkmk 2.4.0
checkmk checkmk 2.4.0
checkmk checkmk 2.4.0
checkmk checkmk 2.4.0
checkmk checkmk 2.4.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-280 The product does not handle or incorrectly handles when it has insufficient privileges to access resources or functionality as specified by their permissions. This may cause it to follow unexpected code paths that may leave the product in an invalid state.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability in Checkmk's REST API allows low-privileged authenticated users to access sensitive agent information without proper permission validation. Specifically, the API endpoint that shows agent information did not correctly check user permissions, enabling unauthorized viewing of agent configurations and secrets. This affects certain versions of Checkmk prior to the fix and could lead to information disclosure. [1]


How can this vulnerability impact me? :

The vulnerability can lead to unauthorized disclosure of sensitive information such as agent configurations and secrets to low-privileged users. This could potentially expose internal system details that might be leveraged for further attacks or compromise system security. [1]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

You can detect this vulnerability by attempting to access the Checkmk REST API endpoint for agent information: `check_mk/api/1.0/domain-types/agent/collections/all`. If a low-privileged user or an authenticated user without proper permissions can retrieve agent configurations or sensitive data from this endpoint, the system is vulnerable. A practical command to test this could be using curl with a low-privileged user's credentials: `curl -u lowprivuser:password https://<checkmk-server>/check_mk/api/1.0/domain-types/agent/collections/all`. If the response contains agent information, the vulnerability exists. [1]


What immediate steps should I take to mitigate this vulnerability?

The immediate mitigation step is to upgrade Checkmk to version 2.5.0b1 or later, where the fix enforcing proper permission checks on the vulnerable REST API endpoint has been implemented. This fix ensures that only authorized users can access agent information. Since the fix is included in these versions and no manual intervention is required for compatibility, upgrading is the recommended action. [1]


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability allows low-privileged users to access sensitive agent information without proper authorization, leading to potential information disclosure. Such unauthorized access to sensitive data could negatively impact compliance with data protection standards and regulations like GDPR and HIPAA, which require strict access controls and protection of sensitive information. However, specific impacts on compliance are not detailed in the provided resources. [1]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart