Skip to content
Fencer Vulns
medium 6.5

CVE-2019-7251 json

An Integer Signedness issue (for a return code) in the res_pjsip_sdp_rtp module in Digium Asterisk versions 15.7.1 and earlier and 16.1.1 a…

published 2019-03-28 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-16795

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

Summary

An Integer Signedness issue (for a return code) in the res_pjsip_sdp_rtp module in Digium Asterisk versions 15.7.1 and earlier and 16.1.1 and earlier allows remote authenticated users to crash Asterisk via a specially crafted SDP protocol violation.

Patch / fix

  • digium asterisk 15.7.2, 16.2.1
  • asterisk Debian 14 1:16.2.1~dfsg-1

debian advisories DEBIAN-CVE-2019-7251

  • asterisk Alpine 3.24, Alpine 3.23, Alpine 3.22 +12 more 16.3.0-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-7251

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-7251 updated cvss 5.9

asterisk: Remote crash vulnerability with SDP protocol

  • 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.64% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 6.5 CVSS:3.0/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
  • CWE-190 Integer Overflow or Wraparound

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.