CVE-2022-20849
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 Broadband Network Gateway PPP over Ethernet (PPPoE) feature of Cisco IOS XR Software could allow an unauthenticated, adjacent attacker to cause the PPPoE process to continually crash. This vulnerability exists because the PPPoE feature does not properly handle an error condition within a specific crafted packet sequence. An attacker could exploit this vulnerability by sending a sequence of specific PPPoE packets from controlled customer premises equipment (CPE). A successful exploit could allow the attacker to cause the PPPoE process to continually restart, resulting in a denial of service condition (DoS).Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.This advisory is part of the September 2022 release of the Cisco IOS XR Software Security Advisory Bundled Publication. For a complete list of the advisories and links to them, see .
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's Broadband Network Gateway PPPoE feature allows an unauthenticated, adjacent attacker to cause the PPPoE process to continuously crash by sending a specific crafted packet sequence. The flaw stems from improper error handling within the PPPoE feature when processing certain packets, resulting in repeated process restarts and denial of service.
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= 6.5.1= 6.5.2= 6.5.3= 6.5.15= 6.6.1= 6.6.2= 6.6.3= 6.6.4= 6.6.25= 6.7.1= 6.7.2= 6.7.3CVSS 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
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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.
-
Identify the device OS and versionExecute 'show version' or 'admin show version' on the device to confirm it is running Cisco IOS XR and to obtain the exact software version numberAffected if The device runs Cisco IOS XR and the version matches one of the following: 6.5.1, 6.5.2, 6.5.3, 6.5.15, 6.6.1, 6.6.2, 6.6.3, 6.6.4, 6.6.25, 6.7.1, 6.7.2, or 6.7.3
-
Confirm PPPoE configuration on BNGRun 'show running-config | include pppoe' or 'show pppoe interfaces' to check if PPPoE is enabled on any interfaceAffected if PPPoE is configured and active on the device
-
Check for PPPoE process crashesReview logs with 'show logging | include pppoe' or check 'show process crash' for the pppoe process to identify any recent restarts or crashesAffected if The PPPoE process has crashed or restarted repeatedly, indicating potential exploitation
A user is affected if the device runs a vulnerable IOS XR version (6.5.1 through 6.7.3) AND has PPPoE configured, with the vulnerability potentially indicated by PPPoE process instability.
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 software updates released in the September 2022 IOS XR Security Advisory Bundled Publication; no workarounds are available.
Contact Cisco for specific fixed release (refer to September 2022 IOS XR Security Advisory)
- Contact Cisco technical support or visit sec.cloudapps.cisco.com to obtain the specific fixed release for IOS XR version 6.5.x
- Request the PPPoE security update from Cisco's IOS XR Software Security Advisory Bundled Publication (September 2022)
- Plan maintenance window for upgrade as PPPoE service will be briefly interrupted during the software update process
- After upgrade, verify PPPoE process stability using 'show process pppoe' or similar diagnostic commands
- Monitor system logs for any PPPoE process crashes following the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20849 — 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-20849 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