BroadworksApplication · Cisco
CVE-2022-20869
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 Application Delivery Platform Software could allow an unauthenticated, remote attacker to conduct a cross-site scripting attack against a user of the interface. 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 the 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 interface of Cisco BroadWorks Application Delivery Platform. The interface fails to properly sanitize user-supplied input, allowing an attacker to embed malicious JavaScript in a crafted URL. When a legitimate user clicks this link, the script executes in their browser within the context of the affected interface, enabling session hijacking or information theft.
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
BroadworksApplication
>= 22.0, < 22.0.2022.06>= 23.0, < 23.0.2022.06>= 24.0, < 24.0.2022.06CVSS 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 Cisco BroadWorks ADP installationCheck for running processes or services related to BroadWorks Application Delivery Platform on the system. Look for broadworks, as-ad, or similar process names using task manager or system commands.Affected if The system is running Cisco BroadWorks Application Delivery Platform software.
-
Determine installed versionAccess the web-based management interface or use the system command-line interface to retrieve the software version. Typical methods include logging into the admin portal or running 'show version' or similar system commands.Affected if The version cannot be determined or the software is not found.
-
Compare version to affected rangesReview the installed version number and compare it against these vulnerable ranges: 22.0 through 22.0.2022.05, 23.0 through 23.0.2022.05, or 24.0 through 24.0.2022.05.Affected if The installed version falls within any of these ranges: >= 22.0 and < 22.0.2022.06, >= 23.0 and < 23.0.2022.06, or >= 24.0 and < 24.0.2022.06.
-
Verify web management interface accessibilityConfirm whether the web-based management interface is accessible on the network. Check if HTTP/HTTPS ports for the management interface are open and reachable.Affected if The web-based management interface is exposed and accessible to users or attackers.
A system is affected if it runs Cisco BroadWorks Application Delivery Platform version 22.0-22.0.2022.05, 23.0-23.0.2022.05, or 24.0-24.0.2022.06 AND has 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.
dbcve · scoped22.0.2022.0623.0.2022.0624.0.2022.06
Apply the vendor patch from Cisco when available. Until then, implement URL filtering and educate users to avoid clicking untrusted links. Consider deploying a WAF with XSS protection rules as a compensating control.
22.0.2022.06, 23.0.2022.06, or 24.0.2022.06 (depending on current branch)
- Identify the currently installed BroadWorks Application Delivery Platform version using the web-based management interface or command-line tools
- Determine which version branch the current installation belongs to (22.x, 23.x, or 24.x)
- Obtain the appropriate fixed release from Cisco: upgrade to 22.0.2022.06 or later for 22.x branches, 23.0.2022.06 or later for 23.x branches, or 24.0.2022.06 or later for 24.x branches
- Review Cisco's upgrade documentation and release notes for the target version
- Plan maintenance window as upgrades may require service interruption
- Perform backup of current configuration before upgrade
- Execute upgrade following Cisco's documented procedures
- After upgrade, verify the web-based management interface is accessible and functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Broadworks
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20869 — 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-20869 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