dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2023-42433

MEDIUM · 6.7 CVSS v3.1 Published 2024-05-16
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 in some Endurance Gaming Mode software installers before version 1.3.937.0 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 permissions set by Endurance Gaming Mode software installers prior to version 1.3.937.0. The installers apply overly permissive file or registry permissions that allow an authenticated local user to modify privileged resources and achieve elevation of privilege.

MitigationUpgrade Endurance Gaming Mode software to version 1.3.937.0 or later, which contains corrected installer permissions. For already-installed affected versions, review and remediate file/folder and registry permissions to ensure standard least-privilege access controls.

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. Verify Endurance Gaming Mode installation
    Search for Endurance Gaming Mode in installed programs via Control Panel Programs and Features, or query the registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Endurance Gaming Mode'
    Affected if The software is found installed on the system
  2. Determine installed version
    Locate the Endurance Gaming Mode entry in Programs and Features and note the version displayed, or query the uninstall registry key for the DisplayVersion value
    Affected if The displayed version is lower than 1.3.937.0 or the version cannot be determined (indicating a potentially affected build)
  3. Inspect file system permissions on program directory
    Right-click the Endurance Gaming Mode installation folder (typically in Program Files or Program Files x86), select Properties, go to the Security tab, and verify that non-admin users do not have Write or Full Control permissions to the folder and its contents
    Affected if Authenticated users or non-privileged accounts have Write, Modify, or Full Control permissions on the program directory
  4. Inspect registry permissions for Endurance Gaming Mode keys
    Open regedit, navigate to HKLM\SOFTWARE\Endurance Gaming Mode or the installation path identified in the registry, right-click the key, select Permissions, and verify that standard users lack Write or Full Control access to registry keys under this path
    Affected if Non-admin users have Write or Full Control permissions to Endurance Gaming Mode registry keys in HKLM

The environment is affected if Endurance Gaming Mode is installed with a version prior to 1.3.937.0 and overly permissive file or registry permissions exist for non-admin users on the software's directories or 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Endurance Gaming Mode software to version 1.3.937.0 or later, which contains corrected installer permissions. For already-installed affected versions, review and remediate file/folder and registry permissions to ensure standard least-privilege access controls.

Recommended fix Moderate confidence

Endurance Gaming Mode software version 1.3.937.0

  1. Navigate to the official Intel support website or download center
  2. Locate the Endurance Gaming Mode software
  3. Download version 1.3.937.0 or later
  4. Verify the downloaded file's integrity using checksums if provided
  5. Run the installer with appropriate administrator privileges
  6. Follow the installation prompts to complete the update
  7. Restart the system if required by the installer

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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