SecBoard
Zurück zur CVE-Übersicht

CVE-2026-57185

MEDIUM(6.5)

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Risk Signal Score16/100 — NIEDRIG
  • CVSS 6.5 — Mittel

Erwähnungen (letzte 60 Tage)

Artikel

EPSS-Score

0.5%

Exploit-Wahrscheinlichkeit (30 Tage)

CVSS Score

6.5

Technische Schwere

Beschreibung

Asterisk is an open source private branch exchange and telephony toolkit. Prior to Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 20.7-cert11, 22.8-cert3, an authenticated attacker may crash Asterisk through a buffer over-read in the `PJSIP MWI body parser` by sending a carefully crafted `SIP NOTIFY` request. The attacker must pass SIP authentication using either a username/password or `source IP address matching`. This issue is fixed in Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 20.7-cert11, 22.8-cert3.

Erkennung & Indikatoren

Ausnutzung

In den geprüften Quellen nicht genannt

Behobene Versionen

  • Asterisk 20.20.1
  • Asterisk 21.12.3
  • Asterisk 22.10.1
  • Asterisk 23.4.1
  • Certified Asterisk 20.7-cert11
  • Certified Asterisk 22.8-cert3

Threat-Hunting-Queries

Sentinel/Defender KQL

// Detect SIP NOTIFY requests with 'Content-Type: application/simple-message-summary' that might indicate a crafted request
// This query assumes SIP traffic is being monitored and parsed, e.g., from network device logs or a custom SIP sensor.
// Adjust 'YourLogTable' and field names to match your environment.
YourLogTable
| where Protocol == "SIP" and EventType == "NOTIFY"
| where HttpContentType contains "application/simple-message-summary"
| where isnotempty(Body) // Look for requests with a body, which is parsed by the vulnerable component
| project TimeGenerated, SourceIp, DestinationIp, UserName, SipMethod, HttpContentType, Body
| extend Anomaly = "Potential crafted SIP NOTIFY for CVE-2026-57185"
| sort by TimeGenerated desc

Splunk SPL

# Detect SIP NOTIFY requests with 'Content-Type: application/simple-message-summary' that might indicate a crafted request
# This query assumes SIP traffic is being monitored and parsed, e.g., from network device logs or a custom SIP sensor.
# Adjust 'sourcetype' and field names to match your environment.
sourcetype=your_sip_logs (sip.method="NOTIFY" OR sip_method="NOTIFY") (sip.content_type="application/simple-message-summary" OR content_type="application/simple-message-summary") sip.body=*
| table _time, src_ip, dest_ip, user, sip_method, content_type, sip_body
| rename src_ip AS SourceIp, dest_ip AS DestinationIp, user AS UserName, sip_method AS SipMethod, content_type AS HttpContentType, sip_body AS Body
| eval Anomaly = "Potential crafted SIP NOTIFY for CVE-2026-57185"

Sigma

title: Asterisk PJSIP MWI Buffer Over-read Attempt
id: 00000000-0000-0000-0000-000000000000 # Placeholder, generate a unique GUID
status: experimental
description: Detects SIP NOTIFY requests with 'Content-Type: application/simple-message-summary' which could indicate an attempt to exploit CVE-2026-57185.
references:
  - https://nvd.nist.gov/vuln/detail/CVE-2026-57185
logsource:
  category: network_traffic
  product: sip_server # Or relevant network device/sensor
detection:
  selection:
    protocol: sip
    method: NOTIFY
    content_type: application/simple-message-summary
    body_exists: true # Ensure there is a body to be parsed
  condition: selection
fields:
  - source_ip
  - destination_ip
  - user
  - method
  - content_type
  - body
level: medium

Elastic ES|QL

// Detect SIP NOTIFY requests with 'Content-Type: application/simple-message-summary' that might indicate a crafted request
// This query assumes SIP traffic is being monitored and parsed, e.g., from network device logs or a custom SIP sensor.
// Adjust 'your_sip_index' and field names to match your environment.
FROM your_sip_index
WHERE sip.method == "NOTIFY" AND sip.content_type == "application/simple-message-summary" AND LENGTH(sip.body) > 0
SELECT @timestamp, source.ip, destination.ip, user.name, sip.method, sip.content_type, sip.body
ORDER BY @timestamp DESC

SecBoard-generated · behavioral · requires customization — Von SecBoard erzeugt und nicht in einer Zielumgebung validiert. Vor dem Einsatz an die eigene Protokollierung anpassen.

Indikatoren

Datei-Hashes (6)

  • 07aec894a1fdfa7fa989d3ab40fdf0dcda8005bb
  • 1039bed76fa3248f58b6880e4b3f1421ef98b01f
  • 1b2d99d8eb9206d37fd47115996f67fd28bd056f
  • 3100a0d331affbf0995b8c57aaddb31cf3971f6e
  • 57ce484a45b098de417f19265c95c64497782e36
  • 919f2ffda03329c9014bedcb3c7789d38660c9ed

Übernommen wurden nur Indikatoren, die wörtlich in einer Hersteller- oder Research-Quelle standen.

Referenzen