CVE-2022-20659
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 web-based management interface of Cisco Prime Infrastructure and Cisco Evolved Programmable Network (EPN) Manager could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the interface of an affected device. This vulnerability exists because the web-based management interface does not properly validate user-supplied input. An attacker could exploit this vulnerability by persuading a user of an affected interface to click a crafted link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected interface or access sensitive, browser-based information.
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 confidenceThis is a reflected cross-site scripting (XSS) vulnerability in the web-based management interfaces of Cisco Prime Infrastructure and Cisco Evolved Programmable Network (EPN) Manager. The interface fails to properly validate user-supplied input, allowing an attacker to embed malicious JavaScript in a crafted link. When a user clicks the link, the script executes in the context of the affected interface, potentially stealing session cookies or performing actions on behalf of the user.
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.0< 3.10CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 installed productDetermine whether Cisco Evolved Programmable Network (EPN) Manager or Cisco Prime Infrastructure is deployed in your environment. Check installed software listings or consult system documentation.Affected if Either product is installed
-
Check EPN Manager versionAccess the EPN Manager web interface, then navigate to Administration > Software Updates > Installed Software, or run 'show version' via CLI. Record the exact version number.Affected if Version is less than 6.0 (for example, 5.x)
-
Check Prime Infrastructure versionAccess the Prime Infrastructure web interface, then go to Administration > Software Updates > Installed Software, or run 'show version' via CLI. Record the exact version number.Affected if Version is less than 3.10 (for example, 3.9.x or earlier)
-
Assess web interface exposureDetermine if the web-based management interface is accessible from untrusted networks. Review firewall rules, ACLs, and VPN policies that control access to port 443 or the management web port.Affected if Interface is reachable from untrusted or public networks without proper access controls
You are affected if either EPN Manager version is below 6.0 or Prime Infrastructure version is below 3.10, and the web management interface is accessible to users who could click crafted links.
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 · scoped3.106.0
Apply the vendor-supplied patch when available. In the interim, users should avoid clicking untrusted links and organizations may consider restricting web management interface exposure to trusted networks only.
Prime Infrastructure: 3.10 or later; Evolved Programmable Network Manager: 6.0 or later
- 1. Identify the currently installed version of Cisco Prime Infrastructure or Evolved Programmable Network Manager
- 2. If running Prime Infrastructure, upgrade to version 3.10 or later
- 3. If running Evolved Programmable Network Manager, upgrade to version 6.0 or later
- 4. Verify the upgrade was successful by checking the software version in the web-based management interface
- 5. Test that the web interface functions normally after upgrade
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-20659 — 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-20659 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