CVE-2024-2659
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 command injection vulnerability was identified in SMM/SMM2 and FPC that could allow an authenticated user with elevated privileges to execute system commands when performing a specific administrative function.
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 command injection vulnerability in SMM/SMM2 (System Management Mode) and FPC allows authenticated users with elevated privileges to execute arbitrary system commands through a specific administrative function, potentially leading to complete system compromise.
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< FHET62A-3.50< TESM40B-1.27< TESM40B-1.27< tesm40b-1.27< tesm40b-1.27< tesm40b-1.27< tesm40b-1.27< tesm40b-1.27CVSS 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 Lenovo product modelLocate the system model label on the server chassis or check the system information in UEFI/BIOS setup (accessible during boot via F1). Look for model numbers: Nextscale N1200, Thinkagile Cp Cb 10, Thinkagile Cp Cb 10e, Thinkagile Hx, Thinkagile Hx3721, Thinkagile Hx1021, Thinkagile Hx E1, or Thinkagile Hx E2.Affected if The product model is any of the eight affected models listed.
-
Check the enclosure firmware versionAccess the BMC/IPMI or Lenovo XClarity Administrator interface for the system. Navigate to the firmware/inventory section and record the enclosure firmware version. Alternatively, run command 'ipmitool -I lanplus -H <BMC_IP> -U <admin> -P <pass> raw' or use Lenovo System Update to retrieve firmware version information.Affected if The firmware version returned matches the affected version ranges: for Nextscale N1200, version is below FHET62A-3.50; for Thinkagile models, version is below TESM40B-1.27 (or tesm40b-1.27).
-
Confirm the SMM/SMM2 firmware component versionWithin the BMC web interface or XClarity, navigate to the Firmware/Software inventory. Look for specific entries for System Management Mode (SMM) or SMM2 firmware. Record the version number displayed next to these components.Affected if The SMM or SMM2 component version is present and is lower than the fixed enclosure firmware version needed for the patch.
-
Verify if administrative interface is accessibleAttempt to log into the BMC web interface, IPMI, or XClarity with administrative credentials. Confirm that elevated/privileged administrative accounts exist and are reachable over the network.Affected if Administrative credentials are valid and the web interface or IPMI is reachable on the network, exposing the vulnerable function.
The environment is affected if the product model matches any of the eight affected Lenovo models and the enclosure firmware version is below FHET62A-3.50 (for Nextscale N1200) or below TESM40B-1.27 (for Thinkagile models), with administrative access available to reach the vulnerable function.
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 firmware patches for SMM/SMM2 and FPC components; restrict administrative access and validate input sanitization in affected administrative functions until patch is available.
FHET62A-3.50 for Nextscale N1200 Enclosure; TESM40B-1.27 for all Thinkagile models (Cp Cb 10, Cp Cb 10e, Hx Enclosure, Hx3721, Hx1021, Hx E1 Enclosure, Hx E2 Enclosure)
- Identify the specific Thinkagile or Nextscale model from the affected products list
- Navigate to Lenovo support portal (support.lenovo.com) and locate the firmware download page for your specific model
- Download the firmware version FHET62A-3.50 (for Nextscale N1200) or TESM40B-1.27 (for all Thinkagile models)
- Review the firmware update instructions provided by Lenovo
- Apply the firmware update following the documented procedure, ensuring stable power during the process
- Verify the firmware version has been successfully updated after the process completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2659 — 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-2024-2659 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