-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Firecracker serial console emulation may allocate an unbounded amount of memory #2177
Labels
Priority: High
Indicates than an issue or pull request should be resolved ahead of issues or pull requests labelled
Type: Bug
Indicates an unexpected problem or unintended behavior
Comments
sandreim
added
Type: Bug
Indicates an unexpected problem or unintended behavior
Priority: High
Indicates than an issue or pull request should be resolved ahead of issues or pull requests labelled
labels
Oct 14, 2020
This was referenced Oct 14, 2020
9 tasks
Issue was fixed in v0.22.1, v0.21.3 and v0.23.0. Closing this issue after adding the fix in mainline. |
amshinde
added a commit
to amshinde/kata-runtime
that referenced
this issue
Dec 3, 2020
In addition to features related to gathering metrics around several data-points, the releases leading to this release carry a few secirty fixes. Lets update to latest fircracker release. References: firecracker-microvm/firecracker#2057 firecracker-microvm/firecracker#2177 Fixes: kata-containers#3095 Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
amshinde
added a commit
to amshinde/kata-runtime
that referenced
this issue
Dec 9, 2020
Release included important security updates. References: firecracker-microvm/firecracker#2057 firecracker-microvm/firecracker#2177 Fixes: kata-containers#3095 Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
amshinde
added a commit
to amshinde/kata-runtime
that referenced
this issue
Dec 9, 2020
Release included important security updates. References: firecracker-microvm/firecracker#2057 firecracker-microvm/firecracker#2177 Fixes: kata-containers#3095 Signed-off-by: Archana Shinde <archana.m.shinde@intel.com> (cherry picked from commit 11c8c19)
amshinde
added a commit
to amshinde/kata-runtime
that referenced
this issue
Dec 9, 2020
Release included important security updates. References: firecracker-microvm/firecracker#2057 firecracker-microvm/firecracker#2177 Fixes: kata-containers#3095 Signed-off-by: Archana Shinde <archana.m.shinde@intel.com> (cherry picked from commit 11c8c19)
This was referenced Dec 9, 2020
amshinde
added a commit
to amshinde/kata-runtime
that referenced
this issue
Dec 11, 2020
Release included important security updates. References: firecracker-microvm/firecracker#2057 firecracker-microvm/firecracker#2177 Fixes: kata-containers#3095 Depends-on: github.com/kata-containers/osbuilder#508 (cherry picked from commit 11c8c19) Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
amshinde
added a commit
to amshinde/kata-runtime
that referenced
this issue
Dec 11, 2020
Release included important security updates. References: firecracker-microvm/firecracker#2057 firecracker-microvm/firecracker#2177 Fixes: kata-containers#3095 Depends-on: github.com/kata-containers/osbuilder#508 (cherry picked from commit 11c8c19) Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
amshinde
added a commit
to amshinde/kata-runtime
that referenced
this issue
Dec 23, 2020
Release included important security updates. References: firecracker-microvm/firecracker#2057 firecracker-microvm/firecracker#2177 Fixes: kata-containers#3095 (cherry picked from commit 11c8c19) Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Priority: High
Indicates than an issue or pull request should be resolved ahead of issues or pull requests labelled
Type: Bug
Indicates an unexpected problem or unintended behavior
We have identified an issue in the Firecracker serial console emulation of all Firecracker versions up to v0.21.2 and Firecracker v0.22.0
Issue Description
The Firecracker implementation of the serial console emulation allows buffering of an unlimited number of bytes when data is written to the Firecracker process standard input at a high rate.
Impact
Firecracker customers that forward the standard input of the Firecracker process to untrusted users can become subject to DoS attacks. If memory limits are not imposed on the Firecracker process, this might impair other microVMs on the same host from allocating memory, potentially becoming an availability issue.
Serial output generated by the guest can’t trigger the issue.
Affected Systems
Firecracker versions v0.22.0 and v0.21.2, while all older releases might be impacted.
Mitigation
Impact can be mitigated by applying memory limits to the Firecracker process or by applying a rate limit when writing to the Firecracker process standard input.
Customers may apply:
Patched binaries mitigating this issue have been released as Firecracker v0.21.3[1] and Firecracker v0.22.1[2].
If you are using Firecracker versions up to v0.21.2 or Firecracker v0.22.0, we recommend you apply the provided fix.
[1] https://github.com/firecracker-microvm/firecracker/releases/tag/v0.21.3
[2] https://github.com/firecracker-microvm/firecracker/releases/tag/v0.22.1
The text was updated successfully, but these errors were encountered: