dbcve.org
One FirmwareOperating system · Veeam

CVE-2020-15418

HIGH · 7.5 CVSS v3.1 Published 2020-07-28
Fix available
A fix is available. Upgrade to 9.5.4.4587 / 10.0.0.750 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
This vulnerability allows remote attackers to disclose sensitive information on affected installations of Veeam ONE 10.0.0.750_20200415. Authentication is not required to exploit this vulnerability. The specific flaw exists within the SSRSReport class. Due to the improper restriction of XML External Entity (XXE) references, a specially crafted document specifying a URI causes the XML parser to access the URI and embed the contents back into the XML document for further processing. An attacker can leverage this vulnerability to disclose file contents in the context of SYSTEM. Was ZDI-CAN-10709.

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

This is an XML External Entity (XXE) injection vulnerability in Veeam ONE 10.0.0.750_20200415 affecting the SSRSReport class. The XML parser does not properly restrict external entity references, allowing unauthenticated remote attackers to craft malicious XML documents that can access internal URIs and embed sensitive file contents back into the XML for exfiltration. The attack requires no authentication and executes in SYSTEM context.

MitigationDisable external entity processing in the XML parser used by the SSRSReport class, implement strict input validation on XML documents, and apply the vendor patch when available. Consider restricting outbound network access as a defense-in-depth measure.

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
One FirmwareOperating system
Affected:< 9.5.4.4587>= 10.0.0.0, < 10.0.0.750

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Confirm Veeam ONE is installed
    Check the installed programs list on the system, or look for Veeam ONE installation directories (typically in C:\Program Files\Veeam\ or C:\Program Files (x86)\Veeam\)
    Affected if Veeam ONE software is present on the system
  2. Identify the installed Veeam ONE version
    Locate the version information in the Veeam ONE installation: check the file version of Veeam.One.Common.dll or the Veeam ONE version displayed in Add/Remove Programs, or run 'veeamversion' if the command-line tool is available
    Affected if The installed version falls within < 9.5.4.4587 OR >= 10.0.0.0 and < 10.0.0.750
  3. Determine if the SSRS Report service is enabled
    Check if SQL Server Reporting Services (SSRS) is configured and the Veeam ONE reporting component is active. Look for the SSRSReport endpoint or web service in the Veeam ONE installation directory under the Reporting or Web subfolders
    Affected if SSRSReport functionality is accessible and the XML parser processes incoming documents
  4. Check XML parser configuration for external entity processing
    Inspect the configuration files in the Veeam ONE installation directory (look for .config files in the Reporting or bin folders) for XML parser settings. Search for settings related to DTD processing, external entity resolution, or XML validation
    Affected if External entity processing is enabled in the XML parser configuration (XmlResolver or similar settings allow external DTDs/entities)
  5. Verify network exposure of the SSRSReport endpoint
    Review firewall rules and IIS/bindings configuration to determine if the SSRSReport endpoint is exposed to unauthenticated network access. Check if the Veeam ONE web interface or reporting port is accessible from untrusted networks
    Affected if The SSRSReport endpoint is accessible over the network without authentication

The system is affected if Veeam ONE is installed with a version in the ranges < 9.5.4.4587 or >= 10.0.0.0 to < 10.0.0.750 AND the SSRSReport class with its vulnerable XML parser is accessible on the network.

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 9.5.4.4587 / 10.0.0.750 or later
Fixed in 9.5.4.458710.0.0.750
Interim mitigation

Disable external entity processing in the XML parser used by the SSRSReport class, implement strict input validation on XML documents, and apply the vendor patch when available. Consider restricting outbound network access as a defense-in-depth measure.

Fix this in One Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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