Cyber Resilience

CVE-2024-20314

Cisco Ios Xe 16.1.1 … 17.9.4a

Published
27 March 2024
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 8.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
EPSS Score 0.0080 53th percentile
Risk Priority 64 floored blend · peak EPSS

Summary

CVE-2024-20314 is a high-severity Operator Precedence Logic Error (CWE-783) vulnerability in Cisco Ios Xe. Its CVSS base score is 8.6 (High).

Operationally, ranked in the top 47% of CVEs by exploit likelihood; 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

Vulnerability Data

A vulnerability in the IPv4 Software-Defined Access (SD-Access) fabric edge node feature of Cisco IOS XE Software could allow an unauthenticated, remote attacker to cause high CPU utilization and stop all traffic processing, resulting in a denial of service (DoS)…

more

condition on an affected device. This vulnerability is due to improper handling of certain IPv4 packets. An attacker could exploit this vulnerability by sending certain IPv4 packets to an affected device. A successful exploit could allow the attacker to cause the device to exhaust CPU resources and stop processing traffic, resulting in a DoS condition.

CWE(s)
CWE-783

Related Threats

CVEs Like This One

CVE-2024-20480Same product: Cisco Ios Xe
CVE-2025-20202Same product: Cisco Ios Xe
CVE-2025-20198Same product: Cisco Ios Xe
CVE-2024-20464Same product: Cisco Ios Xe
CVE-2024-20437Same product: Cisco Ios Xe
CVE-2024-20467Same product: Cisco Ios Xe
CVE-2025-20214Same product: Cisco Ios Xe
CVE-2025-20338Same product: Cisco Ios Xe
CVE-2024-20434Same product: Cisco Ios Xe
CVE-2025-20221Same product: Cisco Ios Xe

Affected Assets

cisco
ios xe
16.1.1, 16.1.2, 16.1.3, 16.10.1, 16.10.1a

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and static analysis directly find incorrect evaluation results caused by precedence mistakes.

SA-15 Development Process, Standards, and Tools partial match

Documented development standards and coding rules can require constructs that eliminate ambiguous operator precedence.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can mandate explicit parentheses and precedence rules that structurally prevent the logic error from being written.

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 (reviews, static analysis, testing) directly catch precedence errors while the control also addresses many other development risks.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect logic errors caused by precedence issues.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes code review and testing that can catch precedence errors.

A.8.28 Secure coding partial match
prevents

Secure coding standards and guidelines directly address operator precedence mistakes.

References