CVE-2023-2992
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 · uneditedAn unauthenticated denial of service vulnerability exists in the SMM v1, SMM v2, and FPC management web server which can be triggered under crafted conditions. Rebooting SMM or FPC will restore access to the management web server.
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 confidenceAn unauthenticated denial of service vulnerability affects the SMM v1, SMM v2, and FPC management web servers. By sending specially crafted requests under specific conditions, an attacker can cause the management web server to become unresponsive, requiring a reboot of the SMM or FPC module to restore access.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/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 the enclosure product modelAccess the system management interface or use IPMI/Redfish to query the enclosure or SMM module model information. Look for model identifiers such as N1200, Thinkagile Cp Cb 10, Thinkagile Hx, Thinkagile Vx, Thinksystem D2, Thinksystem Da240, or Thinksystem Dw612.Affected if The product model matches any of the following: Lenovo Nextscale N1200, Thinkagile Cp Cb 10/10e, Thinkagile Hx, Thinkagile Vx, Thinksystem D2, Thinksystem Da240, or Thinksystem Dw612 enclosures.
-
Check the SMM or FPC firmware versionUse the enclosure's web management interface, IPMI, or Redfish API to query the SMM (System Management Module) or FPC (Fabric Pass-Through Controller) firmware version. The version string typically appears in the firmware or module information section.Affected if The firmware version is lower than fhet60b-3.40 (for N1200), lower than tesm38c-1.26 (for Thinkagile Cp Cb 10/10e, Hx, Vx, and Thinksystem D2), or lower than umsm10s-1.07 (for Thinksystem Da240 and Dw612).
-
Verify the management web server is accessibleAttempt to access the SMM or FPC web management interface via HTTPS/HTTP on the management network. Check if the web interface responds to requests on the typical management ports (typically 443 or 8443 for HTTPS).Affected if The SMM v1, SMM v2, or FPC management web server is reachable over the network and responds to HTTP/HTTPS requests.
-
Confirm the web server type is SMM or FPCExamine the management interface banner, login page, or API responses to identify if the management web server is specifically an SMM v1, SMM v2, or FPC module web interface. This may be visible in the HTML title, favicon, or welcome message.Affected if The management web server is identified as an SMM v1, SMM v2, or FPC management interface.
You are affected if your enclosure matches one of the listed product models AND your firmware version is below the specified threshold AND the SMM or FPC management web server is accessible on your 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.
dbcve · scopedApply vendor-provided patches or firmware updates for SMM and FPC modules. If patches are unavailable, consider network segmentation to restrict access to management interfaces and implement rate limiting or firewall rules to mitigate malformed request attacks.
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)
- 1. Identify the specific Lenovo enclosure or node model from the affected product list
- 2. Navigate to Lenovo support portal (support.lenovo.com) and locate the firmware download page for your specific model
- 3. Download the appropriate fixed firmware version based on your model: For Nextscale N1200 use fhet60b-3.40 or later, for Thinkagile Cp Cb 10/10e, Thinkagile Hx, Thinkagile Vx, or Thinksystem D2 use tesm38c-1.26 or later, for Thinksystem Da240 or Dw612 use umsm10s-1.07 or later
- 4. Follow Lenovo's standard firmware update procedure for the enclosure/node (typically via BMC/IMM web interface or Lenovo XClarity Administrator)
- 5. After firmware update, verify the SMM or FPC management web server is accessible
- 6. If the web server becomes unresponsive post-update, reboot the SMM or FPC component to restore access as a fallback
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2023-2992 — 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-2992 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