Cyber Resilience

CVE-2023-20031

Cisco Secure Firewall Threat Defense 6.7.0 … 7.2.0.1

Published
01 November 2023
Modified
11 August 2026
Patch / advisory
CVSS Score v3.1 4.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N
EPSS Score 0.0028 21th percentile
Risk Priority 33 floored blend · peak EPSS

Summary

CVE-2023-20031 is a medium-severity Heap Inspection (CWE-244) vulnerability in Cisco Secure Firewall Threat Defense. Its CVSS base score is 4.0 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

A vulnerability in the SSL/TLS certificate handling of Snort 3 Detection Engine integration with Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to cause the Snort 3 detection engine to restart. This vulnerability is due to…

more

a logic error that occurs when an SSL/TLS certificate that is under load is accessed when it is initiating an SSL connection. Under specific, time-based constraints, an attacker could exploit this vulnerability by sending a high rate of SSL/TLS connection requests to be inspected by the Snort 3 detection engine on an affected device. A successful exploit could allow the attacker to cause the Snort 3 detection engine to reload, resulting in either a bypass or a denial of service (DoS) condition, depending on device configuration. The Snort detection engine will restart automatically. No manual intervention is required.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1003 OS Credential Dumping Credential Access
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password.
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-20177Same product: Cisco Secure Firewall Threat Defense
CVE-2023-20070Same product: Cisco Secure Firewall Threat Defense
CVE-2026-20039Same product: Cisco Secure Firewall Threat Defense
CVE-2026-20349Same product: Cisco Secure Firewall Threat Defense
CVE-2023-20083Same product: Cisco Secure Firewall Threat Defense
CVE-2023-20267Same product: Cisco Secure Firewall Threat Defense
CVE-2024-20351Same product: Cisco Secure Firewall Threat Defense
CVE-2026-20017Same product: Cisco Secure Firewall Threat Defense
CVE-2024-20431Same product: Cisco Secure Firewall Threat Defense
CVE-2023-20270Same product: Cisco Secure Firewall Threat Defense

Affected Assets

cisco
secure firewall threat defense
6.7.0, 6.7.0.1, 6.7.0.2, 6.7.0.3, 7.0.0

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-244

Forces clearing of heap memory contents prior to release, preventing subsequent processes from inspecting prior sensitive data.

addresses: CWE-244

Information management requirements drive clearing of sensitive contents from memory prior to release or reuse.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.DS-10 mostly match
prevents

Explicit example of removing confidential data from process memory directly prevents heap inspection exposure.

PR.PS-06 partial match
prevents

Secure SDLC practices encompass proper sensitive-memory handling but fixing this single CWE does not achieve the control.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Explicitly requires secure deletion of sensitive data, directly addressing improper heap clearing.

prevents

Secure SDLC processes can incorporate memory-safety requirements but do not specifically mandate heap clearing.

prevents

Mandates secure coding practices that include proper memory sanitization before release.

none

Secure architecture principles may reduce exposure but do not prescribe explicit heap-clearing techniques.

References