CVE-2022-20667
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 · uneditedMultiple vulnerabilities in the web-based management interface of Cisco Common Services Platform Collector (CSPC) Software could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the interface. These vulnerabilities are due to insufficient validation of user-supplied input by the web-based management interface. An attacker could exploit these vulnerabilities by persuading a user of the interface to click a crafted link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the 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 stored or reflected cross-site scripting (XSS) vulnerability in the web-based management interface of Cisco Common Services Platform Collector (CSPC) Software. The vulnerability exists due to insufficient validation of user-supplied input, allowing an unauthenticated attacker to inject malicious scripts via crafted links that, when clicked by a user, execute in the context of the interface.
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.10.0.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 CSPC versionAccess the CSPC web management interface and navigate to the About or System Information page to view the software version. Alternatively, log into the CSPC server via CLI and run: show version or similar command to retrieve the installed CSPC software version.Affected if The displayed version number is less than 2.10.0.2 (for example, 2.9.x, 2.8.x, or earlier releases).
-
Confirm web-based management interface is enabledVerify that the CSPC web-based management interface is accessible by attempting to reach the management URL (typically https://<CSPC-IP> or the configured management hostname) from a browser or curl request.Affected if The web interface responds and is reachable, meaning the attack surface is active.
-
Determine if unauthenticated access to the login page is possibleAttempt to access the CSPC login page without credentials to confirm the interface accepts unauthenticated requests.Affected if The login page or unauthenticated endpoints are accessible without authentication, allowing an attacker to potentially deliver malicious links.
You are affected if your installed Cisco CSPC version is below 2.10.0.2 and the web-based management interface is enabled and 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 · scoped2.10.0.2
Apply the vendor patch from Cisco when available. As an interim measure, users should avoid clicking untrusted links to the CSPC management interface.
Upgrade to Cisco CSPC version 2.10.0.2 or later
- Identify the currently installed Cisco Common Services Platform Collector (CSPC) version
- Access the CSPC management interface or use command-line tools to check the version
- Download Cisco CSPC version 2.10.0.2 or later from the Cisco website or your Cisco smart account
- Follow Cisco's standard upgrade procedure for CSPC - typically via the administration interface or CLI using the upgrade command
- After upgrade, verify the new version is 2.10.0.2 or higher
- Clear browser cache to ensure no cached vulnerable code remains
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20667 — 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-20667 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