CVE-2023-34351
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 · uneditedBuffer underflow in some Intel(R) PCM software before version 202307 may allow an unauthenticated user to potentially enable denial of service 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 · high confidenceA buffer underflow vulnerability in Intel(R) PCM software versions prior to 202307 allows unauthenticated remote attackers to potentially cause a denial of service via network access due to insufficient bounds checking when processing input.
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< 202307CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 PCM is installedCheck for Intel Performance Counter Monitor software on the system. Look for the PCM.exe process running, or check installed programs list.Affected if Intel PCM software is found installed on the system
-
Determine installed versionLocate the Intel PCM installation directory and check version information in the executable or associated metadata files. Compare the version number to 202307.Affected if Installed version is prior to 202307 (version number less than 202307)
-
Assess network exposureDetermine if the Intel PCM service is configured to accept remote network connections. Check if the service is bound to network interfaces and listening on TCP/UDP ports.Affected if Intel PCM is listening on network ports and accessible from remote systems
The system is affected if Intel PCM software is installed with a version prior to 202307 and the service is exposed to network access.
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.
dbcve · scoped202307
Upgrade Intel(R) PCM software to version 202307 or later to remediate this vulnerability.
202307
- 1. Identify the current installed version of Intel Performance Counter Monitor by checking the executable version or using 'pcm --version'
- 2. Download Intel Performance Counter Monitor version 202307 or later from the official Intel download center or GitHub repository
- 3. Stop any running instances of the Intel PCM software
- 4. Uninstall the current version of Intel PCM using the standard uninstallation process for your operating system
- 5. Install the newly downloaded version 202307 or later
- 6. Verify the installation was successful by checking the version with 'pcm --version'
- 7. Restart any services or applications that depend on Intel PCM
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34351 — 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-34351 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