CVE-2022-20958
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 BroadWorks CommPilot application could allow an unauthenticated, remote attacker to perform a server-side request forgery (SSRF) attack on an affected device. This vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vulnerability by sending a crafted HTTP request to the web interface. A successful exploit could allow the attacker to obtain confidential information from the BroadWorks server and other device on the network. {{value}} ["%7b%7bvalue%7d%7d"])}]]
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 Server-Side Request Forgery (SSRF) vulnerability in the web-based management interface of Cisco BroadWorks CommPilot. An unauthenticated, remote attacker can send crafted HTTP requests to the web interface, and due to insufficient validation of user-supplied input, the vulnerable server can be induced to make requests to internal resources. This allows the attacker to access confidential information from the BroadWorks server itself and potentially other devices on the internal network.
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< 23.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 Cisco BroadWorks CommPilot installationLocate the BroadWorks CommPilot application on the system. Check for processes named 'CommPilot' or directories containing 'broadworks' and 'compilot' in the installation path.Affected if The application is present on the system
-
Determine the installed versionUse the application's administrative interface, command-line tool, or check version files in the installation directory to retrieve the exact version number.Affected if The version is less than 23.0
-
Verify web management interface is enabledCheck the application configuration for web server settings. Look for HTTP/HTTPS listener configuration for the management interface, typically on ports 80, 443, or custom ports.Affected if The web-based management interface is exposed and accessible over the network
-
Confirm the SSRF attack surface existsAttempt to access the web management interface via HTTP from an external or internal IP address to confirm it accepts requests. The vulnerability requires the interface to process user-supplied URLs.Affected if The web interface accepts requests from network sources without requiring authentication
The environment is affected if Cisco BroadWorks CommPilot is installed with a version less than 23.0 and the web-based management interface is accessible over the network.
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 · scoped23.0
Implement proper input validation and URL sanitization on all user-supplied URLs/hosts in HTTP requests. Apply network segmentation to restrict the management interface and limit internal network access from the application server. Monitor for anomalous outbound requests from the application.
BroadWorks CommPilot Application 23.0 or later
- 1. Back up the current BroadWorks CommPilot configuration and any custom settings.
- 2. Review the Cisco BroadWorks 23.0 release notes and migration guide for any pre-upgrade requirements.
- 3. Download the BroadWorks CommPilot Application version 23.0 or later from the Cisco software download portal (requires valid service contract).
- 4. Execute the upgrade procedure according to the Cisco BroadWorks upgrade guide for the CommPilot application.
- 5. After upgrade, verify the CommPilot web interface is accessible and functioning normally.
- 6. Confirm the SSRF vulnerability is remediated by reviewing the security fixes in the 23.0 release notes.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20958 — 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-20958 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