CVE-2025-15615: Wazuh Manager authd service Improper SSL/TLS Renegotiation Handling leading to Denial of Service
Wazuh Manager authd service in wazuh-manager packages through version 4.7.3 contains an improper restriction of client-initiated SSL/TLS renegotiation vulnerability that allows remote attackers to cause a denial of service by sending excessive renegotiation requests. Attackers can exploit the lack of renegotiation limits to consume CPU resources and render the authd service unavailable.
Security readout for executives and security teams
Plain-English summary
This issue can let an unauthenticated remote attacker overload the Wazuh Manager authd service by abusing TLS renegotiation. The expected business impact is service disruption, not data theft or code execution, based on the provided CVSS vector and description.
Executive priority
Treat as a moderate availability risk to security operations infrastructure. Prioritize internet-exposed or broadly reachable Wazuh Manager deployments, because authd disruption could impair agent enrollment or authentication workflows.
Technical view
Wazuh Manager authd lacks sufficient restriction on client-initiated SSL/TLS renegotiation. Excessive renegotiation requests can consume CPU and make authd unavailable. The provided record rates this CVSS 4.0 score 6.9 with network attack vector, low complexity, no privileges, and availability impact.
Likely exposure
Organizations running Wazuh Manager packages with authd reachable over the network are the likely exposure group. The description says packages through 4.7.3; the affected version data is internally inconsistent, so confirm exact version status with Wazuh guidance.
Exploitation context
The bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation is described as remote and unauthenticated, focused on denial of service through excessive TLS renegotiation rather than compromise of confidentiality or integrity.
Researcher notes
Evidence supports a TLS renegotiation resource-exhaustion issue in authd. No exploit code, active exploitation, or definitive remediation details are included in the bundle. Version status should be verified against the vendor advisory because the affected-version metadata appears inconsistent.
Mitigation direction
Review the Wazuh advisory for confirmed affected and fixed versions.
Apply vendor-published updates or configuration guidance once confirmed.
Restrict authd exposure to trusted management networks where operationally possible.
Monitor Wazuh Manager CPU and authd availability for abnormal spikes.
Validation and detection
Inventory Wazuh Manager deb and rpm package versions across environments.
Confirm whether authd is enabled and reachable from untrusted networks.
Compare installed versions against the Wazuh advisory and CVE record.
Review logs and monitoring for authd outages or CPU exhaustion patterns.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-276: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-276 · source CWE mapping
Incorrect Default Permissions
Incorrect Default Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.