CVE-2023-2993
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 valid, authenticated user with limited privileges may be able to use specifically crafted web management server API calls to execute a limited number of commands on SMM v1, SMM v2, and FPC that the user does not normally have sufficient privileges to execute.
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 confidenceAuthenticated users with limited privileges can use specially crafted web management server API calls to execute commands on SMM v1, SMM v2, and FPC that exceed their assigned permission level, representing a privilege escalation vulnerability in the web management interface.
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< fhet60b-3.40< tesm38c-1.26< tesm38c-1.26< tesm38c-1.26< tesm38c-1.26< tesm38c-1.26< umsm10s-1.07< umsm10s-1.07CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 enclosure modelLocate the product model number on the physical chassis or check system inventory documentationAffected if The model is one of: Nextscale N1200, Thinkagile Cp Cb 10, Thinkagile Cp Cb 10e, Thinkagile Hx Enclosure, Thinkagile Vx Enclosure, Thinksystem D2, Thinksystem Da240, or Thinksystem Dw612
-
Check the installed firmware versionAccess the web management interface and navigate to Firmware/Software Inventory, or use the command line interface with 'ipmiutil' or vendor-specific tools to query the BMC for firmware versionAffected if The firmware version is lower than the affected threshold: fhet60b-3.40 for N1200, tesm38c-1.26 for Thinkagile/D2 models, or umsm10s-1.07 for Da240/Dw612
-
Verify SMM web management interface is enabledCheck the BMC/web management server status via the interface or CLI command such as 'ipmiutil sel' or the vendor's management toolAffected if The SMM (Server Management Module) web interface is accessible and running
-
Confirm user accounts with limited privileges existReview user accounts in the web management interface under User Management or Authentication settingsAffected if There are user accounts with limited or non-administrative privileges configured in the system
A user is affected if they have one of the listed enclosure models with firmware versions below the thresholds AND the SMM web management interface is accessible with user accounts configured.
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 · scopedApply vendor-provided patches or firmware updates for SMM v1, SMM v2, and FPC components to address the privilege escalation vector, and audit user API access permissions.
Firmware version fhet60b-3.40 (Nextscale N1200), tesm38c-1.26 (ThinkAgile Cp Cb 10/10e, ThinkAgile Hx, ThinkAgile Vx, ThinkSystem D2), or umsm10s-1.07 (ThinkSystem Da240, ThinkSystem DW612) depending on model
- 1. Identify the specific Lenovo enclosure or node model from the affected product list (Nextscale N1200, ThinkAgile Cp Cb 10, ThinkAgile Cp Cb 10e, ThinkAgile Hx, ThinkAgile Vx, ThinkSystem D2, ThinkSystem Da240, or ThinkSystem DW612)
- 2. Determine the current firmware version running on the affected enclosure or node via the web management interface or Lenovo XClarity Administrator
- 3. Download the appropriate firmware update from Lenovo support website (support.lenovo.com) based on your specific model
- 4. For ThinkSystem Da240 and DW612 enclosures: upgrade to firmware version umsm10s-1.07 or later
- 5. For ThinkAgile Cp Cb 10, Cp Cb 10e, Hx, Vx, and ThinkSystem D2 enclosures: upgrade to firmware version tesm38c-1.26 or later
- 6. For Nextscale N1200 enclosures: upgrade to firmware version fhet60b-3.40 or later
- 7. Apply the firmware update through the web management interface or Lenovo XClarity Provisioning Manager
- 8. Verify the firmware version has been successfully updated after reboot
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2993 — 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-2993 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