github/acrn-hypervisor
1
0
Fork 0
mirror of https://github.com/projectacrn/acrn-hypervisor.git synced 2025-08-08 03:35:14 +00:00
Code Issues Projects Releases Wiki Activity

doc: organize security advisory doc

Browse Source 
Add headings to organize security advisory doc by release to make it a
bit easier to read.

Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
This commit is contained in:
David B. Kinder 2020-04-01 21:39:26 -07:00 committed by David Kinder
parent a5ef52094f
commit 7b969d15c0
1 changed files with 37 additions and 33 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

70
doc/asa.rst
View File

@ -1,66 +1,74 @@
.. _asa: .. _asa:
Security Advisory Security Advisory
***************** #################
We recommend that all developers upgrade to this v1.6 release, which Addressed in ACRN v1.6
**********************
We recommend that all developers upgrade to this v1.6 release (or later), which
addresses the following security issues that were discovered in previous releases: addresses the following security issues that were discovered in previous releases:
Hypervisor Crashes When Fuzzing HC_DESTROY_VM ------
- Hypervisor Crashes When Fuzzing HC_DESTROY_VM
The input 'vdev->pdev' should be validated properly when handling The input 'vdev->pdev' should be validated properly when handling
HC_SET_PTDEV_INTR_INFO to ensure that the physical device is linked to HC_SET_PTDEV_INTR_INFO to ensure that the physical device is linked to
'vdev'; otherwise, the hypervisor crashes when fuzzing the 'vdev'; otherwise, the hypervisor crashes when fuzzing the
hypercall HC_DESTROY_VM with crafted input. hypercall HC_DESTROY_VM with crafted input.
| **Affected Release:** v1.5 and earlier. **Affected Release:** v1.5 and earlier.
| Upgrade to ACRN release v1.6.
Hypervisor Crashes When Fuzzing HC_VM_WRITE_PROTECT_PAGE - Hypervisor Crashes When Fuzzing HC_VM_WRITE_PROTECT_PAGE
The input GPA is not validated when handling this hypercall; an "Invalid The input GPA is not validated when handling this hypercall; an "Invalid
GPA" that is not in the scope of the target VM's EPT address space results GPA" that is not in the scope of the target VM's EPT address space results
in the hypervisor crashing when handling this hypercall. in the hypervisor crashing when handling this hypercall.
| **Affected Release:** v1.4 and earlier. **Affected Release:** v1.4 and earlier.
| Upgrade to ACRN release v1.6.
Hypervisor Crashes When Fuzzing HC_NOTIFY_REQUEST_FINISH - Hypervisor Crashes When Fuzzing HC_NOTIFY_REQUEST_FINISH
The input is not validated properly when handing this hypercall; The input is not validated properly when handing this hypercall;
'vcpu_id' should be less than 'vm->hw.created_vcpus' instead of 'vcpu_id' should be less than 'vm->hw.created_vcpus' instead of
'MAX_VCPUS_PER_VM'. When the software fails to validate input properly, 'MAX_VCPUS_PER_VM'. When the software fails to validate input properly,
the hypervisor crashes when handling crafted inputs. the hypervisor crashes when handling crafted inputs.
| **Affected Release:** v1.4 and earlier. **Affected Release:** v1.4 and earlier.
| Upgrade to ACRN release v1.6.
Mitigation for Machine Check Error on Page Size Change
Addressed in ACRN v1.4
**********************
We recommend that all developers upgrade to this v1.4 release (or later), which
addresses the following security issues that were discovered in previous releases:
------
- Mitigation for Machine Check Error on Page Size Change
Improper invalidation for page table updates by a virtual guest operating Improper invalidation for page table updates by a virtual guest operating
system for multiple Intel(R) Processors may allow an authenticated user system for multiple Intel(R) Processors may allow an authenticated user
to potentially enable denial of service of the host system via local to potentially enable denial of service of the host system via local
access. A malicious guest kernel could trigger this issue, CVE-2018-12207. access. A malicious guest kernel could trigger this issue, CVE-2018-12207.
| **Affected Release:** v1.3 and earlier. **Affected Release:** v1.3 and earlier.
| Upgrade to ACRN release v1.4.
AP Trampoline Is Accessible to the Service VM - AP Trampoline Is Accessible to the Service VM
This vulnerability is triggered when validating the memory isolation This vulnerability is triggered when validating the memory isolation
between the VM and the hypervisor. The AP Trampoline code exists in the between the VM and the hypervisor. The AP Trampoline code exists in the
LOW_RAM region of the hypervisor but is potentially accessible to the LOW_RAM region of the hypervisor but is potentially accessible to the
Service VM. This could be used by an attacker to mount DoS attacks on the Service VM. This could be used by an attacker to mount DoS attacks on the
hypervisor if the Service VM is compromised. hypervisor if the Service VM is compromised.
| **Affected Release:** v1.3 and earlier. **Affected Release:** v1.3 and earlier.
| Upgrade to ACRN release v1.4.
Improper Usage Of the ``LIST_FOREACH()`` Macro - Improper Usage Of the ``LIST_FOREACH()`` Macro
Testing discovered that the MACRO ``LIST_FOREACH()`` was incorrectly used Testing discovered that the MACRO ``LIST_FOREACH()`` was incorrectly used
in some cases which could induce a "wild pointer" and cause the ACRN in some cases which could induce a "wild pointer" and cause the ACRN
Device Model to crash. Attackers can potentially use this issue to cause Device Model to crash. Attackers can potentially use this issue to cause
denial of service (DoS) attacks. denial of service (DoS) attacks.
| **Affected Release:** v1.3 and earlier. **Affected Release:** v1.3 and earlier.
| Upgrade to ACRN release v1.4.
Hypervisor Crashes When Fuzzing HC_SET_CALLBACK_VECTOR - Hypervisor Crashes When Fuzzing HC_SET_CALLBACK_VECTOR
This vulnerability was reported by the Fuzzing tool for the debug version This vulnerability was reported by the Fuzzing tool for the debug version
of ACRN. When the software fails to validate input properly, an attacker of ACRN. When the software fails to validate input properly, an attacker
is able to craft the input in a form that is not expected by the rest of is able to craft the input in a form that is not expected by the rest of
@ -68,31 +76,27 @@ Hypervisor Crashes When Fuzzing HC_SET_CALLBACK_VECTOR
unintended inputs, which may result in an altered control flow, arbitrary unintended inputs, which may result in an altered control flow, arbitrary
control of a resource, or arbitrary code execution. control of a resource, or arbitrary code execution.
| **Affected Release:** v1.3 and earlier. **Affected Release:** v1.3 and earlier.
| Upgrade to ACRN release v1.4.
FILE Pointer Is Not Closed After Using - FILE Pointer Is Not Closed After Using
This vulnerability was reported by the Fuzzing tool. Leaving the file This vulnerability was reported by the Fuzzing tool. Leaving the file
unclosed will cause a leaking file descriptor and may cause unexpected unclosed will cause a leaking file descriptor and may cause unexpected
errors in the Device Model program. errors in the Device Model program.
| **Affected Release:** v1.3 and earlier. **Affected Release:** v1.3 and earlier.
| Upgrade to ACRN release v1.4.
Descriptor of Directory Stream Is Referenced After Release - Descriptor of Directory Stream Is Referenced After Release
This vulnerability was reported by the Fuzzing tool. A successful call to This vulnerability was reported by the Fuzzing tool. A successful call to
``closedir(DIR *dirp)`` also closes the underlying file descriptor ``closedir(DIR *dirp)`` also closes the underlying file descriptor
associated with ``dirp``. Access to the released descriptor may point to associated with ``dirp``. Access to the released descriptor may point to
some arbitrary memory location or cause undefined behavior. some arbitrary memory location or cause undefined behavior.
| **Affected Release:** v1.3 and earlier. **Affected Release:** v1.3 and earlier.
| Upgrade to ACRN release v1.4.
Mutex Is Potentially Kept in a Locked State Forever - Mutex Is Potentially Kept in a Locked State Forever
This vulnerability was reported by the Fuzzing tool. Here, This vulnerability was reported by the Fuzzing tool. Here,
pthread_mutex_lock/unlock pairing was not always done. Leaving a mutex in pthread_mutex_lock/unlock pairing was not always done. Leaving a mutex in
a locked state forever can cause program deadlock, depending on the usage a locked state forever can cause program deadlock, depending on the usage
scenario. scenario.
| **Affected Release:** v1.3 and earlier. **Affected Release:** v1.3 and earlier.
| Upgrade to ACRN release v1.4.