{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49832 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2025-49832 is a medium-severity vulnerability in asterisk, published on 1 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-49832 and fix it if it is affected.\n\nWhat it is: CVE-2025-49832 is a medium-severity vulnerability in asterisk, published on 1 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49832 exists.\n\nAffected product: asterisk. 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-2025-49832/ (Markdown: https://insights.sbomify.com/CVE-2025-49832/index.md)","id":"CVE-2025-49832","markdown":"https://insights.sbomify.com/CVE-2025-49832/index.md","name":"CVE-2025-49832","record":{"aliases":["DEBIAN-CVE-2025-49832","GHSA-mrq5-74j5-f5cr","UBUNTU-CVE-2025-49832"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Asterisk PBX","requires_auth":"low_privilege","summary":"Remote attackers can cause denial of service or potentially execute code in Asterisk via crafted SIP headers when STIR/SHAKEN verification is enabled.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"asterisk","vendor":"sangoma"},{"product":"certified_asterisk","vendor":"sangoma"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"Asterisk is an open source private branch exchange and telephony toolkit. In versions up to and including 18.26.2, between 20.00.0 and 20.15.0, 20.7-cert6, 21.00.0, 22.00.0 through 22.5.0, there is a remote DoS and possible RCE condition in `asterisk/res/res_stir_shaken /verification.c` that can be exploited when an attacker can set an arbitrary Identity header, or STIR/SHAKEN is enabled, with verification set in the SIP profile associated with the endpoint to be attacked. This is fixed in versions 18.26.3, 20.7-cert6, 20.15.1, 21.10.1 and 22.5.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Asterisk is Vulnerable to Remote DoS and possible RCE Attacks During Memory Allocation","id":"CVE-2025-49832","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"GHSL-2025-045: GPT-SoVITS Command Injection vulnerability","id":"CVE-2025-49833"},"packages":[],"prev":{"headline":"Auth bypass in conjur","id":"CVE-2025-49831"},"products":["asterisk"],"published":"2025-08-01","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.5,"headline":"Memory corruption in n/a","id":"CVE-2022-37325","kev_date_added":null,"published":"2022-12-05"},{"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"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-01","vendors":["asterisk"]},"summary":"Remote attackers can cause denial of service or potentially execute code in Asterisk via crafted SIP headers when STIR/SHAKEN verification is enabled.","url":"https://insights.sbomify.com/CVE-2025-49832/"}