dbcve.org
CheckmkApplication

CVE-2024-47094

MEDIUM · 5.5 CVSS v3.1 Published 2024-11-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/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
Insertion of Sensitive Information into Log File in Checkmk GmbH's Checkmk versions <2.3.0p22, <2.2.0p37, <2.1.0p50 (EOL) causes remote site secrets to be written to web log files accessible to local site users.

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

Checkmk versions prior to 2.3.0p22, 2.2.0p37, and 2.1.0p50 write remote site secrets (likely API keys or authentication tokens for remote monitoring connections) into web log files. Local users with access to the site can read these log files and obtain the secrets, leading to unauthorized access to monitored remote systems.

MitigationUpgrade Checkmk to the patched versions (2.3.0p22, 2.2.0p37, or later). Additionally, audit existing web log files for exposure of secrets and rotate any compromised credentials as a precaution.

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.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
None
Availability
None

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

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 the installed Checkmk version
    Run the command to retrieve the Checkmk version (typically 'cmk --version' or check the About page in the web interface)
    Affected if The installed version is prior to 2.3.0p22, 2.2.0p37, or 2.1.0p50 (any 2.1.0, 2.2.0, or 2.3.0 version below these patch levels)
  2. Locate web log files
    Identify the directory where Checkmk stores its web server logs (commonly under the var/ or log/ directory within the Checkmk installation)
    Affected if Web log files exist on the system
  3. Search log files for remote site secrets
    Grep or search the web log files for patterns resembling API keys, authentication tokens, or credentials that may belong to remote monitoring connections (look for keywords like 'secret', 'token', 'key', 'password', or base64-encoded strings associated with remote site configurations)
    Affected if Any remote site credentials, API keys, or authentication tokens are found written to the log files

You are affected if you run a Checkmk version in the 2.1.0, 2.2.0, or 2.3.0 branches prior to the patched releases AND your web log files contain exposed remote site secrets or credentials.

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 the patched versions (2.3.0p22, 2.2.0p37, or later). Additionally, audit existing web log files for exposure of secrets and rotate any compromised credentials as a precaution.

Recommended fix High confidence

Checkmk 2.3.0p22, 2.2.0p37, or 2.1.0p50 (2.1.0p50 is EOL)

  1. 1. Identify the current Checkmk version by checking the site version (omd version <site_name>)
  2. 2. If running Checkmk 2.3.x, plan upgrade to version 2.3.0p22 or later
  3. 3. If running Checkmk 2.2.x, plan upgrade to version 2.2.0p37 or later
  4. 4. If running Checkmk 2.1.x, note this version is End of Life (EOL); upgrade to 2.1.0p50 if still under support, otherwise migrate to a supported branch (2.2 or 2.3)
  5. 5. Before upgrading, backup the Checkmk site configuration and data
  6. 6. Perform the upgrade following Checkmk's standard upgrade procedure (omd update command or GUI upgrade)
  7. 7. After upgrade, verify the web log files no longer contain remote site secrets
  8. 8. Consider rotating any exposed secrets as a precautionary measure
Caveat Upgrading across major version branches (e.g., 2.1 to 2.2 or 2.2 to 2.3) may require compatibility checks and testing; review Checkmk migration guides before proceeding

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 help mitigating

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-47094 — 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-47094 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