github/acrn-hypervisor
1
0
Fork 0
mirror of https://github.com/projectacrn/acrn-hypervisor.git synced 2025-06-03 12:49:45 +00:00
Code Issues Projects Releases Wiki Activity

Doc: Grammatical edits to the Advisory doc.

Browse Source 
Signed-off-by: Deb Taylor <deb.taylor@intel.com>
This commit is contained in:
Deb Taylor 2019-11-11 10:56:56 -05:00 committed by deb-intel
parent 95d26da472
commit d3d33ffce9
1 changed files with 24 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

49
doc/asa.rst
View File

@ -1,57 +1,56 @@
.. _asa:
Advisory
Advisory
********
We recommend all developers upgrade to this v1.4 release, which addresses these security
issues discovered in earlier releases:
We recommend that all developers upgrade to this v1.4 release, which addresses the following security
issues that were discovered in previous releases:
AP Trampoline Is Accessible to Service VM
This vulnerability is triggered when validating the memory isolation between
VM and hypervisor. AP Trampoline code exists in LOW_RAM region in hypervisor but is
potentially accessible to service VM. This could be used by an attacker to mount DoS
attacks on the hypervisor if service VM is compromised.
AP Trampoline Is Accessible to the Service VM
This vulnerability is triggered when validating the memory isolation between the VM and hypervisor. The AP Trampoline code exists in the LOW_RAM region in the hypervisor but is
potentially accessible to the Service VM. This could be used by an attacker to mount DoS
attacks on the hypervisor if the Service VM is compromised.
| **Affected Release:** v1.3 and earlier.
| It’s recommended to upgrade ACRN to release v1.4
| Upgrade to ACRN release v1.4.
Improper Usage Of ``LIST_FOREACH()`` macro
Testing discovered that the MACRO ``LIST_FOREACH()`` was incorrectly used for some cases
which may induce a "wild pointer" and cause ACRN Device Model crash. An attacker
could use this issue to cause a denial of service (DoS).
Improper Usage Of the ``LIST_FOREACH()`` Macro
Testing discovered that the MACRO ``LIST_FOREACH()`` was incorrectly used 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 denial of service (DoS) attacks.
| **Affected Release:** v1.3 and earlier.
| It’s recommended to upgrade ACRN to release v1.4
| Upgrade to ACRN release v1.4.
Hypervisor Crashed When Fuzzing HC_SET_CALLBACK_VECTOR
This vulnerability was reported by Fuzzing tool for debug version of ACRN. When software fails
This vulnerability was reported by the Fuzzing tool for the debug version 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 the application. This can lead to parts of the system
receiving unintended input, which may result in altered control flow, arbitrary control
receiving unintended inputs, which may result in an altered control flow, arbitrary control
of a resource, or arbitrary code execution.
| **Affected Release:** v1.3 and earlier.
| It’s recommended to upgrade ACRN to release v1.4
| Upgrade to ACRN release v1.4.
FILE Pointer Is Not Closed After Using
This vulnerability was reported by Fuzzing tool. Leaving the file unclosed will cause
leaking file descriptor and may cause unexpected errors in Device Model program.
This vulnerability was reported by the Fuzzing tool. Leaving the file unclosed will cause a
leaking file descriptor and may cause unexpected errors in the Device Model program.
| **Affected Release:** v1.3 and earlier.
| It’s recommended to upgrade ACRN to release v1.4
| Upgrade to ACRN release v1.4.
Descriptor of Directory Stream Is Referenced After Release
This vulnerability was reported by Fuzzing tool. A successful call to ``closedir(DIR *dirp)``
This vulnerability was reported by the Fuzzing tool. A successful call to ``closedir(DIR *dirp)``
also closes the underlying file descriptor associated with ``dirp``. Access to the released
descriptor may point to some arbitrary memory location or cause undefined behavior.
| **Affected Release:** v1.3 and earlier.
| It’s recommended to upgrade ACRN to release v1.4
| Upgrade to ACRN release v1.4.
Mutex Is Potentially Kept in Locked State Forever
This vulnerability was reported by Fuzzing tool. pthread_mutex_lock/unlock pairing was not
Mutex Is Potentially Kept in a Locked State Forever
This vulnerability was reported by the Fuzzing tool. Here, 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 scenario.
| **Affected Release:** v1.3 and earlier.
| It’s recommended to upgrade ACRN to release v1.4
| Upgrade to ACRN release v1.4.