Encs 5100 FirmwareOperating system · Cisco
CVE-2023-20228
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 Integrated Management Controller (IMC) could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the interface. This vulnerability is due to insufficient validation of user input. An attacker could exploit this vulnerability by persuading a user of an affected interface to click a crafted link. A successful exploit could allow the attacker to execute arbitrary script code in the browser of the targeted user or access sensitive, browser-based information.
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 stored cross-site scripting (XSS) vulnerability in Cisco IMC's web-based management interface allows unauthenticated remote attackers to inject malicious scripts through insufficiently validated user input. Successful exploitation requires a user to click a crafted link, enabling arbitrary script execution in the victim's browser or access to sensitive browser-based information.
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
Encs 5100 FirmwareOperating system
>= 3.2, < 3.2.15.1
Encs 5400 FirmwareOperating system
>= 3.2, < 3.2.15.1
Ucs C220 M5 Rack Server FirmwareOperating system
>= 4.2, < 4.3.2.230207
Ucs E160s M3 FirmwareOperating system
< 3.2.15.1
Ucs E180d M3 FirmwareOperating system
< 3.2.15.1
Ucs E1120d M3 FirmwareOperating system
< 3.2.15.1CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 Cisco IMC accessAccess the Cisco IMC web interface by navigating to the IP address of the server's BMC (Baseboard Management Controller). Confirm you are on the Cisco IMC login page. The interface is typically accessible via HTTPS on port 443 or 8443.Affected if The web interface is reachable and displays Cisco IMC login
-
Check firmware versionAfter logging into Cisco IMC, navigate to the Admin tab or Summary page to view the firmware version. Alternatively, use the CLI via IPMI or SSH to the BMC and run 'show version' or 'ucsmcimcfsck -v' to retrieve the firmware version.Affected if The installed firmware version falls within the affected ranges: ENCS 5100/5400 with version >= 3.2 but < 3.2.15.1, UCS C220 M5 with version >= 4.2 but < 4.3.2.230207, or UCS E160s/E180d/E1120d M3 with version < 3.2.15.1
-
Verify product modelConfirm the specific Cisco product model by checking the system information in the IMC web interface (usually under Admin > Summary or Hardware > Server) or via CLI command 'show inventory' from the BMC.Affected if The model is one of: ENCS 5100, ENCS 5400, UCS C220 M5, UCS E160s M3, UCS E180d M3, or UCS E1120d M3
-
Confirm web management is enabledIn the IMC web interface, verify that the web-based management interface is enabled under Admin > Network Settings or Settings > Services. This vulnerability affects only the web interface.Affected if The Cisco IMC web-based management interface is enabled and accessible
A system is affected if it is running Cisco IMC on an ENCS 5100/5400, UCS C220 M5, or UCS E-series M3 server with firmware versions matching the affected ranges and the web management interface is 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.
dbcve · scoped3.2.15.14.3.2.230207
Apply the Cisco patch for this vulnerability when released; until then, restrict access to the IMC management interface to trusted networks and educate users about not clicking suspicious links.
Cisco IMC Firmware 3.2.15.1 (for Encs 5100, Encs 5400, E160s M3, E180d M3, E1120d M3) or 4.3.2.230207 (for UCS C220 M5)
- 1. Identify the exact Cisco IMC firmware version currently installed on the affected device
- 2. Determine the product model (Encs 5100, Encs 5400, UCS C220 M5, UCS E160s M3, UCS E180d M3, or UCS E1120d M3)
- 3. Download the appropriate fixed firmware version from Cisco's official download portal: version 3.2.15.1 for Encs and E-series models, or version 4.3.2.230207 for UCS C220 M5
- 4. Review Cisco's firmware upgrade documentation for the specific hardware model
- 5. Back up the current IMC configuration before upgrading
- 6. Upload the new firmware to the IMC via the web interface or CLI
- 7. Initiate the firmware upgrade and allow the process to complete without interruption
- 8. Verify the upgrade was successful by checking the firmware version in the IMC web interface
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Encs 5100 Firmware
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20228 — 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-2023-20228 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