Veeam Availability Suite/Backup / Replication up to 9.x VeeamFSR.sys memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Veeam Availability Suite, Backup and Replication up to 9.x. This affects an unknown function in the library VeeamFSR.sys. The manipulation leads to memory corruption. This vulnerability is traded as CVE-2020-15518. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability was found in Veeam Availability Suite, Backup and Replication up to 9.x (Backup Software) and classified as critical. This issue affects some unknown functionality in the library VeeamFSR.sys. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
VeeamFSR.sys in Veeam Availability Suite before 10 and Veeam Backup & Replication before 10 has no device object DACL, which allows unprivileged users to achieve total control over filesystem I/O requests.
The weakness was shared 07/03/2020. The identification of this vulnerability is CVE-2020-15518 since 07/03/2020. The exploitation is known to be easy. The attack may be initiated remotely. A simple authentication is required for exploitation. Technical details are known, but no exploit is available.
Upgrading to version 10.0 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Availability Suite/Backup / Replication 10.0
Timeline
07/03/2020 🔍07/03/2020 🔍
07/04/2020 🔍
07/04/2020 🔍
Sources
Status: Not definedCVE: CVE-2020-15518 (🔍)
GCVE (CVE): GCVE-0-2020-15518
GCVE (VulDB): GCVE-100-157649
Entry
Created: 07/04/2020 07:58Updated: 07/04/2020 08:03
Changes: 07/04/2020 07:58 (37), 07/04/2020 08:03 (18)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.