dbcve.org
Emc Data Protection AdvisorApplication · Dell

CVE-2019-18582

HIGH · 7.2 CVSS v3.1 Published 2020-03-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 EMC Data Protection Advisor versions 6.3, 6.4, 6.5, 18.2 versions prior to patch 83, and 19.1 versions prior to patch 71 contain a server-side template injection vulnerability in the REST API. A remote authenticated malicious user with administrative privileges may potentially exploit this vulnerability to inject malicious report generation scripts in the server. This may lead to OS command execution as the regular user runs the DPA service on the affected system.

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 EMC Data Protection Advisor contains a server-side template injection (SSTI) vulnerability in its REST API. An authenticated attacker with administrative privileges can inject malicious report generation scripts that execute OS commands as the user running the DPA service, due to unsafe handling of user-supplied input in server-side templates.

MitigationApply vendor patches: upgrade to DPA 18.2 patch 83 or 19.1 patch 71 or later. For older versions (6.3-6.5), upgrade to a supported version with corresponding patches. Restrict administrative access to trusted personnel as an interim compensating control.

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
Emc Data Protection AdvisorApplication
Affected:= 6.3= 6.4= 6.5= 18.1= 18.2= 19.1
Emc Integrated Data Protection Appliance FirmwareOperating system
Affected:= 2.0= 2.1= 2.2= 2.3= 2.4

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

CVSS:3.1/AV:N/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 DPA installation and version
    Locate the Dell EMC Data Protection Advisor installation directory and check the version information file or use the DPA version command in the management interface
    Affected if The installed version matches 6.3, 6.4, 6.5, 18.1, 18.2, or 19.1 (or the firmware version matches 2.0-2.4 for Integrated Data Protection Appliance)
  2. Verify REST API service status
    Check if the DPA REST API service is running and accessible on the server. Look for the REST API endpoint (typically port 8443 or configured port) responding to requests
    Affected if The REST API service is exposed and reachable on the network
  3. Review administrative user accounts
    Query the DPA user management console or database to list accounts with administrative privileges. Focus on identifying any unauthorized or unexpected admin accounts
    Affected if There are administrative accounts present in the system (the vulnerability requires admin-level access)
  4. Audit REST API access logs
    Examine DPA REST API access logs for suspicious report generation requests, especially those containing template syntax characters like ${, <% , or unusual script patterns
    Affected if Logs show report generation requests with unexpected template injection patterns or commands that could indicate exploitation attempts

You are affected if Dell EMC Data Protection Advisor version 6.3-6.5, 18.1, 18.2, or 19.1 (or Integrated Data Protection Appliance firmware 2.0-2.4) is installed, the REST API is enabled, and administrative access exists, especially if logs reveal suspicious template injection patterns.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches: upgrade to DPA 18.2 patch 83 or 19.1 patch 71 or later. For older versions (6.3-6.5), upgrade to a supported version with corresponding patches. Restrict administrative access to trusted personnel as an interim compensating control.

Fix this in Emc Data Protection Advisor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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