{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-28327 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2020-28327 is a medium-severity vulnerability in Digium Certified Asterisk, published on 6 Nov 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-28327 and fix it if it is affected.\n\nWhat it is: CVE-2020-28327 is a medium-severity vulnerability in Digium Certified Asterisk, published on 6 Nov 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-28327 in the wild and no public exploit code.\n\nAffected product: Digium Certified 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-2020-28327/ (Markdown: https://insights.sbomify.com/CVE-2020-28327/index.md)","id":"CVE-2020-28327","markdown":"https://insights.sbomify.com/CVE-2020-28327/index.md","name":"CVE-2020-28327","record":{"aliases":["ALPINE-CVE-2020-28327","DEBIAN-CVE-2020-28327","GHSA-ggx6-v629-c48v","UBUNTU-CVE-2020-28327"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Asterisk PBX","requires_auth":"low_privilege","summary":"An authenticated remote attacker can crash Asterisk via a race condition in SIP session handling when using TCP or TLS transport.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"certified_asterisk","vendor":"digium"},{"product":"asterisk","vendor":"sangoma"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-404","name":"Improper Resource Shutdown or Release"}],"description":"A res_pjsip_session crash was discovered in Asterisk Open Source 13.x before 13.37.1, 16.x before 16.14.1, 17.x before 17.8.1, and 18.x before 18.0.1. and Certified Asterisk before 16.8-cert5. Upon receiving a new SIP Invite, Asterisk did not return the created dialog locked or referenced. This caused a gap between the creation of the dialog object, and its next use by the thread that created it. Depending on some off-nominal circumstances and timing, it was possible for another thread to free said dialog in this gap. Asterisk could then crash when the dialog object, or any of its dependent objects, were dereferenced or accessed next by the initial-creation thread. Note, however, that this crash can only occur when using a connection-oriented protocol (e.g., TCP or TLS, but not UDP) for SIP transport. Also, the remote client must be authenticated, or Asterisk must be configured for anonymous calling.","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":"Race condition in n/a","id":"CVE-2020-28327","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"digium:certified_asterisk","products":["digium:certified_asterisk"],"type":"race_condition","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"File upload in n/a","id":"CVE-2020-28328"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2020-28326"},"products":["n/a"],"published":"2020-11-06","related":[{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2017-9359","kev_date_added":null,"published":"2017-06-02"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2017-9372","kev_date_added":null,"published":"2017-06-02"}],"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 authenticated remote attacker can crash Asterisk via a race condition in SIP session handling when using TCP or TLS transport.","url":"https://insights.sbomify.com/CVE-2020-28327/"}