dbcve.org
CheckmkApplication

CVE-2022-46303

HIGH · 7.5 CVSS v3.1 Published 2023-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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
Command injection in SMS notifications in Tribe29 Checkmk <= 2.1.0p10, Checkmk <= 2.0.0p27, and Checkmk <= 1.6.0p29 allows an attacker with User Management permissions, as well as LDAP administrators in certain scenarios, to perform arbitrary commands within the context of the application's local permissions.

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

Command injection vulnerability in the SMS notification functionality of Tribe29 Checkmk allows authenticated attackers with User Management permissions (or LDAP administrators in certain configurations) to execute arbitrary commands with the application's local user privileges. The vulnerability stems from insufficient input sanitization in the SMS notification processing path.

MitigationApply vendor patches (Checkmk 2.1.0p11, 2.0.0p28, 1.6.0p30 or later). As an interim control, restrict User Management permissions to only highly trusted administrators and review LDAP configuration settings to limit exposure.

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.0.0= 1.6.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
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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. Confirm Checkmk installation and identify version
    Locate the Checkmk installation directory and check the version file or use 'cmk --version' command to determine the installed version
    Affected if Installed version is exactly 2.1.0, 2.0.0, or 1.6.0 (without vendor patches)
  2. Verify SMS notification feature is configured
    Access Checkmk Setup > Notifications > Notifications and check if any SMS notification rules or notification methods are enabled
    Affected if SMS notification rules or custom notification scripts are configured and active
  3. Identify users with User Management permissions
    Navigate to Setup > Users > Roles or check the LDAP/Active Directory integration settings to list accounts with User Management or Administrator privileges
    Affected if Multiple users or LDAP admins have User Management permissions, increasing attack surface
  4. Review notification script configuration
    Examine the ~/checkmk/notifications/ or /omd/sites/*/local/lib/python3/cmk/gui/plugins/wato/ directory for custom SMS notification scripts and verify input handling
    Affected if Custom notification scripts exist that pass unsanitized user input to shell commands

Your environment is affected if you run Checkmk versions 2.1.0, 2.0.0, or 1.6.0 with SMS notification functionality configured and users who have User Management permissions.

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

Apply vendor patches (Checkmk 2.1.0p11, 2.0.0p28, 1.6.0p30 or later). As an interim control, restrict User Management permissions to only highly trusted administrators and review LDAP configuration settings to limit exposure.

Recommended fix Moderate confidence

Upgrade to Checkmk 1.6.0p30+ (for 1.6.x), 2.0.0p28+ (for 2.0.x), 2.1.0p11+ (for 2.1.x), or latest stable 2.2.x/2.3.x release

  1. 1. Identify your current Checkmk version by navigating to 'Setup' > 'General' > 'About Checkmk'
  2. 2. If running version 1.6.0, upgrade to version 1.6.0p30 or later
  3. 3. If running version 2.0.0, upgrade to version 2.0.0p28 or later
  4. 4. If running version 2.1.0, upgrade to version 2.1.0p11 or later
  5. 5. If running any version between these (e.g., 2.2.x), verify the version is not in the affected range and upgrade to the latest stable release
  6. 6. After upgrade, verify SMS notification configuration does not contain unexpected commands
  7. 7. Review user permissions in 'Setup' > 'Users' > 'LDAP' to ensure only trusted administrators have access
Caveat Major version upgrades (e.g., 1.6 to 2.x) may require configuration migration and have compatibility considerations with custom plugins or integrations

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

Fix this in Checkmk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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