CVE-2019-13142
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 · uneditedThe RzSurroundVADStreamingService (RzSurroundVADStreamingService.exe) in Razer Surround 1.1.63.0 runs as the SYSTEM user using an executable located in %PROGRAMDATA%\Razer\Synapse\Devices\Razer Surround\Driver\. The DACL on this folder allows any user to overwrite contents of files in this folder, resulting in Elevation of Privilege.
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 RzSurroundVADStreamingService in Razer Surround 1.1.63.0 runs as SYSTEM with its executable located in %PROGRAMDATA%\Razer\Synapse\Devices\Razer Surround\Driver\. The folder's DACL incorrectly grants any user write permissions, allowing privilege escalation by replacing the executable with malicious code that executes with 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= 1.1.63.0CVSS 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.
-
Check if Razer Surround is installedLook for the folder %PROGRAMDATA%\Razer\Synapse\Devices\Razer Surround\Driver\ or check Programs and Features for Razer SurroundAffected if The folder or program exists on the system
-
Verify the installed versionCheck the version of Razer Surround in Programs and Features or look for version information in the driver folderAffected if The installed version is exactly 1.1.63.0
-
Check if RzSurroundVADStreamingService existsRun 'sc query RzSurroundVADStreamingService' in Command Prompt or check Services.msc for the serviceAffected if The service is installed on the system
-
Inspect folder permissions on the driver directoryRight-click the folder %PROGRAMDATA%\Razer\Synapse\Devices\Razer Surround\Driver\, go to Properties > Security, and verify which users have Write or Full Control permissionsAffected if Non-admin users or the 'Users' group have Write or Modify permissions to the folder
-
Confirm service runs as SYSTEMRun 'sc qc RzSurroundVADStreamingService' and check the BINARY_PATH_NAME, or check the service's Log On account in Services.mscAffected if The service is configured to run under the LocalSystem (SYSTEM) account
A user is affected if Razer Surround 1.1.63.0 is installed, the RzSurroundVADStreamingService exists and runs as SYSTEM, and the driver folder grants write permissions to non-administrative 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 dataRestrict folder permissions on the Razer Surround Driver folder to prevent non-administrative users from modifying or replacing files; verify the service runs from a secured location.
- 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-2019-13142 — 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-13142 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