Cyber Resilience

CVE-2023-29163

F5 Big-Ip Access Policy Manager 14.1.0 – 14.1.5.4

Published
03 May 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0062 46th percentile
Risk Priority 59 floored blend · peak EPSS

Summary

CVE-2023-29163 is a high-severity Missing Release of Memory after Effective Lifetime (CWE-401) vulnerability in F5 Big-Ip Access Policy Manager. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 46th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

When UDP profile with idle timeout set to immediate or the value 0 is configured on a virtual server, undisclosed traffic can cause TMM to terminate.  Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-40534Same product: F5 Big-Ip Access Policy Manager
CVE-2025-21091Same product: F5 Big-Ip Access Policy Manager
CVE-2026-42781Same product: F5 Big-Ip Access Policy Manager
CVE-2026-42920Same product: F5 Big-Ip Access Policy Manager
CVE-2026-34019Same product: F5 Big-Ip Access Policy Manager
CVE-2023-24594Same product: F5 Big-Ip Access Policy Manager
CVE-2023-40542Same product: F5 Big-Ip Access Policy Manager
CVE-2023-41085Same product: F5 Big-Ip Access Policy Manager
CVE-2025-20058Same product: F5 Big-Ip Access Policy Manager
CVE-2025-21087Same product: F5 Big-Ip Access Policy Manager

Affected Assets

f5
big-ip access policy manager
17.0.0 · 14.1.0 — 14.1.5.4 · 15.1.0 — 15.1.8.2 · 16.1.0 — 16.1.3.4
f5
big-ip advanced firewall manager
17.0.0 · 14.1.0 — 14.1.5.4 · 15.1.0 — 15.1.8.2 · 16.1.0 — 16.1.3.4
f5
big-ip advanced web application firewall
17.0.0 · 14.1.0 — 14.1.5.4 · 15.1.0 — 15.1.8.2 · 16.1.0 — 16.1.3.4
f5
big-ip analytics
17.0.0 · 14.1.0 — 14.1.5.4 · 15.1.0 — 15.1.8.2 · 16.1.0 — 16.1.3.4
f5
big-ip application acceleration manager
17.0.0 · 14.1.0 — 14.1.5.4 · 15.1.0 — 15.1.8.2 · 16.1.0 — 16.1.3.4
f5
big-ip application security manager
17.0.0 · 14.1.0 — 14.1.5.4 · 15.1.0 — 15.1.8.2 · 16.1.0 — 16.1.3.4
f5
big-ip application visibility and reporting
17.0.0 · 14.1.0 — 14.1.5.4 · 15.1.0 — 15.1.8.2 · 16.1.0 — 16.1.3.4
f5
big-ip carrier-grade nat
17.0.0 · 14.1.0 — 14.1.5.4 · 15.1.0 — 15.1.8.2 · 16.1.0 — 16.1.3.4
f5
big-ip ddos hybrid defender
17.0.0 · 14.1.0 — 14.1.5.4 · 15.1.0 — 15.1.8.2 · 16.1.0 — 16.1.3.4
f5
big-ip domain name system
17.0.0 · 14.1.0 — 14.1.5.4 · 15.1.0 — 15.1.8.2 · 16.1.0 — 16.1.3.4
+9 more product configuration(s) — see NVD for full list

Mitigating Controls

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.PS-06 mostly match
prevents

Secure SDLC practices directly enforce proper memory allocation/deallocation via coding standards, reviews, and tooling.

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.

finds

Security testing in development can detect unreleased memory, providing partial coverage of the weakness.

prevents

Secure development life cycle mandates memory-management practices that reduce missing-release defects.

prevents

Application security requirements can specify explicit memory-release rules, partially mitigating the weakness.

prevents

Secure system architecture and engineering principles include resource-management guidelines that address memory leaks.

prevents

Secure coding standards directly require proper allocation/deallocation, covering most of this weakness.

finds

Capacity management may detect memory exhaustion symptoms but does not prevent the coding flaw.

References