Sf220 24 FirmwareOperating system · Cisco
CVE-2021-1541
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 · uneditedMultiple vulnerabilities in the web-based management interface of Cisco Small Business 220 Series Smart Switches could allow an attacker to do the following: Hijack a user session Execute arbitrary commands as a root user on the underlying operating system Conduct a cross-site scripting (XSS) attack Conduct an HTML injection attack For more information about these vulnerabilities, see the Details section of this advisory.
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 confidenceMultiple vulnerabilities in the web-based management interface of Cisco Small Business 220 Series Smart Switches allow session hijacking, root-level command execution on the underlying OS, cross-site scripting (XSS), and HTML injection attacks. These are separate flaws in the web management layer that can be chained or exploited independently.
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
Sf220 24 FirmwareOperating system
< 1.2.0.6
Sf220 24p FirmwareOperating system
< 1.2.0.6
Sf220 48 FirmwareOperating system
< 1.2.0.6
Sf220 48p FirmwareOperating system
< 1.2.0.6
Sg220 26 FirmwareOperating system
< 1.2.0.6
Sg220 26p FirmwareOperating system
< 1.2.0.6
Sg220 28mp FirmwareOperating system
< 1.2.0.6
Sg220 50 FirmwareOperating system
< 1.2.0.6CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 modelAccess the device via console or check the physical device label to confirm the exact model number (e.g., Sf220-24, Sg220-26, etc.)Affected if The model is one of: Sf220 24, Sf220 24p, Sf220 48, Sf220 48p, Sg220 26, Sg220 26p, Sg220 28mp, or Sg220 50
-
Check the firmware versionLog into the web-based management interface and navigate to Administration > Firmware Upgrade, or use the CLI command 'show version' via console/SSH to retrieve the installed firmware versionAffected if The firmware version is lower than 1.2.0.6 (e.g., 1.1.x.x, 1.0.x.x, etc.)
-
Confirm web-based management is enabledIn the web UI, go to Administration > Management Interface > HTTP/HTTPS settings, or via CLI check 'show http server status' to see if the HTTP or HTTPS management interface is activeAffected if The web-based management interface (HTTP or HTTPS) is enabled and accessible
-
Check remote access configurationIn the web UI, verify the management VLAN and access settings under Administration > Management Interface > Service Availability to determine if web management is accessible from remote networksAffected if Web management is accessible from non-trusted networks or the management VLAN is not properly segmented
The environment is affected if the device is a Cisco 220 Series Smart Switch model from the list and is running firmware version lower than 1.2.0.6 with the web 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 data1.2.0.6
Apply the vendor-supplied firmware update from Cisco for the 220 Series Smart Switches. If immediate patching is not possible, restrict web management interface access to trusted networks or disable remote management where feasible.
Fix this in Sf220 24 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-2021-1541 — 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-1541 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