CVE-2024-21849
F5 Big-Ip Advanced Web Application Firewall 16.1.0 – 16.1.4
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-21849 is a high-severity Return of Pointer Value Outside of Expected Range (CWE-466) vulnerability in F5 Big-Ip Advanced Web Application Firewall. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 43th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-19460
Vulnerability Data
When an Advanced WAF/ASM security policy and a Websockets profile are configured on a virtual server, undisclosed traffic can cause the Traffic Management Microkernel (TMM) process to terminate. Note: Software versions which have reached End of Technical Support (EoTS) are…
more
not evaluated.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.4.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover functions that return pointers outside expected buffer bounds.
Requiring documented development standards and tools can enforce safe pointer arithmetic and bounds checking to avoid out-of-range returns.
Security engineering principles applied during design can include explicit pointer-range validation and safe memory handling.
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.
Secure SDLC practices enforce bounds checking, static analysis, and pointer validation that directly prevent out-of-range pointer returns.
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.
Secure SDLC practices can include pointer-range validation and bounds checking to prevent out-of-range returns.
A.8.26 requires identifying and specifying security requirements (including resilience against attacks like buffer overflows or SQL injection) during development or acquisition; it does not itself enforce, implement, or assure those requirements in code, so a pointer-out-of-range return remains present and exploitable.
Secure coding standards directly address pointer validation and bounds checking, mitigating this specific weakness.
Security testing in development can detect out-of-range pointer returns through static analysis and fuzzing.