CVE-2022-37298 Shinken Solutions Shinken Monitoring vulnerable to Incorrect Access Control
Attackers can execute arbitrary code on the Shinken monitoring server by exploiting weak authentication in the SafeUnpickler class during object deserialization.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2022-37298?
CVE-2022-37298 is a critical unsafe deserialization vulnerability in n/a, published on 20 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-287
Which versions are affected by CVE-2022-37298?
3 open source packages ship an affected version, including shinken and Shinken. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
shinken PyPI | All versions to 2.4.3 | None |
shinken PyPI | All versions to 2.4.3 | None |
Shinken PyPI | All versions to 2.4.3 | None |
Products include Shinken-Monitoring Shinken Monitoring.
How do I fix CVE-2022-37298?
No fix has been published for CVE-2022-37298 yet. Limit exposure of the affected software until one is available.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2022-37298 being exploited?
There is no known exploitation of CVE-2022-37298 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-p373-jqfm-j6wr, PYSEC-2026-540.