Veritas Resiliency Platform 3.4/3.5 on Windows OpenSSL Library openssl.cnf permission
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.8 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Veritas Resiliency Platform 3.4/3.5 on Windows and classified as critical. The impacted element is an unknown function of the file C:\usr\local\ssl\openssl.cnf of the component OpenSSL Library Handler. This manipulation causes permission. This vulnerability is tracked as CVE-2020-36168. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in Veritas Resiliency Platform 3.4/3.5 on Windows. It has been declared as critical. Affected by this vulnerability is an unknown part of the file C:\usr\local\ssl\openssl.cnf of the component OpenSSL Library Handler. The manipulation with an unknown input leads to a permission vulnerability. The CWE definition for the vulnerability is CWE-275. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was disclosed 01/06/2021 as VTS20-015. The advisory is shared at veritas.com. This vulnerability is known as CVE-2020-36168. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1222 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.8VulDB Meta Temp Score: 8.8
VulDB Base Score: 8.8
VulDB Temp Score: 8.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: PermissionCWE: CWE-275 / CWE-266
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/06/2021 🔍01/06/2021 🔍
01/06/2021 🔍
Sources
Advisory: VTS20-015Status: Not defined
CVE: CVE-2020-36168 (🔍)
GCVE (CVE): GCVE-0-2020-36168
GCVE (VulDB): GCVE-100-167317
Entry
Created: 01/06/2021 09:29Changes: 01/06/2021 09:29 (39)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.