tracing

Version	Released
`0.1.44` unknown	Dec 18, 2025
`0.1.43` unknown	Nov 28, 2025
`0.1.42` unknown yanked	Nov 26, 2025
`0.1.41` unknown	Nov 27, 2024
`0.1.40` unknown	Oct 19, 2023
`0.1.39` unknown yanked 1 CVE	Oct 13, 2023
`0.1.38` unknown yanked 1 CVE	Apr 25, 2023
`0.1.37` unknown	Oct 06, 2022
`0.1.36` unknown	Jul 29, 2022
`0.1.35` unknown	Jun 08, 2022
`0.1.34` unknown	Apr 14, 2022
`0.1.33` unknown	Apr 09, 2022
`0.1.32` unknown	Mar 09, 2022
`0.1.31` unknown	Feb 17, 2022
`0.1.30` unknown	Feb 04, 2022
`0.1.29` unknown	Oct 06, 2021
`0.1.28` unknown	Sep 17, 2021
`0.1.27` unknown	Sep 13, 2021
`0.1.26` unknown	Apr 30, 2021
`0.1.25` unknown	Feb 23, 2021
`0.1.24` unknown	Feb 17, 2021
`0.1.23` unknown	Feb 04, 2021
`0.1.22` unknown	Nov 23, 2020
`0.1.21` unknown	Sep 28, 2020
`0.1.20` unknown yanked	Aug 24, 2020
`0.1.19` unknown	Aug 11, 2020
`0.1.18` unknown	Jul 31, 2020
`0.1.17` unknown	Jul 22, 2020
`0.1.16` unknown	Jul 08, 2020
`0.1.15` unknown	Jun 03, 2020
`0.1.14` unknown	May 14, 2020
`0.1.13` unknown	Feb 27, 2020
`0.1.12` unknown	Jan 15, 2020
`0.1.11` unknown	Dec 20, 2019
`0.1.10` unknown	Oct 23, 2019
`0.1.9` unknown	Sep 13, 2019
`0.1.8` unknown	Sep 04, 2019
`0.1.7` unknown	Aug 30, 2019
`0.1.6` unknown	Aug 20, 2019
`0.1.5` unknown	Aug 10, 2019
`0.1.4` unknown	Aug 09, 2019
`0.1.3` unknown	Jul 11, 2019
`0.1.2` unknown	Jul 06, 2019
`0.1.1` unknown	Jul 03, 2019
`0.1.0` unknown	Jun 28, 2019
`0.0.0` unknown	Nov 27, 2017

0.1.44 unknown

Dec 18, 2025

0.1.43 unknown

Nov 28, 2025

0.1.42 unknown yanked

Nov 26, 2025

0.1.41 unknown

Nov 27, 2024

0.1.40 unknown

Oct 19, 2023

0.1.39 unknown yanked

1 CVE

GHSA-8f24-6m29-wm2r RUSTSEC-2023-0078 Jan 17, 2024

use-after-free in tracing

Medium

The implementation of the Instrumented::into_inner method in affected versions of this crate contains undefined behavior due to incorrect use of std::mem::forget The function creates *const pointers to self, calls mem::forget(self), and then moves values out of those pointers using std::ptr::read.

// To manually destructure `Instrumented` without `Drop`, we
// move it into a ManuallyDrop and use pointers to its fields
let span: *const Span = &this.span;
let inner: *const ManuallyDrop<T> = &this.inner;
mem::forget(self);
// SAFETY: Those pointers are valid for reads, because `Drop` didn't
//         run, and properly aligned, because `Instrumented` isn't
//         `#[repr(packed)]`.
let _span = unsafe { span.read() };
let inner = unsafe { inner.read() };

However, the mem::forget documentation states:

Any resources the value manages, such as heap memory or a file handle, will linger forever in an unreachable state. However, it does not guarantee that pointers to this memory will remain valid.

This means that these pointers are no longer valid. This could result in a stack use-after-free if LLVM chooses to reuse self's stack slot for a rebinding after the call to std::mem::forget.

This undefined behavior has not been observed to cause miscompilation as of Rust 1.73.0. However, any use of this method with the affected versions of tracing are unsound.

The flaw was corrected in commit 20a1762 (PR #2765) by replacing the use of std::mem::forget with std::mem::ManuallyDrop, ensuring that the stack slot is not reused and the pointers remain valid when they are read. The fix is published in tracing v0.1.40. Affected versions have been yanked from crates.io.

Thanks to Taylor Cramer and Manish Goregaokar for finding and correcting this issue!

Fixed in


          0.1.40

References

Updated Feb 10, 2024 · Source: OSV.dev

Oct 13, 2023

0.1.38 unknown yanked

1 CVE

GHSA-8f24-6m29-wm2r RUSTSEC-2023-0078 Jan 17, 2024

use-after-free in tracing

Medium

The implementation of the Instrumented::into_inner method in affected versions of this crate contains undefined behavior due to incorrect use of std::mem::forget The function creates *const pointers to self, calls mem::forget(self), and then moves values out of those pointers using std::ptr::read.

// To manually destructure `Instrumented` without `Drop`, we
// move it into a ManuallyDrop and use pointers to its fields
let span: *const Span = &this.span;
let inner: *const ManuallyDrop<T> = &this.inner;
mem::forget(self);
// SAFETY: Those pointers are valid for reads, because `Drop` didn't
//         run, and properly aligned, because `Instrumented` isn't
//         `#[repr(packed)]`.
let _span = unsafe { span.read() };
let inner = unsafe { inner.read() };

However, the mem::forget documentation states:

Any resources the value manages, such as heap memory or a file handle, will linger forever in an unreachable state. However, it does not guarantee that pointers to this memory will remain valid.

This means that these pointers are no longer valid. This could result in a stack use-after-free if LLVM chooses to reuse self's stack slot for a rebinding after the call to std::mem::forget.

This undefined behavior has not been observed to cause miscompilation as of Rust 1.73.0. However, any use of this method with the affected versions of tracing are unsound.

The flaw was corrected in commit 20a1762 (PR #2765) by replacing the use of std::mem::forget with std::mem::ManuallyDrop, ensuring that the stack slot is not reused and the pointers remain valid when they are read. The fix is published in tracing v0.1.40. Affected versions have been yanked from crates.io.

Thanks to Taylor Cramer and Manish Goregaokar for finding and correcting this issue!

Fixed in


          0.1.40

References

Updated Feb 10, 2024 · Source: OSV.dev

Apr 25, 2023

0.1.37 unknown

Oct 06, 2022

0.1.36 unknown

Jul 29, 2022

0.1.35 unknown

Jun 08, 2022

0.1.34 unknown

Apr 14, 2022

0.1.33 unknown

Apr 09, 2022

0.1.32 unknown

Mar 09, 2022

0.1.31 unknown

Feb 17, 2022

0.1.30 unknown

Feb 04, 2022

0.1.29 unknown

Oct 06, 2021

0.1.28 unknown

Sep 17, 2021

0.1.27 unknown

Sep 13, 2021

0.1.26 unknown

Apr 30, 2021

0.1.25 unknown

Feb 23, 2021

0.1.24 unknown

Feb 17, 2021

0.1.23 unknown

Feb 04, 2021

0.1.22 unknown

Nov 23, 2020

0.1.21 unknown

Sep 28, 2020

0.1.20 unknown yanked

Aug 24, 2020

0.1.19 unknown

Aug 11, 2020

0.1.18 unknown

Jul 31, 2020

0.1.17 unknown

Jul 22, 2020

0.1.16 unknown

Jul 08, 2020

0.1.15 unknown

Jun 03, 2020

0.1.14 unknown

May 14, 2020

0.1.13 unknown

Feb 27, 2020

0.1.12 unknown

Jan 15, 2020

0.1.11 unknown

Dec 20, 2019

0.1.10 unknown

Oct 23, 2019

0.1.9 unknown

Sep 13, 2019

0.1.8 unknown

Sep 04, 2019

0.1.7 unknown

Aug 30, 2019

0.1.6 unknown

Aug 20, 2019

0.1.5 unknown

Aug 10, 2019

0.1.4 unknown

Aug 09, 2019

0.1.3 unknown

Jul 11, 2019

0.1.2 unknown

Jul 06, 2019

0.1.1 unknown

Jul 03, 2019

0.1.0 unknown

Jun 28, 2019

0.0.0 unknown

Nov 27, 2017

Activity

Details