CVE-2019-19705
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 · uneditedRealtek Audio Drivers for Windows, as used on the Lenovo ThinkPad X1 Carbon 20A7, 20A8, 20BS, and 20BT before 6.0.8882.1 and 20KH and 20KG before 6.0.8907.1 (and on many other Lenovo and non-Lenovo products), mishandles DLL preloading.
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 confidenceThe Realtek Audio Driver for Windows suffers from a DLL preloading vulnerability where the driver loads DLL files without using fully qualified paths, allowing an attacker to place a malicious DLL in a location where the driver will load it instead of the legitimate library. This enables local privilege escalation to SYSTEM context.
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.8923.1< 6.0.8923.1< 6.0.8924.1< 6.0.8924.1< 6.0.8924.1< 6.0.8924.1< 6.0.8924.1< 6.0.8924.1CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 system modelOpen System Properties (Win+Pause) or run 'msinfo32' to check the computer model name. Confirm it is one of: Ideacentre 510 15ikl, Ideacentre 510s 08ikl, Ideacentre 300s 11ish, Ideacentre 310 15asr, Ideacentre 310 15iap, Ideacentre 310a 15iap, Ideacentre 310s 08iap, or Ideacentre 510 15abr.Affected if The system model matches one of the listed affected Ideacentre models.
-
Check the Realtek audio driver versionOpen Device Manager, expand 'Sound, video and game controllers', right-click on the Realtek Audio device, select Properties, go to the Driver tab, and note the Driver Version. Alternatively, run 'driverquery /v | findstr -i realtek' from an elevated command prompt.Affected if A Realtek audio driver is installed on the system.
-
Compare version against affected thresholdsIf the model is Ideacentre 510 15ikl or 510s 08ikl, compare the driver version to 6.0.8923.1. For all other listed models, compare to 6.0.8924.1. Use numeric comparison treating the version as x.x.xxxx.x.Affected if The installed driver version is lower than 6.0.8923.1 (for 510 15ikl/510s 08ikl) or lower than 6.0.8924.1 (for other models).
-
Verify the vulnerable DLL loading behaviorObserve that the driver loads without using fully qualified paths for its DLL dependencies. This is inherent to the vulnerable version and does not require a specific config check; the vulnerability exists when the driver version is below the threshold.Affected if The driver version is below the threshold, meaning the driver uses unsafe DLL loading.
A user is affected if they are running one of the listed Ideacentre models with a Realtek audio driver version below 6.0.8923.1 or 6.0.8924.1 depending on the 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 · scoped6.0.8923.16.0.8924.1
Apply the vendor-supplied driver updates (6.0.8882.1 or later for ThinkPad X1 Carbon models 20A7/20A8/20BS/20BT, and 6.0.8907.1 or later for 20KH/20KG) to replace the vulnerable driver with a patched version that implements secure DLL loading using full paths.
Firmware 6.0.8923.1 (for 510 15ikl, 510s 08ikl) or 6.0.8924.1 (for all other listed models)
- Identify the exact Ideacentre model number from the affected list (510 15ikl, 510s 08ikl, 300s 11ish, 310 15asr, 310 15iap, 310a 15iap, 310s 08iap, or 510 15abr)
- Navigate to Lenovo Support (support.lenovo.com) and enter the product model number to find driver/firmware downloads
- Locate the Realtek Audio Driver firmware update for the specific Ideacentre model
- For Ideacentre 510 15ikl and 510s 08ikl: download and install firmware version 6.0.8923.1 or later
- For all other affected models (300s 11ish, 310 series, 510 15abr): download and install firmware version 6.0.8924.1 or later
- Restart the system after applying the firmware update to ensure the new audio driver loads correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19705 — 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-2019-19705 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