CVE-2020-10915 in the critical feed json
This vulnerability allows remote attackers to execute arbitrary code on affected installations of VEEAM One Agent 9.5.4.4587.
published 2020-04-22 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-3321
- cvss
- 9.8
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 86.7%
- EPSS 86.7% chance of exploitation in 30 days, percentile 99.7%
- public exploits
- 1
- Metasploit
Summary
This vulnerability allows remote attackers to execute arbitrary code on affected installations of VEEAM One Agent 9.5.4.4587. Authentication is not required to exploit this vulnerability. The specific flaw exists within the HandshakeResult method. The issue results from the lack of proper validation of user-supplied data, which can result in deserialization of untrusted data. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-10401.
Timeline
- First public exploit (Metasploit exploit/windows/misc/veeam_one_agent_deserialization)
- Published
Exploit prediction
86.73% chance of exploitation in the next 30 days, higher than 99.7% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit exploit/windows/misc/veeam_one_agent_deserialization Veeam ONE Agent .NET Deserialization metasploit exploit, normal rank, 2020-04-15
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- VEEAM One Agent
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
veeam.com
/kb3144
vendor-advisory
-
zerodayinitiative.com
/advisories/ZDI-20-546/
third-party-advisory, vdb-entry
- packetstormsecurity.com /files/157529/Veeam-ONE-Agent-.NET-Deserialization.html
Sources
- CVE List CVE-2020-10915
- NVD CVE-2020-10915
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.