dbcve.org
LinkOperating system · Corsair

CVE-2018-19592

HIGH · 7.8 CVSS v3.1 Published 2019-09-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
The "CLink4Service" service is installed with Corsair Link 4.9.7.35 with insecure permissions by default. This allows unprivileged users to take control of the service and execute commands in the context of NT AUTHORITY\SYSTEM, leading to total system takeover, a similar issue to CVE-2018-12441.

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 confidence

The CLink4Service in Corsair Link 4.9.7.35 is installed with insecure default permissions that allow unprivileged users to modify the service configuration. Attackers can replace the service binary path to execute arbitrary code in the context of NT AUTHORITY\SYSTEM, achieving complete system compromise.

MitigationRestrict service permissions to administrators only by modifying ACLs on the service binary and registry keys, or upgrade to a patched version if available from Corsair.

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
LinkOperating system
Affected:= 4.9.7.35

CVSS 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.1/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if CLink4Service is installed
    Run 'sc query CLink4Service' in Command Prompt or 'Get-Service -Name CLink4Service' in PowerShell
    Affected if The service exists on the system, indicating Corsair Link software is present
  2. Confirm Corsair Link version is 4.9.7.35
    Check the program directory at 'C:\Program Files\Corsair Link\' for a version file, or query the registry under HKLM\SOFTWARE\Corsair\Link for the Version value
    Affected if The installed version is exactly 4.9.7.35
  3. Inspect CLink4Service permissions
    Run 'sc sdshow CLink4Service' to view the service's security descriptor, or use PowerShell with 'Get-Acl (Get-Item 'HKLM:\SYSTEM\CurrentControlSet\Services\CLink4Service')' to examine registry ACLs
    Affected if The SDDL shows that non-admin users (such as Everyone, Users, or Authenticated Users) have WRITE_DAC or WRITE_OWNER permissions, or the registry ACL permits modification by non-privileged accounts

A system is affected if Corsair Link version 4.9.7.35 is installed and unprivileged users can modify the CLink4Service configuration or its associated registry keys.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict service permissions to administrators only by modifying ACLs on the service binary and registry keys, or upgrade to a patched version if available from Corsair.

Fix this in Link Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-19592 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-19592 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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