loader: x86_64: elf: Avoid reading beyond file end #125
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
The ELF header contains offsets that the loader uses to find other structures. If those offsets are beyond the end of the file (or would go past the end of the file) it is essential to error out when attempting to read those. Using `Read::read_exact()` permits this. Signed-off-by: Bo Chen <chen.bo@intel.com> Co-authored-by: Rob Bradford <robert.bradford@intel.com>
|
/cc @rbradford @sboeuf |
sboeuf
approved these changes
Dec 6, 2022
rbradford
approved these changes
Dec 6, 2022
andreeaflorescu
added a commit
to andreeaflorescu/vm-memory
that referenced
this pull request
Jan 2, 2023
We cannot mark the returned usize as must use unfortunately. This is what triggered the bug in linux-loader: rust-vmm/linux-loader#125. The least we can do is to validate that when there are more bytes requested than what the reader has available, we do return the correct number of the read. Unfortunately, when this result is not used it can lead to bugs. Signed-off-by: Andreea Florescu <fandree@amazon.com>
andreeaflorescu
added a commit
to andreeaflorescu/vm-memory
that referenced
this pull request
Jan 2, 2023
We cannot mark the returned usize as must use unfortunately. This is what triggered the bug in linux-loader: rust-vmm/linux-loader#125. The least we can do is to validate that when there are more bytes requested than what the reader has available, we do return the correct number of the read. Unfortunately, when this result is not used it can lead to bugs. Signed-off-by: Andreea Florescu <fandree@amazon.com>
andreeaflorescu
added a commit
to rust-vmm/vm-memory
that referenced
this pull request
Jan 3, 2023
We cannot mark the returned usize as must use unfortunately. This is what triggered the bug in linux-loader: rust-vmm/linux-loader#125. The least we can do is to validate that when there are more bytes requested than what the reader has available, we do return the correct number of the read. Unfortunately, when this result is not used it can lead to bugs. Signed-off-by: Andreea Florescu <fandree@amazon.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary of the PR
The ELF header contains offsets that the loader uses to find other structures. If those offsets are beyond the end of the file (or would go past the end of the file) it is essential to error out when attempting to read those. Using
Read::read_exact()permits this.Signed-off-by: Bo Chen chen.bo@intel.com
Co-authored-by: Rob Bradford robert.bradford@intel.com
Requirements
Before submitting your PR, please make sure you addressed the following
requirements:
git commit -s), and the commitmessage has max 60 characters for the summary and max 75 characters for each
description line.
test.
Release" section of CHANGELOG.md (if no such section exists, please create one).
unsafecode is properly documented.