CVE-2014-2330
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 · uneditedMultiple cross-site request forgery (CSRF) vulnerabilities in the Multisite GUI in Check_MK before 1.2.5i2 allow remote attackers to hijack the authentication of users for requests that (1) upload arbitrary snapshots, (2) delete arbitrary files, or possibly have other unspecified impact via unknown vectors.
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 confidenceMultiple CSRF vulnerabilities in Check_MK's Multisite GUI allow remote attackers to hijack authenticated user sessions to upload arbitrary snapshots, delete arbitrary files, and potentially perform other unspecified actions via forged requests.
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
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/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 installed Check_MK versionRun 'cmk --version' or check the Check_MK version file in the installation directory, typically found in /opt/omd/versions or via the OMD management command 'omd version'Affected if The installed version is 1.2.2 or earlier, or 1.2.3 or earlier (any version <= 1.2.2 or <= 1.2.3)
-
Confirm Multisite GUI is enabledCheck if the Multisite web interface is accessible by accessing the Check_MK web URL (typically port 80/443 on the monitoring server)Affected if The Multisite GUI is accessible without additional access restrictions
-
Check for active user sessionsReview active authenticated user sessions in the Check_MK environment or check if users have active sessions in the web interfaceAffected if Users have active authenticated sessions in the Multisite GUI, as CSRF exploits require hijacking these sessions
-
Verify no external CSRF protection existsInspect the Multisite configuration files for anti-CSRF token implementations. Check files like 'web/plugins/security.py' or similar security-related modules in the Check_MK installationAffected if No anti-CSRF tokens are implemented in the Multisite forms (this confirms the vulnerability is present in the version)
The environment is affected if Check_MK version is 1.2.2 or lower, or 1.2.3 or lower, and the Multisite GUI is accessible with active authenticated user sessions.
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 to Check_MK version 1.2.5i2 or later which contains CSRF protection. Alternatively, implement anti-CSRF tokens on all state-changing forms in the Multisite GUI.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2330 — 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-2330 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