dbcve.org
200 Series Smart SwitchesHardware / appliance · Cisco

CVE-2013-1154

MEDIUM · 5.0 CVSS v2.0 Published 2013-03-07
Fix available
A fix is available. Upgrade to after 1.2.7.76 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The Cisco Small Business 200 Series Smart Switch 1.2.7.76 and earlier, Small Business 300 Series Managed Switch 1.2.7.76 and earlier, and Small Business 500 Series Stackable Managed Switch 1.2.7.76 and earlier allow remote attackers to cause a denial of service (SSL/TLS layer outage) via malformed (1) SSH or (2) SSL packets, aka Bug ID CSCua30246.

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 confidence

This CVE affects Cisco Small Business 200/300/500 Series Switches running firmware 1.2.7.76 and earlier. Remote unauthenticated attackers can send malformed SSH or SSL packets to cause a denial of service at the SSL/TLS layer, resulting in service outage. The vulnerability is network-exploitable and requires no authentication.

MitigationUpdate Cisco Small Business switch firmware to a version later than 1.2.7.76. If immediate patching is not feasible, restrict network access to management interfaces to prevent unauthenticated attackers from sending malformed packets.

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
200 Series Smart SwitchesHardware / appliance
Affected:= sf200-24= sf200-24p= sf200-48= sf200-48p= sg200-08= sg200-08p= sg200-18= sg200-26= sg200-26p= sg200-50= sg200-50p
300 Series Managed SwitchesHardware / appliance
Affected:= sf300-08= sf300-24= sf300-24mp= sf300-24p= sf300-48= sf300-48p= sf302-08= sf302-08mp= sf302-08p= sg300-10= sg300-10mp= sg300-10p
200 Series Smart Switches SoftwareApplication
Affected:<= 1.2.7.76
500 Series Stackable Managed SwitchesHardware / appliance
Affected:= sf500-24= sf500-24p= sf500-48= sf500-48p= sg500-28= sg500-28p= sg500-52= sg500-52p= sg500x-24= sg500x-24p= sg500x-48= sg500x-48p

CVSS 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
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify switch model
    Access the switch management interface or check the physical device label to determine the exact model number (e.g., sf200-24, sg300-10, sg500-28)
    Affected if The model matches one of the affected products listed: Cisco 200 Series (sf200-xx, sg200-xx), 300 Series (sf300-xx, sf302-xx, sg300-xx), or 500 Series (sf500-xx, sg500-xx, sg500x-xx)
  2. Determine firmware version
    Log into the switch web interface or CLI and navigate to the Administration or System Info section to view the current firmware/software version
    Affected if The firmware version is 1.2.7.76 or earlier
  3. Verify SSH or HTTPS management is enabled
    Check the switch management settings to confirm whether SSH access or HTTPS (SSL/TLS) web management is enabled and accessible
    Affected if SSH or HTTPS management interfaces are exposed and enabled on the device
  4. Assess network accessibility of management interface
    Determine if the management interface (SSH port 22, HTTPS port 443) is reachable from untrusted networks or the internet
    Affected if Management ports are accessible from external/untrusted networks without proper access controls

The switch is affected if it is a Cisco 200/300/500 Series model running firmware version 1.2.7.76 or earlier, and SSH or SSL/TLS management is enabled and accessible to unauthenticated attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.2.7.76
Interim mitigation

Update Cisco Small Business switch firmware to a version later than 1.2.7.76. If immediate patching is not feasible, restrict network access to management interfaces to prevent unauthenticated attackers from sending malformed packets.

Fix this in 200 Series Smart Switches Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-1154 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-1154 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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