500 Series Switch FirmwareOperating system · Cisco
CVE-2016-1303
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 · uneditedThe web GUI on Cisco Small Business 500 devices 1.2.0.92 allows remote attackers to cause a denial of service via a crafted HTTP request, aka Bug ID CSCul65330.
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 confidenceA denial of service vulnerability exists in the web GUI of Cisco Small Business 500 series switches running firmware version 1.2.0.92. Attackers can remotely crash the device by sending specially crafted HTTP requests to the web interface, causing the service to become unavailable.
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
500 Series Switch FirmwareOperating system
= 1.2.0.92CVSS 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.0/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 device modelAccess the switch CLI and run 'show version' or check the device label to confirm it is a Cisco Small Business 500 series switch.Affected if The device model is not a Cisco Small Business 500 series switch.
-
Check firmware versionRun 'show version' in the switch CLI and locate the firmware/OS version string. Compare it to 1.2.0.92.Affected if The firmware version is exactly 1.2.0.92.
-
Verify web GUI is enabledCheck the switch configuration with 'show running-config' or 'show interface' to see if the web GUI HTTP service is configured and active (look for 'ip http server' or similar web management settings).Affected if The web GUI HTTP service is enabled and reachable.
-
Confirm network accessibility of web interfaceAttempt to reach the web GUI via HTTP from a management station using the switch IP address, or verify the management VLAN/interface settings allow HTTP access.Affected if The web interface responds to HTTP requests on port 80.
A user is affected only if they have a Cisco Small Business 500 series switch running firmware exactly version 1.2.0.92 with the web GUI interface enabled and accessible over the network.
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 dataApply the latest Cisco firmware update for the Small Business 500 series. If no update is available, disable the web GUI management interface or restrict access via ACLs to only trusted management networks.
Fix this in 500 Series Switch 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-2016-1303 — 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-2016-1303 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