CVE-2024-47091: Privilege escalation via mk_mysql agent plugin on Windows
Privilege escalation in the mk_mysql agent plugin on Windows in Checkmk <2.4.0p29, <2.3.0p47, and 2.2.0 (EOL) allows a local unprivileged user able to create a Windows service whose name matches 'MySQL' or 'MariaDB' (or with write access to a binary referenced by such a service) to execute arbitrary code in the context of the Checkmk agent service, which typically runs as SYSTEM.
Security readout for executives and security teams
Plain-English summary
This is a local privilege escalation issue in Checkmk’s Windows mk_mysql agent plugin. A user who already has limited access to a Windows host may be able to make code run as the Checkmk agent service, typically SYSTEM. It is not a remote internet-facing bug based on the provided sources.
Executive priority
Treat as a targeted host-hardening and patching priority, not a broad emergency. Prioritize Windows monitoring hosts and servers where untrusted local users exist, because successful exploitation can produce SYSTEM-level control on the host.
Technical view
CVE-2024-47091 is a CWE-427 issue affecting Checkmk before 2.4.0p29 and 2.3.0p47, plus 2.2.0 EOL. On Windows, the mk_mysql plugin can trust matching MySQL or MariaDB service references in a way that lets a local low-privileged user escalate to the Checkmk agent service context.
Likely exposure
Exposure is likely limited to Windows systems running affected Checkmk agents with the mk_mysql plugin and relevant MySQL or MariaDB service conditions. Risk increases where local users can create Windows services or modify binaries referenced by those services.
Exploitation context
The source bundle does not show CISA KEV listing or other evidence of active exploitation. Exploitation requires local privileges and a precondition involving service creation rights or write access to a referenced service binary.
Researcher notes
The key exposure questions are plugin presence, Windows platform, Checkmk version, service naming, and local permission model. The provided evidence is sufficient for triage but does not include public exploit evidence, detailed vendor internals, or compensating-control specifics.
Mitigation direction
Upgrade affected Checkmk 2.4 deployments to 2.4.0p29 or later.
Upgrade affected Checkmk 2.3 deployments to 2.3.0p47 or later.
Replace or isolate Checkmk 2.2.0 because it is listed as EOL.
Review vendor guidance before applying compensating controls.
Restrict local service creation and writable service binary paths on Windows hosts.
Validation and detection
Inventory Windows Checkmk agents and identify systems using the mk_mysql plugin.
Confirm installed Checkmk versions against 2.4.0p29 and 2.3.0p47 fixed thresholds.
Check whether local non-admin users can create services on affected hosts.
Review MySQL or MariaDB service binary paths for improper write permissions.
Verify EOL 2.2.0 instances are removed, upgraded, or formally risk accepted.
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-427: 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.
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.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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-427 · source CWE mapping
Uncontrolled Search Path Element
Uncontrolled Search Path Element represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.