Bug 1736766 (CVE-2019-1010299)

Summary:	CVE-2019-1010299 rust: print of uninitialized memory in the debug trait implementation for std::collections::vec_deque::Iter
Product:	[Other] Security Response	Reporter:	Laura Pardo <lpardo>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	igor.raits, jistone, rust-sig, TicoTimo
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	rust 1.30.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-05 01:18:22 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1736769, 1736770, 1736771
Bug Blocks:	1736772

Description Laura Pardo 2019-08-01 23:06:53 UTC

The Rust Programming Language Standard Library 1.18.0 and later is affected by an Information Exposure vulnerability. Contents of uninitialized memory could be printed to string or to log file in the debug trait implementation for std::collections::vec_deque::Iter when the program invokes the debug printing for an iterator over an empty VecDeque.


References:
https://github.com/rust-lang/rust/issues/53566

Upstream Patch:
https://github.com/rust-lang/rust/pull/53571/commits/b85e4cc8fadaabd41da5b9645c08c68b8f89908d

Comment 1 Laura Pardo 2019-08-01 23:28:58 UTC

Created rust tracking bugs for this issue:

Affects: epel-7 [bug 1736771]
Affects: fedora-29 [bug 1736769]
Affects: fedora-30 [bug 1736770]

Comment 2 Josh Stone 2019-08-02 16:01:19 UTC

> 1.18.0 and later

The upstream patch was merged for 1.30.0, so only 1.18.0 through 1.29.* are affected. Fedora and EPEL all have Rust 1.36, so I will close those bugs as CURRENTRELEASE.

Comment 3 Product Security DevOps Team 2019-08-05 01:18:22 UTC

This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2019-1010299