CVE-2022-31258
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 before 1.6.0p29, 2.x before 2.0.0p25, and 2.1.x before 2.1.0b10, a site user can escalate to root by editing an OMD hook symlink.
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 confidenceA local privilege escalation vulnerability in Checkmk allows a site user to gain root access by manipulating an OMD (Open Monitoring Distribution) hook symlink. The vulnerability exists in Checkmk versions prior to 1.6.0p29, 2.0.0p25, and 2.1.0b10.
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= 1.6.0= 2.0.0= 2.1.0= 1.6.0b10= 1.6.0b11= 1.6.0p10= 1.6.0p11= 1.6.0p12= 1.6.0p13= 1.6.0p14= 1.6.0p15= 1.6.0p16= 1.6.0p17= 1.6.0p18CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Checkmk versionRun command: omd version or check /omd/versions/ directory listing. On the Checkmk web interface, go to Help > About to view the version.Affected if Version is earlier than 1.6.0p29, or between 2.0.0 and 2.0.0p24, or between 2.1.0 and 2.1.0b9, or matches any of the specific vulnerable versions (1.6.0b10-b11, 1.6.0p10-p18, 1.6.0, 2.0.0, or 2.1.0).
-
Confirm OMD site user contextRun command: whoami to verify you are running as a site user (typically username starts with 'omd' or is the site name). The vulnerability requires a site user account to exploit.Affected if Running as a site user on an affected Checkmk version.
-
Inspect OMD hook directories for symlinksList contents of OMD hook directories, typically found under /omd/sites/<site_name>/etc/omd/ or within the etc directory structure. Run: ls -la /omd/sites/<site_name>/etc/omd/site_perf. Check for symlinks pointing outside expected locations.Affected if Any suspicious or unexpected symlinks exist in OMD hook directories that were not created by the administrator.
You are affected if your installed Checkmk version falls within the vulnerable ranges AND you are running as a site user with access to OMD hook directories.
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 · scoped1.6.0
Upgrade Checkmk to version 1.6.0p29, 2.0.0p25, 2.1.0b10 or later. If immediate patching is not possible, restrict site user access and monitor for suspicious symlink modifications in OMD hook directories.
1.6.0p29 (1.6.x branch) / 2.0.0p25 (2.0.x branch) / 2.1.0b10 (2.1.x branch)
- Upgrade Checkmk to version 1.6.0p29 or later if using the 1.6.0 branch
- OR upgrade Checkmk to version 2.0.0p25 or later if using the 2.0.x branch
- OR upgrade Checkmk to version 2.1.0b10 or later if using the 2.1.x branch
- After upgrading, verify the OMD hook symlink permissions have been properly secured
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-31258 — 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-31258 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