SecBoard
Zurück zur CVE-Übersicht

CVE-2026-20121

MEDIUM(5.3)

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

Risk Signal Score23/100 — NIEDRIG
  • CVSS 5.3 — Mittel
  • Weniger als 24 Stunden alt

Erwähnungen (letzte 60 Tage)

Artikel

Beschreibung

A vulnerability in the access control list (ACL) Object Group Search (OGS) implementation of Cisco Secure Firewall Adaptive Security Appliance (ASA) Software and Cisco Secure Firewall Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to bypass configured access controls. This vulnerability is due to a logic error in populating group access control policies (ACPs) with OGS configured. An attacker could exploit this vulnerability by sending traffic that should be blocked through the device. A successful exploit could allow the attacker to bypass access controls and reach devices in protected networks.

Erkennung & Indikatoren

Ausnutzung

In den geprüften Quellen nicht genannt

Threat-Hunting-Queries

Detection for traffic bypassing ACLs due to Object Group Search (OGS) logic error. This requires monitoring traffic that should be blocked but is unexpectedly allowed. Specific queries will depend on network logging and expected traffic patterns.

Sentinel/Defender KQL

// This query is a placeholder. Actual detection requires understanding expected traffic patterns and identifying anomalies where traffic that should be blocked by OGS-configured ACLs is allowed.
// Example: Monitor firewall logs for traffic from known malicious sources or to sensitive internal resources that should be denied by ACLs.
// Replace 'YourFirewallLogs' with the actual log table for your Cisco Secure Firewall ASA/FTD.
YourFirewallLogs
| where Action == "Permit"
| where DestinationIP in ("<Sensitive_Internal_IPs>") // IPs that should be protected by OGS ACLs
| where SourceIP in ("<External_Untrusted_IPs>") // IPs that should be blocked by OGS ACLs
| project TimeGenerated, SourceIP, DestinationIP, DestinationPort, Action, RuleName
| extend Anomaly = iff(RuleName has "OGS_ACL" and Action == "Permit", "Potential ACL Bypass", "")
| where isnotempty(Anomaly)

Splunk SPL

# This query is a placeholder. Actual detection requires understanding expected traffic patterns and identifying anomalies where traffic that should be blocked by OGS-configured ACLs is allowed.
# Example: Monitor firewall logs for traffic from known malicious sources or to sensitive internal resources that should be denied by ACLs.
# Replace 'sourcetype=cisco:asa' or 'sourcetype=cisco:ftd' with the actual sourcetype for your Cisco Secure Firewall ASA/FTD logs.
sourcetype=cisco:asa OR sourcetype=cisco:ftd action=permit dest_ip IN ("<Sensitive_Internal_IPs>") src_ip IN ("<External_Untrusted_IPs>")
| eval Anomaly = if(match(_raw, "OGS_ACL") AND action="permit", "Potential ACL Bypass", "")
| where isnotnull(Anomaly)
| table _time, src_ip, dest_ip, dest_port, action, rule_name

Sigma

title: Cisco Secure Firewall OGS ACL Bypass Anomaly
id: 00000000-0000-0000-0000-000000000000 # Placeholder: Generate a unique GUID
status: experimental
description: Detects potential ACL bypass due to OGS logic error on Cisco Secure Firewall ASA/FTD by identifying traffic that should be blocked but is permitted.
references:
  - https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ftd-acl-bypass-8p6vFvw
logsource:
  product: firewall
  vendor: cisco
detection:
  selection:
    action: 'permit'
    # Replace with actual fields and values for sensitive internal IPs and untrusted external IPs
    # Example: dest_ip: ['192.168.1.0/24', '10.0.0.0/8']
    # Example: src_ip: ['<External_Untrusted_IPs>']
    # This requires customization based on your network's protected assets and expected blocked sources.
    # rule_name|contains: 'OGS_ACL' # If rule names explicitly indicate OGS usage
  condition: selection
level: high

Elastic ES|QL

// This query is a placeholder. Actual detection requires understanding expected traffic patterns and identifying anomalies where traffic that should be blocked by OGS-configured ACLs is allowed.
// Example: Monitor firewall logs for traffic from known malicious sources or to sensitive internal resources that should be denied by ACLs.
// Replace 'logs-firewall.cisco.*' with the actual index pattern for your Cisco Secure Firewall ASA/FTD logs.
FROM logs-firewall.cisco.*
WHERE event.action == "permit"
AND destination.ip IN ("<Sensitive_Internal_IPs>") // IPs that should be protected by OGS ACLs
AND source.ip IN ("<External_Untrusted_IPs>") // IPs that should be blocked by OGS ACLs
// AND rule.name : "OGS_ACL*" // If rule names explicitly indicate OGS usage
| SELECT @timestamp, source.ip, destination.ip, destination.port, event.action, rule.name
| EVAL anomaly = IF(rule.name LIKE "OGS_ACL%" AND event.action == "permit", "Potential ACL Bypass", NULL)
| WHERE anomaly IS NOT NULL

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

Referenzen