{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2021-46837 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2021-46837 is a medium-severity vulnerability in Debian Debian Linux, published on 30 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-46837 and fix it if it is affected.\n\nWhat it is: CVE-2021-46837 is a medium-severity vulnerability in Debian Debian Linux, published on 30 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-46837 in the wild and no public exploit code.\n\nAffected product: Debian Debian Linux. 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-2021-46837/ (Markdown: https://insights.sbomify.com/CVE-2021-46837/index.md)","id":"CVE-2021-46837","markdown":"https://insights.sbomify.com/CVE-2021-46837/index.md","name":"CVE-2021-46837","record":{"aliases":["DEBIAN-CVE-2021-46837","GHSA-544v-7w28-m77x","UBUNTU-CVE-2021-46837"],"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":"low_privilege","summary":"An attacker can crash the Asterisk PBX by sending a malformed T.38 re-invite response, causing a denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"certified_asterisk","vendor":"asterisk"},{"product":"debian_linux","vendor":"debian"},{"product":"asterisk","vendor":"digium"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","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":"res_pjsip_t38 in Sangoma Asterisk 16.x before 16.16.2, 17.x before 17.9.3, and 18.x before 18.2.2, and Certified Asterisk before 16.8-cert7, allows an attacker to trigger a crash by sending an m=image line and zero port in a response to a T.38 re-invite initiated by Asterisk. This is a re-occurrence of the CVE-2019-15297 symptoms but not for exactly the same reason. The crash occurs because there is an append operation relative to the active topology, but this should instead be a replace operation.","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":"Null dereference in n/a","id":"CVE-2021-46837","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"debian:debian_linux","products":["debian:debian_linux","digium:asterisk"],"type":"null_dereference","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in EMUI","id":"CVE-2021-46839"},"packages":[],"prev":{"headline":"Information disclosure in EMUI","id":"CVE-2021-46836"},"products":["n/a"],"published":"2022-08-30","related":[{"cvss_score":9.1,"headline":"Out-of-bounds read in multipart parsing in PJSIP","id":"CVE-2022-21723","kev_date_added":null,"published":"2022-01-27"},{"cvss_score":8.1,"headline":"Use after free in PJSIP","id":"CVE-2022-23608","kev_date_added":null,"published":"2022-02-22"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2017-9358","kev_date_added":null,"published":"2017-06-02"},{"cvss_score":7.3,"headline":"Potential integer underflow upon receiving STUN message in PJSIP","id":"CVE-2021-37706","kev_date_added":null,"published":"2021-12-22"},{"cvss_score":6.5,"headline":"Denial of service in n/a","id":"CVE-2020-28242","kev_date_added":null,"published":"2020-11-06"},{"cvss_score":5,"headline":"Denial of service in n/a","id":"CVE-2013-2686","kev_date_added":null,"published":"2013-03-29"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"An attacker can crash the Asterisk PBX by sending a malformed T.38 re-invite response, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2021-46837/"}