CVE-2022-20694
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 implementation of the Resource Public Key Infrastructure (RPKI) feature of Cisco IOS XE Software could allow an unauthenticated, remote attacker to cause the Border Gateway Protocol (BGP) process to crash, resulting in a denial of service (DoS) condition. This vulnerability is due to the incorrect handling of a specific RPKI to Router (RTR) Protocol packet header. An attacker could exploit this vulnerability by compromising the RPKI validator server and sending a specifically crafted RTR packet to an affected device. Alternatively, the attacker could use man-in-the-middle techniques to impersonate the RPKI validator server and send a crafted RTR response packet over the established RTR TCP connection to the affected device. A successful exploit could allow the attacker to cause a DoS condition because the BGP process could constantly restart and BGP routing could become unstable.
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 · high confidenceA vulnerability in Cisco IOS XE Software's RPKI (Resource Public Key Infrastructure) feature allows an unauthenticated remote attacker to crash the BGP process by sending a specifically crafted RTR (RPKI to Router) Protocol packet. The flaw is in incorrect handling of the RTR packet header. Attackers can exploit this either by compromising the RPKI validator server or performing man-in-the-middle attacks on the RTR TCP connection, causing BGP to continuously restart and create routing instability.
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= 3.7.0bs= 3.7.0s= 3.7.0xas= 3.7.0xbs= 3.7.1as= 3.7.1s= 3.7.2s= 3.7.2ts= 3.7.3s= 3.7.4as= 3.7.4s= 3.7.5sCVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:H
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.
-
Check the IOS XE versionExecute 'show version' or 'show version | include Version' to display the running IOS XE versionAffected if The displayed version matches any of: 3.7.0bs, 3.7.0s, 3.7.0xas, 3.7.0xbs, 3.7.1as, 3.7.1s, 3.7.2s, 3.7.2ts, 3.7.3s, 3.7.4as, 3.7.4s, or 3.7.5s
-
Verify if RPKI is configuredExecute 'show ip rpki' or 'show run | include rpki' to check for RPKI configuration in the deviceAffected if RPKI is configured and operational on the device
-
Confirm RTR protocol session statusExecute 'show ip rpki table' or 'show ip rpki connections' to check if an RTR connection to an RPKI validator server is activeAffected if An active RTR session exists to an RPKI validator server
The device is affected if it runs an affected IOS XE version listed above AND has RPKI with an active RTR session configured, exposing the RTR packet handling vulnerability.
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.
dbcve · scopedApply the Cisco IOS XE software update when available. Additionally, secure the RPKI validator server infrastructure and consider using encrypted/authenticated channels for RTR communications to mitigate MITM attack vectors.
Upgrade to the fixed IOS XE release as documented in the Cisco security advisory for CVE-2022-20694 (check advisory for exact version number)
- Identify the current Cisco IOS XE version using 'show version' command
- Access Cisco.com and navigate to the Cisco IOS XE Software security advisory for CVE-2022-20694
- Download and install the fixed IOS XE release as specified in the advisory (typically a later 3.7.x release or 3.8.x/3.9.x depending on advisory)
- After upgrade, verify RPKI functionality is operational with 'show ip rpki server' and 'show bgp rpki servers'
- Monitor BGP stability using 'show ip bgp summary' to confirm no further crashes occur
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2022-20694 — 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-2022-20694 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