CVE-2023-43747
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 for some Intel(R) Connectivity Performance Suite software installers before version 2.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 confidenceIntel Connectivity Performance Suite installers before version 2.0 ship with incorrect default file system permissions, allowing authenticated local users to modify executable files or directories to achieve privilege escalation.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Intel Connectivity Performance Suite is installedSearch for the software in the system registry (Windows) or check common installation directories such as C:\Program Files\Intel\ or C:\Program Files (x86)\Intel\ for the Intel Connectivity Performance Suite folder, or use system inventory tools to list installed softwareAffected if The software is found installed on the system
-
Determine the installed versionLocate the version information in the installation directory, typically in an About or version file, or right-click the main executable and select Properties to view the File Version, or check Add/Remove Programs for the installed versionAffected if The installed version is any version prior to 2.0 (for example, 1.x or earlier versions)
-
Inspect executable file permissions in the installation directoryRight-click the main executable files and folders within the Intel Connectivity Performance Suite installation directory, select Properties, then Security, and verify which users or groups have Write or Modify permissionsAffected if Non-privileged authenticated users (such as standard user accounts) have Write or Modify permissions on executable files or directories within the installation folder
-
Check for world-writable executables or scriptsUse the icacls command (on Windows) or ls -la (on Linux) to list permissions on executables, DLLs, and configuration scripts in the installation directory, looking for entries that grant Write access to Users or Everyone groupsAffected if Executables or configuration files are writable by standard users or authenticated users without administrative privileges
The system is affected if Intel Connectivity Performance Suite version 1.x or earlier is installed AND non-admin users have write or modify access to executable files or directories in the installation location, creating a privilege escalation risk.
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 dataUpgrade Intel Connectivity Performance Suite to version 2.0 or later which corrects the default permission assignments in the installer.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43747 — 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-43747 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