dbcve.org
Catalyst Sd Wan ManagerApplication · Cisco

CVE-2024-20475

MEDIUM · 5.4 CVSS v3.1 Published 2024-09-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
A vulnerability in the web-based management interface of Cisco Catalyst SD-WAN Manager, formerly Cisco SD-WAN vManage, could allow an authenticated, remote attacker to conduct a cross-site scripting (XSS) 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 inserting malicious data into a specific data field in an affected interface. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected interface.

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 confidence

Stored XSS vulnerability in Cisco Catalyst SD-WAN Manager's web-based management interface. An authenticated attacker can inject malicious JavaScript into a specific data field that lacks proper input validation, causing the script to execute in the browsers of other users viewing that data.

MitigationApply Cisco's security patch when available. Implement server-side input validation and output encoding for all user-supplied data displayed in the web interface to prevent script execution.

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
Affected:= 20.6.0.18.3= 20.6.0.18.4= 20.6.1= 20.6.1.0.1= 20.6.1.1= 20.6.1.2= 20.6.2= 20.6.2.0.4= 20.6.2.1= 20.6.2.2= 20.6.2.2.2= 20.6.2.2.3

CVSS 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Cisco Catalyst SD-WAN Manager is installed
    Access the system CLI or admin interface and identify the product name. Typically running 'show version' or checking the web UI login page will display the product as 'Cisco Catalyst SD-WAN Manager' or 'Cisco vManage'.
    Affected if The product is not Cisco Catalyst SD-WAN Manager, then this CVE does not apply.
  2. Determine the installed software version
    Log into the SD-WAN Manager web interface and navigate to Administration > Software or use the CLI command 'show version' to retrieve the exact version number. The version will appear in format like 20.6.x.x.
    Affected if The installed version matches one of the affected versions: 20.6.0.18.3, 20.6.0.18.4, 20.6.1, 20.6.1.0.1, 20.6.1.1, 20.6.1.2, 20.6.2, 20.6.2.0.4, 20.6.2.1, 20.6.2.2, 20.6.2.2.2, or 20.6.2.2.3.
  3. Verify the web-based management interface is enabled
    Confirm that the SD-WAN Manager web interface is accessible and active. Check via browser access to the management IP or by reviewing network listener configurations.
    Affected if The web interface is disabled and no users can access it, the exploitation vector is not reachable, though the vulnerable code still exists in the software.
  4. Review user-accessible data input fields
    Log into the web interface as an authenticated user and examine fields where user-supplied data is stored and displayed back to users, such as device names, descriptions, policy names, or template fields.
    Affected if Any authenticated user can input data into fields that are visible to other users without proper validation, indicating the vulnerable condition exists.

The environment is affected if Cisco Catalyst SD-WAN Manager is running one of the listed affected versions and the web-based management interface is accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Cisco's security patch when available. Implement server-side input validation and output encoding for all user-supplied data displayed in the web interface to prevent script execution.

Fix this in Catalyst Sd Wan Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-20475 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-20475 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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