Open
Bug 1748363
Opened 2 years ago
Updated 2 years ago
When NSPR and Rust libstd are used together, they don't use the same environment lock
Categories
(NSPR :: NSPR, defect, P2)
NSPR
NSPR
Tracking
(Not tracked)
NEW
People
(Reporter: briansmith, Unassigned)
References
Details
(Keywords: csectype-race, sec-low)
Rust's libstd implements its equivalent to PR_SetEnv and PR_GetEnv with its own lock. Obviously, this doesn't compose very well with NSPR's lock. A single lock must be used across both NSPR and Rust.
Filing as a security issue so it gets attention as it potentially causes memory corruption, though it was extensively publicly discussed in https://github.com/rust-lang/rust/issues/27970. (Sorry!)
|
Reporter | |
Comment 1•2 years ago
|
||
See also bug 1748361.
|
||
Updated•2 years ago
|
Group: core-security
Keywords: csectype-race,
sec-low
See Also: → https://github.com/rust-lang/rust/issues/27970, 1748361
|
||
Comment 2•2 years ago
|
||
The severity field is not set for this bug.
:KaiE, could you have a look please?
For more information, please visit auto_nag documentation.
Flags: needinfo?(kaie)
|
||
Updated•2 years ago
|
Severity: -- → S2
Flags: needinfo?(kaie)
Priority: -- → P2
You need to log in
before you can comment on or make changes to this bug.
Description
•