Devid Espenschied PC Analyser up to 4.10.12 IOCTL Handler Function PCADRVX64.SYS memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Devid Espenschied PC Analyser up to 4.10.12. This affects an unknown part in the library PCADRVX64.SYS of the component IOCTL Handler Function. This manipulation causes memory corruption. The identification of this vulnerability is CVE-2020-28921. There is no exploit available.
Details
A vulnerability was found in Devid Espenschied PC Analyser up to 4.10.12. It has been declared as critical. Affected by this vulnerability is some unknown processing in the library PCADRVX64.SYS of the component IOCTL Handler Function. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was shared 11/27/2020. The advisory is shared at github.com. This vulnerability is known as CVE-2020-28921. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.4VulDB Meta Temp Score: 8.4
VulDB Base Score: 8.0
VulDB Temp Score: 8.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: Partially
Local: Yes
Remote: Partially
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
11/18/2020 🔍11/27/2020 🔍
11/27/2020 🔍
12/11/2020 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2020-28921 (🔍)
GCVE (CVE): GCVE-0-2020-28921
GCVE (VulDB): GCVE-100-165409
Entry
Created: 11/27/2020 22:53Updated: 12/11/2020 08:04
Changes: 11/27/2020 22:53 (37), 12/11/2020 08:00 (2), 12/11/2020 08:04 (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.