Skip to content
Fencer Vulns
medium 6.5

CVE-2019-15297 json

res_pjsip_t38 in Sangoma Asterisk 15.x before 15.7.4 and 16.x before 16.5.1 allows an attacker to trigger a crash by sending a declined str…

published 2019-09-09 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-6304

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.4%
EPSS 3.4% chance of exploitation in 30 days, percentile 88%
public exploits
0
none known

Summary

res_pjsip_t38 in Sangoma Asterisk 15.x before 15.7.4 and 16.x before 16.5.1 allows an attacker to trigger a crash by sending a declined stream in a response to a T.38 re-invite initiated by Asterisk. The crash occurs because of a NULL session media object dereference.

Patch / fix

  • asterisk Debian 14 1:16.10.0~dfsg-1

debian advisories DEBIAN-CVE-2019-15297

  • asterisk Alpine 3.10 16.3.0-r2
  • asterisk Alpine 3.24, Alpine 3.23, Alpine 3.22 +11 more 16.5.1-r0
  • asterisk Alpine 3.8, Alpine 3.7 15.6.2-r0
  • asterisk Alpine 3.9 15.7.4-r0

alpine advisories ALPINE-CVE-2019-15297

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-15297 updated cvss 6.5

asterisk: crash when negotiating T.38 with a zero port

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.39% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:N/I:N/A:P

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.