Unauthenticated code execution via wildcard module trust
Published Oct 20, 2022 · Updated May 8, 2025
Improper authentication in Shinken Monitoring 2.4.3 and earlier allows remote attackers to execute code via crafted node messages. SafeUnpickler.find_class trusts every shinken.* module and class, allowing a pickle to invoke bottle._load without an allowlist. Access to a daemon's internal exchange port is sufficient, with no credentials or user interaction, and code runs on the monitoring server.
Summary
What happened
Improper authentication in Shinken Monitoring 2.4.3 and earlier allows remote attackers to execute code via crafted node messages. SafeUnpickler.find_class trusts every shinken.* module and class, allowing a pickle to invoke bottle._load without an allowlist. Access to a daemon's internal exchange port is sufficient, with no credentials or user interaction, and code runs on the monitoring server.
The record
- CVE
- CVE-2022-37298
- Published
- Oct 20, 2022
- Updated
- May 8, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-287, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 20, 2022CVE publishedPublication date reported by the CVE source.
- May 8, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- CVE-2022-37298 Shinken Monitoring proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo