-
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.
Report uninitialized memory exposure in truetype
- Loading branch information
1 parent
1794cae
commit b4afb83
Showing
1 changed file
with
22 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,22 @@ | ||
```toml | ||
[advisory] | ||
id = "RUSTSEC-0000-0000" | ||
package = "truetype" | ||
date = "2021-02-17" | ||
url = "https://github.com/bodoni/truetype/issues/11" | ||
categories = ["memory-exposure"] | ||
|
||
[versions] | ||
patched = [">= 0.30.1"] | ||
``` | ||
|
||
# Tape::take_bytes exposes uninitialized memory to a user-provided Read | ||
|
||
Affected versions of this crate passed an unininitialized buffer to a | ||
user-provided `Read` instance in `Tape::take_bytes`. | ||
|
||
This can result in safe `Read` implementations reading from the uninitialized | ||
buffer leading to undefined behavior. | ||
|
||
The flaw was corrected in commit `1f2dc7f37dd` by removing the unsafe block | ||
and zero-initializing the buffer. |