CVE-2024-6147
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 · uneditedPoly Plantronics Hub Link Following Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of Poly Plantronics Hub. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the Spokes Update Service. By creating a symbolic link, an attacker can abuse the service to delete a file. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-18271.
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 symbolic link following vulnerability in the Spokes Update Service of Poly Plantronics Hub allows a local attacker with low-privileged code execution to create a symlink that the service follows to delete arbitrary files, enabling escalation to SYSTEM context and arbitrary code execution.
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= 3.24.2CVSS 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.
-
Identify if Poly Plantronics Hub is installedCheck the installed programs list. On Windows, check in Control Panel > Programs and Features, or run: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Plantronics*'}. Also check for the service executable in the installation directory, typically under C:\Program Files\Plantronics or C:\Program Files\HP Poly\Poly Plantronics Hub.Affected if Poly Plantronics Hub is not found in the system, the vulnerability does not apply.
-
Determine the installed versionRight-click the Plantronics Hub application in Programs and Features to view version details, or locate the main executable (typically Spokes.exe or similar) in the installation folder and view its file properties. Compare against version 3.24.2.Affected if The installed version is exactly 3.24.2, indicating this specific affected version.
-
Verify the Spokes Update Service is present and runningOpen Services (services.msc) and look for a service related to Spokes Update or Plantronics Update. Also check via command line: Get-Service | Where-Object {$_.Name -like '*Spokes*' -or $_.DisplayName -like '*Spokes*'}. Note the service status.Affected if The Spokes Update Service is installed and running, which is required for the symlink following to occur.
-
Inspect service-accessible directories for suspicious symlinksExamine directories that the Spokes Update Service has write access to. Look for any .lnk or symbolic link files created in those locations that may point to sensitive files. Use: Get-ChildItem -Path 'C:\Program Files\Plantronics' -Recurse -ErrorAction SilentlyContinue | Where-Object {$_.LinkType -eq 'SymbolicLink'}.Affected if Unexpected symbolic links exist in service directories, indicating potential exploitation activity.
The environment is affected if Poly Plantronics Hub version 3.24.2 is installed AND the Spokes Update Service is running and accessible to create symlinks.
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 dataApply the vendor-provided patch for Poly Plantronics Hub when available; prior to patching, restrict user permissions to prevent creation of symbolic links in service-accessible directories and monitor for suspicious service behavior.
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6147 — 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-2024-6147 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