p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in asterisk · Seite 5

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für asterisk: 20. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 90

  1. CVE-2019-15297

    Mittel · CVSS 6.5EPSS 3,39%Keine Korrektur veröffentlicht

    CVE-2019-15297

    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.

    Veröffentlicht Aktualisiert
  2. CVE-2019-13161

    Mittel · CVSS 5.3EPSS 4,01%Keine Korrektur veröffentlicht

    CVE-2019-13161

    An issue was discovered in Asterisk Open Source through 13.27.0, 14.x and 15.x through 15.7.2, and 16.x through 16.4.0, and Certified Asterisk through 13.21-cert3. A pointer dereference in chan_sip while handling SDP negotiation allows an attacker to crash Asterisk when handling an SDP answer to an outgoing T.38 re-invite. To exploit this vulnerability an attacker must cause the chan_sip module to send a T.38 re-invite request to them. Upon receipt, the attacker must send an SDP answer containing both a T.38 UDPTL stream and another media stream containing only a codec (which is not permitted according to the chan_sip configuration).

    Veröffentlicht Aktualisiert
  3. CVE-2018-17281

    Hoch · CVSS 7.5EPSS 52,45%Keine Korrektur veröffentlicht

    CVE-2018-17281

    There is a stack consumption vulnerability in the res_http_websocket.so module of Asterisk through 13.23.0, 14.7.x through 14.7.7, and 15.x through 15.6.0 and Certified Asterisk through 13.21-cert2. It allows an attacker to crash Asterisk via a specially crafted HTTP request to upgrade the connection to a websocket.

    Veröffentlicht Aktualisiert
  4. CVE-2018-12227

    Mittel · CVSS 5.3EPSS 3,36%Keine Korrektur veröffentlicht

    CVE-2018-12227

    An issue was discovered in Asterisk Open Source 13.x before 13.21.1, 14.x before 14.7.7, and 15.x before 15.4.1 and Certified Asterisk 13.18-cert before 13.18-cert4 and 13.21-cert before 13.21-cert2. When endpoint specific ACL rules block a SIP request, they respond with a 403 forbidden. However, if an endpoint is not identified, then a 401 unauthorized response is sent. This vulnerability just discloses which requests hit a defined endpoint. The ACL rules cannot be bypassed to gain access to the disclosed endpoints.

    Veröffentlicht Aktualisiert
  5. CVE-2018-7286

    Mittel · CVSS 6.5EPSS 52,73%Öffentlicher ExploitKeine Korrektur veröffentlicht

    CVE-2018-7286

    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.

    Veröffentlicht Aktualisiert
  6. CVE-2018-7284

    Hoch · CVSS 7.5EPSS 66,17%Öffentlicher ExploitKeine Korrektur veröffentlicht

    CVE-2018-7284

    A Buffer Overflow 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. When processing a SUBSCRIBE request, the res_pjsip_pubsub module stores the accepted formats present in the Accept headers of the request. This code did not limit the number of headers it processed, despite having a fixed limit of 32. If more than 32 Accept headers were present, the code would write outside of its memory and cause a crash.

    Veröffentlicht Aktualisiert
  7. CVE-2017-17850

    Hoch · CVSS 7.5EPSS 75,35%Keine Korrektur veröffentlicht

    CVE-2017-17850

    An issue was discovered in Asterisk 13.18.4 and older, 14.7.4 and older, 15.1.4 and older, and 13.18-cert1 and older. A select set of SIP messages create a dialog in Asterisk. Those SIP messages must contain a contact header. For those messages, if the header was not present and the PJSIP channel driver was used, Asterisk would crash. The severity of this vulnerability is somewhat mitigated if authentication is enabled. If authentication is enabled, a user would have to first be authorized before reaching the crash point.

    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →