dbcve.org
CheckmkApplication

CVE-2022-33912

HIGH · 7.8 CVSS v3.1 Published 2022-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A permission issue affects users that deployed the shipped version of the Checkmk Debian package. Packages created by the agent bakery (enterprise editions only) were not affected. Using the shipped version of the agents, the maintainer scripts located at /var/lib/dpkg/info/ will be owned by the user and the group with ID 1001. If such a user exists on the system, they can change the content of these files (which are then executed by root). This leads to a local privilege escalation on the monitored host. Version 1.6 through 1.6.9p29, version 2.0 through 2.0.0p26, version 2.1 through 2.1.0p3, and version 2.2.0i1 are affected.

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

The Checkmk Debian package ships with maintainer scripts in /var/lib/dpkg/info/ owned by UID/GID 1001. If a user with UID 1001 exists on the monitored host, they can modify these root-executed scripts to achieve local privilege escalation.

MitigationUpdate to patched versions (1.6.0p30, 2.0.0p27, 2.1.0p4, 2.2.0i2 or later) or use packages from the enterprise edition agent bakery. Alternatively, verify no user with UID 1001 exists on the system.

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:= 1.6.0= 2.0.0= 2.1.0= 2.2.0
CheckmkApplication
Affected:= 1.6.0b10= 1.6.0b11

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. Identify installed Checkmk version
    Run 'dpkg -l | grep checkmk' or 'omd version' to find the installed Checkmk version and compare it to affected versions (1.6.0, 2.0.0, 2.1.0, 2.2.0 or 1.6.0b10, 1.6.0b11)
    Affected if The installed version matches one of the affected versions listed
  2. Verify ownership of dpkg maintainer scripts
    Run 'ls -la /var/lib/dpkg/info/ | grep checkmk' to list the owner UID/GID of the Checkmk package scripts
    Affected if The files are owned by UID 1001 and GID 1001
  3. Check for user with UID 1001
    Run 'getent passwd 1001' or 'grep 1001 /etc/passwd' to check if any user account has UID 1001
    Affected if A user account exists with UID 1001 on the system

You are affected if Checkmk version is one of the affected versions, the dpkg info scripts are owned by UID/GID 1001, AND a local user with UID 1001 exists on the system.

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

Update to patched versions (1.6.0p30, 2.0.0p27, 2.1.0p4, 2.2.0i2 or later) or use packages from the enterprise edition agent bakery. Alternatively, verify no user with UID 1001 exists on the system.

Recommended fix High confidence

Upgrade to the latest stable Checkmk release (2.3.x or newer) or at minimum to the patched version for your branch: 1.6.0p30, 2.0.0p27, 2.1.0p4, or 2.2.0

  1. 1. Identify your current Checkmk version by running: `cmk --version` or checking the apt/dpkg package
  2. 2. For Checkmk 1.6.x: Upgrade to version 1.6.0p30 or later
  3. 3. For Checkmk 2.0.x: Upgrade to version 2.0.0p27 or later
  4. 4. For Checkmk 2.1.x: Upgrade to version 2.1.0p4 or later
  5. 5. For Checkmk 2.2.0: Upgrade to version 2.2.0 or later
  6. 6. After upgrading, verify that files in /var/lib/dpkg/info/ are owned by root:root with proper permissions
  7. 7. If a user with UID/GID 1001 exists on the system, audit any suspicious modifications to dpkg maintenance scripts
Caveat Review Checkmk upgrade documentation for your edition (raw, enterprise) as minor version upgrades may require migration steps; test in staging before production deployment

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

Fix this in Checkmk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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