dbcve.org
CheckmkApplication

CVE-2024-28829

HIGH · 7.8 CVSS v3.1 Published 2024-08-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Least privilege violation and reliance on untrusted inputs in the mk_informix Checkmk agent plugin before Checkmk 2.3.0p12, 2.2.0p32, 2.1.0p47 and 2.0.0 (EOL) allows local users to escalate privileges.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The mk_informix Checkmk agent plugin suffers from a least privilege violation and reliance on untrusted inputs, allowing local users to escalate privileges to higher permission levels. This affects Checkmk versions prior to 2.3.0p12, 2.2.0p32, and 2.1.0p47.

MitigationUpgrade Checkmk to version 2.3.0p12, 2.2.0p32, or 2.1.0p47 (or later) to patch the vulnerable mk_informix plugin.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CheckmkApplication
Affected:= 2.0.0= 2.1.0= 2.2.0= 2.3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the mk_informix plugin
    Search for the mk_informix file in typical Checkmk agent plugin directories (such as /opt/checkmk/agent/plugins/ or the agent plugin folder). Use commands like 'find / -name mk_informix 2>/dev/null' or check the installed Checkmk agent plugin path.
    Affected if The mk_informix plugin file exists on the system - this confirms the vulnerable component is present.
  2. Determine the installed Checkmk version
    Run 'cmk --version' or check the Checkmk package version using the system package manager (dpkg, rpm, etc.). Alternatively, inspect the version file in the Checkmk installation directory.
    Affected if The installed version is 2.0.0, 2.1.0, 2.2.0, or 2.3.0 AND is earlier than 2.3.0p12, 2.2.0p32, or 2.1.0p47 respectively.
  3. Verify the plugin is executable by non-root users
    Check file permissions on the mk_informix plugin using 'ls -la <path_to_mk_informix>'. Look for world-executable permissions or unusual ownership that could allow privilege escalation.
    Affected if The plugin has overly permissive execute permissions (such as world-executable) or is owned by a privileged user but writable by others.
  4. Check plugin configuration for untrusted input handling
    Examine the mk_informix plugin configuration files and the plugin script itself for references to external inputs, environment variables, or file paths that could be manipulated by local users.
    Affected if The plugin accepts or processes untrusted inputs (such as user-controlled file paths or environment variables) without proper validation.

A user is affected if the mk_informix plugin is present AND the installed Checkmk version falls within the vulnerable version range (prior to 2.3.0p12, 2.2.0p32, or 2.1.0p47), especially if the plugin has permissive file permissions or processes untrusted inputs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Checkmk to version 2.3.0p12, 2.2.0p32, or 2.1.0p47 (or later) to patch the vulnerable mk_informix plugin.

Recommended fix High confidence

2.3.0p12 (or 2.2.0p32 or 2.1.0p47 depending on your branch)

  1. Identify the current Checkmk version in use
  2. Determine which version branch (2.0.x, 2.1.x, 2.2.x, or 2.3.x) is currently installed
  3. For version 2.3.x: Upgrade to Checkmk 2.3.0p12 or later
  4. For version 2.2.x: Upgrade to Checkmk 2.2.0p32 or later
  5. For version 1.2.x: Upgrade to Checkmk 2.1.0p47 or later
  6. For version 2.0.x: Note that this branch is End-of-Life (EOL); migrate to a supported version (2.1.0p47, 2.2.0p32, or 2.3.0p12)
  7. Follow Checkmk's standard upgrade procedure (backup configuration, stop services, install new packages, restart services)
  8. Verify the mk_informix plugin has been updated to the patched version
Caveat Version 2.0.0 is End-of-Life; users must migrate to a supported branch

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Checkmk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-28829 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-28829 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data