Catalyst Sd Wan ManagerApplication · Cisco
CVE-2022-20747
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 History API of Cisco SD-WAN vManage Software could allow an authenticated, remote attacker to gain access to sensitive information on an affected system. This vulnerability is due to insufficient API authorization checking on the underlying operating system. An attacker could exploit this vulnerability by sending a crafted API request to Cisco vManage as a lower-privileged user and gaining access to sensitive information that they would not normally be authorized to access.
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 confidenceThe History API in Cisco SD-WAN vManage lacks proper authorization checks, allowing authenticated lower-privileged users to send crafted API requests and access sensitive information outside their authorized scope. This is an authorization bypass vulnerability in the API layer of the vManage web application.
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
Catalyst Sd Wan ManagerApplication
= 20.7
Sd Wan VmanageApplication
< 20.6.1CVSS 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.
-
Identify the installed vManage versionAccess the vManage web UI and navigate to the Administration section, or use the CLI command 'show version' on the vManage device to retrieve the software version numberAffected if The displayed version is exactly 20.7 or is lower than 20.6.1
-
Confirm the History API is accessibleAttempt to access the History API endpoint on your vManage instance by sending a GET request to the API (typically /history or /dataservice/history endpoint) using an authenticated sessionAffected if The API returns historical data or operational logs without proper authorization enforcement
-
Verify user role assignments in vManageNavigate to the Administration > Users or Administration > User Groups section in the vManage web interface and review the assigned roles for non-administrator accountsAffected if There are user accounts with roles that should have restricted access but are able to query broader historical data
-
Review API access logs for authorization anomaliesCheck vManage logs or audit trails for API calls to History endpoints made by users with lower-privilege roles (such as 'viewer' or 'operator')Affected if Logs show that lower-privileged users successfully accessed data outside their expected scope through the History API
-
Test API authorization boundariesUsing a lower-privileged user account, attempt to access different categories of historical data via the API that should be restricted based on role permissionsAffected if The API returns information that should be inaccessible to that privilege level
You are affected if your Cisco SD-WAN vManage version is exactly 20.7 or is lower than 20.6.1, and users with limited privileges can access the History API to retrieve data outside their authorized scope.
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 · scoped20.6.1
Apply the Cisco patch for this vulnerability (refer to Cisco advisory), verify least-privilege user role assignments, and review API access controls to ensure proper authorization enforcement.
Upgrade to Cisco SD-WAN vManage release 20.6.1 or later (20.8 or later for Catalyst SD WAN Manager)
- 1. Identify the current Cisco SD-WAN vManage version by logging into the vManage web interface or running 'show version' via CLI
- 2. Confirm the affected version matches either 'Catalyst SD WAN Manager = 20.7' or 'SD WAN Vmanage < 20.6.1'
- 3. Schedule a maintenance window for the upgrade process
- 4. Download the fixed release (20.6.1 or later / 20.8 or later for Manager) from Cisco Software Central at software.cisco.com
- 5. Back up the current vManage configuration and database using the 'admin' backup utility
- 6. Upload and install the fixed release via the vManage Administration > Software Upgrade screen
- 7. Verify the upgrade completed successfully and the new version is running
- 8. Log in and confirm the History API now properly enforces authorization checks for lower-privileged users
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Catalyst Sd Wan Manager
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20747 — 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-20747 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