- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It say "This project has been identified as having known security escapes.", but what known security escapes?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, that is just to share you the concept of that attack in QEMU.
Focus on the fact that the vulnerability attacks host operating system that runs QEMU.
QEMU-SGX, as the name implies, it uses QEMU so even if Enclave don't trust OS&Host App in VM, or no VM, the vulnerability exist.
Cordially,
Iffa
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Generally, the QEMU is vulnerable to Virtual Machine Escape attack which triggered when fragment packets are reassembled for processing. This allows an attacker to perform arbitrary code execution at the same privilege level as QEMU itself, and completely crash the QEMU process.
Cordially,
Iffa
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for reply!
Any hyper-links or details about this vulnerability or news?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here it is (Note that this is public info):
1. Vulnerability in QEMU allows attackers to perform virtual machine escape
2. NVD for (no 1) vulnerability
3. KVM breakout
Hope this helps!
If you don't have any further inquiries, shall I close this case?
Cordially,
Iffa
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
But it seems that Qemu escape will not influent security of Enclave in VM, since Enclave don't trust OS&Host App in VM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, that is just to share you the concept of that attack in QEMU.
Focus on the fact that the vulnerability attacks host operating system that runs QEMU.
QEMU-SGX, as the name implies, it uses QEMU so even if Enclave don't trust OS&Host App in VM, or no VM, the vulnerability exist.
Cordially,
Iffa
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks!
Thus it's due to Qemu problem, not an SGX problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Glad that helps!
Intel will no longer monitor this thread since this issue has been resolved. If you need any additional information from Intel, please submit a new question.
Cordially,
Iffa
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page