CVE-2025-21105
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 · uneditedDell RecoverPoint for Virtual Machines 6.0.X contains a command execution vulnerability. A Low privileged malicious user with local access could potentially exploit this vulnerability by running the specific binary and perform any administrative action permitted by it resulting in shutting down the server, modifying the configuration leading to gain access to unauthorized data.
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 confidenceDell RecoverPoint for Virtual Machines 6.0.X contains a command execution vulnerability where a low-privileged local user can exploit a specific binary to perform administrative actions, potentially shutting down the server, modifying configurations, and gaining unauthorized data access.
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= 6.0CVSS 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.
-
Confirm Dell RecoverPoint for Virtual Machines is installedLocate the installation directory or check system inventory for Dell RecoverPoint for Virtual Machines. Typical installation paths may be under /opt/dell/rpvm or C:\Program Files\Dell\RecoverPoint. Use 'ls' or directory search tools to find the product.Affected if The product is not installed on the system, the vulnerability does not apply.
-
Verify the installed version is exactly 6.0Check the product version by running 'rpvm --version' or inspecting version files in the installation directory (such as version.txt, build.info, or rpvm-installer.log). Compare the version against the affected range.Affected if The installed version is 6.0, the system falls within the affected range for this CVE.
-
Enumerate local user accounts and privilege levelsList all local users on the system using 'cat /etc/passwd' (Linux) or 'net user' (Windows). Identify which accounts have low or standard privileges versus administrative or root privileges.Affected if Low-privileged local user accounts exist on the system, enabling the attack vector described in the CVE.
-
Identify accessible administrative binariesLocate executables in the RecoverPoint installation directory and surrounding system paths. Use 'find' or file system search to identify binaries with elevated permissions. Inspect file permissions with 'ls -la' or icacls to determine which executables are executable by low-privileged users.Affected if A binary with administrative functionality is present and executable by low-privileged users, fulfilling the exploit condition.
-
Check for unauthorized configuration modificationsReview system configuration files in the RecoverPoint installation directory for unexpected changes. Check log files (such as /var/log/rpvm/* or installation logs) for signs of administrative actions performed by standard users.Affected if Configurations have been modified or administrative actions logged from a low-privilege account, indicating active exploitation.
The environment is affected if Dell RecoverPoint for Virtual Machines version 6.0 is installed AND low-privileged local users can access or execute an administrative binary within the product directory.
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 dataRestrict physical and console access to the system, enforce least-privilege principles for local accounts, and apply vendor patches when available. Investigate which binary is exploitable and remove or restrict its execution for low-privileged users.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-21105 — 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-2025-21105 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