CVE-2022-20657
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 PI and Cisco EPNM could allow an unauthenticated, remote attacker to conduct an 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.Cisco has released software updates that address these vulnerabilities. There are no workarounds that address these vulnerabilities.
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 stored (or reflected) XSS vulnerability in Cisco Prime Infrastructure (PI) and Cisco EPNM's web-based management interface. The flaw stems from improper validation of user-supplied input, allowing an attacker to inject malicious scripts via crafted links that execute in the context of the user's browser when clicked.
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= 2.0.0= 2.1= 2.2= 3.0.0= 3.1.0= 3.1.5= 3.2= 3.2.0-fips= 3.3.0= 3.4.0= 3.5.0= 3.6.0= 1.1= 1.2= 2.0= 2.1= 2.2= 3.0= 3.0.1= 3.0.2= 3.0.3= 3.1= 3.1.1= 3.1.2CVSS 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 the installed productAccess the web-based management interface and check the About or version page, or use CLI command 'show version' if availableAffected if The product is Cisco Prime Infrastructure or Cisco Evolved Programmable Network Manager (EPNM)
-
Determine the exact software versionLocate the version number in the product's web UI footer, about page, or via CLI command 'show version'Affected if The installed version matches any of: Cisco PI 2.0.0, 2.1, 2.2, 3.0.0, 3.1.0, 3.1.5, 3.2, 3.2.0-fips, 3.3.0, 3.4.0, 3.5.0, 3.6.0 OR Cisco EPNM 1.1, 1.2, 2.0, 2.1, 2.2, 3.0, 3.0.1, 3.0.2, 3.0.3, 3.1, 3.1.1, 3.1.2
-
Verify the web management interface is accessibleConfirm the web-based management interface is enabled and reachable on the networkAffected if The web interface is exposed and accessible to users or attackers
-
Check for suspicious user-supplied input in logsReview web server access and error logs for any evidence of malicious script injection attempts in URL parametersAffected if Unusual script tags or HTML elements appear in HTTP request logs targeting the management interface
Your environment is affected if you are running any of the listed versions of Cisco Prime Infrastructure or Cisco EPNM with the web-based management interface enabled and accessible.
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 software updates that address this vulnerability, as no workarounds are available. Until patched, users should be cautious about clicking untrusted links.
- 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-20657 — 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-20657 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