Skip to content
Fencer Intel
medium 6.5

CVE-2018-7286 json

An issue was discovered in Asterisk through 13.19.1, 14.x through 14.7.5, and 15.x through 15.2.1, and Certified Asterisk through 13.18-cer…

published 2018-02-22 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-19020

cvss
6.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
52.7%
EPSS 52.7% chance of exploitation in 30 days, percentile 98%
public exploits
1
Exploit-DB

Summary

An issue was discovered in Asterisk through 13.19.1, 14.x through 14.7.5, and 15.x through 15.2.1, and Certified Asterisk through 13.18-cert2. res_pjsip allows remote authenticated users to crash Asterisk (segmentation fault) by sending a number of SIP INVITE messages on a TCP or TLS connection and then suddenly closing the connection.

Patch / fix

  • asterisk Debian 14 1:13.20.0~dfsg-1

debian advisories DEBIAN-CVE-2018-7286

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-2018-7286 updated cvss 4.3

asterix: Denial of Service (DoS) when sending a repeated number of INVITE messages over TCP or TLS transport

  • 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

Timeline

  1. Published
  2. First public exploit (EDB-44181)

Exploit prediction

52.73% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-44181 Asterisk chan_pjsip 15.2.0 - 'INVITE' Denial of Service dos, 2018-02-27

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

References

Sources

Fencer Intel 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.