CVE-2025-1075
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 · uneditedInsertion of Sensitive Information into Log File in Checkmk GmbH's Checkmk versions <2.3.0p27, <2.2.0p40, and 2.1.0p51 (EOL) causes LDAP credentials to be written to Apache error log file accessible to administrators.
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 confidenceLDAP credentials are being written to Apache error log files in Checkmk versions prior to 2.3.0p27, 2.2.0p40, and 2.1.0p51, exposing sensitive authentication credentials to administrators who have access to these log files.
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< 2.1.0= 2.1.0= 2.2.0= 2.3.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Determine installed Checkmk versionRun command: omd version or check /omd/versions/default_version. This shows the exact Checkmk version including patch level (e.g., 2.3.0p10, 2.2.0p35).Affected if Version is 2.1.0 up to 2.1.0p50, or 2.2.0 up to 2.2.0p39, or 2.3.0 up to 2.3.0p26. Also affects versions below 2.1.0.
-
Verify LDAP authentication is configuredCheck if LDAP user connections exist: Look in Checkmk UI under Setup > Users > LDAP connections, or inspect file /omd/sites/<sitename>/var/confdLDAP.mk if it contains active LDAP connection settings.Affected if LDAP connections are configured and active in Checkmk.
-
Inspect Apache error logs for exposed credentialsSearch Apache error log at /omd/sites/<sitename>/var/log/apache/error.log (or /omd/sites/<sitename>/var/log/apache2/error.log) for LDAP bind password strings. Use: grep -i 'password\|bind' /omd/sites/<sitename>/var/log/apache/error.log 2>/dev/null | head -100Affected if Log entries contain LDAP bind passwords, bind DNs, or cleartext credentials in the Apache error log files.
User is affected if running a Checkmk version prior to 2.3.0p27, 2.2.0p40, or 2.1.0p51 AND has LDAP authentication configured, AND Apache error logs contain visible LDAP credentials.
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 · scoped2.1.0
Upgrade to Checkmk versions 2.3.0p27, 2.2.0p40 or later. Version 2.1.0 is End-of-Life and requires migration to a supported release.
2.3.0p27 or later (2.2.x branch: 2.2.0p40+, 2.1.x branch: 2.1.0p51)
- 1. Identify current Checkmk version by checking the web interface footer or running 'cmk --version'
- 2. For Checkmk 2.3.x: Upgrade to version 2.3.0p27 or later
- 3. For Checkmk 2.2.x: Upgrade to version 2.2.0p40 or later
- 4. For Checkmk 2.1.x: Upgrade to version 2.1.0p51 (note: 2.1.x is End of Life, consider migrating to a supported branch)
- 5. After upgrade, verify Apache error logs no longer contain LDAP credentials
- 6. Rotate any LDAP credentials that may have been exposed in logs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1075 — 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-2025-1075 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