CVE-2018-19523
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 · uneditedDriverAgent 2.2015.7.14, which includes DrvAgent64.sys 1.0.0.1, allows a user to send an IOCTL (0x80002068) with a user defined buffer size. If the size of the buffer is less than 512 bytes, then the driver will overwrite the next pool header if there is one next to the user buffer's pool.
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 confidenceThis is a pool-based buffer overflow vulnerability in the DrvAgent64.sys kernel driver. The driver fails to validate buffer sizes in IOCTL 0x80002068, allowing a user-supplied buffer under 512 bytes to overwrite adjacent kernel pool headers. This could cause denial of service or potentially enable privilege escalation.
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= 2.2015.7.14CVSS 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
- High
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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 the DrvAgent64.sys driver fileSearch for the driver file in system directories: typical paths include C:\Windows\System32\drivers\ or C:\Program Files\Driveagent\. Use PowerShell command: Get-ChildItem -Path C:\ -Recurse -Filter DrvAgent64.sys -ErrorAction SilentlyContinueAffected if The driver file DrvAgent64.sys is present on the system
-
Verify driver file versionRight-click the driver file, select Properties, then Details tab to view File Version. Alternatively, use PowerShell: (Get-Item "C:\Windows\System32\drivers\DrvAgent64.sys").VersionInfo.FileVersionAffected if File version equals exactly 2.2015.7.14
-
Confirm the driver is loaded or loadableCheck if the driver is currently loaded in memory: Run "sc query DrvAgent" or check Device Manager for hidden/non-plug-and-play devices. Also verify the driver service exists: Get-Service -Name DrvAgent*Affected if The driver service exists and the driver can be loaded or is currently loaded
The system is affected if DrvAgent64.sys driver is present with exact version 2.2015.7.14 and is accessible to unprivileged users.
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 dataRemove the vulnerable driver if unnecessary, or apply any vendor-supplied update. If the driver is required, restrict access through proper device ACLs and monitor for exploitation attempts.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19523 — 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-2018-19523 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