CVE-2023-40154
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 · uneditedIncorrect default permissions in the Intel(R) SUR for Gameplay Software before version 2.0.1901 may allow privillaged 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 confidenceIntel SUR (Software Usage and Reporting) for Gameplay Software has incorrect default permissions that allow a privileged user to potentially escalate privileges via local access. The vulnerability stems from improper permission configuration in the affected software versions before 2.0.1901, enabling a local attacker with existing elevated privileges to gain additional unauthorized 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< 2.0.1901CVSS 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 Intel SUR installationCheck if Intel Software Usage and Reporting (SUR) for Gameplay Software is installed on the system by reviewing installed programs in Programs and Features or using system inventory toolsAffected if Intel SUR for Gameplay Software is present on the system
-
Determine installed versionLocate the installed version of Intel SUR for Gameplay Software - typically found in the software's About/Properties section, installation directory, or system registryAffected if Version number cannot be determined or is below 2.0.1901
-
Compare version to affected rangeCompare the identified version against the affected range: versions before 2.0.1901 are vulnerableAffected if Installed version is lower than 2.0.1901 (e.g., 2.0.1800, 2.0.1702, etc.)
-
Assess local privilege contextDetermine if the system has local users with elevated privileges who could exploit the permission misconfigurationAffected if Local users with elevated (administrator) access exist on the affected system
The environment is affected if Intel SUR for Gameplay Software is installed with a version lower than 2.0.1901 and the system allows local elevated users who could potentially exploit the incorrect default permissions.
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 data2.0.1901
Update Intel SUR for Gameplay Software to version 2.0.1901 or later to remediate the incorrect default permissions. Alternatively, review and restrict file/folder permissions on the affected system according to Intel's guidance.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-40154 — 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-2023-40154 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