CVE-2014-2331
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 1.2.2p2, 1.2.2p3, and 1.2.3i5 allows remote authenticated users to execute arbitrary Python code via a crafted rules.mk file in a snapshot. 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 · high confidenceCheck_MK versions 1.2.2p2 through 1.2.3i5 contain a code injection vulnerability in the snapshot import functionality. Remote authenticated attackers can execute arbitrary Python code by uploading a specially crafted rules.mk file within a snapshot. The vulnerability can be chained with CVE-2014-2330 to achieve remote code execution without valid credentials.
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
- M
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:S/C:C/I:C/A:C
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 versionRun 'cmk --version' or 'check_mk --version' from command line, or check the version displayed in the web interface login pageAffected if Version is 1.2.2p2, 1.2.2p3, 1.2.2p4, 1.2.2p5, 1.2.3, 1.2.3i1, 1.2.3i2, 1.2.3i3, 1.2.3i4, or 1.2.3i5 (versions between 1.2.2p2 and 1.2.3i5 inclusive)
-
Verify web interface is exposedConfirm the Check_MK web interface (usually on port 80/443 or 5000) is accessible from network locationsAffected if Web interface is reachable from untrusted networks
-
Check snapshot import availabilityLog into the web interface and navigate to 'WATO - Configuration' > 'Backup & Sync' or similar snapshot/sync section to see if snapshot import option existsAffected if Snapshot import feature is present and accessible to the authenticated user
-
Confirm authentication requirementsDetermine whether snapshot import requires administrative privileges or if any authenticated user can access itAffected if Snapshot import is accessible to non-administrator users
Environment is affected if running Check_MK version 1.2.2p2 through 1.2.3i5 with the web interface accessible and snapshot import functionality enabled for the attacker
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 a patched version. As an interim control, disable or restrict snapshot import functionality and limit access to the web interface to trusted IP addresses only.
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2331 — 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-2331 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