Sd Wan FirmwareOperating system · Cisco
CVE-2020-3372
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 consume excessive system memory and cause a denial of service (DoS) condition on an affected system. The vulnerability is due to inefficient memory management. An attacker could exploit this vulnerability by sending a large number of crafted HTTP requests to the affected web-based management interface. A successful exploit could allow the attacker to exhaust system memory, which could cause the system to stop processing new connections and could result in a DoS condition.
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 vulnerability in the web-based management interface of Cisco SD-WAN vManage Software allows an authenticated attacker to send specially crafted HTTP requests that cause excessive memory consumption due to inefficient memory management, eventually exhausting system memory and causing denial of service by stopping new connection processing.
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.3>= 20.1.0, < 20.1.12CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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 vManage software versionAccess the vManage administrative console or use the 'show version' command via CLI. In the web UI, navigate to Administration > Settings > Software Update or check the dashboard for the running version.Affected if The installed version falls below 19.2.3 or is 20.1.0 through 20.1.12 (excluding 20.1.12).
-
Confirm web-based management interface is enabledVerify that the vManage web interface (HTTP/HTTPS on port 443 or 8443) is listening and accessible. Check with 'netstat -an | grep -E "(443|8443)"' or review interface bindings in vManage network configuration.Affected if The web management interface is exposed and accepting connections.
-
Check for memory exhaustion symptomsMonitor system memory usage via 'show processes memory' CLI command or vManage dashboard. Look for abnormally high memory consumption or memory allocation failures in system logs.Affected if Memory usage is abnormally high or the system is experiencing memory allocation failures without other explanation.
-
Review authentication statusDetermine if user authentication is configured and active on vManage. The vulnerability requires an authenticated attacker, so verify whether local or remote authentication (RADIUS/TACACS+) is enforced.Affected if User authentication is configured but the vManage version is in the affected range.
A system is affected if it runs Cisco SD-WAN vManage firmware version below 19.2.3 or between 20.1.0 and 20.1.12, and has the web-based management interface enabled.
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.320.1.12
Apply the Cisco patch for this vulnerability. Until patched, implement rate limiting on the management interface and restrict access to trusted administrative IP addresses to reduce attack surface.
Fix this in Sd Wan Firmware
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3372 — 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-2020-3372 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