dbcve.org
CheckmkApplication

CVE-2024-0638

MEDIUM · 6.7 CVSS v3.1 Published 2024-03-22
Fix available
A fix is available. Upgrade to after 2.0.0 or later.
See remediation →
69/100
Remediation priority · Elevated
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 in the Checkmk agent plugins mk_oracle, mk_oracle.ps1, and mk_oracle_crs 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 · high confidence

Local privilege escalation vulnerability in Checkmk agent Oracle plugins (mk_oracle, mk_oracle.ps1, mk_oracle_crs) due to least privilege violation. The plugins run with elevated privileges and allow local users to execute code or manipulate the plugin execution flow to gain higher-level system access.

MitigationUpgrade Checkmk to version 2.3.0b4 (beta), 2.2.0p24, or 2.1.0p41 or later. For End-of-Life version 2.0.0, migrate to a supported version. Alternatively, restrict local access to the Checkmk agent plugin directories and Oracle database credentials.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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. Identify Checkmk installation and version
    Run command to determine if Checkmk agent is installed and retrieve its version number (e.g., 'cmk --version' or check package manager). Compare the installed version against the affected ranges: <= 2.0.0, 2.1.0, 2.2.0, or 2.3.0.
    Affected if The installed Checkmk version matches exactly one of the affected versions listed in the CVE (2.0.0 or lower, 2.1.0, 2.2.0, or 2.3.0).
  2. Locate Oracle plugin files
    Search for the presence of Oracle plugin files named 'mk_oracle', 'mk_oracle.ps1', and 'mk_oracle_crs' in the Checkmk agent plugin directories on the system.
    Affected if Any of the Oracle plugin files (mk_oracle, mk_oracle.ps1, or mk_oracle_crs) are present on the system.
  3. Verify plugin execution privileges
    Inspect the file permissions and ownership of the Oracle plugin files to determine if they are configured to run with elevated (root or administrator) privileges, or examine the execution context when the plugins are invoked by the Checkmk agent.
    Affected if The Oracle plugins execute with elevated system privileges (root or administrator) and can be accessed or manipulated by local unprivileged users.
  4. Assess local user access to plugin directories
    Examine the directory permissions on the Checkmk agent plugin directories to determine if local unprivileged users have read or write access to the plugin files or the directories containing them.
    Affected if Local unprivileged users have read or write access to the directories or files containing the Oracle plugins, allowing them to potentially modify or replace the plugins.

A system is affected if it runs a vulnerable Checkmk version (2.0.0 through 2.3.0) with the Oracle plugins (mk_oracle, mk_oracle.ps1, or mk_oracle_crs) installed and the plugins run with elevated privileges accessible to local users.

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, or 2.1.0p41 or later. For End-of-Life version 2.0.0, migrate to a supported version. Alternatively, restrict local access to the Checkmk agent plugin directories and Oracle database credentials.

Recommended fix High confidence

Minimum fixed versions: Checkmk 2.1.0p41 (branch 2.1), 2.2.0p24 (branch 2.2), 2.3.0b4 (branch 2.3); version 2.0.0 is EOL with no patch

  1. Identify the current Checkmk version in use by running 'cmk --version' or checking the Checkmk web interface
  2. Determine which branch (2.0, 2.1, 2.2, or 2.3) is currently deployed
  3. If running Checkmk 2.0.0: Note this version is End-of-Life and no patch is available; plan migration to a supported branch
  4. If running Checkmk 2.1.0: Upgrade to version 2.1.0p41 or later
  5. If running Checkmk 2.2.0: Upgrade to version 2.2.0p24 or later
  6. If running Checkmk 2.3.0: Upgrade to version 2.3.0b4 (beta) or later, or wait for the stable 2.3.1 release
  7. After upgrade, verify the mk_oracle, mk_oracle.ps1, and mk_oracle_crs plugins have been updated in /usr/lib/check_mk_agent/plugins/ or the equivalent installation directory
  8. Restart the Checkmk agent service to ensure the updated plugins are loaded
Caveat Checkmk 2.0.0 is End-of-Life with no patch available; users must migrate to a supported branch (2.1, 2.2, or 2.3)

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

Fix this in Checkmk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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