Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2020-25603 | First vendor Publication | 2020-09-23 |
Vendor | Cve | Last vendor Modification | 2023-11-07 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | |||
---|---|---|---|
Overall CVSS Score | 7.8 | ||
Base Score | 7.8 | Environmental Score | 7.8 |
impact SubScore | 5.9 | Temporal Score | 7.8 |
Exploitabality Sub Score | 1.8 | ||
Attack Vector | Local | Attack Complexity | Low |
Privileges Required | Low | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | High |
Integrity Impact | High | Availability Impact | High |
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : (AV:L/AC:L/Au:N/C:P/I:P/A:P) | |||
---|---|---|---|
Cvss Base Score | 4.6 | Attack Range | Local |
Cvss Impact Score | 6.4 | Attack Complexity | Low |
Cvss Expoit Score | 3.9 | Authentication | None Required |
Calculate full CVSS 2.0 Vectors scores |
Detail
An issue was discovered in Xen through 4.14.x. There are missing memory barriers when accessing/allocating an event channel. Event channels control structures can be accessed lockless as long as the port is considered to be valid. Such a sequence is missing an appropriate memory barrier (e.g., smp_*mb()) to prevent both the compiler and CPU from re-ordering access. A malicious guest may be able to cause a hypervisor crash resulting in a Denial of Service (DoS). Information leak and privilege escalation cannot be excluded. Systems running all versions of Xen are affected. Whether a system is vulnerable will depend on the CPU and compiler used to build Xen. For all systems, the presence and the scope of the vulnerability depend on the precise re-ordering performed by the compiler used to build Xen. We have not been able to survey compilers; consequently we cannot say which compiler(s) might produce vulnerable code (with which code generation options). GCC documentation clearly suggests that re-ordering is possible. Arm systems will also be vulnerable if the CPU is able to re-order memory access. Please consult your CPU vendor. x86 systems are only vulnerable if a compiler performs re-ordering. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25603 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-670 | Always-Incorrect Control Flow Implementation |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2023-11-07 21:36:38 |
|
2023-08-02 01:53:31 |
|
2022-04-29 02:04:39 |
|
2021-09-02 01:39:29 |
|
2021-08-05 01:38:13 |
|
2021-07-21 17:23:22 |
|
2021-05-05 01:39:05 |
|
2021-05-04 13:50:33 |
|
2021-04-22 03:02:03 |
|
2021-03-27 01:34:08 |
|
2021-02-05 01:31:31 |
|
2020-11-11 12:29:36 |
|
2020-10-08 05:22:54 |
|
2020-10-05 17:22:57 |
|
2020-10-04 17:22:52 |
|
2020-10-03 09:22:53 |
|
2020-10-01 12:27:53 |
|
2020-09-27 09:22:48 |
|
2020-09-24 17:22:55 |
|
2020-09-24 05:22:57 |
|