dbcve.org
CheckmkApplication

CVE-2023-0284

HIGH · 8.1 CVSS v3.1 Published 2023-01-26
Fix available
A fix is available. Upgrade to 2.0.0 or later.
See remediation →
87/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
Improper Input Validation of LDAP user IDs in Tribe29 Checkmk allows attackers that can control LDAP user IDs to manipulate files on the server. Checkmk <= 2.1.0p19, Checkmk <= 2.0.0p32, and all versions of Checkmk 1.6.0 (EOL) 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

Improper input validation of LDAP user IDs in Tribe29 Checkmk allows attackers who can control LDAP user IDs to manipulate files on the server. This is a path traversal or file inclusion vulnerability stemming from insufficient validation of user-supplied LDAP attributes.

MitigationUpgrade Checkmk to a version beyond 2.1.0p19 or 2.0.0p32. For EOL version 1.6.0, migrate to a supported version. Implement strict input validation on LDAP user attributes before using them in file operations.

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.0.0= 2.1.0
CheckmkApplication
Affected:>= 1.6.0, < 2.0.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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 the installed Checkmk version
    Run the command 'cmk --version' or check the version through the web interface under 'Help' > 'About Checkmk'. Compare this version number against the affected ranges: exactly 2.0.0 or 2.1.0, or any version from 1.6.0 up to but not including 2.0.0.
    Affected if The installed version is 2.0.0, 2.1.0, or falls within 1.6.0 to 1.9.x inclusive.
  2. Confirm LDAP user synchronization is configured
    In the web interface, navigate to 'Setup' > 'Users' > 'LDAP' (or 'Setup' > 'General' > 'LDAP/Active Directory') to check if any LDAP connections or LDAP user sync rules are defined and enabled.
    Affected if LDAP integration is active and users are being synchronized from an LDAP directory.
  3. Verify LDAP connector configuration for user attribute mapping
    Examine the LDAP connector configuration file (typically found under /omd/sites/<site>/etc/check_mk/conf.d/wato/ or accessed via the web interface) to see which LDAP attributes are mapped to Checkmk user fields, particularly any attributes that could influence file paths or be used in file operations.
    Affected if Custom LDAP attribute mappings exist that map user-supplied LDAP attributes to user profile settings in Checkmk.
  4. Check for recent LDAP user sync operations
    Review the audit log or event log for Checkmk (accessible via 'General' > 'Audit Log' in the web interface) to look for any unusual or unexpected LDAP sync events that may indicate exploitation attempts.
    Affected if Audit logs show unexpected file operations or attribute modifications during LDAP synchronization that were not initiated by legitimate administrators.

A user is affected if they run Checkmk version 1.6.0 through 1.9.x, or exactly version 2.0.0 or 2.1.0, and have LDAP synchronization enabled with user attributes that could be manipulated by an attacker who controls LDAP entries.

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
Upgrade available Upgrade to 2.0.0 or later
Fixed in 2.0.0
Interim mitigation

Upgrade Checkmk to a version beyond 2.1.0p19 or 2.0.0p32. For EOL version 1.6.0, migrate to a supported version. Implement strict input validation on LDAP user attributes before using them in file operations.

Recommended fix High confidence

Checkmk 2.0.0p33+ or 2.1.0p20+ (1.6.0 is EOL, migrate to 2.x)

  1. 1. Identify your current Checkmk version using the Checkmk web interface or command line (omd version)
  2. 2. If running Checkmk 1.6.0: This version is End-of-Life (EOL); migrate to a supported version (2.0.0 or 2.1.0)
  3. 3. If running Checkmk 2.0.0.x: Upgrade to Checkmk 2.0.0p33 or later
  4. 4. If running Checkmk 2.1.0.x: Upgrade to Checkmk 2.1.0p20 or later
  5. 5. Download the appropriate update from checkmk.com and follow standard upgrade procedures
  6. 6. After upgrade, verify LDAP user configuration and test authentication
Caveat Upgrading to newer Checkmk versions may require testing of existing configurations; 1.6.0 is EOL with no patches available

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

Fix this in Checkmk Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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