CVE-2019-0113
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 · uneditedInsufficient bounds checking in Intel(R) Graphics Drivers before version 10.18.14.5067 (aka 15.36.x.5067) and 10.18.10.5069 (aka 15.33.x.5069) may allow an authenticated user to potentially enable a denial of service via local access.
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 confidenceInsufficient bounds checking in Intel(R) Graphics Drivers before versions 15.36.x.5067 and 15.33.x.5069 allows an authenticated local user to potentially cause a denial of service. The vulnerability stems from inadequate boundary checks in the graphics driver component that could lead to a system crash or instability when triggered locally.
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= 15.33.43.4425= 15.33.45.4653= 15.33.46.4885= 15.36.26.4294= 15.36.28.4332= 15.36.31.4414= 15.36.33.4578= 15.36.34.4889CVSS 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.0/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.
-
Locate installed Intel Graphics Driver versionOn Windows, open Device Manager, expand 'Display adapters', right-click the Intel graphics device, select 'Properties', then view the 'Driver' tab for the version. On Linux, run 'lspci | grep -i vga' or check the driver module version with 'modinfo i915' if applicable.Affected if The displayed driver version matches one of these: 15.33.43.4425, 15.33.45.4653, 15.33.46.4885, 15.36.26.4294, 15.36.28.4332, 15.36.31.4414, 15.36.33.4578, or 15.36.34.4889
-
Confirm graphics driver is loadedVerify the Intel graphics driver is active on the system. On Windows, ensure the display adapter appears in Device Manager without errors. On Linux, check that the i915 or i965 driver module is loaded via 'lsmod | grep i915' or similar.Affected if The Intel graphics driver component is installed and running, enabling the vulnerable code path to be exercised.
-
Check for local user accessDetermine whether untrusted or unauthenticated local users have access to log into the system interactively. Review user accounts and remote access policies.Affected if Local user accounts exist on the system, as the vulnerability requires an authenticated local user to trigger the insufficient bounds check.
You are affected if the Intel Graphics Driver version running on your system matches any of the eight listed versions and local users have interactive access to the machine.
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 dataUpdate Intel Graphics Drivers to version 10.18.14.5067 (15.36.x.5067) or 10.18.10.5069 (15.33.x.5069) or later to remediate this vulnerability. For systems where updating is not immediately feasible, consider restricting local access to trusted users only.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0113 — 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-0113 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