CVE-2022-37298

Shinken Solutions Shinken Monitoring Version 2.4.3 affected is vulnerable to Incorrect Access Control. The SafeUnpickler class found in shinken/safepickle.py implements a weak authentication scheme when unserializing objects passed from monitoring nodes to the Shinken monitoring server.

Published: 2022-10-20 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-37298 is rated Moderate Risk (61.5/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 1.99%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-37298

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 16.35% 1.99% -14.36%
2 2026-04-15 15.67% 16.35% +0.68%
3 2026-02-19 — 15.67% —

Full EPSS history (27 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-37298

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2022-37298

GitHub Security Advisory for CVE-2022-37298

GHSA-p373-jqfm-j6wr · Severity: critical · Ecosystem: pip — Shinken Solutions Shinken Monitoring vulnerable to Incorrect Access Control

OS Trackers for CVE-2022-37298

vendor priority summary link
ubuntu medium CVE-2022-37298 medium priority: Ubuntu including 1 source packages (shinken), 6 status rows across 6 suites (bionic, focal, jammy, trusty, upstream, xenial): DNE 3, ignored 2, needs-triage 1. https://ubuntu.com/security/CVE-2022-37298

Affected software / configurations for CVE-2022-37298

Vendor Product Version Raw CPE
shinken-monitoring shinken_monitoring 2.4.3 cpe:2.3:a:shinken-monitoring:shinken_monitoring:2.4.3:*:*:*:*:*:*:*

References for CVE-2022-37298

cvelogic Threat Intelligence