Shinken Monitoring 2.4.3 shinken/safepickle.py SafeUnpickler improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Shinken Monitoring 2.4.3. It has been classified as critical. This issue affects the function SafeUnpickler of the file shinken/safepickle.py. The manipulation leads to improper authentication.
This vulnerability is listed as CVE-2022-37298. There is no available exploit.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability, which was classified as critical, has been found in Shinken Monitoring 2.4.3. This issue affects the function SafeUnpickler of the file shinken/safepickle.py. The manipulation with an unknown input leads to a improper authentication vulnerability. Using CWE to declare the problem leads to CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was presented 10/20/2022. The advisory is shared at github.com. The identification of this vulnerability is CVE-2022-37298 since 08/01/2022. Technical details are known, but no exploit is available.
Applying the patch 2dae40fd1e713aec9e1966a0ab7a580b9180cff2 is able to eliminate this problem. The bugfix is ready for download at github.com.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 2dae40fd1e713aec9e1966a0ab7a580b9180cff2
Timeline
08/01/2022 🔍10/20/2022 🔍
10/20/2022 🔍
05/08/2025 🔍
Sources
Advisory: 2dae40fd1e713aec9e1966a0ab7a580b9180cff2Status: Confirmed
CVE: CVE-2022-37298 (🔍)
GCVE (CVE): GCVE-0-2022-37298
GCVE (VulDB): GCVE-100-211853
Entry
Created: 10/20/2022 15:06Updated: 05/08/2025 18:49
Changes: 10/20/2022 15:06 (42), 11/18/2022 13:51 (1), 11/18/2022 13:57 (11), 05/08/2025 18:49 (19)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.