-
Notifications
You must be signed in to change notification settings - Fork 377
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #728 from JOE1994/0118-postscript
postscript: `Read` on uninitialized buffer may cause UB (`impl Walue for Vec<u8>`)
- Loading branch information
Showing
1 changed file
with
20 additions
and
0 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
```toml | ||
[advisory] | ||
id = "RUSTSEC-0000-0000" | ||
package = "postscript" | ||
date = "2021-01-30" | ||
url = "https://github.com/bodoni/postscript/issues/1" | ||
categories = ["memory-exposure"] | ||
|
||
[versions] | ||
patched = [">= 0.14.0"] | ||
``` | ||
|
||
# `Read` on uninitialized buffer may cause UB (`impl Walue for Vec<u8>`) | ||
|
||
Affected versions of this crate passes an uninitialized buffer to a user-provided `Read` implementation. | ||
|
||
Arbitrary `Read` implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer. | ||
Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior. | ||
|
||
This flaw was fixed in commit 8026286 by zero-initializing the buffer before handing to a user-provided `Read`. |