dbcve.org
One FirmwareOperating system · Veeam

CVE-2020-15419

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
High EPSS 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 Reporter_ImportLicense 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-10710.

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's Reporter_ImportLicense class. The XML parser does not properly restrict external entity references, allowing unauthenticated remote attackers to supply a specially crafted XML document containing a URI that the parser will dereference. This enables disclosure of arbitrary file contents from the server filesystem running as the SYSTEM user.

MitigationApply the vendor patch for CVE-2020-15419 (update to fixed Veeam ONE version) and/or disable external entity processing in the XML parser configuration for the Reporter service.

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. Identify Veeam ONE installation and version
    Locate the Veeam ONE installation directory and check the version information, typically found in the product's about or version details within the Veeam ONE component. On Windows, this may be in the installation path (commonly C:\Program Files\Veeam\One\) or accessible via the Veeam ONE interface or registry.
    Affected if The installed version is lower than 9.5.4.4587 OR falls between 10.0.0.0 and 10.0.0.749 inclusive.
  2. Verify the Reporter component is installed
    Confirm that the Veeam ONE Reporter component is installed on the system. This may be visible in the Windows Services list as 'Veeam ONE Reporter Service' or within the Veeam ONE installation components.
    Affected if The Reporter service exists and is installed on the target system.
  3. Confirm Reporter service is running
    Check if the Veeam ONE Reporter service is currently running. On Windows, use the Services console (services.msc) or the sc query command to check the service status.
    Affected if The Reporter service is running and accessible.
  4. Assess network exposure of the Reporter interface
    Determine if the Veeam ONE Reporter service is exposed to network access. This typically involves checking firewall rules, listening ports (the Reporter service often uses ports in the 3000-4000 range), and whether the service is bound to non-localhost interfaces.
    Affected if The Reporter service is accessible over the network (not bound to localhost only) and accepts external connections.

A system is affected if it runs a vulnerable version of Veeam ONE (below 9.5.4.4587 or between 10.0.0.0 and 10.0.0.749) with the Reporter component installed, running, and network-accessible.

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

Apply the vendor patch for CVE-2020-15419 (update to fixed Veeam ONE version) and/or disable external entity processing in the XML parser configuration for the Reporter service.

Fix this in One Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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