CVE-2021-3897
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 authentication bypass vulnerability was discovered in an internal service of the Lenovo Fan Power Controller2 (FPC2) and Lenovo System Management Module (SMM) firmware during an that could allow an unauthenticated attacker to execute commands on the SMM and FPC2. SMM2 is not affected.
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 authentication bypass vulnerability exists in the internal service of Lenovo Fan Power Controller2 (FPC2) and Lenovo System Management Module (SMM) firmware that allows unauthenticated attackers to execute arbitrary commands on affected components. SMM2 is explicitly not affected.
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< fhet50b-2.90< tesm28b-1.21< tesm28b-1.21< tesm28b-1.21< 44a-3.70CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 enclosure modelLocate the physical enclosure or check system inventory for one of: Lenovo Nextscale N1200, Lenovo Thinkagile Hx, Lenovo Thinkagile Vx, Lenovo Thinksystem D2, or IBM Nextscale. Use BMC/IPMI or system management interface to retrieve the enclosure name.Affected if The enclosure is any of these five models.
-
Determine the enclosure firmware versionAccess the BMC or management module web interface, or run IPMI command `ipmi-fru` or `ipmi-dcmi get asset info` to retrieve the current firmware version string.Affected if The firmware version string matches one of the affected patterns (e.g., fhet50b-2.90, tesm28b-1.21, 44a-3.70) but is lower than the fixed version.
-
Verify the controller typeCheck the management module or firmware inventory to identify whether the Fan Power Controller is FPC2 or the System Management Module is SMM (not SMM2). This may be visible in the firmware version string or component listing.Affected if The system uses FPC2 or SMM (SMM2 is explicitly not affected per the CVE).
-
Compare version against affected rangesMatch your installed firmware version to these thresholds: Lenovo Nextscale N1200 < fhet50b-2.90, Thinkagile Hx/Vx and Thinksystem D2 < tesm28b-1.21, IBM Nextscale FPC < 44a-3.70. Use string comparison on the numeric portions.Affected if Your installed version is lower than the specified threshold for your model.
You are affected if your enclosure model is in the affected list, the controller is FPC2 or SMM (not SMM2), and the installed firmware version is below the threshold for your specific model.
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 · scoped44a-3.70
Apply Lenovo firmware updates for FPC2 and SMM when released, as this is a firmware-level vulnerability requiring vendor patches; network segmentation may help limit exposure until updates are available.
fhet50b-2.90 (Nextscale N1200), tesm28b-1.21 (Thinkagile Hx/Vx, Thinksystem D2), 44a-3.70 (Nextscale Fan Power Controller)
- 1. Identify the specific Lenovo enclosure or fan power controller model from the affected product list
- 2. Determine the current firmware version currently installed on the device
- 3. Navigate to Lenovo support portal (support.lenovo.com) and search for the firmware update using the product model number
- 4. Download the fixed firmware version: fhet50b-2.90 for Nextscale N1200, tesm28b-1.21 for Thinkagile Hx/Vx and Thinksystem D2, or 44a-3.70 for Nextscale Fan Power Controller
- 5. Review Lenovo firmware update instructions for your specific hardware
- 6. Apply the firmware update following Lenovo's standard update procedure, ensuring stable power during the process
- 7. After update completes, verify the firmware version matches the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-3897 — 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-3897 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