{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-37325 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2022-37325 is a high-severity memory corruption vulnerability in n/a, published on 5 Dec 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-37325 and fix it if it is affected.\n\nWhat it is: CVE-2022-37325 is a high-severity memory corruption vulnerability in n/a, published on 5 Dec 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-37325 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-37325/ (Markdown: https://insights.sbomify.com/CVE-2022-37325/index.md)","id":"CVE-2022-37325","markdown":"https://insights.sbomify.com/CVE-2022-37325/index.md","name":"CVE-2022-37325","record":{"aliases":["ALPINE-CVE-2022-37325","DEBIAN-CVE-2022-37325","GHSA-m52q-h2w3-62w3","UBUNTU-CVE-2022-37325"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Asterisk PBX","requires_auth":"none","summary":"A malformed H.323 message can cause a crash in Asterisk, leading to denial of service for the PBX system.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"asterisk","vendor":"sangoma"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"In Sangoma Asterisk through 16.28.0, 17.x and 18.x through 18.14.0, and 19.x through 19.6.0, an incoming Setup message to addons/ooh323c/src/ooq931.c with a malformed Calling or Called Party IE can cause a crash.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Memory corruption in n/a","id":"CVE-2022-37325","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Path traversal in n/a","id":"CVE-2022-37326"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2022-37318"},"products":["n/a"],"published":"2022-12-05","related":[{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2024-57520","kev_date_added":null,"published":"2025-02-05"},{"cvss_score":7.7,"headline":"Using malformed From header can forge identity with \";\" or NULL in name portion","id":"CVE-2025-47779","kev_date_added":null,"published":"2025-05-22"},{"cvss_score":7.5,"headline":"Asterisk can crash from a specifically malformed Authorization header in an incoming SIP request","id":"CVE-2025-57767","kev_date_added":null,"published":"2025-08-28"},{"cvss_score":7,"headline":"Asterisk Unsafe Shell Sourcing in safe_asterisk Leads to Local Privilege Escalation","id":"CVE-2025-1131","kev_date_added":null,"published":"2025-09-23"},{"cvss_score":6.5,"headline":"Asterisk remotely exploitable leak of RTP UDP ports and internal resources","id":"CVE-2025-54995","kev_date_added":null,"published":"2025-08-28"},{"cvss_score":6.5,"headline":"Asterisk is Vulnerable to Remote DoS and possible RCE Attacks During Memory Allocation","id":"CVE-2025-49832","kev_date_added":null,"published":"2025-08-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-02","vendors":["n/a"]},"summary":"A malformed H.323 message can cause a crash in Asterisk, leading to denial of service for the PBX system.","url":"https://insights.sbomify.com/CVE-2022-37325/"}