Incorrect Default PermissionsWeakness · CWE-276

CVE-2024-47550

MEDIUM · 6.7 CVSS v3.1 Published 2025-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated

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
Incorrect default permissions for some Endurance Gaming Mode software installers may allow an authenticated user to potentially enable escalation of privilege via local access.

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 confidence

This vulnerability involves incorrect default file system permissions on Endurance Gaming Mode software installers. An authenticated local user can exploit these overly permissive file or folder permissions to potentially modify installer files or associated executables, allowing them to escalate privileges by replacing legitimate binaries with malicious ones.

MitigationRemediate by reviewing and correcting file system permissions on the Endurance Gaming Mode installer directories and files to follow the principle of least privilege, ensuring only authorized SYSTEM/Admin accounts have write access to installer locations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/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 if Endurance Gaming Mode is installed
    Check the system for Endurance Gaming Mode software by looking in Program Files, Program Files (x86), or using registry keys under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
    Affected if The software is found installed on the system
  2. Locate Endurance Gaming Mode installation directory
    Find the primary installation path by examining the installer folder location, typically under C:\Program Files\Endurance or C:\Program Files (x86)\Endurance, or query the installation path from uninstall registry entries
    Affected if An installation directory exists for Endurance Gaming Mode software
  3. Verify file permissions on installer directories
    Right-click the installer directory, select Properties, go to the Security tab, and review the permissions. Alternatively, run 'icacls <installer_directory>' from an elevated command prompt to list all access control entries
    Affected if Users without administrator or SYSTEM privileges are granted Write or Full Control permissions to the installer directory or its contents
  4. Check for overly permissive executable files
    Run 'icacls <installer_directory>\*.exe' to review permissions on all executable files in the installer directory, or manually inspect each .exe file's permissions via the Security tab
    Affected if Standard users have Modify, Write, or Full Control permissions on any executable files within the installer directory
  5. Verify write access as a non-admin user
    Attempt to create or modify a test file in the installer directory using a standard (non-elevated) user account, or use Sysinternals Process Monitor to confirm write attempts are allowed
    Affected if A standard authenticated user can successfully write to the installer directory or modify existing installer executables

A user is affected if Endurance Gaming Mode is installed and non-privileged users have write access to installer directories or executable files, allowing potential binary replacement for privilege escalation.

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

Remediate by reviewing and correcting file system permissions on the Endurance Gaming Mode installer directories and files to follow the principle of least privilege, ensuring only authorized SYSTEM/Admin accounts have write access to installer locations.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47550 — 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-2024-47550 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