CVE-2021-1491
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 SD-WAN vManage Software could allow an authenticated, remote attacker to read arbitrary files on the underlying file system of the device. This vulnerability is due to insufficient file scope limiting. An attacker could exploit this vulnerability by creating a specific file reference on the file system and then accessing it through the web-based management interface. A successful exploit could allow the attacker to read arbitrary files from the file system of the underlying operating system.Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.
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 confidenceA path traversal vulnerability in Cisco SD-WAN vManage's web-based management interface allows authenticated remote attackers to read arbitrary files from the OS filesystem. The vulnerability stems from insufficient file scope limiting in the web component, where an attacker can manipulate file references to access files outside the intended scope.
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= 17.2.4= 17.2.5= 17.2.6= 17.2.7= 17.2.8= 17.2.9= 17.2.10= 18.2.0= 18.3.0= 18.3.1= 18.3.1.1= 18.3.3CVSS 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.0/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 if Cisco SD-WAN vManage is installedLocate the vManage installation and note its installation path. Common locations include /opt/sdwan/vmanage or check system packages for 'vmanage' or 'sdwan' components.Affected if The system runs Cisco Catalyst SD-WAN Manager (vManage)
-
Determine the installed vManage versionRun 'vmanage -version' or check /opt/sdwan/vmanage/version.txt, or use the web interface login page which often displays the version, or query the API endpoint /dataservice/system/device/mode if accessible.Affected if The installed version matches one of these: 17.2.4, 17.2.5, 17.2.6, 17.2.7, 17.2.8, 17.2.9, 17.2.10, 18.2.0, 18.3.0, 18.3.1, 18.3.1.1, or 18.3.3
-
Verify the web-based management interface is enabledCheck if the vManage web service is running and accessible. Look for httpd or nginx processes related to vManage on ports 443 or 8443. Confirm the '/dataservice' API endpoint is reachable.Affected if The vManage web management interface (HTTPS on port 443 or 8443) is exposed and operational
-
Confirm authentication is configured for the web interfaceVerify that the web interface requires valid credentials. Check the authentication configuration in /opt/sdwan/vmanage/webui/config or verify login is enforced when accessing the management portal.Affected if The web management interface accepts authentication credentials (even if using default or weak credentials)
A system is affected if it runs Cisco Catalyst SD-WAN Manager versions 17.2.4 through 18.3.3 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 · scopedApply the Cisco software updates that address this vulnerability. No workarounds are available.
Any version later than 17.2.7 (e.g., 17.2.8 or later in the 17.2.x train)
- Identify the current Cisco SD-WAN vManage software version using the web interface or CLI
- Navigate to the Cisco Software Download page or contact Cisco to obtain the fixed release
- Upgrade to a version later than 17.2.7 that contains the security fix
- After upgrade, verify the system is running the patched version
- Confirm the vulnerability is resolved by attempting (and failing) the file read with the previously exploitable method
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1491 — 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-2021-1491 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