dbcve.org
Repository ManagerApplication · Dell

CVE-2025-45376

HIGH · 7.8 CVSS v3.1 Published 2025-09-29
Fix available
A fix is available. Upgrade to 3.4.9 or later.
See remediation →
80/100
Remediation priority · High
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
Dell Repository Manager (DRM), versions 3.4.7 and 3.4.8, contains an Improper Handling of Insufficient Permissions or Privileges vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Elevation of privileges.

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

Dell Repository Manager versions 3.4.7 and 3.4.8 contain an improper handling of insufficient permissions vulnerability that allows a low-privileged local attacker to elevate privileges. The vulnerability stems from inadequate permission checks that can be bypassed to gain elevated access. This is a local privilege escalation flaw requiring physical or console access to the system.

MitigationApply vendor-supplied patches for DRM versions 3.4.7 and 3.4.8 when available, and restrict local access to trusted administrative users only.

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
Repository ManagerApplication
Affected:>= 3.4.7, < 3.4.9

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
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 checks

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

  1. Identify Dell Repository Manager installation and version
    Check installed programs or running services for Dell Repository Manager. On Windows, use Programs and Features or 'Get-ItemProperty' registry queries under HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall. On Linux, check for RPM/DEB packages with 'rpm -qa' or 'dpkg -l' looking for 'dell-repository-manager' or similar package names.
    Affected if The software version is 3.4.7 or 3.4.8.
  2. Confirm exact installed version number
    Run the application with version flag (typically --version or -v) or check the About section in the application UI if accessible. Compare the displayed version against the affected range.
    Affected if Version displayed is 3.4.7 or 3.4.8.
  3. Verify service accessibility for local users
    Check if the Dell Repository Manager service or application is accessible to unprivileged user accounts on the system. Review file permissions on the installation directory and service configuration to determine if standard users can interact with the application.
    Affected if Unprivileged local users can execute or interact with the Dell Repository Manager service or executable.

You are affected if Dell Repository Manager version 3.4.7 or 3.4.8 is installed and unprivileged local users can access the application, enabling potential privilege escalation.

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

Apply vendor-supplied patches for DRM versions 3.4.7 and 3.4.8 when available, and restrict local access to trusted administrative users only.

Recommended fix Moderate confidence

Dell Repository Manager 3.4.9

  1. Identify the currently installed version of Dell Repository Manager
  2. Download Dell Repository Manager version 3.4.9 from the official Dell support website (www.dell.com)
  3. Backup the existing DRM configuration and data according to Dell backup procedures
  4. Install or upgrade to Dell Repository Manager version 3.4.9 using the Dell-provided installation package
  5. Verify the installation completed successfully and the version is reported as 3.4.9
  6. Test that DRM functionality operates normally after the upgrade

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

Fix this in Repository Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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