Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RUSTSEC-2022-0040: Multiple soundness issues in owning_ref #530

Closed
github-actions bot opened this issue Aug 3, 2022 · 1 comment · Fixed by #661
Closed

RUSTSEC-2022-0040: Multiple soundness issues in owning_ref #530

github-actions bot opened this issue Aug 3, 2022 · 1 comment · Fixed by #661
Assignees
Labels
help wanted Extra attention is needed tech-debt The issue is to improve the current code and make it more clear/generic/reusable/pretty/avoidable.

Comments

@github-actions
Copy link
Contributor

github-actions bot commented Aug 3, 2022

Multiple soundness issues in owning_ref

Details
Package owning_ref
Version 0.4.1
URL https://github.com/noamtashma/owning-ref-unsoundness
Date 2022-01-26
  • OwningRef::map_with_owner is unsound and may result in a use-after-free.
  • OwningRef::map is unsound and may result in a use-after-free.
  • OwningRefMut::as_owner and OwningRefMut::as_owner_mut are unsound and may result in a use-after-free.
  • The crate violates Rust's aliasing rules, which may cause miscompilations on recent compilers that emit the LLVM noalias attribute.

No patched versions are available at this time. While a pull request with some fixes is outstanding, the maintainer appears to be unresponsive.

See advisory page for additional details.

@Voxelot Voxelot added tech-debt The issue is to improve the current code and make it more clear/generic/reusable/pretty/avoidable. help wanted Extra attention is needed labels Aug 15, 2022
@leviathanbeak leviathanbeak self-assigned this Sep 26, 2022
@leviathanbeak
Copy link
Contributor

Investigated this, turns out one of the dependencies of libp2p is using owning-ref but they already moved away from it, so I think updating libp2p to the latest version should solve the issue. Having said that, libp2p itself is going through major refactors so it won't be as simple as bumping the version to the current number.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed tech-debt The issue is to improve the current code and make it more clear/generic/reusable/pretty/avoidable.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants