util: Zero-initialize result to prevent possible uninit memory read#470
Merged
Conversation
Fixes #354 `io::Read::read_exact` does not receive `MaybeUninit` memory and a trait implementation can possibly read from our uninitialized vector without `unsafe`, which is UB. As there is no proper solution to this problem yet (see linked issue), our safest bet is to just take the perf-hit and zero-initialize this vector.
MarijnS95
force-pushed
the
read-spv-initialize-mem
branch
from
0984587 to
ea809ba
Compare
MarijnS95
added a commit
to MarijnS95/advisory-db
that referenced
this pull request
Aug 23, 2021
MarijnS95
added a commit
to MarijnS95/advisory-db
that referenced
this pull request
Aug 23, 2021
Shnatsel
pushed a commit
to rustsec/advisory-db
that referenced
this pull request
Aug 23, 2021
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #354
io::Read::read_exactdoes not receiveMaybeUninitmemory and a trait implementation can possibly read from our uninitialized vector withoutunsafe, which is UB. As there is no proper solution to this problem yet (see linked issue), our safest bet is to just take the perf-hit and zero-initialize this vector.