CVE-2014-2332
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 · uneditedCheck_MK before 1.2.2p3 and 1.2.3x before 1.2.3i5 allows remote authenticated users to delete arbitrary files via a request to an unspecified link, related to "Insecure Direct Object References." NOTE: this can be exploited by remote attackers by leveraging CVE-2014-2330.
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 · moderate confidenceCheck_MK versions before 1.2.2p3 and 1.2.3x before 1.2.3i5 contain an Insecure Direct Object Reference (IDOR) vulnerability that allows authenticated remote users to delete arbitrary files on the system via an unspecified URL endpoint. The vulnerability can be chained with CVE-2014-2330 (authentication bypass) to allow unauthenticated remote attackers to exploit the file deletion capability.
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<= 1.2.2<= 1.2.3CVSS 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
- Authentication
- Single
- Confidentiality
- None
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:N/I:P/A:P
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.
-
Identify Check_MK installation and versionLocate the Check_MK installation directory and check the version file or use the 'cmk --version' command if available. Common paths include /opt/omd, /usr/local/check_mk, or within OMD (Open Monitoring Distribution) setups.Affected if Installed version is 1.2.2 or lower, or 1.2.3i4 or lower (1.2.3x versions before 1.2.3i5)
-
Verify web interface exposureDetermine if the Check_MK web interface (typically on port 80/443 or OMD default ports like 5000) is accessible from untrusted networks. Check firewall rules, reverse proxy configurations, and network ACLs.Affected if The Check_MK web interface is reachable from networks outside trusted administration IPs
-
Confirm authentication configurationReview Check_MK authentication settings in the etc/authentication configuration files or OMD site configuration. Verify that user accounts are properly secured with strong passwords and that default credentials are not in use.Affected if Authentication is not properly configured, weak passwords exist, or the site uses default credentials (making chaining with CVE-2014-2330 possible)
-
Check for unauthorized file access indicatorsReview web server access logs and Check_MK audit logs for unusual delete requests or requests to unexpected URL endpoints that could indicate exploitation attempts.Affected if Suspicious delete operations appear in logs, especially from unauthenticated sources or unusual IP addresses
You are affected if Check_MK version is 1.2.2p2 or lower, or 1.2.3i4 or lower AND the web interface is network-accessible to untrusted users.
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.
From vendor dataUpgrade Check_MK to version 1.2.2p3, 1.2.3i5, or later. If immediate patching is not possible, restrict network access to the Check_MK web interface to trusted IPs only.
- Consultation2.0 h
- Implementation1.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2332 — 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-2014-2332 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