dbcve.org
CheckmkApplication

CVE-2024-28824

HIGH · 7.8 CVSS v3.1 Published 2024-03-22
Fix available
A fix is available. Upgrade to after 2.0.0 or later.
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.0b4 (beta), 2.2.0p24, 2.1.0p41 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 · moderate confidence

Local privilege escalation vulnerability in the mk_informix Checkmk agent plugin where the plugin runs with elevated privileges and relies on untrusted inputs that local users can manipulate to gain higher privileges. The flaw involves improper input validation and least privilege violations.

MitigationUpgrade Checkmk to version 2.3.0b4 (beta), 2.2.0p24, 2.1.0p41 or later. Until patched, restrict local untrusted users access to the Checkmk agent plugin directory.

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
    Find the mk_informix plugin file in your Checkmk agent plugin directory. Common locations include /usr/lib/check_mk_agent/plugins/ or /opt/check_mk/agent/plugins/
    Affected if The mk_informix plugin file exists on the system and is being used with Checkmk versions 2.0.0 or earlier, 2.1.0, 2.2.0, or 2.3.0
  2. Identify the installed Checkmk version
    Run the command to check the Checkmk version - typically 'cmk --version' or check the package version installed on the system
    Affected if The installed Checkmk version is 2.0.0 or earlier, 2.1.0, 2.2.0, or 2.3.0 (the mk_informix plugin in these versions is vulnerable)
  3. Verify plugin execution context
    Check if the mk_informix plugin is executed with elevated privileges - inspect the plugin file permissions and ownership, and check if it runs as root or another privileged user
    Affected if The mk_informix plugin runs with elevated privileges (such as root) and local untrusted users can influence its input or configuration
  4. Review plugin directory permissions
    Inspect the permissions on the directory containing the mk_informix plugin - verify which local users have read or write access to the plugin file or its configuration
    Affected if Local untrusted users have write access to the plugin file, its configuration, or the directory containing it, allowing them to manipulate inputs the plugin relies on

You are affected if the mk_informix plugin exists on your system, runs with elevated privileges, and your Checkmk version is 2.0.0 or earlier, 2.1.0, 2.2.0, or 2.3.0 with insufficient access controls on the plugin.

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
Upgrade available Upgrade to a release after 2.0.0
Interim mitigation

Upgrade Checkmk to version 2.3.0b4 (beta), 2.2.0p24, 2.1.0p41 or later. Until patched, restrict local untrusted users access to the Checkmk agent plugin directory.

Recommended fix High confidence

Upgrade to Checkmk 2.3.0b4+ (beta/stable), 2.2.0p24+, or 2.1.0p41+ depending on your current branch; 2.0.0 users must migrate to a supported branch

  1. 1. Identify the current Checkmk version by running 'cmk --version' or checking the web interface.
  2. 2. If running 2.3.0, upgrade to version 2.3.0b4 (beta) or later stable 2.3.x release.
  3. 3. If running 2.2.0, upgrade to version 2.2.0p24 or later.
  4. 4. If running 2.1.0, upgrade to version 2.1.0p41 or later.
  5. 5. If running 2.0.0, this version is EOL (End of Life); migrate to a supported version line (2.1.x, 2.2.x, or 2.3.x).
  6. 6. After upgrade, verify the mk_informix plugin has been updated and test functionality.
Caveat Upgrading across major/minor versions may introduce configuration or compatibility changes; review Checkmk migration documentation

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

Fix this in Checkmk Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-28824 — 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-28824 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