|
KVM Multiple Vulnerabilities
|
|
Secunia Advisory:
|
SA29129
|
|
|
Release Date:
|
2008-02-26
|
|
Last Update:
|
2008-12-26
|
|
Popularity:
|
5,303 views
|
|
|
Critical:
|
Moderately critical
|
|
Impact:
|
Security Bypass
DoS
|
|
Where:
|
Local system
|
|
Solution Status:
|
Partial Fix
|
|
| Software: | KVM (Kernel-based Virtual Machine)
|
|
|
Secunia CVSS-2 Score:
|
Available in Secunia business solutions 
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities
|
|
| Advisory Content (Page 1 of 3) | [ 1 ] [ 2 ] [ 3 ] | |
|
Description:
Some vulnerabilities have been reported in KVM, which can be exploited by malicious, local users to bypass certain security restrictions or cause a DoS (Denial of Service).
1) The block device backends do not properly check a guest's read or write attempts, which can be exploited out of a KVM guest system to e.g. crash the KVM host or potentially escape the virtualisation jail by writing into arbitrary host memory.
Note: Successful exploitation requires privileges to send specially crafted read or write requests to the block device backends.
This is related to vulnerability #7 in:
SA25073
2) Several vulnerabilities can be exploited by malicious, local users to bypass certain security restrictions or cause a DoS (Denial of Service).
For more information see vulnerabilities #1-#6 in:
SA25073
3) An error can be exploited by a guest to read arbitrary files on the host via a specially crafted disk header.
For more information:
SA30111
Change Page:
[ 1 ] [ 2 ] [ 3 ]
|
|
|
Track this Secunia Advisory
|
Customers of the Secunia Vulnerability Intelligence solutions will automatically receive updates when new information regarding this advisory is released.
Read more about our Vulnerability Intelligence solutions and what they can do for you and your company.
|
|
|
About this Secunia Advisory
|
Please note: The information that this Secunia Advisory is based on comes from a third party unless stated otherwise.
Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others.
|
