deardaniel/secdata-raw huggingface dataset:
GitHub Security Advisory: GHSA-c6px-4grw-hrjr
Package: binjs_io (RUST)
Severity: HIGH (CVSS 0.0)
Vulnerable versions: <= 0.2.1
Patched in: unpatched

Summary: 'Read' on uninitialized memory may cause UB

Details:
Affected versions of this crate passes an uninitialized buffer to a user-provided `Read` implementation. The crate currently contains 4 occurrences of such cases. Arbitrary `Read` implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer.
Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.
GitHub Security Advisory: GHSA-5j8w-r7g8-5472
Package: arrow2 (RUST)
Severity: HIGH (CVSS 0.0)
CWE: CWE-415: Double Free
Vulnerable versions: >= 0.9.0, < 0.9.2
Patched in: 0.9.2

Summary: Arrow2 allows double free in `safe` code

Details:
The struct `Ffi_ArrowArray` implements `#derive(Clone)` that is inconsistent with
its custom implementation of `Drop`, resulting in a double free when cloned.

Cloning this struct in `safe` results in a segmentation fault, which is unsound.

This derive was removed from this struct. All users are advised to either:
* bump the patch version of this crate (for versions `v0.7,v0.8,v0.9`), or
* migrate to a more recent version of  the crate (when using `<0.7`).

Doing so elimitates this vulnerability (code no longer compiles).
GitHub Security Advisory: GHSA-5j8w-r7g8-5472
Package: arrow2 (RUST)
Severity: HIGH (CVSS 0.0)
CWE: CWE-415: Double Free
Vulnerable versions: >= 0.8.0, < 0.8.2
Patched in: 0.8.2

Summary: Arrow2 allows double free in `safe` code

Details:
The struct `Ffi_ArrowArray` implements `#derive(Clone)` that is inconsistent with
its custom implementation of `Drop`, resulting in a double free when cloned.

Cloning this struct in `safe` results in a segmentation fault, which is unsound.

This derive was removed from this struct. All users are advised to either:
* bump the patch version of this crate (for versions `v0.7,v0.8,v0.9`), or
* migrate to a more recent version of  the crate (when using `<0.7`).

Doing so elimitates this vulnerability (code no longer compiles).
GitHub Security Advisory: GHSA-5j8w-r7g8-5472
Package: arrow2 (RUST)
Severity: HIGH (CVSS 0.0)
CWE: CWE-415: Double Free
Vulnerable versions: < 0.7.1
Patched in: 0.7.1

Summary: Arrow2 allows double free in `safe` code

Details:
The struct `Ffi_ArrowArray` implements `#derive(Clone)` that is inconsistent with
its custom implementation of `Drop`, resulting in a double free when cloned.

Cloning this struct in `safe` results in a segmentation fault, which is unsound.

This derive was removed from this struct. All users are advised to either:
* bump the patch version of this crate (for versions `v0.7,v0.8,v0.9`), or
* migrate to a more recent version of  the crate (when using `<0.7`).

Doing so elimitates this vulnerability (code no longer compiles).
GitHub Security Advisory: GHSA-qgrp-8f3v-q85p
Package: arrow (RUST)
Severity: HIGH (CVSS 0.0)
Vulnerable versions: < 6.4.0
Patched in: 6.4.0

Summary: `FixedSizeBinaryArray` does not perform bound checks on accessing values and offsets

Details:
`FixedSizeBinaryArray` performs insufficient bounds checks, which allows out-of-bounds reads in safe code.
GitHub Security Advisory: GHSA-h588-76vg-prgj
Package: arrow (RUST)
Severity: HIGH (CVSS 0.0)
Vulnerable versions: < 6.4.0
Patched in: 6.4.0

Summary: `DecimalArray` does not perform bound checks on accessing values and offsets

Details:
`DecimalArray` performs insufficient bounds checks, which allows out-of-bounds reads in safe code if the lenght of the backing buffer is not a multiple of 16.
GitHub Security Advisory: GHSA-qj69-c89v-jwq2
Package: ash (RUST)
Severity: HIGH (CVSS 0.0)
Vulnerable versions: < 0.33.1
Patched in: 0.33.1

Summary: Reading on uninitialized memory may cause UB ( `util::read_spv()` )

Details:
Affected versions of this crate passes an uninitialized buffer to a user-provided `Read` implementation.

Arbitrary `Read` implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer.
Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.
GitHub Security Advisory: GHSA-r7cj-wmwv-hfw5
Package: arrow (RUST)
Severity: HIGH (CVSS 0.0)
Vulnerable versions: < 6.4.0
Patched in: 6.4.0

Summary: `BinaryArray` does not perform bound checks on reading values and offsets

Details:
`BinaryArray` performs insufficient validation on creation, which allows out-of-bounds reads in safe code.
GitHub Security Advisory: GHSA-p2g9-94wh-65c2
Package: ammonia (RUST)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Vulnerable versions: >= 3.0.0, < 3.1.3
Patched in: 3.1.3

Summary: Space bug in `clean_text`

Details:
An incorrect mapping from HTML specification to ASCII codes was used.
Because HTML treats the Form Feed as whitespace, code like this has an injection bug:

    let html = format!("<div title={}>", clean_text(user_supplied_string));

Applications are not affected if they quote their attributes, or if they don't use `clean_text` at all.
GitHub Security Advisory: GHSA-hv9v-7w3v-rj6f
Package: acc_reader (RUST)
Severity: HIGH (CVSS 0.0)
Vulnerable versions: <= 2.0.0
Patched in: unpatched

Summary: `Read` on uninitialized buffer in `fill_buf()` and `read_up_to()`

Details:
Affected versions of this crate passes an uninitialized buffer to a user-provided `Read` implementation.

Arbitrary `Read` implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer.

Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.
GitHub Security Advisory: GHSA-hfxp-p695-629x
Package: abomonation (RUST)
Severity: HIGH (CVSS 0.0)
Vulnerable versions: <= 0.7.3
Patched in: unpatched

Summary: abomonation transmutes &T to and from &[u8] without sufficient constraints

Details:
This transmute is at the core of the abomonation crates. It's so easy to use it to violate alignment requirements that no test in the crate's test suite passes under miri.

The use of this transmute in serialization/deserialization also incorrectly assumes that the layout of a repr(Rust) type is stable.
This transmute can also disclose both the contents of padding bytes which may be an information leak and the contents of pointers, which may be used to defeat ASLR.
GitHub Security Advisory: GHSA-cpqj-r29q-chrh
Package: bam (RUST)
Severity: CRITICAL (CVSS 9.8)
CWE: CWE-191: Integer Underflow (Wrap or Wraparound)
Vulnerable versions: < 0.1.3
Patched in: 0.1.3

Summary: Loading a bgzip block can write out of bounds if size overflows.

Details:
An issue was discovered in the bam crate before 0.1.3 for Rust. There is an integer underflow and out-of-bounds write during the loading of a bgzip block.
GitHub Security Advisory: GHSA-9pqx-g3jh-qpqq
Package: arc-swap (RUST)
Severity: HIGH (CVSS 7.5)
Vulnerable versions: >= 1.0.0, < 1.1.0
Patched in: 1.1.0

Summary: Dangling reference in `access::Map` with Constant

Details:
An issue has been discovered in the arc-swap crate before 0.4.8 (and 1.x before 1.1.0) for Rust. Use of arc_swap::access::Map with the Constant test helper (or with a user-supplied implementation of the Access trait) could sometimes lead to dangling references being returned by the map.
GitHub Security Advisory: GHSA-9pqx-g3jh-qpqq
Package: arc-swap (RUST)
Severity: HIGH (CVSS 7.5)
Vulnerable versions: >= 0.4.2, < 0.4.8
Patched in: 0.4.8

Summary: Dangling reference in `access::Map` with Constant

Details:
An issue has been discovered in the arc-swap crate before 0.4.8 (and 1.x before 1.1.0) for Rust. Use of arc_swap::access::Map with the Constant test helper (or with a user-supplied implementation of the Access trait) could sometimes lead to dangling references being returned by the map.
GitHub Security Advisory: GHSA-gfg9-x6px-r7gr
Package: plutonium (RUST)
Severity: MODERATE (CVSS 0.0)
Vulnerable versions: <= 0.5.2
Patched in: unpatched

Summary: Library exclusively intended to obfuscate code.

Details:
This crate allows you to write safe functions with unsafe bodies without the `unsafe` keyword.

The value this adds is questionable, and hides `unsafe` usages from naive analysis.
GitHub Security Advisory: GHSA-qj3v-q2vj-4c8h
Package: ark-r1cs-std (RUST)
Severity: CRITICAL (CVSS 9.8)
CWE: CWE-682: Incorrect Calculation
Vulnerable versions: >= 0.2.0, < 0.3.1
Patched in: 0.3.1

Summary: Calculation error in ark-r1cs-std

Details:
An issue was discovered in the ark-r1cs-std crate before 0.3.1 for Rust. It does not enforce any constraints in the FieldVar::mul_by_inverse method. Thus, a prover can produce a proof that is unsound but is nonetheless verified.
GitHub Security Advisory: GHSA-gx73-2498-r55c
Package: flatbuffers (RUST)
Severity: CRITICAL (CVSS 9.8)
CWE: CWE-704: Incorrect Type Conversion or Cast
Vulnerable versions: >= 0.4.0, < 0.6.1
Patched in: 0.6.1

Summary: Unsound casting in flatbuffers

Details:
The implementation of impl Follow for bool allows to reinterpret arbitrary bytes as a bool.

In Rust bool has stringent requirements for its in-memory representation. Use of this function allows to violate these requirements and invoke undefined behaviour in safe code.
GitHub Security Advisory: GHSA-g4xg-fxmg-vcg5
Package: grep-cli (RUST)
Severity: CRITICAL (CVSS 9.8)
CWE: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Vulnerable versions: < 0.1.6
Patched in: 0.1.6

Summary: OS command injection in ripgrep

Details:
ripgrep before 13 on Windows allows attackers to trigger execution of arbitrary programs from the current working directory via the -z/--search-zip or --pre flag.
GitHub Security Advisory: GHSA-6rhx-hqxm-8p36
Package: http (RUST)
Severity: CRITICAL (CVSS 9.8)
CWE: CWE-415: Double Free
Vulnerable versions: < 0.1.20
Patched in: 0.1.20

Summary: Double free in http

Details:
An issue was discovered in the http crate before 0.1.20 for Rust. The HeaderMap::Drain API can use a raw pointer, defeating soundness.
GitHub Security Advisory: GHSA-jjx5-3f36-6927
Package: iced-x86 (RUST)
Severity: CRITICAL (CVSS 9.8)
CWE: CWE-131: Incorrect Calculation of Buffer Size
Vulnerable versions: < 1.11.0
Patched in: 1.11.0

Summary: Incorrect buffer size calculation in iced-x86

Details:
An issue was discovered in the iced-x86 crate through 1.10.3 for Rust. In Decoder::new(), slice.get_unchecked(slice.length()) is used unsafely.
GitHub Security Advisory: GHSA-9wgh-vjj7-7433
Package: image (RUST)
Severity: MODERATE (CVSS 5.5)
CWE: CWE-400: Uncontrolled Resource Consumption
Vulnerable versions: < 0.23.12
Patched in: 0.23.12

Summary: Mutable reference with immutable provenance in image

Details:
A mutable reference to a struct was constructed by dereferencing a pointer obtained from slice::as_ptr. Instead, slice::as_mut_ptr should have been called on the mutable slice argument. The former performs an implicit reborrow as an immutable shared reference which does not allow writing through the derived pointer.
GitHub Security Advisory: GHSA-qc36-q22q-cjw3
Package: lettre (RUST)
Severity: CRITICAL (CVSS 9.8)
CWE: CWE-147: Improper Neutralization of Input Terminators
Vulnerable versions: >= 0.7.0, < 0.9.6
Patched in: 0.9.6

Summary: SMTP command injection in lettre

Details:
### Impact

Affected versions of lettre allowed SMTP command injection through an attacker's controlled message body. The module for escaping lines starting with a period wouldn't catch a period that was placed after a double CRLF sequence, allowing the attacker to end the current message and write arbitrary SMTP commands after it.

### Fix

The flaw is fixed by correctly handling consecutive CRLF sequences.

### References

* [RUSTSEC-2021-0069](https://rustsec.org/advisories/RUSTSEC-2021-0069.html)
GitHub Security Advisory: GHSA-96w3-p368-4h8c
Package: internment (RUST)
Severity: HIGH (CVSS 8.1)
CWE: CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Vulnerable versions: >= 0.3.12, < 0.4.0
Patched in: 0.4.0

Summary: Use after free in internment

Details:
ArcIntern::drop has a race condition where it can release memory which is about to get another user. The new user will get a reference to freed memory.

This was fixed by serializing access to an interned object while it is being deallocated.

Versions prior to 0.3.12 used stronger locking which avoided the problem.
GitHub Security Advisory: GHSA-vc2p-r46x-m3vx
Package: lettre (RUST)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')
Vulnerable versions: >= 0.8.0, < 0.8.4
Patched in: 0.8.4

Summary: Argument injection in lettre

Details:
### Impact

Affected versions of lettre allowed argument injection to the sendmail command. It was possible, using forged to addresses, to pass arbitrary arguments to the sendmail executable.

Depending on the implementation (original sendmail, postfix, exim, etc.) it could be possible in some cases to write email data into abritrary files (using sendmail's logging features).

*NOTE*: This vulnerability only affects the sendmail transport. Others, including smtp, are not affected.

### Fix

The flaw is corrected by modifying the executed command to stop parsing arguments before passing the destination addresses.

### References

* [RUSTSEC-2020-0069](https://rustsec.org/advisories/RUSTSEC-2020-0069.html)
* [CVE-2020-28247](https://nvd.nist.gov/vuln/detail/CVE-2020-28247)
GitHub Security Advisory: GHSA-vc2p-r46x-m3vx
Package: lettre (RUST)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')
Vulnerable versions: >= 0.9.0, < 0.9.5
Patched in: 0.9.5

Summary: Argument injection in lettre

Details:
### Impact

Affected versions of lettre allowed argument injection to the sendmail command. It was possible, using forged to addresses, to pass arbitrary arguments to the sendmail executable.

Depending on the implementation (original sendmail, postfix, exim, etc.) it could be possible in some cases to write email data into abritrary files (using sendmail's logging features).

*NOTE*: This vulnerability only affects the sendmail transport. Others, including smtp, are not affected.

### Fix

The flaw is corrected by modifying the executed command to stop parsing arguments before passing the destination addresses.

### References

* [RUSTSEC-2020-0069](https://rustsec.org/advisories/RUSTSEC-2020-0069.html)
* [CVE-2020-28247](https://nvd.nist.gov/vuln/detail/CVE-2020-28247)
GitHub Security Advisory: GHSA-ghpq-vjxw-ch5w
Package: libpulse-binding (RUST)
Severity: HIGH (CVSS 0.0)
CWE: CWE-416: Use After Free
Vulnerable versions: < 1.2.1
Patched in: 1.2.1

Summary: Use after free in libpulse-binding

Details:
### Overview

Version 1.2.1 of the `libpulse-binding` Rust crate, released on the 15th of June 2018, fixed a pair of use-after-free issues with the objects returned by the `get_format_info` and `get_context` methods of `Stream` objects. These objects were mistakenly being constructed without setting an important flag to prevent destruction of the underlying C objects they reference upon their own destruction.

This advisory is being written retrospectively, having previously only been noted in the changelog. No CVE assignment was sought.

### Patches

Users are required to update to version 1.2.1 or newer.

Versions older than 1.2.1 have been yanked from crates.io. This was believed to have already been done at the time of the 1.2.1 release, but upon double checking now they were found to still be available, so has been done now (22nd October 2020).
GitHub Security Advisory: GHSA-39xg-8p43-h76x
Package: reffers (RUST)
Severity: MODERATE (CVSS 4.7)
CWE: CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'), CWE-787: Out-of-bounds Write
Vulnerable versions: < 0.6.1
Patched in: 0.6.1

Summary: Data races in reffers

Details:
ARefss<'a, V> is a type that is assumed to contain objects that are Send + Sync.

In the affected versions of this crate, Send/Sync traits are unconditionally implemented for ARefss<'a, V>.

By using the ARefss::map() API, we can insert a !Send or !Sync object into ARefss<'a, V>. After that, it is possible to create a data race to the inner object of ARefss<'a, V>, which can lead to undefined behavior & memory corruption.

The flaw was corrected in commit `6dd7ca0` by adding trait bound V: Send + Sync to ARefss::map() API.
GitHub Security Advisory: GHSA-x4qm-mcjq-v2gf
Package: prost-types (RUST)
Severity: HIGH (CVSS 7.5)
CWE: CWE-120: Buffer Copy without Checking Size of Input ('Classic Buffer Overflow'), CWE-190: Integer Overflow or Wraparound
Vulnerable versions: < 0.8.0
Patched in: 0.8.0

Summary: Overflow in prost-types

Details:
Affected versions of this crate contained a bug in which untrusted input could cause an overflow and panic when converting a Timestamp to SystemTime. It is recommended to upgrade to prost-types v0.8 and switch the usage of From<Timestamp> for SystemTime to TryFrom<Timestamp> for SystemTime.
GitHub Security Advisory: GHSA-r6ff-2q3c-v3pv
Package: pnet (RUST)
Severity: MODERATE (CVSS 6.0)
CWE: CWE-908: Use of Uninitialized Resource
Vulnerable versions: < 0.27.2
Patched in: 0.27.2

Summary: Compiler optimisation leads to SEGFAULT

Details:
Affected versions of the `pnet` crate were optimized out by compiler, which caused dereference of uninitialized file descriptor which caused segfault.
GitHub Security Advisory: GHSA-45w7-7g63-2m5w
Package: stack_dst (RUST)
Severity: CRITICAL (CVSS 9.8)
CWE: CWE-908: Use of Uninitialized Resource
Vulnerable versions: < 0.6.1
Patched in: 0.6.1

Summary: Drop of uninitialized memory in stack_dst

Details:
Affected versions of stack_dst used a push_inner function that increased the internal length of the array and then called val.clone(). If the val.clone() call panics, the stack could drop an already dropped element or drop uninitialized memory. This issue was fixed in `2a4d538` by increasing the length of the array after elements are cloned.
GitHub Security Advisory: GHSA-62jx-8vmh-4mcw
Package: tar (RUST)
Severity: HIGH (CVSS 7.5)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: < 0.4.36
Patched in: 0.4.36

Summary: Links in archive can create arbitrary directories

Details:
When unpacking a tarball that contains a symlink the tar crate may create directories outside of the directory it's supposed to unpack into. The function errors when it's trying to create a file, but the folders are already created at this point.
GitHub Security Advisory: GHSA-2grh-hm3w-w7hv
Package: tokio (RUST)
Severity: MODERATE (CVSS 5.9)
CWE: CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'), CWE-366: Race Condition within a Thread
Vulnerable versions: >= 0.3.0, < 1.5.1
Patched in: 1.5.1

Summary: Race condition in tokio

Details:
When aborting a task with JoinHandle::abort, the future is dropped in the thread calling abort if the task is not currently being executed. This is incorrect for tasks spawned on a LocalSet. This can easily result in race conditions as many projects use Rc or RefCell in their Tokio tasks for better performance.
GitHub Security Advisory: GHSA-2grh-hm3w-w7hv
Package: tokio (RUST)
Severity: MODERATE (CVSS 5.9)
CWE: CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'), CWE-366: Race Condition within a Thread
Vulnerable versions: >= 1.6.0, < 1.6.3
Patched in: 1.6.3

Summary: Race condition in tokio

Details:
When aborting a task with JoinHandle::abort, the future is dropped in the thread calling abort if the task is not currently being executed. This is incorrect for tasks spawned on a LocalSet. This can easily result in race conditions as many projects use Rc or RefCell in their Tokio tasks for better performance.
GitHub Security Advisory: GHSA-2grh-hm3w-w7hv
Package: tokio (RUST)
Severity: MODERATE (CVSS 5.9)
CWE: CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'), CWE-366: Race Condition within a Thread
Vulnerable versions: >= 1.7.0, < 1.7.2
Patched in: 1.7.2

Summary: Race condition in tokio

Details:
When aborting a task with JoinHandle::abort, the future is dropped in the thread calling abort if the task is not currently being executed. This is incorrect for tasks spawned on a LocalSet. This can easily result in race conditions as many projects use Rc or RefCell in their Tokio tasks for better performance.
GitHub Security Advisory: GHSA-2grh-hm3w-w7hv
Package: tokio (RUST)
Severity: MODERATE (CVSS 5.9)
CWE: CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'), CWE-366: Race Condition within a Thread
Vulnerable versions: >= 1.8.0, < 1.8.1
Patched in: 1.8.1

Summary: Race condition in tokio

Details:
When aborting a task with JoinHandle::abort, the future is dropped in the thread calling abort if the task is not currently being executed. This is incorrect for tasks spawned on a LocalSet. This can easily result in race conditions as many projects use Rc or RefCell in their Tokio tasks for better performance.
GitHub Security Advisory: GHSA-566x-hhrf-qf8m
Package: ordered-float (RUST)
Severity: MODERATE (CVSS 5.5)
CWE: CWE-460: Improper Cleanup on Thrown Exception
Vulnerable versions: >= 0.2.2, < 1.1.1
Patched in: 1.1.1

Summary: ordered_float:NotNan may contain NaN after panic in assignment operators

Details:
After using an assignment operators such as NotNan::add_assign, NotNan::mul_assign, etc., it was possible for the resulting NotNan value to contain a NaN. This could cause undefined behavior in safe code, because the safe NotNan::cmp method contains internal unsafe code that assumes the value is never NaN. (It could also cause undefined behavior in third-party unsafe code that makes the same assumption, as well as logic errors in safe code.)

This was mitigated starting in version 0.4.0, by panicking if the assigned value is NaN. However, in affected versions from 0.4.0 onward, code that uses the NotNan value during unwinding, or that continues after catching the panic, could still observe the invalid value and trigger undefined behavior.

The flaw is fully corrected in versions 1.1.1 and 2.0.1, by ensuring that the assignment operators panic without modifying the operand, if the result would be NaN.
GitHub Security Advisory: GHSA-566x-hhrf-qf8m
Package: ordered-float (RUST)
Severity: MODERATE (CVSS 5.5)
CWE: CWE-460: Improper Cleanup on Thrown Exception
Vulnerable versions: = 2.0.0
Patched in: 2.0.1

Summary: ordered_float:NotNan may contain NaN after panic in assignment operators

Details:
After using an assignment operators such as NotNan::add_assign, NotNan::mul_assign, etc., it was possible for the resulting NotNan value to contain a NaN. This could cause undefined behavior in safe code, because the safe NotNan::cmp method contains internal unsafe code that assumes the value is never NaN. (It could also cause undefined behavior in third-party unsafe code that makes the same assumption, as well as logic errors in safe code.)

This was mitigated starting in version 0.4.0, by panicking if the assigned value is NaN. However, in affected versions from 0.4.0 onward, code that uses the NotNan value during unwinding, or that continues after catching the panic, could still observe the invalid value and trigger undefined behavior.

The flaw is fully corrected in versions 1.1.1 and 2.0.1, by ensuring that the assignment operators panic without modifying the operand, if the result would be NaN.
GitHub Security Advisory: GHSA-rwf4-gx62-rqfw
Package: crossbeam (RUST)
Severity: MODERATE (CVSS 0.0)
Vulnerable versions: < 0.3.0
Patched in: 0.3.0

Summary: `MsQueue` `push`/`pop` use the wrong orderings

Details:
Affected versions of this crate use orderings which are too weak to support this data structure.
It is likely this has caused memory corruption in the wild: <https://github.com/crossbeam-rs/crossbeam/issues/97#issuecomment-412785919>.