First published: Wed Mar 12 2025(Updated: )
A vulnerability in the IPv4 access control list (ACL) feature and quality of service (QoS) policy feature of Cisco IOS XR Software for Cisco ASR 9000 Series Aggregation Services Routers, ASR 9902 Compact High-Performance Routers, and ASR 9903 Compact High-Performance Routers could allow an unauthenticated, remote attacker to cause a line card to reset, resulting in a denial of service (DoS) condition. This vulnerability is due to the incorrect handling of malformed IPv4 packets that are received on line cards where the interface has either an IPv4 ACL or QoS policy applied. An attacker could exploit this vulnerability by sending crafted IPv4 packets through an affected device. A successful exploit could allow the attacker to cause network processor errors, resulting in a reset or shutdown of the network process. Traffic over that line card would be lost while the line card reloads. Note: This vulnerability has predominantly been observed in Layer 2 VPN (L2VPN) environments where an IPv4 ACL or QoS policy has been applied to the bridge virtual interface. Layer 3 configurations where the interface has either an IPv4 ACL or QoS policy applied are also affected, though the vulnerability has not been observed.
Credit: psirt@cisco.com
Affected Software | Affected Version | How to fix |
---|---|---|
Cisco IOS XRv 9000 | ||
Cisco ASR 9000 | ||
Cisco ASR 9902 Compact High-Performance Router | ||
Cisco ASR 9903 Compact High-Performance Router |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-20142 has been rated as a high severity vulnerability due to its potential impact on network security.
To resolve CVE-2025-20142, update your Cisco IOS XR software to the latest version provided by Cisco.
CVE-2025-20142 could allow unauthorized access and modification of network traffic if exploited.
CVE-2025-20142 affects Cisco ASR 9000 Series Routers, ASR 9902, and ASR 9903 Compact High-Performance Routers.
No official workaround has been provided for CVE-2025-20142; patching the software is the recommended approach.