{"answers":{"affected":"3 open source packages ship an affected version, including shinken and Shinken. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-37298 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-37298 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2022-37298 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2022-37298 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- shinken (PyPI): affected all versions up to 2.4.3; no fix listed\n- shinken (PyPI): affected all versions up to 2.4.3; no fix listed\n- Shinken (PyPI): affected all versions up to 2.4.3; no fix listed\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-37298/ (Markdown: https://insights.sbomify.com/CVE-2022-37298/index.md)","id":"CVE-2022-37298","markdown":"https://insights.sbomify.com/CVE-2022-37298/index.md","name":"CVE-2022-37298","record":{"aliases":["GHSA-p373-jqfm-j6wr","PYSEC-2026-540"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Shinken monitoring server","requires_auth":"none","summary":"Attackers can execute arbitrary code on the Shinken monitoring server by exploiting weak authentication in the SafeUnpickler class during object deserialization.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"shinken_monitoring","vendor":"shinken-monitoring"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":"2022-10-13","github_poc":1,"max_poc_stars":2,"metasploit":0,"nuclei":0,"refs":[{"date":"2022-10-13T21:07:02Z","kind":"github_poc","ref":"https://github.com/dbyio/cve-2022-37298","stars":2,"title":"CVE-2022-37298 Shinken Monitoring"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Shinken Solutions Shinken Monitoring vulnerable to Incorrect Access Control","id":"CVE-2022-37298","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"deserialization","year":"2022"},"n_packages":3,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2022-37299"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.4.3"],"package":"Shinken","purl":null,"source":"GHSA-p373-jqfm-j6wr"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.4.3"],"package":"shinken","purl":"pkg:pypi/shinken","source":"GHSA-p373-jqfm-j6wr"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.4.3"],"package":"shinken","purl":"pkg:pypi/shinken","source":"PYSEC-2026-540"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2022-37292"},"products":["n/a"],"published":"2022-10-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-08","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code on the Shinken monitoring server by exploiting weak authentication in the SafeUnpickler class during object deserialization.","url":"https://insights.sbomify.com/CVE-2022-37298/"}