This repository has been archived by the owner on Dec 7, 2023. It is now read-only.
Patch CVE-2019-18960 -- Use Firecracker v0.18.1 for ignite 0.6.x #499
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stealthybox
force-pushed
the
0.6-CVE-2019-18960
branch
from
66d6be2 to
6eaa3a9
Compare
|
LGTM! thank you @stealthybox |
chanwit
approved these changes
Dec 10, 2019
stealthybox
force-pushed
the
0.6-CVE-2019-18960
branch
from
6eaa3a9 to
c9ee7ae
Compare
|
This is looking good. A local |
This was referenced Dec 10, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ignite was unaffected as it was not using vsock for its vm's, but we were distributing vulnerable binaries.
This dependency update resolves the security issue.
Firecracker v0.18.1 Release Notes
Other details in #500