CVE-2022-37298: Shinken Solutions Shinken Monitoring Version 2.4.3 affected is vulnerable to Incorrect Access Control

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2022-37298 is a critical-severity flaw (CVSS 9.8) affecting shinken monitoring. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	3.1% (top 12%)
CISA exploited list	No
Weakness	CWE-287
Published	2022-10-20
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: shinken-monitoring

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-10-20 11:15 UTCPublished CVE record published
2026-06-17 04:54 UTCUpdated Record last modified

shinken-monitoring shinken monitoring DOWNGRADE

Affected: 2.4.3

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.4.3

1. Check installed version

apt-cache policy shinken-monitoring || rpm -q shinken-monitoring || shinken-monitoring --version

2. No fixed release: DOWNGRADE to a release before 2.4.3 (Debian / Ubuntu)

apt-cache madison shinken-monitoring sudo apt install shinken-monitoring=<VERSION_BEFORE_2.4.3> sudo apt-mark hold shinken-monitoring

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list shinken-monitoring sudo dnf downgrade shinken-monitoring-<VERSION_BEFORE_2.4.3> sudo dnf versionlock add shinken-monitoring

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-37298?

shinken monitoring: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-37298 being exploited?

CVE-2022-37298 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-37298 affect?

CVE-2022-37298 affects shinken monitoring. Severity is critical (CVSS 9.8). 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 mon

How urgent is CVE-2022-37298?

Priority 61/100. Critical severity; Remotely exploitable, no login, no user action

References

← Back to latest CVEs