enumflags2

Version	Released
`0.7.12` unknown	Jun 09, 2025
`0.7.11` unknown	Jan 17, 2025
`0.7.10` unknown	Jun 07, 2024
`0.7.9` unknown	Feb 12, 2024
`0.7.8` unknown	Sep 13, 2023
`0.7.7` unknown	Apr 17, 2023
`0.7.6` unknown yanked 1 CVE	Apr 01, 2023
`0.7.5` unknown yanked 1 CVE	Apr 10, 2022
`0.7.4` unknown yanked 1 CVE	Mar 24, 2022
`0.7.3` unknown yanked 1 CVE	Dec 26, 2021
`0.7.2` unknown yanked 1 CVE	Dec 14, 2021
`0.7.1` unknown yanked 1 CVE	Feb 24, 2021
`0.7.0` unknown yanked 1 CVE	Feb 24, 2021
`0.7.0-preview1` unknown	Aug 12, 2020
`0.6.4` unknown	Apr 21, 2020
`0.6.3` unknown	Apr 11, 2020
`0.6.2` unknown	Nov 16, 2019
`0.6.1` unknown	Oct 24, 2019
`0.6.0` unknown	Oct 04, 2019
`0.5.2` unknown	May 02, 2019
`0.5.1` unknown	Apr 02, 2019
`0.5.0` unknown	Jan 29, 2019

0.7.12 unknown

Jun 09, 2025

0.7.11 unknown

Jan 17, 2025

0.7.10 unknown

Jun 07, 2024

0.7.9 unknown

Feb 12, 2024

0.7.8 unknown

Sep 13, 2023

0.7.7 unknown

Apr 17, 2023

0.7.6 unknown yanked

1 CVE

GHSA-qvc4-78gw-pv8p RUSTSEC-2023-0035 Apr 24, 2023

Adverserial use of `make_bitflags!` macro can cause undefined behavior

Medium

The macro relied on an expression of the form Enum::Variant always being a variant of the enum. However, it may also be an associated integer constant, in which case there's no guarantee that the value of said constant consists only of bits valid for this bitflag type.

Thus, code like this could create an invalid BitFlags<Test>, which would cause iterating over it to trigger undefined behavior. As the debug formatter internally iterates over the value, it is also affected.

use enumflags2::{bitflags, make_bitflags};

#[bitflags]
#[repr(u8)]
#[derive(Copy, Clone, Debug)]
enum Test {
    A = 1,
    B = 2,
}

impl Test {
    const C: u8 = 69;
}

fn main() {
    let x = make_bitflags!(Test::{C});
    // printing or iterating over x is UB
}

Fixed in


          0.7.7

References

Updated Nov 08, 2023 · Source: OSV.dev

Apr 01, 2023

0.7.5 unknown yanked

1 CVE

GHSA-qvc4-78gw-pv8p RUSTSEC-2023-0035 Apr 24, 2023

Adverserial use of `make_bitflags!` macro can cause undefined behavior

Medium

The macro relied on an expression of the form Enum::Variant always being a variant of the enum. However, it may also be an associated integer constant, in which case there's no guarantee that the value of said constant consists only of bits valid for this bitflag type.

Thus, code like this could create an invalid BitFlags<Test>, which would cause iterating over it to trigger undefined behavior. As the debug formatter internally iterates over the value, it is also affected.

use enumflags2::{bitflags, make_bitflags};

#[bitflags]
#[repr(u8)]
#[derive(Copy, Clone, Debug)]
enum Test {
    A = 1,
    B = 2,
}

impl Test {
    const C: u8 = 69;
}

fn main() {
    let x = make_bitflags!(Test::{C});
    // printing or iterating over x is UB
}

Fixed in


          0.7.7

References

Updated Nov 08, 2023 · Source: OSV.dev

Apr 10, 2022

0.7.4 unknown yanked

1 CVE

GHSA-qvc4-78gw-pv8p RUSTSEC-2023-0035 Apr 24, 2023

Adverserial use of `make_bitflags!` macro can cause undefined behavior

Medium

The macro relied on an expression of the form Enum::Variant always being a variant of the enum. However, it may also be an associated integer constant, in which case there's no guarantee that the value of said constant consists only of bits valid for this bitflag type.

Thus, code like this could create an invalid BitFlags<Test>, which would cause iterating over it to trigger undefined behavior. As the debug formatter internally iterates over the value, it is also affected.

use enumflags2::{bitflags, make_bitflags};

#[bitflags]
#[repr(u8)]
#[derive(Copy, Clone, Debug)]
enum Test {
    A = 1,
    B = 2,
}

impl Test {
    const C: u8 = 69;
}

fn main() {
    let x = make_bitflags!(Test::{C});
    // printing or iterating over x is UB
}

Fixed in


          0.7.7

References

Updated Nov 08, 2023 · Source: OSV.dev

Mar 24, 2022

0.7.3 unknown yanked

1 CVE

GHSA-qvc4-78gw-pv8p RUSTSEC-2023-0035 Apr 24, 2023

Adverserial use of `make_bitflags!` macro can cause undefined behavior

Medium

The macro relied on an expression of the form Enum::Variant always being a variant of the enum. However, it may also be an associated integer constant, in which case there's no guarantee that the value of said constant consists only of bits valid for this bitflag type.

Thus, code like this could create an invalid BitFlags<Test>, which would cause iterating over it to trigger undefined behavior. As the debug formatter internally iterates over the value, it is also affected.

use enumflags2::{bitflags, make_bitflags};

#[bitflags]
#[repr(u8)]
#[derive(Copy, Clone, Debug)]
enum Test {
    A = 1,
    B = 2,
}

impl Test {
    const C: u8 = 69;
}

fn main() {
    let x = make_bitflags!(Test::{C});
    // printing or iterating over x is UB
}

Fixed in


          0.7.7

References

Updated Nov 08, 2023 · Source: OSV.dev

Dec 26, 2021

0.7.2 unknown yanked

1 CVE

GHSA-qvc4-78gw-pv8p RUSTSEC-2023-0035 Apr 24, 2023

Adverserial use of `make_bitflags!` macro can cause undefined behavior

Medium

The macro relied on an expression of the form Enum::Variant always being a variant of the enum. However, it may also be an associated integer constant, in which case there's no guarantee that the value of said constant consists only of bits valid for this bitflag type.

Thus, code like this could create an invalid BitFlags<Test>, which would cause iterating over it to trigger undefined behavior. As the debug formatter internally iterates over the value, it is also affected.

use enumflags2::{bitflags, make_bitflags};

#[bitflags]
#[repr(u8)]
#[derive(Copy, Clone, Debug)]
enum Test {
    A = 1,
    B = 2,
}

impl Test {
    const C: u8 = 69;
}

fn main() {
    let x = make_bitflags!(Test::{C});
    // printing or iterating over x is UB
}

Fixed in


          0.7.7

References

Updated Nov 08, 2023 · Source: OSV.dev

Dec 14, 2021

0.7.1 unknown yanked

1 CVE

GHSA-qvc4-78gw-pv8p RUSTSEC-2023-0035 Apr 24, 2023

Adverserial use of `make_bitflags!` macro can cause undefined behavior

Medium

The macro relied on an expression of the form Enum::Variant always being a variant of the enum. However, it may also be an associated integer constant, in which case there's no guarantee that the value of said constant consists only of bits valid for this bitflag type.

Thus, code like this could create an invalid BitFlags<Test>, which would cause iterating over it to trigger undefined behavior. As the debug formatter internally iterates over the value, it is also affected.

use enumflags2::{bitflags, make_bitflags};

#[bitflags]
#[repr(u8)]
#[derive(Copy, Clone, Debug)]
enum Test {
    A = 1,
    B = 2,
}

impl Test {
    const C: u8 = 69;
}

fn main() {
    let x = make_bitflags!(Test::{C});
    // printing or iterating over x is UB
}

Fixed in


          0.7.7

References

Updated Nov 08, 2023 · Source: OSV.dev

Feb 24, 2021

0.7.0 unknown yanked

1 CVE

GHSA-qvc4-78gw-pv8p RUSTSEC-2023-0035 Apr 24, 2023

Adverserial use of `make_bitflags!` macro can cause undefined behavior

Medium

The macro relied on an expression of the form Enum::Variant always being a variant of the enum. However, it may also be an associated integer constant, in which case there's no guarantee that the value of said constant consists only of bits valid for this bitflag type.

Thus, code like this could create an invalid BitFlags<Test>, which would cause iterating over it to trigger undefined behavior. As the debug formatter internally iterates over the value, it is also affected.

use enumflags2::{bitflags, make_bitflags};

#[bitflags]
#[repr(u8)]
#[derive(Copy, Clone, Debug)]
enum Test {
    A = 1,
    B = 2,
}

impl Test {
    const C: u8 = 69;
}

fn main() {
    let x = make_bitflags!(Test::{C});
    // printing or iterating over x is UB
}

Fixed in


          0.7.7

References

Updated Nov 08, 2023 · Source: OSV.dev

Feb 24, 2021

0.7.0-preview1 unknown

Aug 12, 2020

0.6.4 unknown

Apr 21, 2020

0.6.3 unknown

Apr 11, 2020

0.6.2 unknown

Nov 16, 2019

0.6.1 unknown

Oct 24, 2019

0.6.0 unknown

Oct 04, 2019

0.5.2 unknown

May 02, 2019

0.5.1 unknown

Apr 02, 2019

0.5.0 unknown

Jan 29, 2019

Activity

Details