GalaxyApplication · Gog

CVE-2018-4049

HIGH · 7.8 CVSS v3.1 Published 2019-04-02
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
An exploitable local privilege elevation vulnerability exists in the file system permissions of GOG Galaxy's “Games” directory, version 1.2.48.36 (Windows 64-bit Installer). An attacker can overwrite executables of installed games to exploit this vulnerability and execute arbitrary code with elevated privileges.

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

A local privilege elevation vulnerability exists in GOG Galaxy 1.2.48.36 where improper file system permissions on the 'Games' directory allow unprivileged users to overwrite game executables. An attacker with local access can replace legitimate game binaries with malicious code to execute with elevated privileges.

MitigationFix NTFS access control lists (ACLs) on the GOG Galaxy 'Games' directory to remove write permissions for non-admin users, ensuring only privileged accounts can modify or replace game executables.

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
GalaxyApplication
Affected:= 1.2.48.36

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. Identify installed GOG Galaxy version
    Check the Windows Registry at HKLM\SOFTWARE\WOW6432Node\GOG.com\Games or look in Programs and Features for 'GOG Galaxy' entry and note the installed version
    Affected if The installed version is exactly 1.2.48.36
  2. Locate the GOG Galaxy Games directory
    Check the default installation path, typically C:\Program Files (x86)\GOG Galaxy\Games or C:\GOG Galaxy\Games, and verify the directory exists
    Affected if The Games directory exists on the system
  3. Examine NTFS permissions on the Games directory
    Open Command Prompt as administrator and run 'icacls "C:\Program Files (x86)\GOG Galaxy\Games"' (or your actual Games path) to list all user permissions
    Affected if Any non-admin users or groups (such as Users, Everyone, or Authenticated Users) appear with (F) Full Control or (W) Write permissions in the output
  4. Verify write access for standard users
    As a non-administrator user (or using 'icacls' with /grant flag test), attempt to create or modify a file in the Games directory to confirm write capability exists for unprivileged accounts
    Affected if Non-admin users can successfully create or modify files in the Games directory
  5. Inspect permissions on game executables within the directory
    Run 'icacls "C:\Program Files (x86)\GOG Galaxy\Games\*"' to check ACLs on individual game executables
    Affected if Game executables are writable by non-privileged users (not just the SYSTEM or Administrators group)

A system is affected if GOG Galaxy version 1.2.48.36 is installed AND the Games directory grants write permissions to non-admin users, allowing them to replace game binaries with malicious code.

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

Fix NTFS access control lists (ACLs) on the GOG Galaxy 'Games' directory to remove write permissions for non-admin users, ensuring only privileged accounts can modify or replace game executables.

Fix this in Galaxy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-4049 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-4049 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