ecosystem
stringclasses 14
values | vuln_id
stringlengths 10
19
| summary
stringlengths 4
267
⌀ | details
stringlengths 9
13.5k
| aliases
stringlengths 17
144
⌀ | modified_date
stringdate 2010-05-27 05:47:00
2022-05-10 08:46:52
| published_date
stringdate 2005-12-31 05:00:00
2022-05-10 08:46:50
| severity
stringclasses 5
values | score
float64 0
10
⌀ | cwe_id
stringclasses 988
values | refs
stringlengths 30
17.7k
⌀ | introduced
stringlengths 75
4.26k
⌀ |
|---|---|---|---|---|---|---|---|---|---|---|---|
crates.io
|
RUSTSEC-2021-0121
|
Non-aligned u32 read in Chacha20 encryption and decryption
|
The implementation does not enforce alignment requirements on input slices while incorrectly assuming 4-byte alignment through an unsafe call to `std::slice::from_raw_parts_mut`, which breaks the contract and introduces undefined behavior.
This affects Chacha20 encryption and decryption in crypto2.
| null |
2021-10-18T16:22:07Z
|
2021-10-08T12:00:00Z
| null | null | null |
{'https://github.com/shadowsocks/crypto2/issues/27', 'https://crates.io/crates/crypto2', 'https://rustsec.org/advisories/RUSTSEC-2021-0121.html'}
| null |
crates.io
|
RUSTSEC-2021-0064
|
`cpuid-bool` has been renamed to `cpufeatures`
|
Please use the `cpufeatures`` crate going forward:
<https://github.com/RustCrypto/utils/tree/master/cpufeatures>
There will be no further releases of `cpuid-bool`.
| null |
2021-05-06T23:45:32Z
|
2021-05-06T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2021-0064.html', 'https://github.com/RustCrypto/utils/pull/381', 'https://crates.io/crates/cpuid-bool'}
| null |
crates.io
|
GHSA-xm9m-2vj8-fmfr
|
Uninitialized memory access in toodee
|
An issue was discovered in the toodee crate before 0.3.0 for Rust. The row-insertion feature allows attackers to read the contents of uninitialized memory locations.
|
{'CVE-2021-28029'}
|
2021-08-30T21:56:39Z
|
2021-09-01T18:30:40Z
|
HIGH
| null |
{'CWE-908'}
|
{'https://rustsec.org/advisories/RUSTSEC-2021-0028.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-28029', 'https://github.com/antonmarsden/toodee'}
| null |
crates.io
|
RUSTSEC-2018-0019
|
Multiple memory safety issues
|
Affected versions contain multiple memory safety issues, such as:
- Unsoundly coercing immutable references to mutable references
- Unsoundly extending lifetimes of strings
- Adding the `Send` marker trait to objects that cannot be safely sent between threads
This may result in a variety of memory corruption scenarios, most likely use-after-free.
A significant refactoring effort has been conducted to resolve these issues.
| null |
2021-08-22T01:18:11Z
|
2018-06-08T12:00:00Z
| null | null | null |
{'https://github.com/actix/actix-web/issues/289', 'https://crates.io/crates/actix-web', 'https://rustsec.org/advisories/RUSTSEC-2018-0019.html'}
| null |
crates.io
|
RUSTSEC-2020-0078
|
`net2` invalidly assumes the memory layout of std::net::SocketAddr
|
The [`net2`](https://crates.io/crates/net2) crate has assumed `std::net::SocketAddrV4`
and `std::net::SocketAddrV6` have the same memory layout as the system C representation
`sockaddr`. It has simply casted the pointers to convert the socket addresses to the
system representation. The standard library does not say anything about the memory
layout, and this will cause invalid memory access if the standard library
changes the implementation. No warnings or errors will be emitted once the
change happens.
|
{'CVE-2020-35919'}
|
2021-10-19T22:14:35Z
|
2020-11-07T12:00:00Z
| null | null | null |
{'https://github.com/deprecrated/net2-rs/issues/105', 'https://crates.io/crates/net2', 'https://rustsec.org/advisories/RUSTSEC-2020-0078.html'}
| null |
crates.io
|
RUSTSEC-2019-0005
|
Format string vulnerabilities in `pancurses`
|
`pancurses::mvprintw` and `pancurses::printw` passes a pointer from a rust `&str` to C,
allowing hostile input to execute a format string attack, which trivially allows writing
arbitrary data to stack memory.
|
{'CVE-2019-15546'}
|
2021-10-19T22:14:35Z
|
2019-06-15T12:00:00Z
| null | null | null |
{'https://github.com/RustSec/advisory-db/issues/106', 'https://crates.io/crates/pancurses', 'https://rustsec.org/advisories/RUSTSEC-2019-0005.html'}
| null |
crates.io
|
GHSA-45p7-c959-rgcm
|
Process crashes when the cell used as DepGroup is not alive
|
### Impact
It's easy to create a malign transaction which uses the dead cell as the DepGroup in the DepCells. The transaction can crash all the receiving nodes.
| null |
2021-08-02T21:57:02Z
|
2021-08-25T21:01:18Z
|
CRITICAL
| null | null |
{'https://github.com/nervosnetwork/ckb/security/advisories/GHSA-45p7-c959-rgcm'}
| null |
crates.io
|
GHSA-ppqp-78xx-3r38
|
Out of bounds write in calamine
|
An issue was discovered in the calamine crate before 0.17.0 for Rust. It allows attackers to overwrite heap-memory locations because Vec::set_len is used without proper memory claiming, and this uninitialized memory is used for a user-provided Read operation, as demonstrated by Sectors::get.
|
{'CVE-2021-26951'}
|
2022-04-26T18:11:53Z
|
2021-08-25T20:53:25Z
|
CRITICAL
| null |
{'CWE-787'}
|
{'https://github.com/tafia/calamine/issues/199', 'https://github.com/tafia/calamine', 'https://nvd.nist.gov/vuln/detail/CVE-2021-26951', 'https://rustsec.org/advisories/RUSTSEC-2021-0015.html'}
| null |
crates.io
|
RUSTSEC-2020-0097
|
Soundness issue with base::Error
|
`base::Error` type contains public field named `ptr`.
With this definition, it is possible to create a `base::Error` with an invalid pointer and trigger memory safety errors
such as use-after-free or double-free with safe Rust.
The users of `xcb` crate are advised not to manipulate the field.
|
{'CVE-2020-36205'}
|
2021-10-19T22:14:35Z
|
2020-12-10T12:00:00Z
| null | null | null |
{'https://crates.io/crates/xcb', 'https://rustsec.org/advisories/RUSTSEC-2020-0097.html', 'https://github.com/rtbo/rust-xcb/issues/93'}
| null |
crates.io
|
GHSA-qpjr-ch72-2qq4
|
Use after free in portaudio-rs
|
An issue was discovered in the portaudio-rs crate through 0.3.1 for Rust. There is a use-after-free with resultant arbitrary code execution because of a lack of unwind safety in stream_callback and stream_finished_callback.
|
{'CVE-2019-16881'}
|
2021-08-19T21:21:17Z
|
2021-08-25T20:45:17Z
|
CRITICAL
| null |
{'CWE-416'}
|
{'https://github.com/mvdnes/portaudio-rs/issues/20', 'https://rustsec.org/advisories/RUSTSEC-2019-0022.html', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16881', 'https://github.com/mvdnes/portaudio-rs'}
| null |
crates.io
|
GHSA-jqqr-c2r2-9cvr
|
Improper Certificate Validation in security-framework
|
An issue was discovered in the security-framework crate before 0.1.12 for Rust. Hostname verification for certificates does not occur if ClientBuilder uses custom root certificates.
|
{'CVE-2017-18588'}
|
2021-08-19T21:25:26Z
|
2021-08-25T20:42:59Z
|
MODERATE
| null |
{'CWE-295'}
|
{'https://github.com/sfackler/rust-security-framework', 'https://github.com/sfackler/rust-security-framework/pull/27', 'https://rustsec.org/advisories/RUSTSEC-2017-0003.html', 'https://nvd.nist.gov/vuln/detail/CVE-2017-18588'}
| null |
crates.io
|
GHSA-32v7-ghpr-c8hg
|
Mishandling of format strings in ncurses
|
An issue was discovered in the ncurses crate for Rust. There are format string issues in printw functions because C format arguments are mishandled.
|
{'CVE-2019-15547'}
|
2021-08-18T17:45:13Z
|
2021-08-25T20:58:47Z
|
HIGH
| null |
{'CWE-134'}
|
{'https://github.com/jeaye/ncurses-rs/issues/172', 'https://rustsec.org/advisories/RUSTSEC-2019-0006.html', 'https://github.com/RustSec/advisory-db/issues/106', 'https://github.com/jeaye/ncurses-rs', 'https://nvd.nist.gov/vuln/detail/CVE-2019-15547'}
| null |
crates.io
|
GHSA-h7qh-3h6f-w79p
|
Unexpected panic in multihash
|
An issue was discovered in the multihash crate before 0.11.3 for Rust. The from_slice parsing code can panic via unsanitized data from a network server.
|
{'CVE-2020-35909'}
|
2021-08-19T20:51:29Z
|
2021-08-25T20:49:41Z
|
HIGH
| null |
{'CWE-20'}
|
{'https://rustsec.org/advisories/RUSTSEC-2020-0068.html', 'https://github.com/multiformats/rust-multihash', 'https://github.com/multiformats/rust-multihash/pull/72', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35909'}
| null |
crates.io
|
RUSTSEC-2021-0033
|
push_cloned can drop uninitialized memory or double free on panic
|
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.
|
{'CVE-2021-28034', 'CVE-2021-28035'}
|
2021-10-19T22:14:35Z
|
2021-02-22T12:00:00Z
| null | null | null |
{'https://github.com/thepowersgang/stack_dst-rs/issues/5', 'https://crates.io/crates/stack_dst', 'https://rustsec.org/advisories/RUSTSEC-2021-0033.html'}
| null |
crates.io
|
RUSTSEC-2019-0013
|
Wrong memory orderings in RwLock potentially violates mutual exclusion
|
Wrong memory orderings inside the RwLock implementation allow for two writers to acquire the lock at the same time. The drop implementation used Ordering::Relaxed, which allows the compiler or CPU to reorder a mutable access on the locked data after the lock has been yielded.
Only users of the RwLock implementation are affected. Users of Once (including users of lazy_static with the `spin_no_std` feature enabled) are NOT affected.
On strongly ordered CPU architectures like x86, the only real way that this would lead to a memory corruption is if the compiler reorders an access after the lock is yielded, which is possible but in practice unlikely. It is a more serious issue on weakly ordered architectures such as ARM which, except in the presence of certain instructions, allow the hardware to decide which accesses are seen at what times. Therefore on an ARM system it is likely that using the wrong memory ordering would result in a memory corruption, even if the compiler itself doesn't reorder the memory accesses in a buggy way.
The flaw was corrected by https://github.com/mvdnes/spin-rs/pull/66.
|
{'CVE-2019-16137'}
|
2021-10-19T22:14:35Z
|
2019-08-27T12:00:00Z
| null | null | null |
{'https://github.com/mvdnes/spin-rs/issues/65', 'https://crates.io/crates/spin', 'https://rustsec.org/advisories/RUSTSEC-2019-0013.html'}
| null |
crates.io
|
GHSA-2f5j-3mhq-xv58
|
Double free in sys-info
|
An issue was discovered in the sys-info crate before 0.8.0 for Rust. sys_info::disk_info calls can trigger a double free.
|
{'CVE-2020-36434'}
|
2021-08-18T20:16:40Z
|
2021-08-25T20:58:15Z
|
CRITICAL
| null |
{'CWE-415'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-36434', 'https://github.com/FillZpp/sys-info-rs', 'https://rustsec.org/advisories/RUSTSEC-2020-0100.html', 'https://github.com/FillZpp/sys-info-rs/issues/63', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/sys-info/RUSTSEC-2020-0100.md'}
| null |
crates.io
|
RUSTSEC-2020-0081
|
`mio` invalidly assumes the memory layout of std::net::SocketAddr
|
The [`mio`](https://crates.io/crates/mio) crate has assumed `std::net::SocketAddrV4`
and `std::net::SocketAddrV6` have the same memory layout as the system C representation
`sockaddr`. It has simply casted the pointers to convert the socket addresses to the
system representation. The standard library does not say anything about the memory
layout, and this will cause invalid memory access if the standard library
changes the implementation. No warnings or errors will be emitted once the
change happens.
|
{'CVE-2020-35922'}
|
2021-10-19T22:14:35Z
|
2020-11-02T12:00:00Z
| null | null | null |
{'https://crates.io/crates/mio', 'https://github.com/tokio-rs/mio/issues/1386', 'https://rustsec.org/advisories/RUSTSEC-2020-0081.html'}
| null |
crates.io
|
GHSA-p46c-w9m3-7qr2
|
Use of Uninitialized Resource in flumedb.
|
An issue was discovered in the flumedb crate through 2021-01-07 for Rust. read_entry may read from uninitialized memory locations.
|
{'CVE-2021-45684'}
|
2022-01-07T16:14:36Z
|
2022-01-06T22:18:35Z
|
CRITICAL
| null |
{'CWE-908'}
|
{'https://github.com/sunrise-choir/flumedb-rs', 'https://nvd.nist.gov/vuln/detail/CVE-2021-45684', 'https://rustsec.org/advisories/RUSTSEC-2021-0086.html', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/flumedb/RUSTSEC-2021-0086.md'}
| null |
crates.io
|
GHSA-hqc8-j86x-2764
|
Off-by-one error in simple-slab
|
An issue was discovered in the simple-slab crate before 0.3.3 for Rust. remove() has an off-by-one error, causing memory leakage and a drop of uninitialized memory.
|
{'CVE-2020-35893'}
|
2021-08-19T21:06:47Z
|
2021-08-25T20:48:33Z
|
HIGH
| null |
{'CWE-193'}
|
{'https://rustsec.org/advisories/RUSTSEC-2020-0039.html', 'https://github.com/nathansizemore/simple-slab', 'https://github.com/nathansizemore/simple-slab/issues/2', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35893'}
| null |
crates.io
|
RUSTSEC-2016-0001
|
SSL/TLS MitM vulnerability due to insecure defaults
|
All versions of rust-openssl prior to 0.9.0 contained numerous insecure defaults
including off-by-default certificate verification and no API to perform hostname
verification.
Unless configured correctly by a developer, these defaults could allow an attacker
to perform man-in-the-middle attacks.
The problem was addressed in newer versions by enabling certificate verification
by default and exposing APIs to perform hostname verification. Use the
`SslConnector` and `SslAcceptor` types to take advantage of these new features
(as opposed to the lower-level `SslContext` type).
|
{'CVE-2016-10931'}
|
2021-10-19T22:14:35Z
|
2016-11-05T12:00:00Z
| null | null | null |
{'https://github.com/sfackler/rust-openssl/releases/tag/v0.9.0', 'https://crates.io/crates/openssl', 'https://rustsec.org/advisories/RUSTSEC-2016-0001.html'}
| null |
crates.io
|
RUSTSEC-2021-0025
|
crate has been renamed to `qjsonrpc`
|
This crate has been renamed from `jsonrpc-quic` to `qjsonrpc`.
The new repository location is:
<https://github.com/maidsafe/sn_api>
| null |
2021-02-15T16:43:30Z
|
2021-02-15T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2021-0025.html', 'https://github.com/maidsafe/sn_api/pull/623', 'https://crates.io/crates/jsonrpc-quic'}
| null |
crates.io
|
GHSA-62jx-8vmh-4mcw
|
Path trav in tar
|
An issue was discovered in the tar crate before 0.4.36 for Rust. When symlinks are present in a TAR archive, extraction can create arbitrary directories via .. traversal.
|
{'CVE-2021-38511'}
|
2021-08-18T20:08:23Z
|
2021-08-25T20:58:23Z
|
HIGH
| null |
{'CWE-22'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-38511', 'https://github.com/alexcrichton/tar-rs', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/tar/RUSTSEC-2021-0080.md', 'https://rustsec.org/advisories/RUSTSEC-2021-0080.html', 'https://github.com/alexcrichton/tar-rs/issues/238'}
| null |
crates.io
|
RUSTSEC-2020-0039
|
`index()` allows out-of-bound read and `remove()` has off-by-one error
|
`Slab::index()` does not perform the boundary checking, which leads to out-of-bound read access. `Slab::remove()` copies an element from an invalid address due to off-by-one error, resulting in memory leakage and uninitialized memory drop.
|
{'CVE-2020-35892', 'CVE-2020-35893'}
|
2021-01-04T17:02:59Z
|
2020-09-03T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2020-0039.html', 'https://github.com/nathansizemore/simple-slab/issues/2', 'https://crates.io/crates/simple-slab'}
| null |
crates.io
|
GHSA-f3mq-99jr-ww4r
|
Multiple mutable pointers in cgc
|
Affected versions of this crate have the following issues:
1. `Ptr` implements `Send` and `Sync` for all types, this can lead to data
races by sending non-thread safe types across threads.
2. `Ptr::get` violates mutable alias rules by returning multiple mutable
references to the same object.
3. `Ptr::write` uses non-atomic writes to the underlying pointer. This means
that when used across threads it can lead to data races.
|
{'CVE-2020-36467'}
|
2021-08-24T18:18:53Z
|
2021-08-25T20:56:16Z
|
MODERATE
| null |
{'CWE-657'}
|
{'https://github.com/playXE/cgc', 'https://github.com/playXE/cgc/issues/5', 'https://rustsec.org/advisories/RUSTSEC-2020-0148.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36467'}
| null |
crates.io
|
GHSA-qgm6-9472-pwq7
|
Integer Overflow in openssl-src
|
Calls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the function call will be 1 (indicating success), but the output length value will be negative. This could cause applications to behave incorrectly or crash. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x).
|
{'CVE-2021-23840'}
|
2022-02-08T21:34:31Z
|
2021-08-25T20:52:19Z
|
HIGH
| null |
{'CWE-190'}
|
{'https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=9b1129239f3ebb1d1c98ce9ed41d5c9476c47cb2', 'https://kc.mcafee.com/corporate/index?page=content&id=SB10366', 'https://www.debian.org/security/2021/dsa-4855', 'https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf', 'https://www.openssl.org/news/secadv/20210216.txt', 'https://lists.apache.org/thread.html/rf4c02775860db415b4955778a131c2795223f61cb8c6a450893651e4@%3Cissues.bookkeeper.apache.org%3E', 'https://www.tenable.com/security/tns-2021-09', 'https://rustsec.org/advisories/RUSTSEC-2021-0057.html', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://www.oracle.com//security-alerts/cpujul2021.html', 'https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=6a51b9e1d0cf0bf8515f7201b68fb0a3482b3dc1', 'https://kb.pulsesecure.net/articles/Pulse_Security_Advisories/SA44846', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23840', 'https://www.tenable.com/security/tns-2021-10', 'https://www.tenable.com/security/tns-2021-03', 'https://lists.apache.org/thread.html/r58af02e294bd07f487e2c64ffc0a29b837db5600e33b6e698b9d696b@%3Cissues.bookkeeper.apache.org%3E', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://github.com/alexcrichton/openssl-src-rs', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://security.netapp.com/advisory/ntap-20210219-0009/', 'https://security.gentoo.org/glsa/202103-03'}
| null |
crates.io
|
GHSA-69fv-gw6g-8ccg
|
Potential memory corruption in arrayfire
|
An issue was discovered in the arrayfire crate before 3.6.0 for Rust. Addition of the repr() attribute to an enum is mishandled, leading to memory corruption.
|
{'CVE-2018-20998'}
|
2021-08-19T21:24:28Z
|
2021-08-25T20:43:26Z
|
CRITICAL
| null |
{'CWE-119'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2018-20998', 'https://github.com/arrayfire/arrayfire-rust', 'https://rustsec.org/advisories/RUSTSEC-2018-0011.html', 'https://github.com/arrayfire/arrayfire-rust/pull/177'}
| null |
crates.io
|
GHSA-pfjq-935c-4895
|
Data races in v9
|
Affected versions of this crate unconditionally implement `Sync` for `SyncRef<T>`.
This definition allows data races if `&T` is accessible through `&SyncRef`.
`SyncRef<T>` derives `Clone` and `Debug`, and the default implementations of those traits access `&T` by invoking `T::clone()` & `T::fmt()`. It is possible to create data races & undefined behavior by concurrently invoking `SyncRef<T>::clone()` or `SyncRef<T>::fmt()` from multiple threads with `T: !Sync`.
| null |
2021-08-18T23:41:25Z
|
2021-08-25T21:00:37Z
|
MODERATE
| null |
{'CWE-362'}
|
{'https://rustsec.org/advisories/RUSTSEC-2020-0127.html', 'https://github.com/purpleposeidon/v9/issues/1'}
| null |
crates.io
|
RUSTSEC-2021-0072
|
Task dropped in wrong thread when aborting `LocalSet` task
|
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.
See [tokio#3929][issue] for more details.
[issue]: https://github.com/tokio-rs/tokio/issues/3929
|
{'CVE-2021-38191'}
|
2021-11-06T20:37:35Z
|
2021-07-07T12:00:00Z
| null | null | null |
{'https://github.com/tokio-rs/tokio/issues/3929', 'https://rustsec.org/advisories/RUSTSEC-2021-0072.html', 'https://crates.io/crates/tokio'}
| null |
crates.io
|
GHSA-qc36-q22q-cjw3
|
SMTP command injection in lettre
|
### 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)
|
{'CVE-2021-38189'}
|
2021-08-18T18:52:26Z
|
2021-07-12T17:03:27Z
|
CRITICAL
| null |
{'CWE-147'}
|
{'https://github.com/lettre/lettre', 'https://github.com/lettre/lettre/security/advisories/GHSA-qc36-q22q-cjw3', 'https://rustsec.org/advisories/RUSTSEC-2021-0069.html', 'https://github.com/lettre/lettre/commit/8bfc20506cc5e098fe6eb3d1cafe3bea791215ce', 'https://github.com/lettre/lettre/pull/627/commits/93458d01fed0ec81c0e7b4e98e6f35961356fae2'}
| null |
crates.io
|
RUSTSEC-2020-0107
|
hashconsing's HConsed lacks Send/Sync bound for its Send/Sync trait.
|
Affected versions of `hashconsing` implements `Send`/`Sync` for its `HConsed` type without restricting it to `Send`able types and `Sync`able types.
This allows non-`Sync` types such as `Cell` to be shared across threads leading to undefined behavior and memory corruption in concurrent programs.
|
{'CVE-2020-36215'}
|
2021-10-19T22:14:35Z
|
2020-11-10T12:00:00Z
| null | null | null |
{'https://crates.io/crates/hashconsing', 'https://rustsec.org/advisories/RUSTSEC-2020-0107.html', 'https://github.com/AdrienChampion/hashconsing/issues/1'}
| null |
crates.io
|
GHSA-3h87-v52r-p9rg
|
Out of bounds write in reorder
|
An issue was discovered in the reorder crate through 2021-02-24 for Rust. swap_index has an out-of-bounds write if an iterator returns a len() that is too small.
|
{'CVE-2021-29941'}
|
2021-08-19T17:17:20Z
|
2021-08-25T20:54:08Z
|
HIGH
| null |
{'CWE-787'}
|
{'https://github.com/tiby312/reorder', 'https://github.com/tiby312/reorder/issues/1', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29941', 'https://rustsec.org/advisories/RUSTSEC-2021-0050.html'}
| null |
crates.io
|
GHSA-4vhw-4rw7-jfpv
|
Path traversal in mozwire
|
An issue was discovered in the mozwire crate through 2020-08-18 for Rust. A ../ directory-traversal situation allows overwriting local files that have .conf at the end of the filename.
|
{'CVE-2020-35883'}
|
2021-08-19T20:56:07Z
|
2021-08-25T20:49:02Z
|
CRITICAL
| null |
{'CWE-22'}
|
{'https://github.com/NilsIrl/MozWire/', 'https://rustsec.org/advisories/RUSTSEC-2020-0030.html', 'https://github.com/NilsIrl/MozWire/issues/14', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35883'}
| null |
crates.io
|
RUSTSEC-2020-0042
|
Missing check in ArrayVec leads to out-of-bounds write.
|
ArrayVec::insert allows insertion of an element into the array object into the
specified index. Due to a missing check on the upperbound of this index, it is
possible to write out of bounds.
|
{'CVE-2020-35895'}
|
2021-10-19T22:14:35Z
|
2020-09-24T12:00:00Z
| null | null | null |
{'https://crates.io/crates/stack', 'https://rustsec.org/advisories/RUSTSEC-2020-0042.html', 'https://github.com/arcnmx/stack-rs/issues/4'}
| null |
crates.io
|
RUSTSEC-2021-0009
|
panic safety issue in `impl TransformContent<S, D> for [S; (2|3|4)]`
|
Affected versions of this crate did not guard against double drop while temporarily duplicating objects' ownership using `ptr::read()`. Upon panic in a user-provided function `conversion`, objects that are copied by `ptr::read()` are dropped twice, leading to memory corruption.
The flaw was corrected in v0.9.2 by using `ManuallyDrop<T>` to enclose objects that are to be temporarily duplicated.
|
{'CVE-2021-25906'}
|
2021-10-19T22:14:35Z
|
2021-01-10T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2021-0009.html', 'https://github.com/liebharc/basic_dsp/issues/47', 'https://crates.io/crates/basic_dsp_matrix'}
| null |
crates.io
|
GHSA-mxv6-q98x-h958
|
Data races in model
|
`Shared` data structure in `model` crate implements `Send` and `Sync` traits regardless of the inner type.
This allows safe Rust code to trigger a data race, which is undefined behavior in Rust.
Users are advised to treat `Shared` as an unsafe type.
It should not be used outside of the testing context,
and care must be taken so that the testing code does not have a data race
besides a race condition that is expected to be caught by the test.
|
{'CVE-2020-36460'}
|
2021-08-24T18:00:46Z
|
2021-08-25T20:56:07Z
|
HIGH
| null |
{'CWE-843', 'CWE-362'}
|
{'https://rustsec.org/advisories/RUSTSEC-2020-0140.html', 'https://github.com/spacejam/model/issues/3', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36460', 'https://github.com/spacejam/model'}
| null |
crates.io
|
RUSTSEC-2020-0150
|
RingBuffer can create multiple mutable references and cause data races
|
The `RingBuffer` type retrieves mutable references from the `DataProvider` in a
non-atomic manner, potentially allowing the creation of multiple mutable
references. `RingBuffer` also implements the `Send` and `Sync` traits for all
types `T`.
This allows undefined behavior from the aliased mutable references as well
as data races.
|
{'CVE-2020-36470'}
|
2022-02-21T21:23:42Z
|
2020-12-17T12:00:00Z
| null | null | null |
{'https://crates.io/crates/disrustor', 'https://rustsec.org/advisories/RUSTSEC-2020-0150.html', 'https://github.com/sklose/disrustor/issues/1'}
| null |
crates.io
|
GHSA-rfgg-vccr-m46m
|
Missing release of memory in sized-chunks
|
An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, clone can have a memory-safety issue upon a panic.
|
{'CVE-2020-25794'}
|
2021-08-19T21:20:37Z
|
2021-08-25T20:45:58Z
|
HIGH
| null |
{'CWE-401'}
|
{'https://github.com/bodil/sized-chunks', 'https://nvd.nist.gov/vuln/detail/CVE-2020-25794', 'https://rustsec.org/advisories/RUSTSEC-2020-0041.html', 'https://github.com/bodil/sized-chunks/issues/11'}
| null |
crates.io
|
RUSTSEC-2020-0015
|
Crash causing Denial of Service attack
|
Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3
handshake may crash due to a NULL pointer dereference as a result of incorrect handling of the
"signature_algorithms_cert" TLS extension. The crash occurs if an invalid or unrecognised signature
algorithm is received from the peer. This could be exploited by a malicious peer in a Denial of
Service attack.
|
{'CVE-2020-1967'}
|
2021-10-19T22:14:35Z
|
2020-04-25T12:00:00Z
| null | null | null |
{'https://crates.io/crates/openssl-src', 'https://rustsec.org/advisories/RUSTSEC-2020-0015.html', 'https://www.openssl.org/news/secadv/20200421.txt'}
| null |
crates.io
|
RUSTSEC-2020-0146
|
arr! macro erases lifetimes
|
Affected versions of this crate allowed unsoundly extending
lifetimes using `arr!` macro. This may result in a variety of
memory corruption scenarios, most likely use-after-free.
|
{'CVE-2020-36465'}
|
2021-10-19T22:14:35Z
|
2020-04-09T12:00:00Z
| null | null | null |
{'https://crates.io/crates/generic-array', 'https://github.com/fizyk20/generic-array/issues/98', 'https://rustsec.org/advisories/RUSTSEC-2020-0146.html'}
| null |
crates.io
|
RUSTSEC-2020-0003
|
rust_sodium is unmaintained; switch to a modern alternative
|
The `rust_sodium` crate is no longer maintained by its current owner, who
advise in the repository readme that they are looking for
someone else to take ownership of it.
We recommend you switch to an alternative crate such as:
- [`sodiumoxide`](https://crates.io/crates/sodiumoxide)
| null |
2020-10-02T01:29:11Z
|
2020-01-20T12:00:00Z
| null | null | null |
{'https://crates.io/crates/rust_sodium', 'https://rustsec.org/advisories/RUSTSEC-2020-0003.html', 'https://github.com/maidsafe/rust_sodium/pull/117'}
| null |
crates.io
|
RUSTSEC-2021-0048
|
StackVec::extend can write out of bounds when size_hint is incorrect
|
`StackVec::extend` used the lower and upper bounds from an Iterator's
`size_hint` to determine how many items to push into the stack based vector.
If the `size_hint` implementation returned a lower bound that was larger than
the upper bound, `StackVec` would write out of bounds and overwrite memory
on the stack. As mentioned by the [size_hint](https://doc.rust-lang.org/std/iter/trait.Iterator.html#provided-methods)
documentation, `size_hint` is mainly for optimization and incorrect
implementations should not lead to memory safety issues.
|
{'CVE-2021-29939'}
|
2021-10-19T22:14:35Z
|
2021-02-19T12:00:00Z
| null | null | null |
{'https://crates.io/crates/stackvector', 'https://rustsec.org/advisories/RUSTSEC-2021-0048.html', 'https://github.com/Alexhuszagh/rust-stackvector/issues/2'}
| null |
crates.io
|
GHSA-c3cw-c387-pj65
|
Double free in crossbeam
|
An issue was discovered in the crossbeam crate before 0.4.1 for Rust. There is a double free because of destructor mishandling.
|
{'CVE-2018-20996'}
|
2021-08-19T21:24:34Z
|
2021-08-25T20:43:21Z
|
CRITICAL
| null |
{'CWE-415'}
|
{'https://rustsec.org/advisories/RUSTSEC-2018-0009.html', 'https://github.com/crossbeam-rs/crossbeam-epoch', 'https://github.com/crossbeam-rs/crossbeam-epoch/issues/82', 'https://nvd.nist.gov/vuln/detail/CVE-2018-20996'}
| null |
crates.io
|
GHSA-r626-fc64-3q28
|
Data race in abox
|
An issue was discovered in the abox crate before 0.4.1 for Rust.
Affected versions of this crate implements `Send`/`Sync` for `AtomicBox<T>` without requiring `T: Send`/`T: Sync`. This allows to create data races to `T: !Sync` and send `T: !Send` to another thread.
Such behavior breaks the compile-time thread safety guarantees of Rust, and allows users to incur undefined behavior using safe Rust (e.g. memory corruption from data race).
The flaw was corrected in commit 34c2b9e by adding trait bound `T: Send` to `Send` impl for `AtomicBox<T>` and trait bound `T: Sync` to `Sync` impl for `AtomicBox<T>`.
|
{'CVE-2020-36441'}
|
2021-08-24T19:15:13Z
|
2021-08-25T20:59:06Z
|
HIGH
| null |
{'CWE-119', 'CWE-362'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-36441', 'https://github.com/SonicFrog/abox/issues/1', 'https://github.com/SonicFrog/abox', 'https://github.com/SonicFrog/abox/pull/2', 'https://rustsec.org/advisories/RUSTSEC-2020-0121.html', 'https://github.com/SonicFrog/abox/commit/34c2b9e'}
| null |
crates.io
|
GHSA-34p9-f4q3-c4r7
|
Improper Certificate Validation in openssl
|
An issue was discovered in the openssl crate before 0.9.0 for Rust. There is an SSL/TLS man-in-the-middle vulnerability because certificate verification is off by default and there is no API for hostname verification.
|
{'CVE-2016-10931'}
|
2021-08-19T21:25:06Z
|
2021-08-25T20:43:11Z
|
HIGH
| null |
{'CWE-295'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2016-10931', 'https://github.com/sfackler/rust-openssl/releases/tag/v0.9.0', 'https://github.com/sfackler/rust-openssl', 'https://rustsec.org/advisories/RUSTSEC-2016-0001.html'}
| null |
crates.io
|
GHSA-pqqp-xmhj-wgcw
|
Data race in crossbeam-deque
|
### Impact
In the affected version of this crate, the result of the race condition is that one or more tasks in the worker queue can be popped twice instead of other tasks that are forgotten and never popped. If tasks are allocated on the heap, this can cause double free and a memory leak. If not, this still can cause a logical bug.
Crates using `Stealer::steal`, `Stealer::steal_batch`, or `Stealer::steal_batch_and_pop` are affected by this issue.
### Patches
This has been fixed in crossbeam-deque 0.8.1 and 0.7.4.
### Credits
This issue was reported and fixed by Maor Kleinberger.
|
{'CVE-2021-32810'}
|
2021-08-10T17:02:12Z
|
2021-08-25T21:01:15Z
|
CRITICAL
| null |
{'CWE-362'}
|
{'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/U3LSN3B43TJSFIOB3QLPBI3RCHRU5BLO/', 'https://github.com/crossbeam-rs/crossbeam', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WGB2H35CTZDHOV3VLC5BM6VFGURLLVRP/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LCIBFGBSL3JSVJQTNEDEIMZGZF23N2KE/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CY5T3FCE4MUYSPKEWICLVJBBODGJ6SZE/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EW5B2VTDVMJ6B3DA4VLMAMW2GGDCE2BK/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OCLMH7B7B2MF55ET4NQNPH7JWISFX4RT/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZQDIBB7VR3ER52FMSMNJPAWNDO5SITCE/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AWHNNBJCU4EHA2X5ZAMJMGLDUYS5FEPP/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RRPKBRXCRNGNMVFQPFD4LM3QKPEMBQQR/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VQZIEJQBV3S72BHD5GKJQF3NVYNRV5CF/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XFBZWCLG7AGLJO4A7K5IMJVPLSWZ5TJP/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AYBSLIYFANZLCYWOGTIYZUM26TJRH7WU/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TFUBWBYCPSSXTJGEAQ67CJUNQJBOCM26/', 'https://github.com/crossbeam-rs/crossbeam/security/advisories/GHSA-pqqp-xmhj-wgcw', 'https://rustsec.org/advisories/RUSTSEC-2021-0093.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7EZILHZDRGDPOBQ4KTW3E5PPMKLHGH5N/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32810'}
| null |
crates.io
|
RUSTSEC-2020-0111
|
may_queue's Queue lacks Send/Sync bound for its Send/Sync trait.
|
Affected versions of `may_queue` implements `Send`/`Sync` for its `Queue` type without restricting it to `Send`able types and `Sync`able types.
This allows non-`Sync` types such as `Cell` to be shared across threads leading to undefined behavior and memory corruption in concurrent programs.
|
{'CVE-2020-36217'}
|
2021-10-19T22:14:35Z
|
2020-11-10T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2020-0111.html', 'https://crates.io/crates/may_queue', 'https://github.com/Xudong-Huang/may/issues/88'}
| null |
crates.io
|
GHSA-4873-36h9-wv49
|
Out-of-bounds read/write and invalid free with `externref`s and GC safepoints in Wasmtime
|
### Impact
There was an invalid free and out-of-bounds read and write bug when running Wasm that uses `externref`s in Wasmtime.
To trigger this bug, Wasmtime needs to be running Wasm that uses `externref`s, the host creates non-null `externrefs`, Wasmtime performs a garbage collection (GC), and there has to be a Wasm frame on the stack that is at a GC safepoint where
* there are no live references at this safepoint, and
* there is a safepoint with live references earlier in this frame's function.
Under this scenario, Wasmtime would incorrectly use the GC stack map for the safepoint from earlier in the function instead of the empty safepoint. This would result in Wasmtime treating arbitrary stack slots as `externref`s that needed to be rooted for GC. At the *next* GC, it would be determined that nothing was referencing these bogus `externref`s (because nothing could ever reference them, because they are not really `externref`s) and then Wasmtime would deallocate them and run `<ExternRef as Drop>::drop` on them. This results in a free of memory that is not necessarily on the heap (and shouldn't be freed at this moment even if it was), as well as potential out-of-bounds reads and writes.
Even though support for `externref`s (via the reference types proposal) is enabled by default, unless you are creating non-null `externref`s in your host code or explicitly triggering GCs, you cannot be affected by this bug.
We have reason to believe that the effective impact of this bug is relatively small because usage of `externref` is currently quite rare.
### Patches
This bug has been patched and users should upgrade to Wasmtime version 0.30.0.
Additionally, we have updated [our primary `externref` fuzz target](https://github.com/bytecodealliance/wasmtime/blob/37c094faf53f1b356aab3c79d451395e4f7edb34/fuzz/fuzz_targets/table_ops.rs) such that it better exercises these code paths and we can have greater confidence in their correctness going forward.
### Workarounds
If you cannot upgrade Wasmtime at this time, you can avoid this bug by disabling the reference types proposal by passing `false` to [`wasmtime::Config::wasm_reference_types`](https://docs.rs/wasmtime/0.29.0/wasmtime/struct.Config.html#method.wasm_reference_types)
### References
* [The Wasm reference types proposal, which introduces `externref`](https://github.com/WebAssembly/reference-types/)
### For more information
If you have any questions or comments about this advisory:
* Reach out to us on [the Bytecode Alliance Zulip chat](https://bytecodealliance.zulipchat.com/#narrow/stream/217126-wasmtime)
* Open an issue in [the `bytecodealliance/wasmtime` repository](https://github.com/bytecodealliance/wasmtime/)
|
{'CVE-2021-39218'}
|
2021-09-17T20:05:58Z
|
2021-09-20T19:54:16Z
|
MODERATE
| null |
{'CWE-590', 'CWE-125', 'CWE-787'}
|
{'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WAVBRYDDUIY2ZR3K3FO4BVYJKIMJ5TP7/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39218', 'https://github.com/bytecodealliance/wasmtime', 'https://github.com/bytecodealliance/wasmtime/commit/398a73f0dd862dbe703212ebae8e34036a18c11c', 'https://crates.io/crates/wasmtime', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Z2Z33FTXFQ6EOINVEQIP4DFBG53G5XIY/', 'https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-4873-36h9-wv49'}
| null |
crates.io
|
RUSTSEC-2019-0029
|
ChaCha20 counter overflow can expose repetitions in the keystream
|
The ChaCha20 stream cipher can produce a maximum of 2^32 blocks (~256GB)
before the 32-bit counter overflows. Releases of the `chacha20` crate prior
to v0.2.3 allow generating keystreams larger than this, including seeking
past the limit. When this occurs, the keystream is duplicated, with failure
modes similar to nonce reuse (i.e. exposure of the XOR of two plaintexts).
The v0.2.3 release now panics in this event, rather than exposing the
duplicated keystream. Note this is a "hot fix" solution to the problem
and future releases will pursue returning an error in this case.
Users of the `chacha20poly1305` crate are unaffected by this as this crate
properly asserts the length of the plaintext is less than the maximum allowed
(`P_MAX` as described in RFC 8439 Section 2.8).
|
{'CVE-2019-25005'}
|
2021-10-19T22:14:35Z
|
2019-10-22T12:00:00Z
| null | null | null |
{'https://crates.io/crates/chacha20', 'https://rustsec.org/advisories/RUSTSEC-2019-0029.html', 'https://github.com/RustCrypto/stream-ciphers/pull/64'}
| null |
crates.io
|
GHSA-rm4w-6696-r77p
|
nb-connect invalidly assumes the memory layout of std::net::SocketAddr
|
An issue was discovered in the nb-connect crate before 1.0.3 for Rust. It may have invalid memory access for certain versions of the standard library because it relies on a direct cast of std::net::SocketAddrV4 and std::net::SocketAddrV6 data structures.
|
{'CVE-2021-27376'}
|
2021-08-19T17:34:37Z
|
2021-08-25T20:52:14Z
|
CRITICAL
| null |
{'CWE-119'}
|
{'https://rustsec.org/advisories/RUSTSEC-2021-0021.html', 'https://github.com/smol-rs/nb-connect', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27376', 'https://github.com/smol-rs/nb-connect/issues/1'}
| null |
crates.io
|
GHSA-8q2v-67v7-6vc6
|
Data races in rocket
|
An issue was discovered in the rocket crate before 0.4.5 for Rust. LocalRequest::clone creates more than one mutable references to the same object, possibly causing a data race.
|
{'CVE-2020-35882'}
|
2021-08-19T21:07:49Z
|
2021-08-25T20:48:07Z
|
HIGH
| null |
{'CWE-362'}
|
{'https://github.com/SergioBenitez/Rocket/issues/1312', 'https://rustsec.org/advisories/RUSTSEC-2020-0028.html', 'https://github.com/SergioBenitez/Rocket', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35882'}
| null |
crates.io
|
GHSA-9783-42pm-x5jq
|
Use of Uninitialized Resource in csv-sniffer.
|
An issue was discovered in the csv-sniffer crate through 2021-01-05 for Rust. preamble_skipcount may read from uninitialized memory locations.
|
{'CVE-2021-45686'}
|
2022-01-07T17:33:33Z
|
2022-01-06T22:13:58Z
|
CRITICAL
| null |
{'CWE-908'}
|
{'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/csv-sniffer/RUSTSEC-2021-0088.md', 'https://github.com/jblondin/csv-sniffer', 'https://nvd.nist.gov/vuln/detail/CVE-2021-45686', 'https://rustsec.org/advisories/RUSTSEC-2021-0088.html'}
| null |
crates.io
|
GHSA-x3v2-fgr6-3wmm
|
Double free in fil-ocl
|
An issue was discovered in the fil-ocl crate through 2021-01-04 for Rust. From<EventList> can lead to a double free.
|
{'CVE-2021-25908'}
|
2021-08-19T18:40:57Z
|
2021-08-25T20:53:03Z
|
HIGH
| null |
{'CWE-415'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-25908', 'https://rustsec.org/advisories/RUSTSEC-2021-0011.html', 'https://github.com/cogciprocate/ocl/issues/194', 'https://github.com/filecoin-project/fil-ocl'}
| null |
crates.io
|
GHSA-m57c-4vvx-gjgq
|
Format string vulnerabilities in pancurses
|
An issue was discovered in the pancurses crate through 0.16.1 for Rust. printw and mvprintw have format string vulnerabilities.
|
{'CVE-2019-15546'}
|
2021-08-18T17:45:17Z
|
2021-08-25T20:58:27Z
|
HIGH
| null |
{'CWE-134'}
|
{'https://github.com/ihalila/pancurses/issues/66', 'https://rustsec.org/advisories/RUSTSEC-2019-0005.html', 'https://nvd.nist.gov/vuln/detail/CVE-2019-15546', 'https://github.com/RustSec/advisory-db/issues/106', 'https://github.com/ihalila/pancurses'}
| null |
crates.io
|
RUSTSEC-2021-0087
|
columnar: `Read` on uninitialized buffer may cause UB (ColumnarReadExt::read_typed_vec())
|
Affected versions of this crate passes an uninitialized buffer to a user-provided `Read` implementation (`ColumnarReadExt::read_typed_vec()`).
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.
| null |
2021-08-22T01:27:48Z
|
2021-01-07T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2021-0087.html', 'https://github.com/frankmcsherry/columnar/issues/6', 'https://crates.io/crates/columnar'}
| null |
crates.io
|
RUSTSEC-2018-0015
|
term is looking for a new maintainer
|
The author of the `term` crate does not have time to maintain it and is looking
for a new maintainer.
Some maintained alternatives you can potentially switch to instead, depending
on your needs:
- [`crossterm`](https://github.com/crossterm-rs/crossterm)
- [`termcolor`](https://crates.io/crates/termcolor)
- [`yansi`](https://crates.io/crates/yansi)
| null |
2020-10-02T01:29:11Z
|
2018-11-19T12:00:00Z
| null | null | null |
{'https://github.com/Stebalien/term/issues/93', 'https://crates.io/crates/term', 'https://rustsec.org/advisories/RUSTSEC-2018-0015.html'}
| null |
crates.io
|
RUSTSEC-2021-0068
|
Soundness issue in `iced-x86` versions <= 1.10.3
|
Versions of iced-x86 <= 1.10.3 invoke undefined behavior which may cause soundness
issues in crates using the `iced_x86::Decoder` struct. The `Decoder::new()` function
made a call to `slice.get_unchecked(slice.length())` to get the end position of
the input buffer. The flaw was fixed with safe logic that does not invoke undefined
behavior.
More details can be found at <https://github.com/icedland/iced/issues/168>.
|
{'CVE-2021-38188'}
|
2021-11-06T20:37:35Z
|
2021-05-19T12:00:00Z
| null | null | null |
{'https://github.com/icedland/iced/issues/168', 'https://crates.io/crates/iced-x86', 'https://rustsec.org/advisories/RUSTSEC-2021-0068.html'}
| null |
crates.io
|
RUSTSEC-2020-0023
|
Lifetime boundary for `raw_slice` and `raw_slice_mut` are incorrect
|
The affected version of `rulinalg` has incorrect lifetime boundary definitions
for `RowMut::raw_slice` and `RowMut::raw_slice_mut`. They do not conform with
Rust's borrowing rule and allows the user to create multiple mutable references
to the same location. This may result in unexpected calculation result and data
race if both references are used at the same time.
|
{'CVE-2020-35879'}
|
2021-10-19T22:14:35Z
|
2020-02-11T12:00:00Z
| null | null | null |
{'https://crates.io/crates/rulinalg', 'https://github.com/AtheMathmo/rulinalg/issues/201', 'https://rustsec.org/advisories/RUSTSEC-2020-0023.html'}
| null |
crates.io
|
RUSTSEC-2017-0007
|
lz4-compress is unmaintained
|
[According to the developers](https://gitlab.redox-os.org/redox-os/tfs/issues/89) this crate is no longer maintained.
The suggested alternative is [`lz4-compression`](https://crates.io/crates/lz4-compression), a maintained fork of `lz4-compress`.
See also [lz-fear](https://crates.io/crates/lz-fear) which is compatible with the reference LZ4 implementation in C, but not with lz4-compress.
| null |
2020-10-02T01:29:11Z
|
2017-04-17T12:00:00Z
| null | null | null |
{'https://gitlab.redox-os.org/redox-os/tfs/issues/89', 'https://rustsec.org/advisories/RUSTSEC-2017-0007.html', 'https://crates.io/crates/lz4-compress'}
| null |
crates.io
|
GHSA-7qcc-g2m9-8533
|
Null pointer deference in fltk
|
An issue was discovered in the fltk crate before 0.15.3 for Rust. There is a NULL pointer dereference during attempted use of a non-raster image for a window icon.
|
{'CVE-2021-28307'}
|
2021-08-19T17:22:29Z
|
2021-08-25T20:53:53Z
|
HIGH
| null |
{'CWE-476'}
|
{'https://github.com/MoAlyousef/fltk-rs/issues/519', 'https://github.com/MoAlyousef/fltk-rs', 'https://rustsec.org/advisories/RUSTSEC-2021-0038.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-28307'}
| null |
crates.io
|
GHSA-76w9-p8mg-j927
|
Out-of-bounds Write in nix
|
An issue was discovered in the nix crate before 0.20.2, 0.21.x before 0.21.2, and 0.22.x before 0.22.2 for Rust. unistd::getgrouplist has an out-of-bounds write if a user is in more than 16 /etc/groups groups.
|
{'CVE-2021-45707'}
|
2022-01-07T18:28:40Z
|
2022-01-06T22:07:14Z
|
CRITICAL
| null |
{'CWE-787'}
|
{'https://github.com/nix-rust/nix', 'https://nvd.nist.gov/vuln/detail/CVE-2021-45707', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/nix/RUSTSEC-2021-0119.md', 'https://rustsec.org/advisories/RUSTSEC-2021-0119.html'}
| null |
crates.io
|
RUSTSEC-2019-0009
|
Double-free and use-after-free in SmallVec::grow()
|
Attempting to call `grow` on a spilled SmallVec with a value equal to the current capacity causes it to free the existing data. This performs a double free immediately and may lead to use-after-free on subsequent accesses to the SmallVec contents.
An attacker that controls the value passed to `grow` may exploit this flaw to obtain memory contents or gain remote code execution.
Credits to @ehuss for discovering, reporting and fixing the bug.
|
{'CVE-2019-15551'}
|
2021-10-19T22:14:35Z
|
2019-06-06T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2019-0009.html', 'https://github.com/servo/rust-smallvec/issues/148', 'https://crates.io/crates/smallvec'}
| null |
crates.io
|
RUSTSEC-2020-0074
|
Reference counting error in `From<Py<T>>`
|
A bug in `From<Py<T>>` would lead to an extra reference count decrement, often
leading to use-after-free issues.
|
{'CVE-2020-35917'}
|
2021-10-19T22:14:35Z
|
2020-11-28T12:00:00Z
| null | null | null |
{'https://github.com/PyO3/pyo3/pull/1297', 'https://rustsec.org/advisories/RUSTSEC-2020-0074.html', 'https://crates.io/crates/pyo3'}
| null |
crates.io
|
RUSTSEC-2020-0131
|
Send/Sync bound needed on T for Send/Sync impl of RcuCell<T>
|
Affected versions of this crate unconditionally implement Send/Sync for `RcuCell<T>`.
This allows users to send `T: !Send` to other threads (while `T` enclosed within `RcuCell<T>`), and allows users to concurrently access `T: !Sync` by using the APIs of `RcuCell<T>` that provide access to `&T`.
This can result in memory corruption caused by data races.
|
{'CVE-2020-36451'}
|
2021-10-19T22:14:35Z
|
2020-11-14T12:00:00Z
| null | null | null |
{'https://crates.io/crates/rcu_cell', 'https://rustsec.org/advisories/RUSTSEC-2020-0131.html', 'https://github.com/Xudong-Huang/rcu_cell/issues/3'}
| null |
crates.io
|
GHSA-rh89-x75f-rh3c
|
Exposure of uninitialized memory in memoffset
|
An issue was discovered in the memoffset crate before 0.5.0 for Rust. offset_of and span_of can cause exposure of uninitialized memory.
|
{'CVE-2019-15553'}
|
2021-08-19T21:23:41Z
|
2021-08-25T20:44:00Z
|
HIGH
| null |
{'CWE-908'}
|
{'https://github.com/Gilnaa/memoffset', 'https://nvd.nist.gov/vuln/detail/CVE-2019-15553', 'https://rustsec.org/advisories/RUSTSEC-2019-0011.html', 'https://github.com/Gilnaa/memoffset/issues/9#issuecomment-505461490'}
| null |
crates.io
|
GHSA-2969-8hh9-57jc
|
Allocation of Resources Without Limits or Throttling in ckb
|
An issue was discovered in the ckb crate before 0.40.0 for Rust. Remote attackers may be able to conduct a 51% attack against the Nervos CKB blockchain by triggering an inability to allocate memory for the misbehavior HashMap.
|
{'CVE-2021-45699'}
|
2022-01-07T17:53:54Z
|
2022-01-06T22:09:49Z
|
HIGH
| null |
{'CWE-770'}
|
{'https://rustsec.org/advisories/RUSTSEC-2021-0108.html', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/ckb/RUSTSEC-2021-0108.md', 'https://nvd.nist.gov/vuln/detail/CVE-2021-45699', 'https://github.com/nervosnetwork/ckb'}
| null |
crates.io
|
RUSTSEC-2021-0029
|
Tape::take_bytes exposes uninitialized memory to a user-provided Read
|
Affected versions of this crate passed an unininitialized buffer to a
user-provided `Read` instance in `Tape::take_bytes`.
This can result in safe `Read` implementations reading from the uninitialized
buffer leading to undefined behavior.
The flaw was corrected in commit `1f2dc7f37dd` by removing the unsafe block
and zero-initializing the buffer.
|
{'CVE-2021-28030'}
|
2021-10-19T22:14:35Z
|
2021-02-17T12:00:00Z
| null | null | null |
{'https://crates.io/crates/truetype', 'https://github.com/bodoni/truetype/issues/11', 'https://rustsec.org/advisories/RUSTSEC-2021-0029.html'}
| null |
crates.io
|
RUSTSEC-2020-0062
|
Improper `Sync` implementation on `FuturesUnordered` in futures-utils can cause data corruption
|
Affected versions of the crate had an unsound `Sync` implementation on the `FuturesUnordered` structure, which used a `Cell` for
interior mutability without any code to handle synchronized access to the underlying task list's length and head safely.
This could of lead to data corruption since two threads modifying the list at once could see incorrect values due to the lack
of access synchronization.
The issue was fixed by adding access synchronization code around insertion of tasks into the list.
|
{'CVE-2020-35908'}
|
2021-10-19T22:14:35Z
|
2020-01-24T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2020-0062.html', 'https://crates.io/crates/futures-util', 'https://github.com/rust-lang/futures-rs/issues/2050'}
| null |
crates.io
|
GHSA-c3m3-c39q-pv23
|
Out of bounds write in slice-deque
|
An issue was discovered in the slice-deque crate before 0.2.0 for Rust. There is memory corruption in certain allocation cases.
|
{'CVE-2019-15543'}
|
2021-08-19T21:23:28Z
|
2021-08-25T20:44:10Z
|
CRITICAL
| null |
{'CWE-787'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2019-15543', 'https://github.com/gnzlbg/slice_deque/issues/57', 'https://rustsec.org/advisories/RUSTSEC-2019-0002.html', 'https://github.com/gnzlbg/slice_deque'}
| null |
crates.io
|
GHSA-3jc5-5hc5-33gj
|
Data races in conquer-once
|
An issue was discovered in the conquer-once crate before 0.3.2 for Rust. Thread crossing can occur for a non-Send but Sync type, leading to memory corruption.
|
{'CVE-2020-36208'}
|
2021-08-19T18:51:18Z
|
2021-08-25T20:50:49Z
|
HIGH
| null |
{'CWE-662', 'CWE-787'}
|
{'https://github.com/oliver-giersch/conquer-once/issues/3', 'https://github.com/oliver-giersch/conquer-once', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36208', 'https://rustsec.org/advisories/RUSTSEC-2020-0101.html'}
| null |
crates.io
|
GHSA-wr55-mf5c-hhwm
|
Data races in late-static
|
An issue was discovered in the late-static crate before 0.4.0 for Rust. Because Sync is implemented for LateStatic with T: Send, a data race can occur.
|
{'CVE-2020-36209'}
|
2021-08-19T18:52:13Z
|
2021-08-25T20:50:44Z
|
HIGH
| null |
{'CWE-662'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-36209', 'https://github.com/Richard-W/late-static', 'https://github.com/Richard-W/late-static/issues/1', 'https://rustsec.org/advisories/RUSTSEC-2020-0102.html'}
| null |
crates.io
|
RUSTSEC-2020-0127
|
SyncRef's clone() and debug() allow data races
|
Affected versions of this crate unconditionally implement `Sync` for `SyncRef<T>`.
This definition allows data races if `&T` is accessible through `&SyncRef`.
`SyncRef<T>` derives `Clone` and `Debug`, and the default implementations of those traits access `&T` by invoking `T::clone()` & `T::fmt()`. It is possible to create data races & undefined behavior by concurrently invoking `SyncRef<T>::clone()` or `SyncRef<T>::fmt()` from multiple threads with `T: !Sync`.
|
{'CVE-2020-36447'}
|
2021-10-19T22:14:35Z
|
2020-12-18T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2020-0127.html', 'https://crates.io/crates/v9', 'https://github.com/purpleposeidon/v9/issues/1'}
| null |
crates.io
|
RUSTSEC-2021-0091
|
Reading on uninitialized buffer may cause UB ( `gfx_auxil::read_spirv()` )
|
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.
| null |
2021-08-22T01:39:27Z
|
2021-01-07T12:00:00Z
| null | null | null |
{'https://github.com/gfx-rs/gfx/issues/3567', 'https://crates.io/crates/gfx-auxil', 'https://rustsec.org/advisories/RUSTSEC-2021-0091.html'}
| null |
crates.io
|
GHSA-gm68-g349-gxgg
|
Denial of service in bingrep
|
Bingrep v0.8.5 was discovered to contain a memory allocation failure which can cause a Denial of Service (DoS).
|
{'CVE-2021-39480'}
|
2022-01-28T22:20:30Z
|
2022-01-28T22:35:16Z
|
MODERATE
| null |
{'CWE-770'}
|
{'https://github.com/m4b/bingrep', 'https://github.com/m4b/bingrep/issues/30', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39480'}
| null |
crates.io
|
GHSA-rxr4-x558-x7hw
|
Double free in smallvec
|
An issue was discovered in the smallvec crate before 0.6.3 for Rust. The Iterator implementation mishandles destructors, leading to a double free.
|
{'CVE-2018-20991'}
|
2021-08-19T21:25:34Z
|
2021-08-25T20:42:54Z
|
CRITICAL
| null |
{'CWE-415'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2018-20991', 'https://github.com/servo/rust-smallvec/issues/96', 'https://rustsec.org/advisories/RUSTSEC-2018-0003.html', 'https://github.com/servo/rust-smallvec'}
| null |
crates.io
|
GHSA-39wr-f4ff-xm6p
|
Incorrect implementation in streebog
|
An issue was discovered in the streebog crate before 0.8.0 for Rust. The Streebog hash function can cause a panic.
|
{'CVE-2019-25007'}
|
2021-08-19T21:19:50Z
|
2021-08-25T20:46:41Z
|
HIGH
| null |
{'CWE-617'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2019-25007', 'https://github.com/RustCrypto/hashes/pull/91', 'https://rustsec.org/advisories/RUSTSEC-2019-0030.html', 'https://github.com/RustCrypto/hashes/tree/master/streebog'}
| null |
crates.io
|
GHSA-vc2p-r46x-m3vx
|
Argument injection in lettre
|
### 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)
|
{'CVE-2020-28247'}
|
2021-08-18T20:59:57Z
|
2021-08-25T20:56:48Z
|
MODERATE
| null |
{'CWE-77'}
|
{'https://github.com/RustSec/advisory-db/pull/478/files', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28247', 'https://github.com/lettre/lettre', 'https://github.com/lettre/lettre/pull/508/commits/bbe7cc5381c5380b54fb8bbb4f77a3725917ff0b', 'https://github.com/lettre/lettre/security/advisories/GHSA-vc2p-r46x-m3vx', 'https://rustsec.org/advisories/RUSTSEC-2020-0069.html'}
| null |
crates.io
|
RUSTSEC-2018-0003
|
Possible double free during unwinding in SmallVec::insert_many
|
If an iterator passed to `SmallVec::insert_many` panicked in `Iterator::next`,
destructors were run during unwinding while the vector was in an inconsistent
state, possibly causing a double free (a destructor running on two copies of
the same value).
This is fixed in smallvec 0.6.3 by ensuring that the vector's length is not
updated to include moved items until they have been removed from their
original positions. Items may now be leaked if `Iterator::next` panics, but
they will not be dropped more than once.
Thank you to @Vurich for reporting this bug.
|
{'CVE-2018-20991'}
|
2021-10-19T22:14:35Z
|
2018-07-19T12:00:00Z
| null | null | null |
{'https://github.com/servo/rust-smallvec/issues/96', 'https://rustsec.org/advisories/RUSTSEC-2018-0003.html', 'https://crates.io/crates/smallvec'}
| null |
crates.io
|
RUSTSEC-2020-0035
|
Chunk API does not respect align requirement
|
Chunk API does not respect the align requirement of types. Unaligned reference can be created with the API, which is an undefined behavior.
|
{'CVE-2020-36433'}
|
2021-10-19T22:14:35Z
|
2020-08-25T12:00:00Z
| null | null | null |
{'https://crates.io/crates/chunky', 'https://rustsec.org/advisories/RUSTSEC-2020-0035.html', 'https://github.com/aeplay/chunky/issues/2'}
| null |
crates.io
|
GHSA-88xq-w8cq-xfg7
|
Invalid drop of partially-initialized instances in the pooling instance allocator for modules with defined `externref` globals
|
### Impact
There exists a bug in the pooling instance allocator in Wasmtime's runtime where a failure to instantiate an instance for a module that defines an `externref` global will result in an invalid drop of a `VMExternRef` via an uninitialized pointer.
As instance slots may be reused between consecutive instantiations, the value of the uninitialized pointer may be from a previous instantiation and therefore under the control of an attacker via a module's initial values for its globals. If the attacker can somehow determine an address under their control inside the mapped memory representing the instance pool, it is possible to trick the runtime to call `drop_in_place` on a trait object under the attacker's control and therefore cause remote code execution.
Exploiting the bug to cause remote code execution would be very difficult as attackers cannot determine the addresses of globals from code executing within the WebAssembly VM and the memory space for the instance pool cannot be statically determined. Operating system mitigations, such as [address space layout randomization](https://en.wikipedia.org/wiki/Address_space_layout_randomization), would additionally increase the difficulty for attackers to determine useful executable code to target with an exploit. It is also very unlikely that attackers will be able to directly influence the conditions that trigger the bug as described below.
When the conditions to trigger the bug are met, however, it is much easier to exploit this bug to cause a denial of service by crashing the host with an invalid memory read.
The following engine configuration (via [Config](https://docs.rs/wasmtime/0.34.0/wasmtime/struct.Config.html)) is required to be impacted by this bug:
* support for the reference types proposal must be enabled (this is the default for `Config`).
* a pooling allocation strategy must be configured via [Config::allocation_strategy](https://docs.rs/wasmtime/0.34.0/wasmtime/struct.Config.html#method.allocation_strategy), which is **not the default allocation strategy**.
A module must be instantiated with **all the following characteristics**:
* The module defines at least one table or memory.
* The module defines at least one `externref` global.
During instantiation, **one of the following** must occur to cause the instantiation to fail:
* a call to `mprotect` or `VirtualAlloc` fails (e.g. out-of-memory conditions).
* a resource limiter was configured in the associated `Store` (via [Store::limiter](https://docs.rs/wasmtime/0.34.0/wasmtime/struct.Store.html#method.limiter) or [Store::limiter_async](https://docs.rs/wasmtime/0.34.0/wasmtime/struct.Store.html#method.limiter_async)) and the limiter returns `false` from the initial call to `memory_growing` or `table_growing`. **Stores do not have a resource limiter set by default**.
This results in a partially-initialized instance being dropped and that attempts to drop the uninitialized `VMExternRef` representing the defined `externref` global.
We have reason to believe that the effective impact of this bug is relatively small because the usage of `externref` is still uncommon and without a resource limiter configured on the `Store`, which is not the default configuration, it is only possible to trigger the bug from an error returned by `mprotect` or `VirtualAlloc`.
Note that on Linux with the `uffd` feature enabled, it is only possible to trigger the bug from a resource limiter as the call to `mprotect` is skipped; if no resource limiter is used, then this configuration is not vulnerable.
### Patches
The bug has been fixed in 0.34.1 and 0.33.1; users are encouraged to upgrade as soon as possible.
### Workarounds
If it is not possible to upgrade to 0.34.1 or 0.33.1 of the `wasmtime` crate, it is recommend that support for the reference types proposal be disabled by passing `false` to [Config::wasm_reference_types](https://docs.rs/wasmtime/latest/wasmtime/struct.Config.html#method.wasm_reference_types).
Doing so will prevent modules that use `externref` from being loaded entirely.
### For more information
If you have any questions or comments about this advisory:
* Reach out to us on [the Bytecode Alliance Zulip chat](https://bytecodealliance.zulipchat.com/#narrow/stream/217126-wasmtime)
* Open an issue in [the bytecodealliance/wasmtime repository](https://github.com/bytecodealliance/wasmtime/)
|
{'CVE-2022-23636'}
|
2022-02-16T22:35:03Z
|
2022-02-16T22:35:03Z
|
MODERATE
| null |
{'CWE-824'}
|
{'https://github.com/bytecodealliance/wasmtime/commit/886ecc562040bef61faf19438c22285c2d62403a', 'https://github.com/bytecodealliance/wasmtime', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23636', 'https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-88xq-w8cq-xfg7'}
| null |
crates.io
|
GHSA-2vx6-fcw6-hpr6
|
Reference counting error in pyo3
|
An issue was discovered in the pyo3 crate before 0.12.4 for Rust. There is a reference-counting error and use-after-free in From<Py<T>>.
|
{'CVE-2020-35917'}
|
2021-08-19T20:50:20Z
|
2021-08-25T20:49:52Z
|
MODERATE
| null |
{'CWE-416'}
|
{'https://github.com/PyO3/pyo3/pull/1297', 'https://github.com/PyO3/pyo3', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35917', 'https://rustsec.org/advisories/RUSTSEC-2020-0074.html'}
| null |
crates.io
|
RUSTSEC-2021-0005
|
Double drop upon panic in 'fn map_array()'
|
Affected versions of this crate did not guard against panic within the user-provided function `f` (2nd parameter of `fn map_array`), and thus panic within `f`
causes double drop of a single object.
The flaw was corrected in the 0.4.0 release by wrapping the object vulnerable
to a double drop within `ManuallyDrop<T>`.
|
{'CVE-2021-25902'}
|
2021-10-19T22:14:35Z
|
2021-01-10T12:00:00Z
| null | null | null |
{'https://github.com/rustgd/glsl-layout/pull/10', 'https://crates.io/crates/glsl-layout', 'https://rustsec.org/advisories/RUSTSEC-2021-0005.html'}
| null |
crates.io
|
GHSA-2wc6-2rcj-8v76
|
scalarmult() vulnerable to degenerate public keys
|
The `scalarmult()` function included in previous versions of this crate
accepted all-zero public keys, for which the resulting Diffie-Hellman shared
secret will always be zero regardless of the private key used.
This issue was fixed by checking for this class of keys and rejecting them
if they are used.
|
{'CVE-2017-1000168'}
|
2021-08-05T21:10:47Z
|
2021-08-25T21:00:41Z
|
MODERATE
| null |
{'CWE-1240'}
|
{'https://rustsec.org/advisories/RUSTSEC-2017-0001.html', 'https://github.com/sodiumoxide/sodiumoxide', 'https://nvd.nist.gov/vuln/detail/CVE-2017-1000168', 'https://github.com/dnaq/sodiumoxide/issues/154', 'https://github.com/sodiumoxide/sodiumoxide/commit/24c7a5550807ac8a09648b5878f19d14c3a69135'}
| null |
crates.io
|
RUSTSEC-2019-0033
|
Integer Overflow in HeaderMap::reserve() can cause Denial of Service
|
`HeaderMap::reserve()` used `usize::next_power_of_two()` to calculate the increased capacity.
However, `next_power_of_two()` silently overflows to 0 if given a sufficiently large number
in release mode.
If the map was not empty when the overflow happens,
the library will invoke `self.grow(0)` and start infinite probing.
This allows an attacker who controls the argument to `reserve()`
to cause a potential denial of service (DoS).
The flaw was corrected in 0.1.20 release of `http` crate.
|
{'CVE-2020-25574', 'CVE-2019-25008'}
|
2021-10-19T22:14:35Z
|
2019-11-16T12:00:00Z
| null | null | null |
{'https://crates.io/crates/http', 'https://github.com/hyperium/http/issues/352', 'https://rustsec.org/advisories/RUSTSEC-2019-0033.html'}
| null |
crates.io
|
RUSTSEC-2021-0052
|
Multiple functions can cause double-frees
|
The following functions in the crate are affected:
## `IdMap::clone_from`
The `clone_from` implementation for `IdMap` drops the values present in the
map and then begins cloning values from the other map. If a `.clone()` call
pancics, then the afformentioned dropped elements can be freed again.
## `get_or_insert`
`get_or_insert` reserves space for a value, before calling the user provided
insertion function `f`. If the function `f` panics then uninitialized or
previously freed memory can be dropped.
## `remove_set`
When removing a set of elements, `ptr::drop_in_place` is called on each of the
element to be removed. If the `Drop` impl of one of these elements panics then
the previously dropped elements can be dropped again.
|
{'CVE-2021-30457', 'CVE-2021-30456', 'CVE-2021-30455'}
|
2021-04-13T21:10:09Z
|
2021-02-26T12:00:00Z
| null | null | null |
{'https://github.com/andrewhickman/id-map/issues/3', 'https://crates.io/crates/id-map', 'https://rustsec.org/advisories/RUSTSEC-2021-0052.html'}
| null |
crates.io
|
RUSTSEC-2022-0007
|
A malicious coder can get unsound access to TCell or TLCell memory
|
This is impossible to do by accident, but by carefully constructing
marker types to be covariant, a malicious coder can cheat the
singleton check in `TCellOwner` and `TLCellOwner`, giving unsound
access to cell memory. This could take the form of getting two
mutable references to the same memory, or a mutable reference and an
immutable reference.
The fix is for the crate to internally force the marker type to be
invariant. This blocks the conversion between covariant types which
Rust normally allows.
| null |
2022-01-24T17:41:17Z
|
2022-01-24T12:00:00Z
| null | null | null |
{'https://github.com/uazu/qcell/issues/20', 'https://crates.io/crates/qcell', 'https://rustsec.org/advisories/RUSTSEC-2022-0007.html'}
| null |
crates.io
|
RUSTSEC-2021-0117
|
`DecimalArray` does not perform bound checks on accessing values and offsets
|
`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.
| null |
2021-12-22T21:15:54Z
|
2021-09-14T12:00:00Z
| null | null | null |
{'https://github.com/apache/arrow-rs/issues/775', 'https://rustsec.org/advisories/RUSTSEC-2021-0117.html', 'https://crates.io/crates/arrow'}
| null |
crates.io
|
GHSA-q3cc-7p7g-392c
|
Use after free in rusqlite
|
An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated because sessions.rs has a use-after-free.
|
{'CVE-2020-35873'}
|
2021-08-19T21:08:56Z
|
2021-08-25T20:47:43Z
|
CRITICAL
| null |
{'CWE-416'}
|
{'https://github.com/rusqlite/rusqlite/releases/tag/0.23.0', 'https://rustsec.org/advisories/RUSTSEC-2020-0014.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35873', 'https://github.com/rusqlite/rusqlite/commit/ac30e169ae51b262bc8cf7026469851ce39b23c6', 'https://github.com/rusqlite/rusqlite'}
| null |
crates.io
|
RUSTSEC-2020-0019
|
tokio-rustls reads may cause excessive memory usage
|
`tokio-rustls` does not call `process_new_packets` immediately after `read`,
so the expected termination condition `wants_read` always returns true.
As long as new incoming data arrives faster than it is processed
and the reader does not return pending, data will be buffered.
This may cause DoS.
|
{'CVE-2020-35875'}
|
2021-10-19T22:14:35Z
|
2020-05-19T12:00:00Z
| null | null | null |
{'https://crates.io/crates/tokio-rustls', 'https://rustsec.org/advisories/RUSTSEC-2020-0019.html', 'https://github.com/tokio-rs/tls/pull/14'}
| null |
crates.io
|
GHSA-fhvc-gp6c-h2wx
|
Read on uninitialized buffer in postscript
|
An issue was discovered in the postscript crate before 0.14.0 for Rust. It might allow attackers to obtain sensitive information from uninitialized memory locations via a user-provided Read implementation.
|
{'CVE-2021-26953'}
|
2021-08-19T17:35:31Z
|
2021-08-25T20:52:23Z
|
HIGH
| null |
{'CWE-908'}
|
{'https://rustsec.org/advisories/RUSTSEC-2021-0017.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-26953', 'https://github.com/bodoni/postscript/issues/1', 'https://github.com/bodoni/postscript'}
| null |
crates.io
|
GHSA-m296-j53x-xv95
|
Data races in tiny_future
|
`tiny_future` contains a light-weight implementation of `Future`s. The `Future`
type it has lacked bound on its `Send` and `Sync` traits.
This allows for a bug where non-thread safe types such as `Cell` can be used in
`Future`s and cause data races in concurrent programs.
The flaw was corrected in commit `c791919` by adding trait bounds to `Future`'s
`Send` and `Sync`.
| null |
2021-08-18T23:36:06Z
|
2021-08-25T21:00:32Z
|
MODERATE
| null |
{'CWE-362'}
|
{'https://rustsec.org/advisories/RUSTSEC-2020-0118.html', 'https://github.com/KizzyCode/tiny_future/commit/c7919199a0f6d1ce0e3c33499d1b37f862c990e4', 'https://github.com/KizzyCode/tiny_future/commit/7ab8a264980d23c2ed64e72f4636f38b7381eb39', 'https://github.com/KizzyCode/tiny_future', 'https://github.com/KizzyCode/tiny_future/issues/1'}
| null |
crates.io
|
RUSTSEC-2022-0011
|
Miscomputation when performing AES encryption in rust-crypto
|
The following Rust program demonstrates some strangeness in AES encryption - if you have an immutable key slice and then operate on that slice, you get different encryption output than if you operate on a copy of that key.
For these functions, we expect that extending a 16 byte key to a 32 byte key by repeating it gives the same encrypted data, because the underlying rust-crypto functions repeat key data up to the necessary key size for the cipher.
```rust
use crypto::{
aes, blockmodes, buffer,
buffer::{BufferResult, ReadBuffer, WriteBuffer},
symmetriccipher,
};
fn encrypt(
key: &[u8],
iv: &[u8],
data: &str,
) -> Result<String, symmetriccipher::SymmetricCipherError> {
let mut encryptor =
aes::cbc_encryptor(aes::KeySize::KeySize256, key, iv, blockmodes::PkcsPadding);
let mut encrypted_data = Vec::<u8>::new();
let mut read_buffer = buffer::RefReadBuffer::new(data.as_bytes());
let mut buffer = [0; 4096];
let mut write_buffer = buffer::RefWriteBuffer::new(&mut buffer);
loop {
let result = encryptor.encrypt(&mut read_buffer, &mut write_buffer, true)?;
encrypted_data.extend(
write_buffer
.take_read_buffer()
.take_remaining()
.iter()
.copied(),
);
match result {
BufferResult::BufferUnderflow => break,
BufferResult::BufferOverflow => {}
}
}
Ok(hex::encode(encrypted_data))
}
fn working() {
let data = "data";
let iv = [
0xF0, 0xF1, 0xF2, 0xF3, 0xF4, 0xF5, 0xF6, 0xF7, 0xF8, 0xF9, 0xFA, 0xFB, 0xFC, 0xFD, 0xFE,
0xFF,
];
let key = [
0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E,
0x0F,
];
// The copy here makes the code work.
let key_copy = key;
let key2: Vec<u8> = key_copy.iter().cycle().take(32).copied().collect();
println!("key1:{} key2: {}", hex::encode(&key), hex::encode(&key2));
let x1 = encrypt(&key, &iv, data).unwrap();
println!("X1: {}", x1);
let x2 = encrypt(&key2, &iv, data).unwrap();
println!("X2: {}", x2);
assert_eq!(x1, x2);
}
fn broken() {
let data = "data";
let iv = [
0xF0, 0xF1, 0xF2, 0xF3, 0xF4, 0xF5, 0xF6, 0xF7, 0xF8, 0xF9, 0xFA, 0xFB, 0xFC, 0xFD, 0xFE,
0xFF,
];
let key = [
0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E,
0x0F,
];
// This operation shouldn't affect the contents of key at all.
let key2: Vec<u8> = key.iter().cycle().take(32).copied().collect();
println!("key1:{} key2: {}", hex::encode(&key), hex::encode(&key2));
let x1 = encrypt(&key, &iv, data).unwrap();
println!("X1: {}", x1);
let x2 = encrypt(&key2, &iv, data).unwrap();
println!("X2: {}", x2);
assert_eq!(x1, x2);
}
fn main() {
working();
broken();
}
```
The output from this program:
```shell
Running `target/host/debug/rust-crypto-test`
key1:000102030405060708090a0b0c0d0e0f key2: 000102030405060708090a0b0c0d0e0f000102030405060708090a0b0c0d0e0f
X1: 90462bbe32965c8e7ea0addbbed4cddb
X2: 90462bbe32965c8e7ea0addbbed4cddb
key1:000102030405060708090a0b0c0d0e0f key2: 000102030405060708090a0b0c0d0e0f000102030405060708090a0b0c0d0e0f
X1: 26e847e5e7df1947bf82a650548a7d5b
X2: 90462bbe32965c8e7ea0addbbed4cddb
thread 'main' panicked at 'assertion failed: `(left == right)`
left: `"26e847e5e7df1947bf82a650548a7d5b"`,
right: `"90462bbe32965c8e7ea0addbbed4cddb"`', src/main.rs:83:5
```
Notably, the X1 key in the `broken()` test changes every time after rerunning the program.
| null |
2022-03-01T16:17:42Z
|
2022-02-28T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2022-0011.html', 'https://crates.io/crates/rust-crypto'}
| null |
crates.io
|
RUSTSEC-2021-0044
|
Use after free possible in `uri::Formatter` on panic
|
Affected versions of this crate transmuted a `&str` to a `&'static str` before
pushing it into a `StackVec`, this value was then popped later in the same
function.
This was assumed to be safe because the reference would be valid while the
method's stack was active. In between the push and the pop, however, a function
`f` was called that could invoke a user provided function.
If the user provided panicked, then the assumption used by the function was no
longer true and the transmute to `&'static` would create an illegal static
reference to the string. This could result in a freed string being used during
(such as in a `Drop` implementation) or after (e.g through `catch_unwind`) the
panic unwinding.
This flaw was corrected in commit [e325e2f](https://github.com/SergioBenitez/Rocket/commit/e325e2fce4d9f9f392761e9fb58b418a48cef8bb)
by using a guard object to ensure that the `&'static str` was dropped inside
the function.
|
{'CVE-2021-29935'}
|
2021-10-19T22:14:35Z
|
2021-02-09T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2021-0044.html', 'https://github.com/SergioBenitez/Rocket/issues/1534', 'https://crates.io/crates/rocket'}
| null |
crates.io
|
GHSA-8h4j-vm3r-vcq3
|
Use after free in rusqlite
|
An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via an Auxdata API use-after-free.
|
{'CVE-2020-35870'}
|
2021-08-19T21:08:47Z
|
2021-08-25T20:47:48Z
|
CRITICAL
| null |
{'CWE-416'}
|
{'https://github.com/rusqlite/rusqlite/releases/tag/0.23.0', 'https://rustsec.org/advisories/RUSTSEC-2020-0014.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35870', 'https://github.com/rusqlite/rusqlite/commit/2ef3628dac35aeba0a97d5fb3a57746b4e1d62b3', 'https://github.com/rusqlite/rusqlite'}
| null |
crates.io
|
GHSA-gq4h-f254-7cw9
|
Data races in ticketed_lock
|
Affected versions of this crate unconditionally implemented `Send` for `ReadTicket<T>` & `WriteTicket<T>`.
This allows to send non-Send `T` to other threads.
This can allows creating data races by cloning types with internal mutability and sending them to other threads (as `T` of `ReadTicket<T>`/`WriteTicket<T>`). Such data races can cause memory corruption or other undefined behavior.
The flaw was corrected in commit a986a93 by adding `T: Send` bounds to `Send` impls of `ReadTicket<T>`/`WriteTicket<T>`.
| null |
2021-08-18T23:35:09Z
|
2021-08-25T21:00:34Z
|
MODERATE
| null |
{'CWE-362'}
|
{'https://rustsec.org/advisories/RUSTSEC-2020-0119.html', 'https://github.com/kvark/ticketed_lock/pull/8/commits/a986a9335d591fa5c826157d1674d47aa525357f', 'https://github.com/kvark/ticketed_lock/issues/7'}
| null |
crates.io
|
RUSTSEC-2021-0101
|
Permissions bypass in pleaser
|
Failure to normalize the umask in pleaser before 0.4 allows a local attacker to gain full root privileges if they are allowed to execute at least one command.
|
{'GHSA-vc5p-j8vw-mc6x', 'CVE-2021-31155'}
|
2021-09-10T15:58:27Z
|
2021-05-27T12:00:00Z
| null | null | null |
{'https://crates.io/crates/pleaser', 'https://rustsec.org/advisories/RUSTSEC-2021-0101.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-31155'}
| null |
crates.io
|
GHSA-g83m-67wh-whpw
|
Command injection in kekbit
|
An issue was discovered in the kekbit crate before 0.3.4 for Rust. For ShmWriter<H>, Send is implemented without requiring H: Send.
|
{'CVE-2020-36449'}
|
2021-08-18T20:31:24Z
|
2021-08-25T20:57:10Z
|
HIGH
| null |
{'CWE-77'}
|
{'https://github.com/motoras/kekbit', 'https://rustsec.org/advisories/RUSTSEC-2020-0129.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36449', 'https://github.com/motoras/kekbit/issues/34'}
| null |
crates.io
|
RUSTSEC-2021-0013
|
Soundness issues in `raw-cpuid`
|
## Undefined behavior in `as_string()` methods
`VendorInfo::as_string()`, `SoCVendorBrand::as_string()`,
and `ExtendedFunctionInfo::processor_brand_string()` construct byte slices
using `std::slice::from_raw_parts()`, with data coming from
`#[repr(Rust)]` structs. This is always undefined behavior.
See https://github.com/gz/rust-cpuid/issues/40.
This flaw has been fixed in v9.0.0, by making the relevant structs
`#[repr(C)]`.
## `native_cpuid::cpuid_count()` is unsound
`native_cpuid::cpuid_count()` exposes the unsafe `__cpuid_count()` intrinsic
from `core::arch::x86` or `core::arch::x86_64` as a safe function, and uses
it internally, without checking the
[safety requirement](https://doc.rust-lang.org/core/arch/index.html#overview):
> The CPU the program is currently running on supports the function being
> called.
CPUID is available in most, but not all, x86/x86_64 environments. The crate
compiles only on these architectures, so others are unaffected.
This issue is mitigated by the fact that affected programs are expected
to crash deterministically every time.
See https://github.com/gz/rust-cpuid/issues/41.
The flaw has been fixed in v9.0.0, by intentionally breaking compilation
when targeting SGX or 32-bit x86 without SSE. This covers all affected CPUs.
|
{'CVE-2021-26307', 'CVE-2021-26306'}
|
2021-08-22T01:18:11Z
|
2021-01-20T12:00:00Z
| null | null | null |
{'https://crates.io/crates/raw-cpuid', 'https://rustsec.org/advisories/RUSTSEC-2021-0013.html', 'https://github.com/RustSec/advisory-db/pull/614'}
| null |
crates.io
|
GHSA-p24j-h477-76q3
|
Uncontrolled Search Path Element in sharkdp/bat
|
bat on windows before 0.18.2 executes programs named less.exe from the current working directory. This can lead to unintended code execution.
|
{'CVE-2021-36753'}
|
2021-09-09T16:57:53Z
|
2021-08-25T21:01:37Z
|
HIGH
| null |
{'CWE-427'}
|
{'https://github.com/sharkdp/bat/commit/bf2b2df9c9e218e35e5a38ce3d03cffb7c363956', 'https://github.com/sharkdp/bat/pull/1724', 'https://github.com/sharkdp/bat/releases/tag/v0.18.2', 'https://nvd.nist.gov/vuln/detail/CVE-2021-36753', 'https://github.com/sharkdp/bat', 'https://vuln.ryotak.me/advisories/53'}
| null |
crates.io
|
RUSTSEC-2020-0058
|
crate has been renamed to `cipher`
|
This crate has been renamed from `stream-cipher` to `cipher`.
The new repository location is at:
<https://github.com/RustCrypto/traits/tree/master/cipher>
| null |
2020-10-25T19:14:03Z
|
2020-10-15T12:00:00Z
| null | null | null |
{'https://github.com/RustCrypto/traits/pull/337', 'https://rustsec.org/advisories/RUSTSEC-2020-0058.html', 'https://crates.io/crates/stream-cipher'}
| null |
crates.io
|
RUSTSEC-2019-0025
|
Flaw in CBOR deserializer allows stack overflow
|
Affected versions of this crate did not properly check if semantic tags were nested excessively during deserialization.
This allows an attacker to craft small (< 1 kB) CBOR documents that cause a stack overflow.
The flaw was corrected by limiting the allowed number of nested tags.
|
{'CVE-2019-25001'}
|
2021-10-19T22:14:35Z
|
2019-10-03T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2019-0025.html', 'https://github.com/pyfisch/cbor/releases/tag/v0.10.2', 'https://crates.io/crates/serde_cbor'}
| null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.