dbcve.org
Peripheral ManagerApplication · Dell

CVE-2024-22447

HIGH · 7.8 CVSS v3.1 Published 2026-06-16
Fix available
A fix is available. Upgrade to 1.7.3 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
Dell Peripheral Manager, versions prior to 1.7.3, contain an uncontrolled search path element vulnerability. An attacker could potentially exploit this vulnerability through preloading malicious dll., leading to arbitrary code execution.

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 confidence

Dell Peripheral Manager versions prior to 1.7.3 contain an uncontrolled search path element vulnerability allowing DLL preloading. An attacker with write access to directories in the application's DLL search path can place a malicious DLL that the application will load, resulting in arbitrary code execution with the privileges of the running user.

MitigationUpgrade to Dell Peripheral Manager version 1.7.3 or later. As a temporary compensating control, ensure unprivileged users cannot write to directories in the application's search path and remove untrusted directories from the system PATH.

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
Peripheral ManagerApplication
Affected:< 1.7.3

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

CVSS:3.1/AV:L/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Dell Peripheral Manager installation
    Search for 'Dell Peripheral Manager' in Program Files (e.g., C:\Program Files\Dell\Dell Peripheral Manager) or check Start Menu for the application shortcut, then right-click and open file location.
    Affected if The application is not found in expected installation directories.
  2. Identify the installed version
    Right-click the Dell Peripheral Manager executable (commonly named DellPeripheralManager.exe or similar), select Properties, and check the Details tab for the Product Version.
    Affected if The version shown is blank, unreadable, or the executable does not exist.
  3. Compare version to the affected range
    If the version is readable, compare it to 1.7.3. Versions prior to 1.7.3 (such as 1.7.2, 1.7.1, 1.6.x, 1.5.x, etc.) are considered vulnerable.
    Affected if The installed version is less than 1.7.3.
  4. Verify via Windows Registry (alternative method)
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\, look for a Dell Peripheral Manager entry and check the DisplayVersion value.
    Affected if Registry shows a version less than 1.7.3.

The environment is affected if Dell Peripheral Manager is installed and its version is lower than 1.7.3.

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 1.7.3 or later
Fixed in 1.7.3
Interim mitigation

Upgrade to Dell Peripheral Manager version 1.7.3 or later. As a temporary compensating control, ensure unprivileged users cannot write to directories in the application's search path and remove untrusted directories from the system PATH.

Recommended fix High confidence

1.7.3

  1. Open Dell Peripheral Manager on the system
  2. Navigate to Help > About to check the currently installed version
  3. If version is below 1.7.3, close the application
  4. Visit www.dell.com and navigate to the Dell Peripheral Manager support/download page
  5. Download Dell Peripheral Manager version 1.7.3 or later
  6. Uninstall the current version of Dell Peripheral Manager from the system via Windows Control Panel > Programs and Features
  7. Run the installer for version 1.7.3 and follow the installation prompts
  8. Restart the system if prompted by the installer

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

Fix this in Peripheral Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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