CVE-2022-37298

Description

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.

Category

9.8
CVSS
Severity: Critical
CVSS 3.1 •
EPSS 36.57% Top 5%
Third-Party Advisory github.com Third-Party Advisory github.com
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://github.com/naparuba/shinken/commit/2dae40fd1e713aec9e1966a0ab7a580b9180cff2 third party advisory patch
https://github.com/dbyio/cve-2022-37298 third party advisory patch

Frequently Asked Questions

What is the severity of CVE-2022-37298?
CVE-2022-37298 has been scored as a critical severity vulnerability.
How to fix CVE-2022-37298?
To fix CVE-2022-37298, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-37298 being actively exploited in the wild?
It is possible that CVE-2022-37298 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~37% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.