array-macro

Version	Released
`2.1.8` unknown	Nov 08, 2023
`2.1.7` unknown	Nov 08, 2023
`2.1.6` unknown	Nov 08, 2023
`2.1.5` unknown	May 29, 2022
`2.1.4` unknown	May 29, 2022
`2.1.3` unknown	Apr 27, 2022
`2.1.2` unknown yanked	Apr 27, 2022
`2.1.1` unknown yanked 1 CVE	Jan 27, 2022
`2.1.0` unknown yanked 1 CVE	Mar 26, 2021
`2.0.0` unknown	Dec 31, 2020
`1.0.5` unknown	May 07, 2020
`1.0.4` unknown yanked 1 CVE	Jul 05, 2019
`1.0.3` unknown yanked 1 CVE	Dec 31, 2018
`1.0.2` unknown yanked 1 CVE	Apr 09, 2018
`1.0.1` unknown yanked 1 CVE	Apr 01, 2018
`1.0.0` unknown yanked 1 CVE	Nov 30, 2017
`0.1.2` unknown yanked 1 CVE	Nov 18, 2017
`0.1.1` unknown yanked	Aug 01, 2017
`0.1.0` unknown yanked	Aug 01, 2017

2.1.8 unknown

Nov 08, 2023

2.1.7 unknown

Nov 08, 2023

2.1.6 unknown

Nov 08, 2023

2.1.5 unknown

May 29, 2022

2.1.4 unknown

May 29, 2022

2.1.3 unknown

Apr 27, 2022

2.1.2 unknown yanked

Apr 27, 2022

2.1.1 unknown yanked

1 CVE

Jan 27, 2022

2.1.0 unknown yanked

1 CVE

Mar 26, 2021

2.0.0 unknown

Dec 31, 2020

1.0.5 unknown

May 07, 2020

1.0.4 unknown yanked

1 CVE

GHSA-83gg-pwxf-jr89 RUSTSEC-2020-0161 Jun 16, 2022

`array!` macro is unsound in presence of traits that implement methods it calls internally

Medium

Affected versions of this crate called some methods using auto-ref. The affected code looked like this.

let mut arr = $crate::__core::mem::MaybeUninit::uninit();
let mut vec = $crate::__ArrayVec::<T>::new(arr.as_mut_ptr() as *mut T);

In this case, the problem is that as_mut_ptr is a method of &mut MaybeUninit, not MaybeUninit. This made it possible for traits to hijack the method calls in order to cause unsoundness.

trait AsMutPtr<T> {
    fn as_mut_ptr(&self) -> *mut T;
}
impl<T> AsMutPtr<T> for std::mem::MaybeUninit<T> {
    fn as_mut_ptr(&self) -> *mut T {
        std::ptr::null_mut()
    }
}
array![0; 1];

The flaw was corrected by explicitly referencing variables in macro body in order to avoid auto-ref.

Fixed in


          1.0.5

References

Updated Nov 08, 2023 · Source: OSV.dev

Jul 05, 2019

1.0.3 unknown yanked

1 CVE

GHSA-83gg-pwxf-jr89 RUSTSEC-2020-0161 Jun 16, 2022

`array!` macro is unsound in presence of traits that implement methods it calls internally

Medium

Affected versions of this crate called some methods using auto-ref. The affected code looked like this.

let mut arr = $crate::__core::mem::MaybeUninit::uninit();
let mut vec = $crate::__ArrayVec::<T>::new(arr.as_mut_ptr() as *mut T);

In this case, the problem is that as_mut_ptr is a method of &mut MaybeUninit, not MaybeUninit. This made it possible for traits to hijack the method calls in order to cause unsoundness.

trait AsMutPtr<T> {
    fn as_mut_ptr(&self) -> *mut T;
}
impl<T> AsMutPtr<T> for std::mem::MaybeUninit<T> {
    fn as_mut_ptr(&self) -> *mut T {
        std::ptr::null_mut()
    }
}
array![0; 1];

The flaw was corrected by explicitly referencing variables in macro body in order to avoid auto-ref.

Fixed in


          1.0.5

References

Updated Nov 08, 2023 · Source: OSV.dev

Dec 31, 2018

1.0.2 unknown yanked

1 CVE

GHSA-83gg-pwxf-jr89 RUSTSEC-2020-0161 Jun 16, 2022

`array!` macro is unsound in presence of traits that implement methods it calls internally

Medium

Affected versions of this crate called some methods using auto-ref. The affected code looked like this.

let mut arr = $crate::__core::mem::MaybeUninit::uninit();
let mut vec = $crate::__ArrayVec::<T>::new(arr.as_mut_ptr() as *mut T);

In this case, the problem is that as_mut_ptr is a method of &mut MaybeUninit, not MaybeUninit. This made it possible for traits to hijack the method calls in order to cause unsoundness.

trait AsMutPtr<T> {
    fn as_mut_ptr(&self) -> *mut T;
}
impl<T> AsMutPtr<T> for std::mem::MaybeUninit<T> {
    fn as_mut_ptr(&self) -> *mut T {
        std::ptr::null_mut()
    }
}
array![0; 1];

The flaw was corrected by explicitly referencing variables in macro body in order to avoid auto-ref.

Fixed in


          1.0.5

References

Updated Nov 08, 2023 · Source: OSV.dev

Apr 09, 2018

1.0.1 unknown yanked

1 CVE

GHSA-83gg-pwxf-jr89 RUSTSEC-2020-0161 Jun 16, 2022

`array!` macro is unsound in presence of traits that implement methods it calls internally

Medium

Affected versions of this crate called some methods using auto-ref. The affected code looked like this.

let mut arr = $crate::__core::mem::MaybeUninit::uninit();
let mut vec = $crate::__ArrayVec::<T>::new(arr.as_mut_ptr() as *mut T);

In this case, the problem is that as_mut_ptr is a method of &mut MaybeUninit, not MaybeUninit. This made it possible for traits to hijack the method calls in order to cause unsoundness.

trait AsMutPtr<T> {
    fn as_mut_ptr(&self) -> *mut T;
}
impl<T> AsMutPtr<T> for std::mem::MaybeUninit<T> {
    fn as_mut_ptr(&self) -> *mut T {
        std::ptr::null_mut()
    }
}
array![0; 1];

The flaw was corrected by explicitly referencing variables in macro body in order to avoid auto-ref.

Fixed in


          1.0.5

References

Updated Nov 08, 2023 · Source: OSV.dev

Apr 01, 2018

1.0.0 unknown yanked

1 CVE

GHSA-83gg-pwxf-jr89 RUSTSEC-2020-0161 Jun 16, 2022

`array!` macro is unsound in presence of traits that implement methods it calls internally

Medium

Affected versions of this crate called some methods using auto-ref. The affected code looked like this.

let mut arr = $crate::__core::mem::MaybeUninit::uninit();
let mut vec = $crate::__ArrayVec::<T>::new(arr.as_mut_ptr() as *mut T);

In this case, the problem is that as_mut_ptr is a method of &mut MaybeUninit, not MaybeUninit. This made it possible for traits to hijack the method calls in order to cause unsoundness.

trait AsMutPtr<T> {
    fn as_mut_ptr(&self) -> *mut T;
}
impl<T> AsMutPtr<T> for std::mem::MaybeUninit<T> {
    fn as_mut_ptr(&self) -> *mut T {
        std::ptr::null_mut()
    }
}
array![0; 1];

The flaw was corrected by explicitly referencing variables in macro body in order to avoid auto-ref.

Fixed in


          1.0.5

References

Updated Nov 08, 2023 · Source: OSV.dev

Nov 30, 2017

0.1.2 unknown yanked

1 CVE

GHSA-83gg-pwxf-jr89 RUSTSEC-2020-0161 Jun 16, 2022

`array!` macro is unsound in presence of traits that implement methods it calls internally

Medium

Affected versions of this crate called some methods using auto-ref. The affected code looked like this.

let mut arr = $crate::__core::mem::MaybeUninit::uninit();
let mut vec = $crate::__ArrayVec::<T>::new(arr.as_mut_ptr() as *mut T);

In this case, the problem is that as_mut_ptr is a method of &mut MaybeUninit, not MaybeUninit. This made it possible for traits to hijack the method calls in order to cause unsoundness.

trait AsMutPtr<T> {
    fn as_mut_ptr(&self) -> *mut T;
}
impl<T> AsMutPtr<T> for std::mem::MaybeUninit<T> {
    fn as_mut_ptr(&self) -> *mut T {
        std::ptr::null_mut()
    }
}
array![0; 1];

The flaw was corrected by explicitly referencing variables in macro body in order to avoid auto-ref.

Fixed in


          1.0.5

References

Updated Nov 08, 2023 · Source: OSV.dev

Nov 18, 2017

0.1.1 unknown yanked

Aug 01, 2017

0.1.0 unknown yanked

Aug 01, 2017

Activity

Details