SecBoard
Zurück zur CVE-Übersicht

CVE-2026-120722

CRITICAL(9.8)

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

Risk Signal Score30/100 — MITTEL
  • CVSS 9.8 — Kritisch

Erwähnungen (letzte 60 Tage)

Artikel

EPSS-Score

0.7%

Exploit-Wahrscheinlichkeit (30 Tage)

CVSS Score

9.8

Technische Schwere

Beschreibung

Description: When an iRule that processes client traffic using the DNS::scrape command is configured on a virtual server, undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate and may lead to remote code execution (RCE).  Impact: Traffic is disrupted while the TMM process restarts. This vulnerability allows a remote, unauthenticated attacker to cause a denial-of-service (DoS) on the BIG-IP system. In addition, the attacker may be able to perform RCE. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Erkennung & Indikatoren

Ausnutzung

In den geprüften Quellen nicht genannt

Threat-Hunting-Queries

Sentinel/Defender KQL

// This query is a placeholder. Specific logs for F5 BIG-IP iRule DNS::scrape command processing and TMM termination are needed.
// Look for unusual TMM restarts or crashes, especially correlated with specific iRule executions or unusual DNS traffic patterns.
// Example (conceptual, requires F5 logs ingested):
// F5Logs
// | where EventType == "TMM_Crash" or EventType == "TMM_Restart"
// | join kind=inner (F5Logs | where EventType == "iRule_DNS_Scrape_Execution") on CorrelationId
// | project TimeGenerated, Hostname, EventType, iRuleName, SourceIP, DestinationIP, DNSQuery

Splunk SPL

# This query is a placeholder. Specific logs for F5 BIG-IP iRule DNS::scrape command processing and TMM termination are needed.
# Look for unusual TMM restarts or crashes, especially correlated with specific iRule executions or unusual DNS traffic patterns.
# Example (conceptual, requires F5 logs ingested):
# index=f5 sourcetype=bigip (eventtype=TMM_Crash OR eventtype=TMM_Restart) 
# | join CorrelationId [search index=f5 sourcetype=bigip eventtype=iRule_DNS_Scrape_Execution] 
# | table _time, host, eventtype, iRuleName, src_ip, dest_ip, dns_query

Sigma

title: F5 BIG-IP TMM Crash or Restart with DNS Scrape iRule
id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
status: experimental
description: Detects potential TMM crashes or restarts on F5 BIG-IP systems, possibly related to iRules using DNS::scrape.
references:
  - https://nvd.nist.gov/vuln/detail/CVE-2026-120722
logsource:
  product: f5
  service: bigip
detection:
  tmm_crash_restart:
    EventID: 'TMM_Crash' OR 'TMM_Restart' # Placeholder, actual EventID/message needed
  dns_scrape_irule:
    Message|contains: 'iRule' AND 'DNS::scrape' # Placeholder, actual message content needed
  condition: tmm_crash_restart AND dns_scrape_irule
level: high

Elastic ES|QL

// This query is a placeholder. Specific logs for F5 BIG-IP iRule DNS::scrape command processing and TMM termination are needed.
// Look for unusual TMM restarts or crashes, especially correlated with specific iRule executions or unusual DNS traffic patterns.
// Example (conceptual, requires F5 logs ingested):
// from f5_logs
// | where event.type in ("TMM_Crash", "TMM_Restart")
// | join (from f5_logs | where message : "iRule" and message : "DNS::scrape") on correlation_id
// | select @timestamp, host.name, event.type, f5.irule.name, source.ip, destination.ip, dns.query.name

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

Referenzen