CVE-2025-62787: Wazuh Vulnerable to Heap-based Buffer Over-read in DecodeWinevt
Wazuh is a free and open source platform used for threat prevention, detection, and response. Prior to 4.10.2, a buffer over-read occurs in DecodeWinevt() when childattr[p]->attributes[j] is accessed, because the corresponding index (j) is incorrect. A compromised agent can cause a READ operation beyond the end of the allocated buffer (which may contain sensitive information) by sending a specially crafted message to the wazuh manager. An attacker who is able to craft and send an agent message to the wazuh manager can cause a buffer over-read and potentially access sensitive data. While the buffer over-read is always triggered while resolving the arguments of mdebug2, specific configuration options (analysisd.debug=2) need to be in place for the respective data to be leaked. This vulnerability is fixed in 4.10.2.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Wazuhto a version that resolves this vulnerability.Fixed in 4.10.2
Event History
Frequently Asked Questions
What is the severity of CVE-2025-62787?
CVE-2025-62787 has a medium severity rating due to the potential for a buffer over-read vulnerability.
How do I fix CVE-2025-62787?
To address CVE-2025-62787, upgrade to Wazuh version 4.10.2 or later.
What impact does CVE-2025-62787 have on Wazuh?
CVE-2025-62787 allows a compromised agent to cause a buffer over-read, which may lead to information disclosure.
Is CVE-2025-62787 exploitable remotely?
Yes, CVE-2025-62787 can potentially be exploited remotely if an attacker can control a compromised agent.
What versions of Wazuh are affected by CVE-2025-62787?
CVE-2025-62787 affects all versions of Wazuh prior to 4.10.2.