Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix for VENOM vulnerability (CVE-2015-3456) #20

Closed
wants to merge 1 commit into from
Closed

Fix for VENOM vulnerability (CVE-2015-3456) #20

wants to merge 1 commit into from

Conversation

danmcd
Copy link

@danmcd danmcd commented May 13, 2015

Three variants-on-a-theme patches were issued via the oss-security list this morning. This is a direct application of xsa133-qemuu.patch (using "patch < xsa133-qemuu.patch" with PWD=illumos-kvm-cmd/hw).

@rmustacc
Copy link
Contributor

Resolved in 407546e. Thanks Dan!

@misterbisson
Copy link

Thanks for the quick patch @danmcd.

It's been noted elsewhere, but worth repeating here:

From Alex:

One other thing to note is that the qemu process on SmartOS runs inside a zone, so escaping the qemu just gets you root in a zone that has basically nothing in it except the qemu binary and some config.

You would need an additional kernel privesc vuln to escape that zone and take control over the entire box.

And from Robert

This is correct, the processes in there are running in a stripped privilege environment. It cannot fork.

tl;dr: this vulnerability poses no risk on SmartOS.

@misterbisson
Copy link

Support statement regarding Joyent's public and private cloud offerings posted earlier today: https://help.joyent.com/entries/68099220-Security-Advisory-on-Venom-CVE-2015-3456-in-KVM-QEMU

citrus-it pushed a commit to citrus-it/illumos-kvm-cmd that referenced this pull request Dec 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants