dbcve.org
Emc Data Protection AdvisorApplication · Dell

CVE-2018-11048

HIGH · 8.1 CVSS v3.1 Published 2018-08-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/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.2, 6,3, 6.4, 6.5 and Dell EMC Integrated Data Protection Appliance (IDPA) versions 2.0, 2.1 contain a XML External Entity (XXE) Injection vulnerability in the REST API. An authenticated remote malicious user could potentially exploit this vulnerability to read certain system files in the server or cause denial of service by supplying specially crafted Document Type Definitions (DTDs) in an XML request.

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 and IDPA contain an XML External Entity (XXE) Injection vulnerability in their REST API. An authenticated attacker can exploit this by submitting XML requests with specially crafted Document Type Definitions (DTDs) to read sensitive system files from the server or cause denial of service.

MitigationDisable XML external entity processing in the REST API's XML parser configuration and implement strict input validation on all XML requests. Apply vendor-provided patches for versions 6.2-6.5 and IDPA 2.0-2.1.

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.2= 6.3= 6.4= 6.5
Emc Integrated Data Protection ApplianceApplication
Affected:= 2.0= 2.1

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 product and version
    Check the installed version of Dell EMC Data Protection Advisor or Dell EMC Integrated Data Protection Appliance using the product's version information panel, about page, or system information command. Compare this version against the affected ranges: DPA versions 6.2, 6.3, 6.4, 6.5 and IDPA versions 2.0, 2.1.
    Affected if The installed version matches exactly 6.2, 6.3, 6.4, 6.5 for DPA or 2.0, 2.1 for IDPA.
  2. Confirm REST API is accessible
    Verify that the REST API service is running and accessible on the affected system. Check if the API endpoint is listening on its configured port (typically 443 or 8443 for HTTPS).
    Affected if The REST API service is running and network-accessible to potential attackers.
  3. Verify XML parsing is enabled for the REST API
    Inspect the REST API configuration files or settings to confirm that XML request processing is enabled. Look for XML parser settings in the API configuration.
    Affected if XML parsing is enabled and the API accepts XML-based requests.
  4. Check XML external entity processing configuration
    Review the XML parser configuration for the REST API to determine if external entity processing is enabled. Look for settings related to DTD processing, external entity resolution, or XXE handling.
    Affected if External entity processing is not explicitly disabled in the XML parser configuration, meaning the parser can process DTDs and resolve external entities.

You are affected if your environment runs DPA version 6.2-6.5 or IDPA version 2.0-2.1 with the REST API enabled and XML parsing that allows external entity processing.

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

Disable XML external entity processing in the REST API's XML parser configuration and implement strict input validation on all XML requests. Apply vendor-provided patches for versions 6.2-6.5 and IDPA 2.0-2.1.

Fix this in Emc Data Protection Advisor Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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