Security readout for executives and security teams
Plain-English summary
Some Wazuh build/provisioning scripts disabled HTTPS certificate checks while downloading dependencies. If an attacker can intercept build network traffic, they could substitute malicious content and compromise the resulting build environment. This is a supply-chain risk rather than a typical internet-facing Wazuh runtime flaw.
Executive priority
Treat this as a moderate supply-chain risk. Prioritize teams that build or customize Wazuh agents, because compromise could affect downstream deployments even if production Wazuh services are not directly exposed.
Technical view
CVE-2025-15612 covers curl use with -k/--insecure in Wazuh provisioning scripts and Dockerfiles. The issue maps to CWE-295 and CWE-829, with CVSS 4.0 score 6.3. Successful exploitation requires network-positioned interception during builds and could lead to modified dependencies, remote code execution, or compromised build artifacts.
Likely exposure
Exposure is most likely in organizations building Wazuh agents or related images from the affected provisioning scripts, especially in CI/CD, shared networks, or environments using internal forks of those files.
Exploitation context
The source bundle does not report active exploitation, and CISA KEV status is false. Practical exploitation requires a man-in-the-middle position during dependency retrieval, making the attack higher effort but meaningful for supply-chain compromise.
Researcher notes
Evidence is limited to the CVE record and referenced advisories. The provided data names insecure TLS validation in build/provisioning scripts, not a remotely exploitable Wazuh server component. No public exploit or confirmed exploitation is cited in the bundle.
Mitigation direction
- Review Wazuh’s advisory for supported remediation or fixed build guidance.
- Stop using affected build scripts on untrusted or shared networks until reviewed.
- Audit internal forks for curl -k or --insecure in provisioning paths.
- Require certificate validation for dependency downloads in build infrastructure.
- Rebuild artifacts only after trusted build inputs and scripts are verified.
Validation and detection
- Inventory Wazuh provisioning scripts, Dockerfiles, and agent build pipelines in use.
- Confirm whether listed affected Wazuh versions or derived scripts are present.
- Review build definitions for curl -k or --insecure usage.
- Check CI/CD logs for builds performed over interceptable network paths.
- Verify build artifacts were produced from trusted scripts and dependencies.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-295: 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.
Open ATT&CK lookupCWE-829: 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.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-15612 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N2.22.5VulnCheckVulnerability scoring details
Base CVSS 4.0 score
6.3MediumVector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
4.8MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/wazuh/wazuh/security/advisories/GHSA-wvg9-7q49-c7mgCVE reference, VulnCheck · vendor-advisory
- https://www.vulncheck.com/advisories/various-uses-of-curl-without-verifying-the-authenticity-of-the-ssl-certificate-leading-to-mitm-rce-in-build-infrastructureCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Certificate Validation
Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Inclusion of Functionality from Untrusted Control Sphere
Inclusion of Functionality from Untrusted Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.