Sd Wan FirmwareOperating system · Cisco
CVE-2019-16002
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 vManage web-based UI (web UI) of the Cisco SD-WAN Solution could allow an unauthenticated, remote attacker to conduct a cross-site request forgery (CSRF) attack on an affected system. The vulnerability is due to insufficient CSRF protections for the web UI on an affected instance of vManage. An attacker could exploit this vulnerability by persuading a user to follow a malicious link. A successful exploit could allow the attacker to perform arbitrary actions with the privilege level of the affected user.
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 confidenceThe vulnerability is a Cross-Site Request Forgery (CSRF) flaw in Cisco SD-WAN vManage's web UI. An unauthenticated remote attacker can craft malicious links that, when clicked by an authenticated user, cause the user's browser to perform unauthorized actions with that user's privileges due to missing or inadequate CSRF token validation.
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
Sd Wan FirmwareOperating system
< 19.2.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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 vManage software versionLog into the vManage CLI and run 'show version' or access the web UI and navigate to Administration > About to view the software version numberAffected if The displayed version is earlier than 19.2.0 (for example, 18.x, 19.1.x, or any release prior to the 19.2.0 patch)
-
Confirm the vManage web UI is enabledCheck via CLI with 'show web-server details' or 'show running-config | include web' to see if the web-based management interface is activeAffected if The web UI is enabled and accessible to users, as this is the attack vector for the CSRF flaw
-
Verify CSRF protection is absent in HTTP responsesUsing a web proxy or browser developer tools, capture a login response to vManage and inspect whether the Set-Cookie headers include CSRF tokens or SameSite attributes, and whether subsequent POST requests to the API require a valid CSRF token headerAffected if No CSRF token is generated and validated for state-changing requests, or the SameSite cookie attribute is missing from session cookies
A system is affected if it runs any version of Cisco SD-WAN vManage prior to 19.2.0 and has the web UI enabled, with no CSRF token validation present in the application.
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.
From vendor data19.2.0
Apply the Cisco security patch for CVE-2019-16002. As a compensating control, enable SameSite cookie attributes on session cookies and implement strict Origin/Referer header validation on the vManage server.
Fix this in Sd Wan Firmware
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16002 — 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-2019-16002 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