The primary concerned a panic-safety downside in Rust’s MapWindows::clone implementation. The perform created a buffer earlier than totally initializing its contents after which known as a user-provided clone operation to populate it. If that operation triggered a panic, Rust’s unwinding mechanism might invoke the buffer’s destructor, which might try and entry uninitialized reminiscence. Microsoft mentioned the reported repair prevents the partially initialized buffer from being destroyed earlier than initialization is full.
One other discovering concerned str::substitute. The researchers discovered that the perform might make an incorrect assumption a couple of customized implementation of the nightly Sample trait. A customized implementation might provide a non-ASCII byte the place the code anticipated an ASCII character, inflicting the substitute operation to supply invalid UTF-8 information. Subsequent string operations might then set off undefined conduct, Microsoft mentioned.
System-level bugs have an effect on secure Rust
Microsoft mentioned the primary two classes of weaknesses have been already being studied in 2021 by Rudra, a static analyzer developed by members of the analysis workforce. The usual library had additionally addressed panic-safety issues way back to 2015, however related weaknesses proceed to seem in its implementations.
