CVE-2017-3767
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 local privilege escalation vulnerability was identified in the Realtek audio driver versions prior to 6.0.1.8224 in some Lenovo ThinkPad products. An attacker with local privileges could execute code with administrative privileges.
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 privilege escalation vulnerability exists in Realtek audio driver versions prior to 6.0.1.8224 on certain Lenovo ThinkPad products. An attacker who already has local user-level access can exploit this to execute arbitrary code with administrative or SYSTEM privileges.
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< 6.0.1.8224CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/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 Realtek audio driver on the systemOpen Device Manager, expand 'Sound, video and game controllers', locate the Realtek Audio device, right-click and select Properties, then check the Driver tab for the driver versionAffected if No Realtek audio driver is found - the system may use a different audio solution and is not affected by this specific CVE
-
Compare installed driver version to the vulnerable rangeNote the Driver Version shown in Device Manager (format typically like 6.0.1.xxxx). Compare this version number to 6.0.1.8224. If the installed version is lower (for example, 6.0.1.7000 or any version below 6.0.1.8224), the system is in the vulnerable rangeAffected if The installed version is a four-part number lower than 6.0.1.8224 (for example, 6.0.1.8000 would still be vulnerable, 6.0.1.8224 or higher is fixed)
-
Verify the system is a Lenovo ThinkPadRun 'wmic computersystem get manufacturer,model' from command prompt or check System Information (msinfo32) to confirm the system manufacturer is Lenovo and the model is a ThinkPad productAffected if The system is not a Lenovo ThinkPad - while other systems may use Realtek audio drivers, this specific CVE was identified in the context of Lenovo ThinkPad products
A user is affected if they are running a Lenovo ThinkPad with a Realtek Audio Driver version lower than 6.0.1.8224 installed.
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.
From vendor data6.0.1.8224
Update the Realtek audio driver to version 6.0.1.8224 or later on all affected ThinkPad systems. This is typically done through Lenovo's driver update utilities or by obtaining the updated driver directly from Lenovo's support website.
- 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-2017-3767 — 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-2017-3767 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