CVE-2022-24566
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 · uneditedIn Checkmk <=2.0.0p19 fixed in 2.0.0p20 and Checkmk <=1.6.0p27 fixed in 1.6.0p28, the title of a Predefined condition is not properly escaped when shown as condition, which can result in Cross Site Scripting (XSS).
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 confidenceThis is a stored Cross Site Scripting (XSS) vulnerability in Checkmk where the title of a Predefined condition is not properly escaped when displayed to users. An attacker who can create or modify predefined conditions could inject malicious JavaScript code that executes in the browsers of other users viewing those conditions.
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= 1.6.0= 2.0.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Checkmk versionRun the command to check the installed Checkmk version (typically via 'cmk --version' or checking the GUI about page)Affected if The version is 1.6.0 through 1.6.0p27, or 2.0.0 through 2.0.0p19 (the version falls within the affected ranges before the patches)
-
Confirm access to predefined conditionsNavigate to the predefined conditions module in the Checkmk interface (usually under 'Setup' > 'Service levels' or similar location where predefined conditions are managed)Affected if The user has permission to create or modify predefined conditions in the Checkmk instance
-
Inspect existing predefined condition titlesView the list of predefined conditions and examine each condition's title field for any unexpected characters, script tags, or JavaScript codeAffected if Any predefined condition title contains raw HTML, script tags, or JavaScript code that would execute if rendered in a browser
-
Test for XSS vulnerability in title fieldCreate a new predefined condition with a benign test payload in the title field (such as <script>alert('XSS')</script>), save it, then view the condition to see if the alert triggersAffected if The JavaScript executes when viewing the predefined condition, indicating the title is not being escaped
You are affected if running a vulnerable Checkmk version (1.6.0 to 1.6.0p27 or 2.0.0 to 2.0.0p19) AND have predefined conditions with unsanitized titles that could execute malicious JavaScript in other users' browsers.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Checkmk to version 2.0.0p20 or 1.6.0p28 (or later) to obtain the patch that properly escapes the condition title field before rendering.
Checkmk 2.0.0p20 (for 2.x branch) or Checkmk 1.6.0p28 (for 1.6.0 branch)
- 1. Identify the current Checkmk version by checking the installation (e.g., via the web UI or command line)
- 2. If running Checkmk 2.0.0 through 2.0.0p19, upgrade to version 2.0.0p20 or later
- 3. If running Checkmk 1.6.0 through 1.6.0p27, upgrade to version 1.6.0p28 or later
- 4. Verify the upgrade was successful by checking the new version number
- 5. Test that predefined conditions with special characters in titles are properly escaped
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24566 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-24566 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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