dbcve.org
CheckmkApplication

CVE-2022-46302

HIGH · 8.8 CVSS v3.1 Published 2023-04-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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
Broad access controls could allow site users to directly interact with the system Apache installation when providing the reverse proxy configurations for Tribe29's Checkmk <= 2.1.0p6, Checkmk <= 2.0.0p27, and all versions of Checkmk 1.6.0 (EOL) allowing an attacker to perform remote code execution with root privileges on the underlying host.

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 2.1.0p6 and earlier, 2.0.0p27 and earlier, and 1.6.0 contain insufficient access control restrictions in their reverse proxy configuration, allowing site users to directly access the underlying Apache web server installation and potentially execute arbitrary code with root privileges on the host system.

MitigationUpgrade Checkmk to version 2.1.0p7 or later (for 2.1.x) and 2.0.0p28 or later (for 2.0.x), and review reverse proxy configurations to enforce proper access restrictions between site users and the Apache service.

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

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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 the Checkmk command to display the version, typically using 'cmk --version' or checking the About section in the Checkmk web interface
    Affected if The installed version is 1.6.0, any 2.0.0 up to patch 27, or any 2.1.0 up to patch 6
  2. Locate Apache configuration files
    Find the Apache configuration directory used by Checkmk, typically under the Checkmk installation path (omd sites) or /etc/apache2 configuration directories
    Affected if Apache configuration files exist and are accessible by site users without proper restrictions
  3. Inspect reverse proxy configuration
    Examine the Apache or reverse proxy configuration files for rules that restrict access between Checkmk site users and the underlying Apache service
    Affected if No access control restrictions exist between site users and the Apache backend, or reverse proxy rules are missing or misconfigured
  4. Verify user isolation between sites
    Test whether a user authenticated to one Checkmk site can directly access the Apache service or other sites by manipulating URL paths or using direct Apache endpoints
    Affected if Users can bypass site boundaries and access the Apache web server directly

A Checkmk installation is affected if it runs version 1.6.0, 2.0.0 up to p27, or 2.1.0 up to p6 and lacks proper access control restrictions in its reverse proxy configuration between site users and Apache.

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 version 2.1.0p7 or later (for 2.1.x) and 2.0.0p28 or later (for 2.0.x), and review reverse proxy configurations to enforce proper access restrictions between site users and the Apache service.

Recommended fix High confidence

Checkmk 2.1.0p7 or later, 2.0.0p28 or later, or migrate from 1.6.0 to 2.0.0/2.1.0

  1. 1. Identify the current Checkmk version in use (1.6.0, 2.0.0, or 2.1.0)
  2. 2. For Checkmk 2.1.0: Upgrade to version 2.1.0p7 or later
  3. 3. For Checkmk 2.0.0: Upgrade to version 2.0.0p28 or later
  4. 4. For Checkmk 1.6.0: This version is End-of-Life (EOL) with no patches; migrate to a supported version such as 2.0.0 or 2.1.0
  5. 5. After upgrade, verify the reverse proxy configuration is properly secured and restrict user access to Apache configuration settings
  6. 6. Test that the site functions correctly after the upgrade
Caveat Checkmk 1.6.0 is EOL with no security patches; upgrade requires migration to 2.x. Test all custom configurations and integrations after upgrading.

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-2022-46302 — 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-46302 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