dbcve.org
Connectivity Performance SuiteApplication · Intel

CVE-2023-32279

HIGH · 7.5 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to 2.1123.214.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Improper access control in user mode driver for some Intel(R) Connectivity Performance Suite before version 2.1123.214.2 may allow unauthenticated user to potentially enable information disclosure via network 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

Improper access control vulnerability in the user-mode driver of Intel Connectivity Performance Suite allows unauthenticated network users to potentially access sensitive information due to missing or insufficient access control checks in the driver code.

MitigationApply the vendor patch by updating Intel Connectivity Performance Suite to version 2.1123.214.2 or later, and verify that network access controls are functioning properly after the update.

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
Connectivity Performance SuiteApplication
Affected:< 2.1123.214.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Confirm Intel Connectivity Performance Suite is installed
    Open Programs and Features (Windows) or check installed packages (Linux) for Intel Connectivity Performance Suite. If using Windows, check Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Intel Connectivity Performance Suite' or 'ICPS'.
    Affected if The software is not found in the system, the user is not affected.
  2. Identify the installed version
    Locate the version information in the software installation directory, typically in an About or version file, or run 'icps --version' from command line if the software provides a CLI. On Windows, right-click the installed executable and select Properties > Details to view FileVersion.
    Affected if No version information can be retrieved, further investigation may be needed.
  3. Compare version against the affected range
    Compare the installed version number to 2.1123.214.2 using semantic version comparison. The system is affected if the installed version is lower than 2.1123.214.2 (for example, 2.1123.214.1, 2.1123.200.0, 1.x.x, etc.).
    Affected if The installed version is less than 2.1123.214.2, the environment is vulnerable.
  4. Verify the user-mode driver component exists
    Check for the presence of the Intel Connectivity Performance Suite driver files in the installation directory, typically named with 'driver', 'icps', or 'conn' in the filename. On Windows, also check Device Manager for Intel network driver components under Network adapters.
    Affected if The driver component is present and the version is below 2.1123.214.2, exploitation is possible.

The environment is affected only if Intel Connectivity Performance Suite is installed with a version lower than 2.1123.214.2 and the user-mode driver component is present and enabled.

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
Upgrade available Upgrade to 2.1123.214.2 or later
Fixed in 2.1123.214.2
Interim mitigation

Apply the vendor patch by updating Intel Connectivity Performance Suite to version 2.1123.214.2 or later, and verify that network access controls are functioning properly after the update.

Recommended fix High confidence

Intel Connectivity Performance Suite version 2.1123.214.2 or later

  1. 1. Identify the currently installed version of Intel(R) Connectivity Performance Suite on the affected system
  2. 2. Download the latest version of Intel Connectivity Performance Suite (version 2.1123.214.2 or later) from the official Intel support website
  3. 3. Close any applications that may be using the Connectivity Performance Suite
  4. 4. Run the installer with appropriate administrative privileges
  5. 5. Follow the on-screen installation prompts to complete the upgrade
  6. 6. Restart the system if prompted by the installer
  7. 7. Verify the installed version matches or exceeds 2.1123.214.2

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

Fix this in Connectivity Performance Suite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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