cve.bz

CVE-2020-28327 Improper Resource Shutdown or Release

5.3 mediumExploit referenceEPSS 1.9%Fix available

Medium (5.3). EPSS 1.9% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
1.9% (unchanged from 1.9% a week ago; 1.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 81st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-404 Improper Resource Shutdown or Release
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2020-28327 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-28327?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-28327?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-28327 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
digium:certified_asterisk16.8
digium:certified_asterisk16.8:cert1-rc1
digium:certified_asterisk16.8:cert1-rc2
digium:certified_asterisk16.8:cert1-rc3
digium:certified_asterisk16.8:cert1-rc4
digium:certified_asterisk16.8:cert2
digium:certified_asterisk16.8:cert3
digium:certified_asterisk16.8:cert4
digium:certified_asterisk16.8:cert4-rc1
digium:certified_asterisk16.8:cert4-rc2
digium:certified_asterisk16.8:cert4-rc3
digium:certified_asterisk16.8:cert4-rc4
sangoma:asteriskfrom 13.0.0 before 13.37.1
sangoma:asteriskfrom 16.0.0 before 16.14.1
sangoma:asteriskfrom 17.0.0 before 17.8.1
sangoma:asteriskfrom 18.0.0 before 18.0.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14asterisk1:16.15.0~dfsg-1DEBIAN-CVE-2020-28327
Ubuntu18.04:LTS, 20.04:LTS, Pro:16.04:LTSasteriskno fix listedUBUNTU-CVE-2020-28327
Alpinev3.12asterisk16.14.1-r0ALPINE-CVE-2020-28327
Alpinev3.13, v3.14, v3.15 and 9 moreasterisk18.0.1-r0ALPINE-CVE-2020-28327

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpine.

Attack patterns (CAPEC)

  • CAPEC-125 Flooding Likelihood: High · Severity: Medium
  • CAPEC-130 Excessive Allocation Likelihood: Medium · Severity: Medium
  • CAPEC-131 Resource Leak Exposure Likelihood: Medium · Severity: Medium
  • CAPEC-494 TCP Fragmentation
  • CAPEC-495 UDP Fragmentation
  • CAPEC-496 ICMP Fragmentation
  • CAPEC-666 BlueSmacking Likelihood: Medium · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON