Sg200 50 FirmwareOperating system · Cisco
CVE-2020-3147
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 UI of Cisco Small Business Switches could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. The vulnerability is due to improper validation of requests sent to the web interface. An attacker could exploit this vulnerability by sending a malicious request to the web interface of an affected device. A successful exploit could allow the attacker to cause an unexpected reload of the device, resulting in a DoS condition. This vulnerability affects firmware releases prior than 1.3.7.18
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 UI of Cisco Small Business Switches allows unauthenticated remote attackers to send malicious requests that exploit improper input validation, causing an unexpected device reload and resulting in denial of service. The vulnerability affects firmware versions prior to 1.3.7.18.
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
Sg200 50 FirmwareOperating system
< 1.3.7.18
Sg200 50p FirmwareOperating system
< 1.3.7.18
Sg200 50fp FirmwareOperating system
< 1.3.7.18
Sg200 26 FirmwareOperating system
< 1.3.7.18
Sg200 26p FirmwareOperating system
< 1.3.7.18
Sg200 26fp FirmwareOperating system
< 1.3.7.18
Sg200 18 FirmwareOperating system
< 1.3.7.18
Sg200 10fp FirmwareOperating system
< 1.3.7.18CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 the switch modelCheck the physical device label or log into the switch CLI and run 'show version' to confirm the model number is one of: SG200-50, SG200-50p, SG200-50fp, SG200-26, SG200-26p, SG200-26fp, SG200-18, or SG200-10fpAffected if The switch is one of the listed SG200 models
-
Check the firmware versionLog into the switch web UI and navigate to Administration > Device Settings > Firmware, or use the CLI command 'show version' to determine the installed firmware versionAffected if Firmware version is below 1.3.7.18
-
Verify web UI is enabledIn the web UI, go to Administration > Management Interface > HTTP/HTTPS Settings, or use the CLI command 'show ip http' to check if HTTP management is enabledAffected if The web UI (HTTP or HTTPS) is currently enabled
The switch is affected if it is a SG200 model with firmware version earlier than 1.3.7.18 and the web UI is 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.
From vendor data1.3.7.18
Upgrade Cisco Small Business Switch firmware to version 1.3.7.18 or later. If immediate patching is not possible, restrict web UI access to trusted networks or disable the web interface until the upgrade can be performed.
Fix this in Sg200 50 Firmware
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3147 — 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-3147 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