{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-49786 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2023-49786 is a high-severity vulnerability in Digium Asterisk, published on 14 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-49786 and fix it if it is affected.\n\nWhat it is: CVE-2023-49786 is a high-severity vulnerability in Digium Asterisk, published on 14 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-49786 exists.\n\nAffected product: Digium 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-2023-49786/ (Markdown: https://insights.sbomify.com/CVE-2023-49786/index.md)","id":"CVE-2023-49786","markdown":"https://insights.sbomify.com/CVE-2023-49786/index.md","name":"CVE-2023-49786","record":{"aliases":["ALPINE-CVE-2023-49786","DEBIAN-CVE-2023-49786","GHSA-hxj9-xwr8-w8pq","UBUNTU-CVE-2023-49786"],"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":"Attackers can cause a Denial of Service on Asterisk servers by exploiting a race condition in DTLS-SRTP handshakes, blocking new encrypted calls.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"asterisk","vendor":"digium"},{"product":"certified_asterisk","vendor":"sangoma"}],"cvss":{"score":7.5,"severity":"high","source":"cna","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-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"},{"id":"CWE-703","name":"Improper Check or Handling of Exceptional Conditions"}],"description":"Asterisk is an open source private branch exchange and telephony toolkit. In Asterisk prior to versions 18.20.1, 20.5.1, and 21.0.1; as well as certified-asterisk prior to 18.9-cert6; Asterisk is susceptible to a DoS due to a race condition in the hello handshake phase of the DTLS protocol when handling DTLS-SRTP for media setup. This attack can be done continuously, thus denying new DTLS-SRTP encrypted calls during the attack. Abuse of this vulnerability may lead to a massive Denial of Service on vulnerable Asterisk servers for calls that rely on DTLS-SRTP. Commit d7d7764cb07c8a1872804321302ef93bf62cba05 contains a fix, which is part of versions 18.20.1, 20.5.1, 21.0.1, amd 18.9-cert6.","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 susceptible to Denial of Service via DTLS Hello packets during call initiation","id":"CVE-2023-49786","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"digium:asterisk","products":["digium:asterisk"],"type":"race_condition","year":"2023"},"n_packages":0,"n_references":7,"next":{"headline":"CVE request originates from private repository","id":"CVE-2023-49787"},"packages":[],"prev":{"headline":"NextChat vulnerable to Server-Side Request Forgery and Cross-site Scripting","id":"CVE-2023-49785"},"products":["asterisk"],"published":"2023-12-14","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2017-14100","kev_date_added":null,"published":"2017-09-02"},{"cvss_score":9,"headline":"Privilege escalation in n/a","id":"CVE-2014-8418","kev_date_added":null,"published":"2014-11-24"},{"cvss_score":9,"headline":"Missing authorization in n/a","id":"CVE-2011-1599","kev_date_added":null,"published":"2011-04-27"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-16671","kev_date_added":null,"published":"2017-11-09"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-7617","kev_date_added":null,"published":"2017-04-10"},{"cvss_score":7.8,"headline":"Denial of service in n/a","id":"CVE-2009-2726","kev_date_added":null,"published":"2009-08-12"},{"cvss_score":7.8,"headline":"Null dereference in n/a","id":"CVE-2007-1306","kev_date_added":null,"published":"2007-03-07"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-13","vendors":["asterisk"]},"summary":"Attackers can cause a Denial of Service on Asterisk servers by exploiting a race condition in DTLS-SRTP handshakes, blocking new encrypted calls.","url":"https://insights.sbomify.com/CVE-2023-49786/"}