Ios XrOperating system · Cisco
CVE-2024-20322
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability in the access control list (ACL) processing on Pseudowire interfaces in the ingress direction of Cisco IOS XR Software could allow an unauthenticated, remote attacker to bypass a configured ACL. This vulnerability is due to improper assignment of lookup keys to internal interface contexts. An attacker could exploit this vulnerability by attempting to send traffic through an affected device. A successful exploit could allow the attacker to access resources behind the affected device that were supposed to be protected by a configured ACL.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA vulnerability in Cisco IOS XR Software allows ACL bypass on pseudowire interfaces in the ingress direction due to improper assignment of lookup keys to internal interface contexts. An unauthenticated remote attacker can send traffic through an affected device to bypass configured ACLs and access protected resources.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Ios XrOperating system
= 7.10.2= 7.11CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the Cisco IOS XR software versionExecute 'show version' or 'admin show version' on the device to retrieve the installed IOS XR versionAffected if The displayed version is exactly 7.10.2 or 7.11
-
Confirm the device is running IOS XRVerify the output from 'show version' indicates Cisco IOS XR software rather than other IOS variantsAffected if The software is confirmed as Cisco IOS XR and version is 7.10.2 or 7.11
-
Check for configured pseudowire interfacesUse 'show interface' or 'show pseudowire' commands to list all pseudowire interfaces configured on the deviceAffected if Any pseudowire interfaces are present on the device running the affected versions
-
Verify ACL application on pseudowire interfaces in ingress directionUse 'show running-config interface <pseudowire-interface>' to examine ACL configurations applied to pseudowire interfaces, specifically looking for 'ip access-group' or 'ipv6 access-group' in the ingress directionAffected if Ingress ACLs are configured on pseudowire interfaces in versions 7.10.2 or 7.11
The device is affected if it runs exactly Cisco IOS XR version 7.10.2 or 7.11, has pseudowire interfaces configured, and has ingress ACLs applied to those pseudowire interfaces.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the Cisco IOS XR Software patch/updates for CVE-2024-20322 when available. Until then, consider implementing additional compensating controls such as interface filtering or alternative segmentation.
Fix this in Ios Xr
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20322 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-20322 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data