CVE-2019-15511
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 · uneditedAn exploitable local privilege escalation vulnerability exists in the GalaxyClientService installed by GOG Galaxy. Due to Improper Access Control, an attacker can send unauthenticated local TCP packets to the service to gain SYSTEM privileges in Windows system where GOG Galaxy software is installed. All GOG Galaxy versions before 1.2.60 and all corresponding versions of GOG Galaxy 2.0 Beta are affected.
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 confidenceImproper access control in GalaxyClientService allows local attackers to send unauthenticated TCP packets and escalate to SYSTEM privileges. The service fails to validate the identity of local clients before granting elevated access.
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.2.60>= 2.0.0, <= 2.0.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify GalaxyClientService is presentOpen Services.msc and look for 'GalaxyClientService' or run 'sc query GalaxyClientService' in an elevated command promptAffected if The service is installed and running on the system
-
Locate GOG Galaxy installation directoryCheck common installation paths: C:\Program Files\GOG Galaxy\GalaxyClient.exe or C:\Program Files (x86)\GOG Galaxy\GalaxyClient.exe; you can also check in Programs and Features for 'GOG Galaxy'Affected if GOG Galaxy software is installed on the machine
-
Retrieve installed GOG Galaxy versionRight-click GalaxyClient.exe, select Properties, then view the Details tab for Product Version; alternatively, run 'wmic product where "name like 'GOG%' get name, version'Affected if The version displayed matches < 1.2.60 OR >= 2.0.0 through 2.0.8
-
Check service executable version directlyIf GalaxyClientService.exe exists in the GOG Galaxy install folder (e.g., C:\Program Files\GOG Galaxy\GalaxyClientService.exe), right-click it, go to Properties > Details to read the Product VersionAffected if The service executable version is < 1.2.60 or between 2.0.0 and 2.0.8 inclusive
A system is affected if the GalaxyClientService is running and the installed GOG Galaxy version is either below 1.2.60 or falls within the 2.0.0 to 2.0.8 range.
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 data1.2.60
Update GOG Galaxy to version 1.2.60 or later (or patched version for Galaxy 2.0 Beta) to remediate. If update is not feasible, disable the GalaxyClientService until patching is possible.
- 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-15511 — 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-15511 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