CVE-2022-20951
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 authenticated, 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 · moderate confidenceThis is a Server-Side Request Forgery (SSRF) vulnerability in Cisco BroadWorks CommPilot's web-based management interface. An authenticated attacker can send specially crafted HTTP requests containing malicious URLs that the server will process, allowing unauthorized access to internal network resources and confidential information from the BroadWorks server and other devices.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Confirm Cisco BroadWorks CommPilot is installedReview system inventory or documentation for Cisco BroadWorks Messaging Server or CommPilot web management interface installations in your environmentAffected if The product is present in your environment
-
Identify the installed versionAccess the web management interface and navigate to the About or System Information page, or check via CLI if available: 'show system information' or similar command for BroadWorksAffected if The version is below 23.0 (e.g., 22.x or earlier)
-
Verify the web management interface is exposedCheck network accessibility of the CommPilot web interface port (typically HTTPS 443 or HTTP 80) from network vantage pointsAffected if The management interface is reachable from network segments accessible to potential attackers
-
Check authentication configurationReview user authentication settings and access controls for the CommPilot web management interface to understand what authenticated access entailsAffected if Low-privilege or weak authentication is configured, allowing easier attacker authentication
-
Inspect outbound network rulesReview firewall or network ACLs governing what destinations the BroadWorks server can initiate connections toAffected if The server has unrestricted or broad outbound network access to internal resources
You are affected if Cisco BroadWorks Messaging Server with CommPilot web management interface version below 23.0 is installed and the web interface is network-accessible to potential attackers.
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
Apply Cisco's patch when available. As compensating controls, implement network segmentation to restrict server outbound access and configure WAF rules to detect and block SSRF patterns in HTTP requests.
BroadWorks Messaging Server 23.0 or later
- 1. Identify the current installed version of Cisco BroadWorks Messaging Server
- 2. Back up all configuration data and user data according to Cisco backup procedures
- 3. Plan maintenance window as upgrade may require service interruption
- 4. Obtain the BroadWorks Messaging Server 23.0 or later release from Cisco
- 5. Follow Cisco's official upgrade documentation to upgrade the BroadWorks Messaging Server to version 23.0 or later
- 6. Verify the upgrade was successful by checking the version number in the management interface
- 7. Test that the web-based management interface functions correctly after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20951 — 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-20951 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