mirror of
https://github.com/OMGeeky/advisory-db.git
synced 2026-01-09 13:09:27 +01:00
ac125ee29a
As proposed in #240 and tracked in #414, this PR translates all advisories into the new "V3" advisory format, which is based on Markdown with leading TOML front matter. This format makes it easier to see rendered Markdown syntax descriptions, whether rendered by an IDE or GitHub. This should help with both crafting advisories initially as well as review, and ideally encourages more lengthy descriptions. Support for this format shipped in `cargo-audit` v0.12.0 on May 6th, 2020.
920 B
920 B
[advisory]
id = "RUSTSEC-2020-0009"
package = "flatbuffers"
date = "2020-04-11"
url = "https://github.com/google/flatbuffers/issues/5825"
[affected.functions]
"flatbuffers::read_scalar" = [">= 0.4.0"]
"flatbuffers::read_scalar_at" = [">= 0.4.0"]
[versions]
patched = []
unaffected = ["< 0.4.0"]
read_scalar and read_scalar_at allow transmuting values without unsafe blocks
The read_scalar and read_scalar_at functions are unsound
because they allow transmuting values without unsafe blocks.
The following example shows how to create a dangling reference:
fn main() {
#[derive(Copy, Clone, PartialEq, Debug)]
struct S(&'static str);
impl flatbuffers::EndianScalar for S {
fn to_little_endian(self) -> Self { self }
fn from_little_endian(self) -> Self { self }
}
println!("{:?}", flatbuffers::read_scalar::<S>(&[1; std::mem::size_of::<S>()]));
}