cve.bz

CVE-2025-20127 cisco: Improper Resource Shutdown or Release

7.7 highEPSS 0.7%

High (7.7) in cisco. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
A vulnerability in the TLS 1.3 implementation for a specific cipher for Cisco Secure Firewall Adaptive Security Appliance (ASA) Software and Cisco Secure Firewall Threat Defense (FTD) Software for Cisco Firepower 3100 and 4200 Series devices could allow an authenticated, remote attacker to consume resources that are associated with incoming TLS 1.3 connections, which eventually could cause the device to stop accepting any new SSL/TLS or VPN requests. This vulnerability is due to the implementation of the TLS 1.3 Cipher TLS_CHACHA20_POLY1305_SHA256. An attacker could exploit this vulnerability by sending a large number of TLS 1.3 connections with the specific TLS 1.3 Cipher TLS_CHACHA20_POLY1305_SHA256. A successful exploit could allow the attacker to cause a denial of service (DoS) condition where no new incoming encrypted connections are accepted. The device must be reloaded to clear this condition. Note: These incoming TLS 1.3 connections include both data traffic and user-management traffic. After the device is in the vulnerable state, no new encrypted connections can be accepted.

Severity

CVSS 3.1

7.7 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 55th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-08-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-404 Improper Resource Shutdown or Release
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-20127 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-20127?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-20127?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-20127 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
cisco:secure_firewall_threat_defense7.4.0
cisco:secure_firewall_threat_defense7.4.1
cisco:secure_firewall_threat_defense7.4.1.1
cisco:secure_firewall_threat_defense7.4.2
cisco:secure_firewall_threat_defense7.4.2.1
cisco:secure_firewall_threat_defense7.6.0
cisco:adaptive_security_appliance_software9.20.1
cisco:adaptive_security_appliance_software9.20.1.5
cisco:adaptive_security_appliance_software9.20.2
cisco:adaptive_security_appliance_software9.20.2.10
cisco:adaptive_security_appliance_software9.20.2.21
cisco:adaptive_security_appliance_software9.20.2.22
cisco:adaptive_security_appliance_software9.20.3
cisco:adaptive_security_appliance_software9.20.3.4
cisco:adaptive_security_appliance_software9.20.3.7
cisco:adaptive_security_appliance_software9.22.1.1

Attack patterns (CAPEC)

  • CAPEC-125 Flooding Likelihood: High · Severity: Medium
  • CAPEC-130 Excessive Allocation Likelihood: Medium · Severity: Medium
  • CAPEC-131 Resource Leak Exposure Likelihood: Medium · Severity: Medium
  • CAPEC-494 TCP Fragmentation
  • CAPEC-495 UDP Fragmentation
  • CAPEC-496 ICMP Fragmentation
  • CAPEC-666 BlueSmacking Likelihood: Medium · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON