CVE-2014-5340: The wato component in Check_MK before 1.2.4p4 and 1.2.5 before 1.2.5i4 uses the pickle Python module unsafely, which allows remote attackers…
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 6.1% (FIRST EPSS); higher than 93.5% of all records.
- Fixed version: glusterfs (Red Hat:storage:2:client:el5) 0:3.7.1-11.el5; glusterfs-api (Red Hat:storage:2:client:el5) 0:3.7.1-11.el5; glusterfs-api-devel (Red Hat:storage:2:client:el5) 0:3.7.1-11.el5.
Low priority for now. Upgrade to glusterfs (Red Hat:storage:2:client:el5) 0:3.7.1-11.el5; glusterfs-api (Red Hat:storage:2:client:el5) 0:3.7.1-11.el5; glusterfs-api-devel (Red Hat:storage:2:client:el5) 0:3.7.1-11.el5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The wato component in Check_MK before 1.2.4p4 and 1.2.5 before 1.2.5i4 uses the pickle Python module unsafely, which allows remote attackers to execute arbitrary code via a crafted serialized object, related to an automation URL.
- Published
- Sep 2, 2014
- Updated
- Jun 16, 2026
- EPSS
- 6.1% · 93th percentile
- CWE
- CWE-94
Report tools
Action score
39
Low priority for now.
- CVSS
- 37 / 40 · 9.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 6.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| check mk project | check mk | cpe:2.3:a:check_mk_project:check_mk |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- check mk project check mkup to 1.2.4 inclusive
- check mk project check mk1.2.4
- check mk project check mk1.2.5
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Red Hat:storage:2:client:el5 | glusterfs | before 0:3.7.1-11.el5 | 0:3.7.1-11.el5 |
| Red Hat:storage:2:client:el5 | glusterfs-api | before 0:3.7.1-11.el5 | 0:3.7.1-11.el5 |
| Red Hat:storage:2:client:el5 | glusterfs-api-devel | before 0:3.7.1-11.el5 | 0:3.7.1-11.el5 |
| Red Hat:storage:2:client:el5 | glusterfs-cli | before 0:3.7.1-11.el5 | 0:3.7.1-11.el5 |
| Red Hat:storage:2:client:el5 | glusterfs-client-xlators | before 0:3.7.1-11.el5 | 0:3.7.1-11.el5 |
| Red Hat:storage:2:client:el5 | glusterfs-debuginfo | before 0:3.7.1-11.el5 | 0:3.7.1-11.el5 |
| Red Hat:storage:2:client:el5 | glusterfs-devel | before 0:3.7.1-11.el5 | 0:3.7.1-11.el5 |
| Red Hat:storage:2:client:el5 | glusterfs-fuse | before 0:3.7.1-11.el5 | 0:3.7.1-11.el5 |
| Red Hat:storage:2:client:el5 | glusterfs-libs | before 0:3.7.1-11.el5 | 0:3.7.1-11.el5 |
| Red Hat:storage:2:client:el5 | glusterfs-rdma | before 0:3.7.1-11.el5 | 0:3.7.1-11.el5 |
| Red Hat:storage:2:client:el5 | python-gluster | before 0:3.7.1-11.el5 | 0:3.7.1-11.el5 |
| Red Hat:storage:3:client:el6 | glusterfs | before 0:3.7.1-11.el6 | 0:3.7.1-11.el6 |
| Red Hat:storage:3:client:el6 | glusterfs-api | before 0:3.7.1-11.el6 | 0:3.7.1-11.el6 |
| Red Hat:storage:3:client:el6 | glusterfs-api-devel | before 0:3.7.1-11.el6 | 0:3.7.1-11.el6 |
| Red Hat:storage:3:client:el6 | glusterfs-cli | before 0:3.7.1-11.el6 | 0:3.7.1-11.el6 |
| Red Hat:storage:3:client:el6 | glusterfs-client-xlators | before 0:3.7.1-11.el6 | 0:3.7.1-11.el6 |
| Red Hat:storage:3:client:el6 | glusterfs-debuginfo | before 0:3.7.1-11.el6 | 0:3.7.1-11.el6 |
| Red Hat:storage:3:client:el6 | glusterfs-devel | before 0:3.7.1-11.el6 | 0:3.7.1-11.el6 |
| Red Hat:storage:3:client:el6 | glusterfs-fuse | before 0:3.7.1-11.el6 | 0:3.7.1-11.el6 |
| Red Hat:storage:3:client:el6 | glusterfs-libs | before 0:3.7.1-11.el6 | 0:3.7.1-11.el6 |
| Red Hat:storage:3:client:el6 | glusterfs-rdma | before 0:3.7.1-11.el6 | 0:3.7.1-11.el6 |
| Red Hat:storage:3:client:el6 | python-gluster | before 0:3.7.1-11.el6 | 0:3.7.1-11.el6 |
| Red Hat:storage:3.1:nagios:el6 | check-mk | before 0:1.2.6p1-3.el6rhs | 0:1.2.6p1-3.el6rhs |
| Red Hat:storage:3.1:nagios:el6 | check-mk-debuginfo | before 0:1.2.6p1-3.el6rhs | 0:1.2.6p1-3.el6rhs |
+96
Same product
check mk project: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-2331Check_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…35Monitor
- CVE-2014-2330Multiple cross-site request forgery (CSRF) vulnerabilities in the Multisite GUI in Check_MK before 1.2.5i2 allow remote attackers to hijack…27Monitor
- CVE-2017-11507A cross site scripting (XSS) vulnerability exists in Check_MK versions 1.2.8x prior to 1.2.8p25 and 1.4.0x prior to 1.4.0p9, allowing an…24Monitor
Published before and after this one in the same product
- ← EarlierCVE-2014-5338Aug 22, 2014 · Multiple cross-site scripting (XSS) vulnerabilities in the multisite component in Check_MK before 1.2.4p4 and 1.2.5 before 1.2.5i4 allow…15Monitor
- ← EarlierCVE-2014-5339Sep 2, 2014 · Check_MK before 1.2.4p4 and 1.2.5 before 1.2.5i4 allows remote authenticated users to write check_mk config files (.mk files) to arbitrary…20Monitor
- Later →CVE-2014-2329Aug 31, 2015 · Multiple cross-site scripting (XSS) vulnerabilities in Check_MK before 1.2.2p3 and 1.2.3x before 1.2.3i5 allow remote authenticated users…14Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| red hat:glusterfs | 0:3.7.1-11.el5 · Red Hat:storage:2:client:el5 | Package registry (OSV) |
| red hat:glusterfs-api | 0:3.7.1-11.el5 · Red Hat:storage:2:client:el5 | Package registry (OSV) |
| red hat:glusterfs-api-devel | 0:3.7.1-11.el5 · Red Hat:storage:2:client:el5 | Package registry (OSV) |
| red hat:glusterfs-cli | 0:3.7.1-11.el5 · Red Hat:storage:2:client:el5 | Package registry (OSV) |
| red hat:glusterfs-client-xlators | 0:3.7.1-11.el5 · Red Hat:storage:2:client:el5 | Package registry (OSV) |
| red hat:glusterfs-debuginfo | 0:3.7.1-11.el5 · Red Hat:storage:2:client:el5 | Package registry (OSV) |
| red hat:glusterfs-devel | 0:3.7.1-11.el5 · Red Hat:storage:2:client:el5 | Package registry (OSV) |
| red hat:glusterfs-fuse | 0:3.7.1-11.el5 · Red Hat:storage:2:client:el5 | Package registry (OSV) |
| red hat:glusterfs-libs | 0:3.7.1-11.el5 · Red Hat:storage:2:client:el5 | Package registry (OSV) |
| red hat:glusterfs-rdma | 0:3.7.1-11.el5 · Red Hat:storage:2:client:el5 | Package registry (OSV) |
| red hat:nfs-ganesha | 0:2.2.0-5.el6rhs · Red Hat:storage:3.1:nfs:el6 | Package registry (OSV) |
| red hat:python-gluster | 0:3.7.1-11.el5 · Red Hat:storage:2:client:el5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
If successful
- Confidentiality
- C · data can be read
- Integrity
- C · data or configuration can be modified
- Availability
- C · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- C
- Integrity impact
- C
- Availability impact
- C
Weakness class (CWE)
CWE-94 · Improper Control of Generation of Code ('Code Injection')CVSS vector
AV:N/AC:M/Au:N/C:C/I:C/A:C
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.