Recoverpoint For Virtual MachinesApplication · Dell

CVE-2016-6649

MEDIUM · 6.7 CVSS v3.0 Published 2017-02-03
Fix available
A fix is available. Upgrade to after 4.4.1.0 or later.
See remediation →
69/100
Remediation priority · Elevated
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
EMC RecoverPoint versions before 4.4.1.1 and EMC RecoverPoint for Virtual Machines versions before 5.0 are affected by multiple command injection vulnerabilities where a malicious administrator with configuration privileges may bypass the user interface and escalate his privileges to root.

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

EMC RecoverPoint and RecoverPoint for Virtual Machines contain command injection vulnerabilities allowing a privileged administrator to bypass the user interface and execute commands as root, achieving privilege escalation beyond their assigned role.

MitigationUpgrade EMC RecoverPoint to version 4.4.1.1 or later, and EMC RecoverPoint for Virtual Machines to version 5.0 or later to address the command injection vulnerability.

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
Recoverpoint For Virtual MachinesApplication
Affected:<= 4.0
RecoverpointApplication
Affected:<= 4.4.1.0

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

CVSS:3.0/AV:L/AC:L/PR:H/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 the installed RecoverPoint version
    Access the RecoverPoint admin interface or use the system CLI to retrieve the version information. Common methods include checking the 'About' page in the web UI or running 'rpccli -version' or similar version commands available in the product documentation.
    Affected if The installed version is Dell RecoverPoint for Virtual Machines 4.0 or earlier, or EMC RecoverPoint 4.4.1.0 or earlier.
  2. Confirm the product type
    Determine whether the installation is EMC RecoverPoint (hardware/standalone) or RecoverPoint for Virtual Machines (RP4VM). This is typically visible in the product name displayed in the admin interface or system information.
    Affected if The product is either EMC RecoverPoint version 4.4.1.0 or below, or RecoverPoint for Virtual Machines version 4.0 or below.
  3. Verify administrative access is enabled
    Confirm that the RecoverPoint administrative web interface or CLI is accessible and operational. Check if privileged administrator accounts exist in the system.
    Affected if The admin interface is accessible and privileged administrator accounts are configured, as this is the attack surface for the command injection.
  4. Check for unexpected administrative actions
    Review admin audit logs, command history, or system logs for any suspicious commands executed through the interface that originate from administrators performing actions outside their intended role scope.

You are affected if your installed RecoverPoint version is 4.4.1.0 or earlier for EMC RecoverPoint, or 4.0 or earlier for RecoverPoint for Virtual Machines, AND the administrative interface is accessible with privileged administrator accounts configured.

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.

From vendor data
Upgrade available Upgrade to a release after 4.4.1.0
Interim mitigation

Upgrade EMC RecoverPoint to version 4.4.1.1 or later, and EMC RecoverPoint for Virtual Machines to version 5.0 or later to address the command injection vulnerability.

Fix this in Recoverpoint For Virtual Machines Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-6649 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-6649 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