CVE-2021-3721
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 denial of service vulnerability was reported in Lenovo PCManager prior to version 4.0.20.10282 that could allow an attacker with local access to trigger a blue screen error.
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 · high confidenceA local denial of service vulnerability in Lenovo PCManager prior to version 4.0.20.10282 allows an attacker with local access to trigger a blue screen error (BSOD), causing system crash and DoS condition.
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< 4.0.10282CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Verify Lenovo PCManager is installedOpen Control Panel > Programs and Features, or use PowerShell command: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Lenovo*PCManager*'}Affected if Lenovo PCManager does not appear in the installed programs list
-
Locate the Lenovo PCManager executableCommon installation paths include C:\Program Files\Lenovo\PCManager\ or C:\Program Files (x86)\Lenovo\PCManager\. Navigate to these folders and locate ImController.exe or similar Lenovo PCManager executable.Affected if The executable exists in the expected installation directory
-
Determine the installed versionRight-click the PCManager executable (e.g., ImController.exe) and select Properties, then view the Details tab for the Product Version. Alternatively, run: (Get-Item 'C:\Program Files\Lenovo\PCManager\ImController.exe').VersionInfo.ProductVersionAffected if The version shown is lower than 4.0.10282 or the Product Version field is empty or unreadable
-
Confirm the vulnerability conditionCompare the identified version against the affected range: any version prior to 4.0.10282 is vulnerable. Document the exact version number found for reference.Affected if The installed version is less than 4.0.10282 (for example, 4.0.10270, 4.0.10100, or any earlier release)
A user is affected if Lenovo PCManager is installed with a version number lower than 4.0.10282, as this is the specific version threshold identified in the CVE.
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 · scoped4.0.10282
Update Lenovo PCManager to version 4.0.20.10282 or later to remediate the vulnerability.
Lenovo PCManager 4.0.20.10282 or later
- Open Lenovo Vantage or visit the official Lenovo support website
- Navigate to the PCManager or driver/software section
- Download Lenovo PCManager version 4.0.20.10282 or later
- Run the installer and follow the prompts to update PCManager
- Restart the system if prompted after installation
- Verify the installed version matches or exceeds 4.0.20.10282
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-3721 — 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-3721 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