CVE-2024-1899

DoS protection mechanisms limit the resource-exhaustion impact of uncontrolled recursion without eliminating the flaw.

System monitoring can observe anomalous resource consumption that signals runaway recursion after it begins.

Secure development life cycle requires controls that prevent uncontrolled recursion through design and code review.

A.8.26 only requires that security requirements (including resilience against attacks such as buffer overflows) be identified and specified during development or acquisition; it does not itself enforce, implement, or prevent uncontrolled recursion from being exploitable in the resulting application.

A.8.27 mandates establishing and applying secure engineering principles (defense-in-depth, least privilege, security by design, input distrust, hardening, design reviews) but does not itself stop uncontrolled recursion from being introduced or from consuming excessive resources when present; the weakness can still be exploited.

Secure coding standards directly prohibit or constrain recursive constructs that could exhaust stack or memory.

Security testing in development can detect excessive recursion via static analysis or fuzzing.

Capacity management includes monitoring and limits that mitigate resource exhaustion from runaway recursion.