# 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.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Oct 2022
- **Updated:** 8 May 2025
- **Also known as:** GHSA-p373-jqfm-j6wr, PYSEC-2026-540

## 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 (Improper Authentication)

## 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 | Ecosystem | 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: 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.

## 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:

- CVE-2022-37298 Shinken Monitoring (github_poc): https://github.com/dbyio/cve-2022-37298

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-37298 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2022-37298 in the wild and no public exploit code.

Affected packages and fixed versions:
- shinken (PyPI): affected all versions up to 2.4.3; no fix listed
- shinken (PyPI): affected all versions up to 2.4.3; no fix listed
- Shinken (PyPI): affected all versions up to 2.4.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-37298/ (Markdown: https://insights.sbomify.com/CVE-2022-37298/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-37298
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-37298
- OSV: https://osv.dev/vulnerability/CVE-2022-37298

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-37298/
Summaries are generated and may contain mistakes; the official description above is the record.