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
|
GHSA-84rm-qf37-fgc2
|
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-23841'}
|
2021-08-19T17:35:19Z
|
2021-08-25T20:52:21Z
|
MODERATE
| null |
{'CWE-190', 'CWE-476'}
|
{'https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=9b1129239f3ebb1d1c98ce9ed41d5c9476c47cb2', 'https://www.debian.org/security/2021/dsa-4855', 'https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=8252ee4d90f3f2004d3d0aeeed003ad49c9a7807', 'https://www.openssl.org/news/secadv/20210216.txt', 'https://www.tenable.com/security/tns-2021-09', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://www.oracle.com//security-alerts/cpujul2021.html', 'http://seclists.org/fulldisclosure/2021/May/68', 'https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=122a19ab48091c657f7cb1fb3af9fc07bd557bbf', 'https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=6a51b9e1d0cf0bf8515f7201b68fb0a3482b3dc1', 'https://support.apple.com/kb/HT212534', 'https://kb.pulsesecure.net/articles/Pulse_Security_Advisories/SA44846', 'https://rustsec.org/advisories/RUSTSEC-2021-0058', 'http://seclists.org/fulldisclosure/2021/May/70', 'https://security.netapp.com/advisory/ntap-20210513-0002/', 'https://www.tenable.com/security/tns-2021-03', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23841', 'https://support.apple.com/kb/HT212528', 'https://support.apple.com/kb/HT212529', '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/', 'http://seclists.org/fulldisclosure/2021/May/67', 'https://security.gentoo.org/glsa/202103-03'}
| null |
crates.io
|
GHSA-rjh8-p66p-jrh5
|
Data races 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 data race.
|
{'CVE-2020-35871'}
|
2021-08-19T21:18:47Z
|
2021-08-25T20:46:59Z
|
HIGH
| null |
{'CWE-362'}
|
{'https://github.com/rusqlite/rusqlite/releases/tag/0.23.0', 'https://rustsec.org/advisories/RUSTSEC-2020-0014.html', 'https://github.com/rusqlite/rusqlite/commit/2ef3628dac35aeba0a97d5fb3a57746b4e1d62b3', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35871', 'https://github.com/rusqlite/rusqlite'}
| null |
crates.io
|
RUSTSEC-2020-0158
|
slice-deque is unmaintained
|
The author of the `slice-deque` crate is unresponsive and is not receiving security patches.
Maintained alternatives:
- [`slice-ring-buffer`](https://crates.io/crates/slice-ring-buffer)
| null |
2021-11-18T14:04:01Z
|
2020-02-10T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2020-0158.html', 'https://crates.io/crates/slice-deque', 'https://github.com/gnzlbg/slice_deque/issues/94'}
| null |
crates.io
|
RUSTSEC-2021-0113
|
AtomicBucket<T> unconditionally implements Send/Sync
|
In the affected versions of the crate, `AtomicBucket<T>` unconditionally implements `Send`/`Sync` traits. Therefore, users can create a data race to the inner
`T: !Sync` by using the `AtomicBucket::data_with()` API.
Such data races can potentially cause memory corruption or other undefined behavior.
The flaw was fixed in commit 8e6daab by adding appropriate Send/Sync bounds to the Send/Sync impl of struct `Block<T>` (which is a data type contained inside `AtomicBucket<T>`).
| null |
2021-09-18T21:35:48Z
|
2021-04-07T12:00:00Z
| null | null | null |
{'https://github.com/metrics-rs/metrics/issues/190', 'https://crates.io/crates/metrics-util', 'https://rustsec.org/advisories/RUSTSEC-2021-0113.html'}
| null |
crates.io
|
RUSTSEC-2022-0003
|
Space bug in `clean_text`
|
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.
| null |
2022-01-19T22:35:01Z
|
2022-01-19T12:00:00Z
| null | null | null |
{'https://crates.io/crates/ammonia', 'https://rustsec.org/advisories/RUSTSEC-2022-0003.html', 'https://github.com/rust-ammonia/ammonia/pull/147'}
| null |
crates.io
|
RUSTSEC-2021-0056
|
CA certificate check bypass with X509_V_FLAG_X509_STRICT
|
The X509_V_FLAG_X509_STRICT flag enables additional security checks of the
certificates present in a certificate chain. It is not set by default.
Starting from OpenSSL version 1.1.1h a check to disallow certificates in
the chain that have explicitly encoded elliptic curve parameters was added
as an additional strict check.
An error in the implementation of this check meant that the result of a
previous check to confirm that certificates in the chain are valid CA
certificates was overwritten. This effectively bypasses the check
that non-CA certificates must not be able to issue other certificates.
If a "purpose" has been configured then there is a subsequent opportunity
for checks that the certificate is a valid CA. All of the named "purpose"
values implemented in libcrypto perform this check. Therefore, where
a purpose is set the certificate chain will still be rejected even when the
strict flag has been used. A purpose is set by default in libssl client and
server certificate verification routines, but it can be overridden or
removed by an application.
In order to be affected, an application must explicitly set the
X509_V_FLAG_X509_STRICT verification flag and either not set a purpose
for the certificate verification or, in the case of TLS client or server
applications, override the default purpose.
|
{'CVE-2021-3450'}
|
2021-10-19T22:14:35Z
|
2021-05-01T12:00:00Z
| null | null | null |
{'https://crates.io/crates/openssl-src', 'https://rustsec.org/advisories/RUSTSEC-2021-0056.html', 'https://www.openssl.org/news/secadv/20210325.txt'}
| null |
crates.io
|
GHSA-2367-c296-3mp2
|
Link following in tar
|
An issue was discovered in the tar crate before 0.4.16 for Rust. Arbitrary file overwrite can occur via a symlink or hardlink in a TAR archive.
|
{'CVE-2018-20990'}
|
2021-08-19T21:24:12Z
|
2021-08-25T20:43:54Z
|
HIGH
| null |
{'CWE-59'}
|
{'https://rustsec.org/advisories/RUSTSEC-2018-0002.html', 'https://github.com/alexcrichton/tar-rs/pull/156', 'https://nvd.nist.gov/vuln/detail/CVE-2018-20990', 'https://github.com/alexcrichton/tar-rs'}
| null |
crates.io
|
GHSA-j2r6-2m5c-vgh5
|
Counter overflow in chacha20
|
An issue was discovered in the chacha20 crate before 0.2.3 for Rust. A ChaCha20 counter overflow makes it easier for attackers to determine plaintext.
|
{'CVE-2019-25005'}
|
2021-08-19T21:20:52Z
|
2021-08-25T20:45:20Z
|
HIGH
| null |
{'CWE-190'}
|
{'https://github.com/RustCrypto/stream-ciphers/tree/master/chacha20', 'https://nvd.nist.gov/vuln/detail/CVE-2019-25005', 'https://rustsec.org/advisories/RUSTSEC-2019-0029.html', 'https://github.com/RustCrypto/stream-ciphers/pull/64'}
| null |
crates.io
|
RUSTSEC-2019-0037
|
Compiler optimisation for next_with_timeout in pnet::transport::IcmpTransportChannelIterator flaws to SEGFAULT
|
Affected versions of this crate were optimized out by compiler,
which caused dereference of uninitialized file descriptor which caused segfault.
| null |
2020-11-28T02:51:11Z
|
2019-06-11T12:00:00Z
| null | null | null |
{'https://crates.io/crates/pnet', 'https://github.com/libpnet/libpnet/issues/449', 'https://rustsec.org/advisories/RUSTSEC-2019-0037.html'}
| null |
crates.io
|
GHSA-wcxc-jf6c-8rx9
|
Uncaught Exception in libpulse-binding
|
Affected versions of this crate failed to catch panics crossing FFI boundaries via callbacks, which
is a form of UB. This flaw was corrected by [this commit][1] which was included in version 2.6.0.
| null |
2021-08-18T20:24:24Z
|
2021-08-25T20:57:21Z
|
MODERATE
| null |
{'CWE-248'}
|
{'https://github.com/jnqnfe/pulse-binding-rust', 'https://github.com/jnqnfe/pulse-binding-rust/commit/7fd282aef7787577c385aed88cb25d004b85f494', 'https://rustsec.org/advisories/RUSTSEC-2019-0038.html'}
| null |
crates.io
|
GHSA-xjxc-vfw2-cg96
|
Use after free in openssl
|
An issue was discovered in the openssl crate before 0.10.9 for Rust. A use-after-free occurs in CMS Signing.
|
{'CVE-2018-20997'}
|
2021-08-19T21:24:24Z
|
2021-08-25T20:43:45Z
|
CRITICAL
| null |
{'CWE-416'}
|
{'https://github.com/sfackler/rust-openssl/pull/942', 'https://github.com/sfackler/rust-openssl', 'https://rustsec.org/advisories/RUSTSEC-2018-0010.html', 'https://nvd.nist.gov/vuln/detail/CVE-2018-20997'}
| null |
crates.io
|
GHSA-p4cr-64x4-f92f
|
Use of Uninitialized Resource in acc_reader.
|
An issue was discovered in the acc_reader crate through 2020-12-27 for Rust. fill_buf may read from uninitialized memory locations.
|
{'CVE-2020-36514'}
|
2022-01-07T16:21:25Z
|
2022-01-06T22:17:23Z
|
CRITICAL
| null |
{'CWE-908'}
|
{'https://github.com/netvl/acc_reader', 'https://rustsec.org/advisories/RUSTSEC-2020-0155.html', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/acc_reader/RUSTSEC-2020-0155.md', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36514'}
| null |
crates.io
|
GHSA-6c65-xcf5-299x
|
Uninitialized memory use in generator
|
An issue was discovered in the generator crate before 0.6.18 for Rust. Uninitialized memory is used by Scope, done, and yield_ during API calls.
|
{'CVE-2019-16144'}
|
2021-08-18T17:52:08Z
|
2021-08-25T20:58:25Z
|
HIGH
| null |
{'CWE-908'}
|
{'https://github.com/Xudong-Huang/generator-rs/issues/14', 'https://github.com/Xudong-Huang/generator-rs/issues/9', 'https://github.com/Xudong-Huang/generator-rs/issues/11', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16144', 'https://github.com/Xudong-Huang/generator-rs', 'https://github.com/Xudong-Huang/generator-rs/issues/13', 'https://rustsec.org/advisories/RUSTSEC-2019-0020.html'}
| null |
crates.io
|
RUSTSEC-2021-0001
|
XSS in mdBook's search page
|
> This is a cross-post of [the official security advisory][ml]. The official post
> contains a signed version with our PGP key, as well.
[ml]: https://groups.google.com/g/rustlang-security-announcements/c/3-sO6of29O0
The Rust Security Response Working Group was recently notified of a security
issue affecting the search feature of mdBook, which could allow an attacker to
execute arbitrary JavaScript code on the page.
The CVE for this vulnerability is [CVE-2020-26297][1].
## Overview
The search feature of mdBook (introduced in version 0.1.4) was affected by a
cross site scripting vulnerability that allowed an attacker to execute
arbitrary JavaScript code on an user's browser by tricking the user into typing
a malicious search query, or tricking the user into clicking a link to the
search page with the malicious search query prefilled.
mdBook 0.4.5 fixes the vulnerability by properly escaping the search query.
## Mitigations
Owners of websites built with mdBook have to upgrade to mdBook 0.4.5 or greater
and rebuild their website contents with it. It's possible to install mdBook
0.4.5 on the local system with:
```
cargo install mdbook --version 0.4.5 --force
```
## Acknowledgements
Thanks to Kamil Vavra for responsibly disclosing the vulnerability to us
according to [our security policy][2].
## Timeline of events
All times are listed in UTC.
* 2020-12-30 20:14 - The issue is reported to the Rust Security Response WG
* 2020-12-30 20:32 - The issue is acknowledged and the investigation began
* 2020-12-30 21:21 - Found the cause of the vulnerability and prepared the patch
* 2021-01-04 15:00 - Patched version released and vulnerability disclosed
[1]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26297
[2]: https://www.rust-lang.org/policies/security
|
{'CVE-2020-26297'}
|
2021-10-19T22:14:35Z
|
2021-01-04T12:00:00Z
| null | null | null |
{'https://crates.io/crates/mdbook', 'https://groups.google.com/g/rustlang-security-announcements/c/3-sO6of29O0', 'https://rustsec.org/advisories/RUSTSEC-2021-0001.html'}
| null |
crates.io
|
GHSA-8928-2fgm-6x9x
|
HTTP Request Smuggling in actix-http
|
Affected versions of this crate did not properly detect invalid requests that could allow HTTP/1 request smuggling (HRS) attacks when running alongside a vulnerable front-end proxy server. This can result in leaked internal and/or user data, including credentials, when the front-end proxy is also vulnerable.
Popular front-end proxies and load balancers already mitigate HRS attacks so it is recommended that they are also kept up to date; check your specific set up. You should upgrade even if the front-end proxy receives exclusively HTTP/2 traffic and connects to the back-end using HTTP/1; several downgrade attacks are known that can also expose HRS vulnerabilities.
|
{'CVE-2021-38512'}
|
2021-08-18T20:13:40Z
|
2021-08-25T20:58:21Z
|
HIGH
| null |
{'CWE-444'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-38512', 'https://github.com/actix/actix-web/commit/e965d8298f421e9c89fe98b1300b8361e948c324', 'https://github.com/actix/actix-web/pull/2363', 'https://github.com/actix/actix-web', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/67URRW4K47SR6LNQB4YALPLGGQMQK7HO/', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/actix-http/RUSTSEC-2021-0081.md', 'https://rustsec.org/advisories/RUSTSEC-2021-0081.html'}
| null |
crates.io
|
GHSA-r6ff-2q3c-v3pv
|
Compiler optimisation leads to SEGFAULT
|
Affected versions of the `pnet` crate were optimized out by compiler, which caused dereference of uninitialized file descriptor which caused segfault.
| null |
2021-08-09T17:13:06Z
|
2021-08-25T21:00:01Z
|
MODERATE
| null |
{'CWE-908'}
|
{'https://github.com/libpnet/libpnet/issues/449', 'https://github.com/libpnet/libpnet/pull/455', 'https://rustsec.org/advisories/RUSTSEC-2019-0037.html', 'https://github.com/libpnet/libpnet'}
| null |
crates.io
|
GHSA-hw4v-5x4h-c3xm
|
Transaction validity oversight in pallet-ethereum
|
### Impact
A bug in `pallet-ethereum` can cause invalid transactions to be included in the Ethereum block state in `pallet-ethereum` due to not validating the input data size. Any invalid transactions included this way have no possibility to alter the internal Ethereum or Substrate state. The transaction will appear to have be included, but is of no effect as it is rejected by the EVM engine. The impact is further limited by Substrate extrinsic size constraints.
### Patches
Patches are applied in PR #465.
### Workarounds
None.
### References
Patch PR: https://github.com/paritytech/frontier/pull/465
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [Frontier repo](https://github.com/paritytech/frontier)
|
{'CVE-2021-39193'}
|
2021-09-03T20:22:28Z
|
2021-09-01T18:22:48Z
|
MODERATE
| null |
{'CWE-20'}
|
{'https://github.com/paritytech/frontier/pull/465/commits/8a2b890a2fb477d5fedd0e4335b00623832849ae', 'https://github.com/paritytech/frontier', 'https://github.com/paritytech/frontier/security/advisories/GHSA-hw4v-5x4h-c3xm', 'https://github.com/paritytech/frontier/pull/465', 'https://github.com/paritytech/frontier/commit/dd112e', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39193', 'https://github.com/paritytech/frontier/commit/0b962f218f0cdd796dadfe26c3f09e68f7861b26'}
| null |
crates.io
|
RUSTSEC-2020-0031
|
HTTP Request smuggling through malformed Transfer Encoding headers
|
HTTP pipelining issues and request smuggling attacks are possible due to incorrect
Transfer encoding header parsing.
It is possible conduct HTTP request smuggling attacks (CL:TE/TE:TE) by sending invalid Transfer Encoding headers.
By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack, or obtain sensitive information
from requests other than their own.
|
{'CVE-2020-35884'}
|
2021-10-19T22:14:35Z
|
2020-06-16T12:00:00Z
| null | null | null |
{'https://github.com/tiny-http/tiny-http/issues/173', 'https://rustsec.org/advisories/RUSTSEC-2020-0031.html', 'https://crates.io/crates/tiny_http'}
| null |
crates.io
|
GHSA-q2x5-6q7q-r872
|
Use After Free in tremor-script
|
An issue was discovered in the tremor-script crate before 0.11.6 for Rust. A patch operation may result in a use-after-free.
|
{'CVE-2021-45701'}
|
2022-01-07T17:52:38Z
|
2022-01-06T22:10:17Z
|
CRITICAL
| null |
{'CWE-416'}
|
{'https://rustsec.org/advisories/RUSTSEC-2021-0111.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-45701', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/tremor-script/RUSTSEC-2021-0111.md'}
| null |
crates.io
|
RUSTSEC-2018-0007
|
Stack overflow when parsing malicious DNS packet
|
There's a stack overflow leading to a crash when Trust-DNS's parses a
malicious DNS packet.
Affected versions of this crate did not properly handle parsing of DNS message
compression (RFC1035 section 4.1.4). The parser could be tricked into infinite
loop when a compression offset pointed back to the same domain name to be
parsed.
This allows an attacker to craft a malicious DNS packet which when consumed
with Trust-DNS could cause stack overflow and crash the affected software.
The flaw was corrected by trust-dns-proto 0.4.3 and upcoming 0.5.0 release.
|
{'CVE-2018-20994'}
|
2021-10-19T22:14:35Z
|
2018-10-09T12:00:00Z
| null | null | null |
{'https://crates.io/crates/trust-dns-proto', 'https://rustsec.org/advisories/RUSTSEC-2018-0007.html'}
| null |
crates.io
|
RUSTSEC-2021-0095
|
`mopa` is technically unsound
|
The `mopa` crate redefines the deprecated `TraitObject` struct from `core::raw` like so:
```rust
#[repr(C)]
#[derive(Copy, Clone)]
#[doc(hidden)]
pub struct TraitObject {
pub data: *mut (),
pub vtable: *mut (),
}
```
This is done to then transmute a reference to a trait object (`&dyn Trait` for any trait `Trait`) into this struct and retrieve the `data` field for the purpose of downcasting. This is used to implement `downcast_ref_unchecked()`, in terms of which `downcast_ref()` is also implemented. Same goes for mutable reference downcasting and `Box` downcasting.
The Rust compiler explicitly reserves the right to change the memory layout of `&dyn Trait` for any trait `Trait`. The worst case scenario is that it swaps `data` and `vtable`, making an executable location breach and compromisation of ASLR possible, since reads from `data` would read `vtable` instead. Likewise, arbitrary code execution is also theoretically possible if reads of `vtable` generated by the compiler read `data` instead.
While, as of Rust 1.52, this unsound assumption still holds true, updating the compiler may silently create UB in a crate which previously compiled and run without issues, compromising the security of builds which are believed to be reproducible.
A potential strategy to resolve this has already been suggested in an issue on the GitHub repository of the crate.
| null |
2021-08-22T01:48:14Z
|
2021-06-01T12:00:00Z
| null | null | null |
{'https://crates.io/crates/mopa', 'https://github.com/chris-morgan/mopa/issues/13', 'https://rustsec.org/advisories/RUSTSEC-2021-0095.html'}
| null |
crates.io
|
RUSTSEC-2020-0123
|
Contents of uninitialized memory exposed in DeflateOutput's AsyncRead implementation
|
Affected versions of this crate passes an uninitialized buffer to a user-provided trait function `AsyncRead::poll_read()`.
Arbitrary `AsyncRead::poll_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.
The flaw was fixed in commit 5ba266a by ensuring the newly allocated part of the buffer is zero-initialized before passing it to a user-provided `AsyncRead::poll_read()`.
|
{'CVE-2020-36443'}
|
2021-10-19T22:14:35Z
|
2020-01-24T12:00:00Z
| null | null | null |
{'https://crates.io/crates/libp2p-deflate', 'https://github.com/libp2p/rust-libp2p/issues/1932', 'https://rustsec.org/advisories/RUSTSEC-2020-0123.html'}
| null |
crates.io
|
GHSA-wcg3-cvx6-7396
|
Segmentation fault in time
|
### Impact
Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
The affected functions from time 0.2.7 through 0.2.22 are:
- `time::UtcOffset::local_offset_at`
- `time::UtcOffset::try_local_offset_at`
- `time::UtcOffset::current_local_offset`
- `time::UtcOffset::try_current_local_offset`
- `time::OffsetDateTime::now_local`
- `time::OffsetDateTime::try_now_local`
The affected functions in time 0.1 (all versions) are:
- `at`
- `at_utc`
- `now`
Non-Unix targets (including Windows and wasm) are unaffected.
### Patches
Pending a proper fix, the internal method that determines the local offset has been modified to always return `None` on the affected operating systems. This has the effect of returning an `Err` on the `try_*` methods and `UTC` on the non-`try_*` methods.
Users and library authors with time in their dependency tree should perform `cargo update`, which will pull in the updated, unaffected code.
Users of time 0.1 do not have a patch and should upgrade to an unaffected version: time 0.2.23 or greater or the 0.3. series.
### Workarounds
No workarounds are known.
### References
time-rs/time#293
|
{'CVE-2020-26235'}
|
2021-10-18T20:47:30Z
|
2021-08-25T20:56:46Z
|
MODERATE
| null |
{'CWE-476'}
|
{'https://github.com/time-rs/time/issues/293', 'https://rustsec.org/advisories/RUSTSEC-2020-0071.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26235', 'https://github.com/time-rs/time', 'https://github.com/time-rs/time/security/advisories/GHSA-wcg3-cvx6-7396'}
| null |
crates.io
|
RUSTSEC-2020-0089
|
nanorand 0.5.0 - RNGs failed to generate properly for non-64-bit numbers
|
In versions of `nanorand` prior to 0.5.1, `RandomGen` implementations for standard unsigned integers could
fail to properly generate numbers, due to using bit-shifting to truncate a 64-bit number, rather than just
an `as` conversion.
This often manifested as RNGs returning nothing but 0, including the cryptographically secure `ChaCha` random
number generator..
|
{'CVE-2020-35926'}
|
2021-01-04T17:02:59Z
|
2020-12-09T12:00:00Z
| null | null | null |
{'https://twitter.com/aspenluxxxy/status/1336684692284772352', 'https://rustsec.org/advisories/RUSTSEC-2020-0089.html', 'https://crates.io/crates/nanorand'}
| null |
crates.io
|
RUSTSEC-2020-0066
|
crate has been renamed to `sn_bindgen`
|
This crate has been renamed from `safe_bindgen` to `sn_bindgen`.
The new repository location is:
<https://github.com/maidsafe/sn_bindgen>
| null |
2020-11-02T14:48:54Z
|
2020-11-02T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2020-0066.html', 'https://crates.io/crates/safe_bindgen', 'https://github.com/maidsafe/sn_bindgen/pull/67'}
| null |
crates.io
|
GHSA-m3ww-7hrp-gw9w
|
Drop of uninitialized memory in Ozone
|
An issue was discovered in the ozone crate through 2020-07-04 for Rust. Memory safety is violated because of the dropping of uninitialized memory.
|
{'CVE-2020-35878'}
|
2021-08-19T21:08:59Z
|
2021-08-25T20:47:41Z
|
CRITICAL
| null |
{'CWE-908', 'CWE-119'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-35878', 'https://rustsec.org/advisories/RUSTSEC-2020-0022.html', 'https://github.com/bqv/ozone'}
| null |
crates.io
|
GHSA-87xh-9q6h-r5cc
|
Use After Free in rusqlite
|
An issue was discovered in the rusqlite crate 0.25.x before 0.25.4 and 0.26.x before 0.26.2 for Rust. create_window_function has a use-after-free.
|
{'CVE-2021-45715'}
|
2022-01-07T16:08:56Z
|
2022-01-06T22:00:49Z
|
HIGH
| null |
{'CWE-416'}
|
{'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/rusqlite/RUSTSEC-2021-0128.md', 'https://nvd.nist.gov/vuln/detail/CVE-2021-45715', 'https://rustsec.org/advisories/RUSTSEC-2021-0128.html', 'https://github.com/rusqlite/rusqlite'}
| null |
crates.io
|
GHSA-gwc9-348x-qwv2
|
Use after free in Wasmtime
|
There is a use after free vulnerability in Wasmtime when both running Wasm that uses `externref`s and enabling [epoch interruption](https://docs.rs/wasmtime/latest/wasmtime/struct.Config.html#method.epoch_interruption) in Wasmtime. If you are not explicitly enabling epoch interruption (it is disabled by default) then you are not affected. If you are explicitly disabling the Wasm reference types proposal (it is enabled by default) then you are also not affected.
The use after free is caused by Cranelift failing to emit stack maps when there are safepoints inside cold blocks. Cold blocks occur when epoch interruption is enabled. Cold blocks are emitted at the end of compiled functions, and change the order blocks are emitted versus defined. This reordering accidentally caused Cranelift to skip emitting some stack maps because it expected to emit the stack maps in block definition order, rather than block emission order. When Wasmtime would eventually collect garbage, it would fail to find live references on the stack because of the missing stack maps, think that they were unreferenced garbage, and therefore reclaim them. Then after the collection ended, the Wasm code could use the reclaimed-too-early references, which is a use after free.
This bug was discovered while extending our fuzz targets for `externref`s and GC in Wasmtime. The updated fuzz target thoroughly exercises these code paths and feature combinations now. We have also added a regression test for this bug. Released versions 0.34.2 and 0.35.2, which fix the vulnerability. We recommend all Wasmtime users upgrade to these patched versions. If upgrading is not an option for you at this time, you can avoid the vulnerability by either disabling the Wasm reference types proposal or by disabling epoch interruption if you were previously enabling it.
|
{'CVE-2022-24791'}
|
2022-04-12T23:16:15Z
|
2022-04-01T13:36:12Z
|
HIGH
| null |
{'CWE-416'}
|
{'https://docs.rs/wasmtime/latest/wasmtime/struct.Config.html#method.epoch_interruption', 'https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-gwc9-348x-qwv2', 'https://github.com/bytecodealliance/wasmtime/commit/666c2554ea0e1728c35aa41178cf235920db888a', 'https://github.com/bytecodealliance/wasmtime', 'https://github.com/WebAssembly/reference-types', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24791'}
| null |
crates.io
|
GHSA-gh87-6jr3-8q47
|
Null pointer deference in cache
|
An issue was discovered in the cache crate through 2021-01-01 for Rust. A raw pointer is dereferenced.
|
{'CVE-2021-25903'}
|
2021-08-19T18:45:43Z
|
2021-08-25T20:52:57Z
|
HIGH
| null |
{'CWE-476'}
|
{'https://github.com/krl/cache/issues/2', 'https://github.com/krl/cache', 'https://rustsec.org/advisories/RUSTSEC-2021-0006.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25903'}
| null |
crates.io
|
RUSTSEC-2020-0135
|
Slock<T> allows sending non-Send types across thread boundaries
|
`Slock<T>` unconditionally implements `Send`/`Sync`.
Affected versions of this crate allows sending non-Send types to other threads,
which can lead to data races and memory corruption due to the data race.
|
{'CVE-2020-36455'}
|
2021-10-19T22:14:35Z
|
2020-11-17T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2020-0135.html', 'https://crates.io/crates/slock', 'https://github.com/BrokenLamp/slock-rs/issues/2'}
| null |
crates.io
|
GHSA-45w7-7g63-2m5w
|
Drop of uninitialized memory in stack_dst
|
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-28035'}
|
2021-08-30T21:56:02Z
|
2021-09-01T18:30:55Z
|
CRITICAL
| null |
{'CWE-908'}
|
{'https://github.com/thepowersgang/stack_dst-rs/issues/5', 'https://nvd.nist.gov/vuln/detail/CVE-2021-28035', 'https://rustsec.org/advisories/RUSTSEC-2021-0033.html', 'https://github.com/thepowersgang/stack_dst-rs/commit/2a4d538', 'https://github.com/thepowersgang/stack_dst-rs'}
| null |
crates.io
|
RUSTSEC-2020-0070
|
Some lock_api lock guard objects can cause data races
|
Affected versions of lock_api had unsound implementations of the `Send` or
`Sync` traits for some guard objects, namely:
* MappedMutexGuard
* MappedRwLockReadGuard
* MappedRwLockWriteGuard
* RwLockReadGuard
* RwLockWriteGuard
These guards could allow data races through types that are not safe to `Send`
across thread boundaries in safe Rust code.
This issue was fixed by changing the trait bounds on the `Mapped` guard types
and removing the `Sync` trait for the `RwLock` guards.
|
{'CVE-2020-35914', 'CVE-2020-35911', 'CVE-2020-35913', 'CVE-2020-35910', 'CVE-2020-35912'}
|
2021-01-31T04:02:50Z
|
2020-11-08T12:00:00Z
| null | null | null |
{'https://crates.io/crates/lock_api', 'https://github.com/Amanieu/parking_lot/pull/262', 'https://rustsec.org/advisories/RUSTSEC-2020-0070.html'}
| null |
crates.io
|
GHSA-8c6g-4xc5-w96c
|
Uninitialized memory exposure in claxon
|
An issue was discovered in the claxon crate before 0.4.1 for Rust. Uninitialized memory can be exposed because certain decode buffer sizes are mishandled.
|
{'CVE-2018-20992'}
|
2021-08-19T21:24:16Z
|
2021-08-25T20:43:52Z
|
MODERATE
| null |
{'CWE-908'}
|
{'https://github.com/ruuda/claxon/commit/8f28ec275e412dd3af4f3cda460605512faf332c', 'https://github.com/ruuda/claxon', 'https://nvd.nist.gov/vuln/detail/CVE-2018-20992', 'https://rustsec.org/advisories/RUSTSEC-2018-0004.html'}
| null |
crates.io
|
GHSA-9p8q-j6q5-mjw8
|
Buffer Overflow in galois_2p8
|
In galois_2p8 before 0.1.2, PrimitivePolynomialField::new has an off-by-one buffer overflow for a vector.
|
{'CVE-2022-24988'}
|
2022-02-25T15:29:16Z
|
2022-02-15T00:02:45Z
|
CRITICAL
| null |
{'CWE-120'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2022-24988', 'https://github.com/djsweet/galois_2p8/blob/master/CHANGELOG.md', 'https://github.com/djsweet/galois_2p8'}
| null |
crates.io
|
RUSTSEC-2017-0003
|
Hostname verification skipped when custom root certs used
|
If custom root certificates were registered with a `ClientBuilder`, the
hostname of the target server would not be validated against its presented leaf
certificate.
This issue was fixed by properly configuring the trust evaluation logic to
perform that check.
|
{'CVE-2017-18588'}
|
2021-10-19T22:14:35Z
|
2017-03-15T12:00:00Z
| null | null | null |
{'https://crates.io/crates/security-framework', 'https://rustsec.org/advisories/RUSTSEC-2017-0003.html', 'https://github.com/sfackler/rust-security-framework/pull/27'}
| null |
crates.io
|
RUSTSEC-2020-0162
|
`tokio-proto` is deprecated/unmaintained
|
The [`tokio-proto`](https://crates.io/crates/tokio-proto) crate has been deprecated, and [its GitHub repository](https://github.com/tokio-rs/tokio-proto) has been archived.
Users may be interested in [`tokio-tower`](https://crates.io/crates/tokio-tower) instead, per https://github.com/tokio-rs/tokio/issues/118#issuecomment-452969665
| null |
2022-02-07T02:25:36Z
|
2020-02-06T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2020-0162.html', 'https://github.com/tokio-rs/tokio-proto/commit/56c720ea3c74efa8f39e36c24e609628222b16a1', 'https://crates.io/crates/tokio-proto'}
| null |
crates.io
|
RUSTSEC-2020-0027
|
traitobject assumes the layout of fat pointers
|
This crate gets the data pointer from fat pointers assuming that the first
element in a fat pointer is the data pointer. This is currently true, but
it may change in a future Rust version, leading to memory corruption.
This has been fixed in the master branch of the crate, but is has not
been released into crates.io.
|
{'CVE-2020-35881'}
|
2021-10-19T22:14:35Z
|
2020-06-01T12:00:00Z
| null | null | null |
{'https://crates.io/crates/traitobject', 'https://rustsec.org/advisories/RUSTSEC-2020-0027.html', 'https://github.com/reem/rust-traitobject/issues/7'}
| null |
crates.io
|
GHSA-q9h2-4xhf-23xx
|
Data races in im
|
An issue was discovered in the im crate through 2020-11-09 for Rust. Because TreeFocus does not have bounds on its Send trait or Sync trait, a data race can occur.
|
{'CVE-2020-36204'}
|
2021-08-19T18:49:57Z
|
2021-08-25T20:51:36Z
|
MODERATE
| null |
{'CWE-662'}
|
{'https://github.com/bodil/im-rs/issues/157', 'https://rustsec.org/advisories/RUSTSEC-2020-0096.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36204', 'https://github.com/bodil/im-rs'}
| null |
crates.io
|
RUSTSEC-2018-0011
|
Enum repr causing potential memory corruption
|
The attribute repr() added to enums to be compatible with C-FFI caused
memory corruption on MSVC toolchain.
arrayfire crates <= version 3.5.0 do not have this issue when used with
Rust versions 1.27 or earlier. The issue only started to appear since
Rust version 1.28.
The issue seems to be interlinked with which version of Rust is being used.
The issue was fixed in crate 3.6.0.
|
{'CVE-2018-20998'}
|
2021-10-19T22:14:35Z
|
2018-12-18T12:00:00Z
| null | null | null |
{'https://github.com/arrayfire/arrayfire-rust/pull/177', 'https://rustsec.org/advisories/RUSTSEC-2018-0011.html', 'https://crates.io/crates/arrayfire'}
| null |
crates.io
|
RUSTSEC-2021-0083
|
QueryInterface should call AddRef before returning pointer
|
Affected version of this crate, which is a required dependency in com-impl,
provides a faulty implementation of the `IUnknown::QueryInterface` method.
`QueryInterface` implementation must call `IUnknown::AddRef` before returning the pointer,
as describe in this documentation:
<https://docs.microsoft.com/en-us/windows/win32/api/unknwn/nf-unknwn-iunknown-queryinterface(refiid_void)>
As it is not incrementing the refcount as expected, the following calls to `IUnknown::Release` method
will cause WMI to drop reference to the interface, and can lead to invalid reference.
This is documented in <https://docs.microsoft.com/en-us/windows/win32/learnwin32/managing-the-lifetime-of-an-object#reference-counting>
There is no simple workaround, as you can't know how many time QueryInterface will be called.
The only way to quick fix this is to use the macro expanded version of the code and modify
the QueryInterface method to add the AddRef call yourself.
The issue was corrected in commit `9803f31fbd1717d482d848f041044d061fca6da7`.
| null |
2021-08-22T01:17:47Z
|
2021-01-20T12:00:00Z
| null | null | null |
{'https://crates.io/crates/derive-com-impl', 'https://rustsec.org/advisories/RUSTSEC-2021-0083.html', 'https://github.com/Connicpu/com-impl/issues/1'}
| null |
crates.io
|
GHSA-fg42-vwxx-xx5j
|
Data race in tiny_future
|
An issue was discovered in the tiny_future crate before 0.4.0 for Rust. Future<T> does not have bounds on its Send and Sync traits.
|
{'CVE-2020-36438'}
|
2021-08-18T19:41:50Z
|
2021-08-25T20:58:53Z
|
HIGH
| null |
{'CWE-119', 'CWE-362'}
|
{'https://github.com/KizzyCode/tiny_future', 'https://rustsec.org/advisories/RUSTSEC-2020-0118.html', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/tiny_future/RUSTSEC-2020-0118.md', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36438'}
| null |
crates.io
|
RUSTSEC-2021-0129
|
Invalid handling of `X509_verify_cert()` internal errors in libssl
|
Internally libssl in OpenSSL calls `X509_verify_cert()` on the client side to
verify a certificate supplied by a server. That function may return a negative
return value to indicate an internal error (for example out of memory). Such a
negative return value is mishandled by OpenSSL and will cause an IO function
(such as `SSL_connect()` or `SSL_do_handshake()`) to not indicate success and a
subsequent call to `SSL_get_error()` to return the value
`SSL_ERROR_WANT_RETRY_VERIFY`. This return value is only supposed to be returned
by OpenSSL if the application has previously called
`SSL_CTX_set_cert_verify_callback()`. Since most applications do not do this the
`SSL_ERROR_WANT_RETRY_VERIFY` return value from `SSL_get_error()` will be totally
unexpected and applications may not behave correctly as a result. The exact
behaviour will depend on the application but it could result in crashes,
infinite loops or other similar incorrect responses.
This issue is made more serious in combination with a separate bug in OpenSSL
3.0 that will cause `X509_verify_cert()` to indicate an internal error when
processing a certificate chain. This will occur where a certificate does not
include the Subject Alternative Name extension but where a Certificate Authority
has enforced name constraints. This issue can occur even with valid chains.
|
{'CVE-2021-4044'}
|
2021-12-15T00:18:24Z
|
2021-12-14T12:00:00Z
| null | null | null |
{'https://crates.io/crates/openssl-src', 'https://rustsec.org/advisories/RUSTSEC-2021-0129.html', 'https://www.openssl.org/news/secadv/20211214.txt'}
| null |
crates.io
|
GHSA-v5r6-6r3c-wqxc
|
Memory exhaustion in asn1_der
|
An issue was discovered in the asn1_der crate before 0.6.2 for Rust. Attackers can trigger memory exhaustion by supplying a large value in a length field.
|
{'CVE-2019-15549'}
|
2021-08-19T21:22:28Z
|
2021-08-25T20:44:56Z
|
HIGH
| null |
{'CWE-400'}
|
{'https://rustsec.org/advisories/RUSTSEC-2019-0007.html', 'https://nvd.nist.gov/vuln/detail/CVE-2019-15549', 'https://github.com/KizzyCode/asn1_der', 'https://github.com/KizzyCode/asn1_der/issues/1'}
| null |
crates.io
|
GHSA-c7fw-cr3w-wvfc
|
Data races in arr
|
An issue was discovered in the arr crate through 2020-08-25 for Rust. An attacker can smuggle non-Sync/Send types across a thread boundary to cause a data race.
|
{'CVE-2020-35886'}
|
2021-08-19T20:56:00Z
|
2021-08-25T20:49:04Z
|
MODERATE
| null |
{'CWE-362'}
|
{'https://github.com/sjep/array', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35886', 'https://github.com/sjep/array/issues/1', 'https://rustsec.org/advisories/RUSTSEC-2020-0034.html'}
| null |
crates.io
|
RUSTSEC-2020-0050
|
VecCopy allows misaligned access to elements
|
`VecCopy::data` is created as a Vec of u8 but can be used to store and retrieve
elements of different types leading to misaligned access.
The issue was resolved in v0.5.0 by replacing data being stored by `Vec<u8>` with a custom managed
pointer. Elements are now stored and retrieved using types with proper alignment corresponding to
original types.
|
{'CVE-2020-35903'}
|
2021-10-19T22:14:35Z
|
2020-09-27T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2020-0050.html', 'https://crates.io/crates/dync', 'https://github.com/elrnv/dync/issues/4'}
| null |
crates.io
|
RUSTSEC-2020-0115
|
Singleton lacks bounds on Send and Sync.
|
`Singleton<T>` is meant to be a static object that can be initialized lazily. In
order to satisfy the requirement that `static` items must implement `Sync`,
`Singleton` implemented both `Sync` and `Send` unconditionally.
This allows for a bug where non-`Sync` types such as `Cell` can be used in
singletons and cause data races in concurrent programs.
The flaw was corrected in commit `b0d2bd20e` by adding trait bounds, requiring
the contaiend type to implement `Sync`.
|
{'CVE-2020-36435'}
|
2021-10-19T22:14:35Z
|
2020-11-16T12:00:00Z
| null | null | null |
{'https://crates.io/crates/ruspiro-singleton', 'https://github.com/RusPiRo/ruspiro-singleton/issues/10', 'https://rustsec.org/advisories/RUSTSEC-2020-0115.html'}
| null |
crates.io
|
GHSA-gwfj-pw2x-h6c2
|
Out of bounds read in simd-json
|
An issue was discovered in the simd-json crate before 0.1.15 for Rust. There is an out-of-bounds read and an incorrect crossing of a page boundary.
|
{'CVE-2019-15550'}
|
2021-08-19T21:23:48Z
|
2021-08-25T20:43:56Z
|
HIGH
| null |
{'CWE-125'}
|
{'https://github.com/Licenser/simdjson-rs', 'https://rustsec.org/advisories/RUSTSEC-2019-0008.html', 'https://github.com/Licenser/simdjson-rs/pull/27', 'https://nvd.nist.gov/vuln/detail/CVE-2019-15550'}
| null |
crates.io
|
GHSA-36cg-4jff-5863
|
Data races in signal-simple
|
An issue was discovered in the signal-simple crate through 2020-11-15 for Rust. There are unconditional implementations of Send and Sync for SyncChannel<T>.
|
{'CVE-2020-36446'}
|
2021-08-18T20:06:20Z
|
2021-08-25T20:59:13Z
|
HIGH
| null |
{'CWE-119', 'CWE-362'}
|
{'http://github.com/kitsuneninetails/signal-rust', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36446', 'https://rustsec.org/advisories/RUSTSEC-2020-0126.html', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/signal-simple/RUSTSEC-2020-0126.md'}
| null |
crates.io
|
RUSTSEC-2021-0109
|
Process crashes when the cell used as DepGroup is not alive
|
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.
|
{'GHSA-45p7-c959-rgcm'}
|
2021-09-10T15:58:38Z
|
2021-07-25T12:00:00Z
| null | null | null |
{'https://github.com/nervosnetwork/ckb/security/advisories/GHSA-45p7-c959-rgcm', 'https://crates.io/crates/ckb', 'https://rustsec.org/advisories/RUSTSEC-2021-0109.html'}
| null |
crates.io
|
GHSA-7v2r-wxmg-mgvc
|
HTTP Request smuggling in tiny_http
|
An issue was discovered in the tiny_http crate through 2020-06-16 for Rust. HTTP Request smuggling can occur via a malformed Transfer-Encoding header.
|
{'CVE-2020-35884'}
|
2021-12-14T15:33:44Z
|
2021-08-25T20:48:56Z
|
MODERATE
| null |
{'CWE-444'}
|
{'https://github.com/tiny-http/tiny-http/pull/190', 'https://rustsec.org/advisories/RUSTSEC-2020-0031.html', 'https://github.com/tiny-http/tiny-http/issues/173', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35884', 'https://github.com/tiny-http/tiny-http', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VO6SRTCEPEYO2OX647I3H5XUWLFDRDWL/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/M3JDNRE5RXJOWZZZF5QSCG4GUCSLTHF2/'}
| null |
crates.io
|
RUSTSEC-2020-0007
|
use-after or double free of allocated memory
|
Conversion of `BitVec` to `BitBox` did not account for allocation movement.
The flaw was corrected by using the address after resizing, rather than the original base address.
|
{'CVE-2020-35862'}
|
2021-10-19T22:14:35Z
|
2020-03-27T12:00:00Z
| null | null | null |
{'https://crates.io/crates/bitvec', 'https://github.com/myrrlyn/bitvec/issues/55', 'https://rustsec.org/advisories/RUSTSEC-2020-0007.html'}
| null |
crates.io
|
GHSA-pq6v-x7gp-7776
|
Source code is downloaded over cleartext HTTP in portaudio
|
An issue was discovered in the portaudio crate through 0.7.0 for Rust. There is a man-in-the-middle issue because the source code is downloaded over cleartext HTTP.
|
{'CVE-2016-10933'}
|
2021-08-19T21:25:09Z
|
2021-08-25T20:43:09Z
|
MODERATE
| null |
{'CWE-319'}
|
{'https://github.com/RustAudio/rust-portaudio', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10933', 'https://rustsec.org/advisories/RUSTSEC-2016-0003.html', 'https://github.com/RustAudio/rust-portaudio/issues/144'}
| null |
crates.io
|
RUSTSEC-2020-0142
|
Send bound needed on T (for Send impl of `Bucket2`)
|
Affected versions of this crate unconditionally implements `Send` for `Bucket2`. This allows sending non-Send types to other threads.
This can lead to data races when non Send types like `Cell<T>` or `Rc<T>` are contained inside `Bucket2` and sent across thread boundaries. The data races can potentially lead to memory corruption (as demonstrated in the PoC from the original report issue).
The flaw was corrected in commit 15b2828 by adding a `T: Send` bound to the `Send` impl of `Bucket2<T>`.
|
{'CVE-2020-36462'}
|
2021-10-19T22:14:35Z
|
2020-11-29T12:00:00Z
| null | null | null |
{'https://github.com/Chopinsky/byte_buffer/issues/2', 'https://rustsec.org/advisories/RUSTSEC-2020-0142.html', 'https://crates.io/crates/syncpool'}
| null |
crates.io
|
GHSA-jjx5-3f36-6927
|
Incorrect buffer size calculation in iced-x86
|
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.
|
{'CVE-2021-38188'}
|
2021-08-18T21:31:51Z
|
2021-08-25T20:55:47Z
|
CRITICAL
| null |
{'CWE-131'}
|
{'https://github.com/icedland/iced/issues/168', 'https://rustsec.org/advisories/RUSTSEC-2021-0068.html', 'https://github.com/icedland/iced', 'https://github.com/icedland/iced/commit/3c607a003e03b773108401d109167d1840487dce', 'https://nvd.nist.gov/vuln/detail/CVE-2021-38188'}
| null |
crates.io
|
RUSTSEC-2020-0011
|
Library exclusively intended to obfuscate code.
|
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.
| null |
2020-10-25T19:51:46Z
|
2020-04-23T12:00:00Z
| null | null | null |
{'https://crates.io/crates/plutonium', 'https://docs.rs/plutonium', 'https://rustsec.org/advisories/RUSTSEC-2020-0011.html'}
| null |
crates.io
|
GHSA-hc92-9h3m-c39j
|
Incorrect cast in anymap
|
An issue was discovered in the anymap crate through 0.12.1 for Rust. It violates soundness via conversion of a *u8 to a *u64.
|
{'CVE-2021-38187'}
|
2021-08-18T21:32:29Z
|
2021-08-25T20:55:45Z
|
CRITICAL
| null |
{'CWE-681', 'CWE-704'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-38187', 'https://github.com/chris-morgan/anymap', 'https://github.com/chris-morgan/anymap/issues/37', 'https://rustsec.org/advisories/RUSTSEC-2021-0065.html'}
| null |
crates.io
|
RUSTSEC-2020-0154
|
InputStream::read_exact : `Read` on uninitialized buffer causes UB
|
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:30:23Z
|
2020-12-31T12:00:00Z
| null | null | null |
{'https://crates.io/crates/buffoon', 'https://github.com/carllerche/buffoon/issues/2', 'https://rustsec.org/advisories/RUSTSEC-2020-0154.html'}
| null |
crates.io
|
GHSA-v3j6-xf77-8r9c
|
Use-after-free in actix-http
|
An issue was discovered in the actix-http crate before 2.0.0-alpha.1 for Rust. There is a use-after-free in BodyStream.
|
{'CVE-2020-35901'}
|
2021-08-19T20:51:41Z
|
2021-08-25T20:49:39Z
|
HIGH
| null |
{'CWE-416'}
|
{'https://github.com/actix/actix-web/issues/1321', 'https://rustsec.org/advisories/RUSTSEC-2020-0048.html', 'https://github.com/actix/actix-web', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35901'}
| null |
crates.io
|
GHSA-wv4p-jp67-jr97
|
Data races in magnetic
|
An issue was discovered in the magnetic crate before 2.0.1 for Rust. MPMCConsumer and MPMCProducer allow cross-thread sending of a non-Send type.
|
{'CVE-2020-35925'}
|
2021-08-19T18:56:53Z
|
2021-08-25T20:50:05Z
|
MODERATE
| null |
{'CWE-362'}
|
{'https://github.com/johnshaw/magnetic', 'https://rustsec.org/advisories/RUSTSEC-2020-0088.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35925', 'https://github.com/johnshaw/magnetic/issues/9'}
| null |
crates.io
|
GHSA-8r7q-r9mx-35rh
|
Mishandling of format strings in rusqlite
|
An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated because rusqlite::trace::log mishandles format strings.
|
{'CVE-2020-35869'}
|
2021-08-19T21:18:40Z
|
2021-08-25T20:47:18Z
|
CRITICAL
| null |
{'CWE-134'}
|
{'https://github.com/rusqlite/rusqlite/commit/2327d3b774927fdf48903c0bdc1ca7ec93c7c8d0', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35869', 'https://github.com/rusqlite/rusqlite/releases/tag/0.23.0', 'https://rustsec.org/advisories/RUSTSEC-2020-0014.html', 'https://github.com/rusqlite/rusqlite'}
| null |
crates.io
|
RUSTSEC-2020-0046
|
bespoke Cell implementation allows obtaining several mutable references to the same data
|
The custom implementation of a Cell primitive in the affected versions of this crate
does not keep track of mutable references to the underlying data.
This allows obtaining several mutable references to the same object
which may result in arbitrary memory corruption, most likely use-after-free.
The flaw was corrected by switching from a bespoke `Cell<T>` implementation to `Rc<RefCell<T>>`.
|
{'CVE-2020-35899'}
|
2021-10-19T22:14:35Z
|
2020-01-08T12:00:00Z
| null | null | null |
{'https://crates.io/crates/actix-service', 'https://rustsec.org/advisories/RUSTSEC-2020-0046.html', 'https://github.com/actix/actix-net/pull/158'}
| null |
crates.io
|
GHSA-3cj3-jrrp-9rxf
|
Unchecked Return Value in xcb
|
An issue was discovered in the xcb crate through 2021-02-04 for Rust. It has a soundness violation because transmutation to the wrong type can happen after xcb::base::cast_event uses std::mem::transmute to return a reference to an arbitrary type.
|
{'CVE-2021-26958'}
|
2021-08-19T17:44:11Z
|
2021-08-25T20:53:18Z
|
HIGH
| null |
{'CWE-252'}
|
{'https://github.com/RustSec/advisory-db/issues/653', 'https://rustsec.org/advisories/RUSTSEC-2021-0019.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-26958', 'https://github.com/rtbo/rust-xcb'}
| null |
crates.io
|
GHSA-6hfq-h8hq-87mf
|
HTTP Request Smuggling in hyper
|
### Summary
hyper's HTTP server code had a flaw that incorrectly understands some requests with multiple transfer-encoding headers to have a chunked payload, when it should have been rejected as illegal. This combined with an upstream HTTP proxy that understands the request payload boundary differently can result in "request smuggling" or "desync attacks".
### Vulnerability
The flaw was introduced in https://github.com/hyperium/hyper/commit/26417fc24a7d05df538e0f39239b373c5c3d61f6, released in v0.12.0.
Consider this example request:
```
POST /yolo HTTP/1.1
Transfer-Encoding: chunked
Transfer-Encoding: cow
```
This request *should* be rejected, according to RFC 7230, since it has a `Transfer-Encoding` header, but after folding, it does not end in `chunked`. hyper would notice the `chunked` in the first line, and then check the second line, and thanks to a missing boolean assignment, *not* set the error condition. hyper would treat the payload as being `chunked`. By differing from the spec, it is possible to send requests like these to endpoints that have different HTTP implementations, with different interpretations of the payload semantics, and cause "desync attacks".
There are several parts of the spec that must also be checked, and hyper correctly handles all of those. Additionally, hyper's *client* does not allow sending requests with improper headers, so the misunderstanding cannot be propagated further.
Read more about desync attacks: https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn
### Impact
To determine if vulnerable, all these things must be true:
- **Using hyper as an HTTP *server*.** The client is not affected.
- **Using HTTP/1.1.** HTTP/2 does not use `transfer-encoding`.
- **Using a vulnerable HTTP proxy upstream to hyper.** If an upstream proxy correctly rejects the illegal transfer-encoding headers, the desync attack cannot succeed. If there is *no* proxy upstream of hyper, hyper cannot *start* the desync attack, as the client will repair the headers before forwarding.
### Patches
We have released and backported the following patch versions:
- v0.14.3
- v0.13.10
### Workarounds
Besides upgrading hyper, you can take the following options:
- Reject requests that contain a `transfer-encoding` header.
- Ensure any upstream proxy handles `transfer-encoding` correctly.
### Credits
This issue was initially reported by ZeddYu Lu From Qi An Xin Technology Research Institute.
|
{'CVE-2021-21299'}
|
2021-08-18T21:07:17Z
|
2021-08-25T20:56:18Z
|
MODERATE
| null |
{'CWE-444'}
|
{'https://github.com/hyperium/hyper/commit/8f93123efef5c1361086688fe4f34c83c89cec02', 'https://github.com/hyperium/hyper/security/advisories/GHSA-6hfq-h8hq-87mf', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21299', 'https://rustsec.org/advisories/RUSTSEC-2021-0020.html', 'https://github.com/hyperium/hyper', 'https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn'}
| null |
crates.io
|
GHSA-vp6r-mrq9-8f4h
|
Data race in syncpool
|
An issue was discovered in the syncpool crate before 0.1.6 for Rust. There is an unconditional implementation of Send for Bucket2.
|
{'CVE-2020-36462'}
|
2021-08-18T20:18:30Z
|
2021-08-25T20:58:11Z
|
HIGH
| null |
{'CWE-77', 'CWE-362'}
|
{'https://rustsec.org/advisories/RUSTSEC-2020-0142.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36462', 'https://github.com/Chopinsky/byte_buffer/issues/2', 'https://github.com/Chopinsky/byte_buffer/tree/master/syncpool', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/syncpool/RUSTSEC-2020-0142.md'}
| null |
crates.io
|
RUSTSEC-2020-0103
|
`impl Random` on arrays can lead to dropping uninitialized memory
|
Affected versions of this crate had a panic safety issue to drop partially uninitialized array of `T` upon panic in a user provided function `T::random()`. Dropping uninitialized `T` can potentially cause memory corruption or undefined behavior.
The flaw was corrected in commit 565d508 by using `MaybeUninit<T>` to avoid possible dropping of uninitialized memory upon panic.
|
{'CVE-2020-36210'}
|
2021-10-19T22:14:35Z
|
2020-12-31T12:00:00Z
| null | null | null |
{'https://crates.io/crates/autorand', 'https://rustsec.org/advisories/RUSTSEC-2020-0103.html', 'https://github.com/mersinvald/autorand-rs/issues/5'}
| null |
crates.io
|
GHSA-gvvv-w559-2hg6
|
Data races in scottqueue
|
An issue was discovered in the scottqueue crate through 2020-11-15 for Rust. There are unconditional implementations of Send and Sync for Queue<T>. This allows (1) creating data races to a `T: !Sync` and (2) sending `T: !Send` to other threads, resulting in memory corruption or other undefined behavior.
|
{'CVE-2020-36453'}
|
2021-08-24T17:59:17Z
|
2021-08-25T20:57:17Z
|
HIGH
| null |
{'CWE-362'}
|
{'https://github.com/rossdylan/rust-scottqueue/issues/1', 'https://github.com/rossdylan/rust-scottqueue', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36453', 'https://rustsec.org/advisories/RUSTSEC-2020-0133.html'}
| null |
crates.io
|
RUSTSEC-2021-0076
|
libsecp256k1 allows overflowing signatures
|
libsecp256k1 accepts signatures whose R or S parameter is larger than the
secp256k1 curve order, which differs from other implementations. This could
lead to invalid signatures being verified.
The error is resolved in 0.5.0 by adding a `check_overflow` flag.
|
{'CVE-2021-38195'}
|
2021-11-06T20:37:35Z
|
2021-07-13T12:00:00Z
| null | null | null |
{'https://crates.io/crates/libsecp256k1', 'https://github.com/paritytech/libsecp256k1/pull/67', 'https://rustsec.org/advisories/RUSTSEC-2021-0076.html'}
| null |
crates.io
|
GHSA-77m6-x95j-75r5
|
Data races in ticketed_lock
|
An issue was discovered in the ticketed_lock crate before 0.3.0 for Rust. There are unconditional implementations of Send for ReadTicket<T> and WriteTicket<T>.
|
{'CVE-2020-36439'}
|
2021-08-18T20:00:14Z
|
2021-08-25T20:58:58Z
|
HIGH
| null |
{'CWE-119', 'CWE-362'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-36439', 'https://rustsec.org/advisories/RUSTSEC-2020-0119.html', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/ticketed_lock/RUSTSEC-2020-0119.md', 'https://github.com/kvark/ticketed_lock/'}
| null |
crates.io
|
GHSA-fg7r-2g4j-5cgr
|
Race Condition in tokio
|
An issue was discovered in the tokio crate before 1.8.4, and 1.9.x through 1.13.x before 1.13.1, for Rust. In certain circumstances involving a closed oneshot channel, there is a data race and memory corruption.
|
{'CVE-2021-45710'}
|
2022-01-07T18:26:27Z
|
2022-01-06T22:04:37Z
|
HIGH
| null |
{'CWE-362'}
|
{'https://rustsec.org/advisories/RUSTSEC-2021-0124.html', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/tokio/RUSTSEC-2021-0124.md', 'https://github.com/tokio-rs/tokio', 'https://nvd.nist.gov/vuln/detail/CVE-2021-45710'}
| null |
crates.io
|
RUSTSEC-2021-0099
|
Crate has been renamed to `cosmrs`
|
The `cosmos_sdk` crate, which provides a basic Rust SDK for the Cosmos ecosystem,
has rebranded to “CosmRS” in the spirit of other projects like CosmJS and CosmWasm.
You can find the new home here:
https://github.com/cosmos/cosmos-rust/tree/main/cosmrs
The new crate name is `cosmrs`:
https://crates.io/crates/cosmrs
| null |
2021-08-25T14:54:10Z
|
2021-08-25T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2021-0099.html', 'https://crates.io/crates/cosmos_sdk', 'https://github.com/cosmos/cosmos-rust/issues/113'}
| null |
crates.io
|
RUSTSEC-2021-0133
|
cargo-download is unmaintained
|
The cargo download subcommand (via cargo-download crate) is broken and maintainer has disappeared from GitHub and hasn't had any commits for a year.
Using this downloader will result to corrupted crates.
Maintainer has not responded to maintenance takeover.
Just use wget / curl directly.
| null |
2021-12-25T18:20:22Z
|
2021-12-25T12:00:00Z
| null | null | null |
{'https://github.com/Xion/cargo-download', 'https://crates.io/crates/cargo-download', 'https://rustsec.org/advisories/RUSTSEC-2021-0133.html'}
| null |
crates.io
|
GHSA-9qvw-46gf-4fv8
|
Use After Free in tremor-script
|
An issue was discovered in the tremor-script crate before 0.11.6 for Rust. A merge operation may result in a use-after-free.
|
{'CVE-2021-45702'}
|
2022-01-07T17:41:11Z
|
2022-01-06T22:09:07Z
|
HIGH
| null |
{'CWE-416'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-45702', 'https://rustsec.org/advisories/RUSTSEC-2021-0111.html', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/tremor-script/RUSTSEC-2021-0111.md'}
| null |
crates.io
|
GHSA-x446-3xhq-5xfp
|
Exposure of Resource to Wrong Sphere in Simple-Wayland-HotKey-Daemon
|
SWHKD 1.1.5 allows arbitrary file-existence tests via the -c option.
|
{'CVE-2022-27814'}
|
2022-04-26T13:03:51Z
|
2022-04-15T00:00:40Z
|
LOW
| null |
{'CWE-668'}
|
{'https://www.openwall.com/lists/oss-security/2022/04/14/1', 'https://github.com/waycrate/swhkd', 'https://nvd.nist.gov/vuln/detail/CVE-2022-27814', 'https://github.com/waycrate/swhkd/releases'}
| null |
crates.io
|
GHSA-458v-4hrf-g3m4
|
socket2 invalidly assumes the memory layout of std::net::SocketAddr
|
The socket2 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-35920'}
|
2021-08-24T17:42:57Z
|
2021-08-25T20:50:37Z
|
MODERATE
| null |
{'CWE-188'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-35920', 'https://rustsec.org/advisories/RUSTSEC-2020-0079.html', 'https://github.com/rust-lang/socket2-rs/issues/119', 'https://github.com/rust-lang/socket2-rs'}
| null |
crates.io
|
RUSTSEC-2021-0021
|
`nb-connect` invalidly assumes the memory layout of std::net::SocketAddr
|
The [`nb-connect`](https://crates.io/crates/nb-connect) 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-2021-27376'}
|
2021-10-19T22:14:35Z
|
2021-02-14T12:00:00Z
| null | null | null |
{'https://github.com/smol-rs/nb-connect/issues/1', 'https://crates.io/crates/nb-connect', 'https://rustsec.org/advisories/RUSTSEC-2021-0021.html'}
| null |
crates.io
|
GHSA-vc5p-j8vw-mc6x
|
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.
|
{'CVE-2021-31155'}
|
2021-06-08T17:14:30Z
|
2021-08-25T21:01:47Z
|
HIGH
| null |
{'CWE-269', 'CWE-279'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-31155', 'https://gitlab.com/edneville/please/-/tree/master/src/bin', 'https://gitlab.com/edneville/please', 'https://crates.io/crates/pleaser', 'https://www.openwall.com/lists/oss-security/2021/05/18/1'}
| null |
crates.io
|
RUSTSEC-2016-0005
|
rust-crypto is unmaintained; switch to a modern alternative
|
The `rust-crypto` crate has not seen a release or GitHub commit since 2016,
and its author is unresponsive.
*NOTE: The (old) `rust-crypto` crate (with hyphen) should not be confused with
similarly named (new) [RustCrypto GitHub Org] (without hyphen). The GitHub Org
is actively maintained.*
We recommend you switch to one of the following crates instead, depending on
which algorithms you need:
- [dalek-cryptography GitHub Org]:
- Key agreement: [`x25519-dalek`]
- Signature algorithms: [`ed25519-dalek`]
- [`ring`]:
- AEAD algorithms: AES-GCM, ChaCha20Poly1305
- Digest algorithms: SHA-256, SHA-384, SHA-512, SHA-512/256 (legacy: SHA-1)
- HMAC
- Key agreement: ECDH (P-256, P-384), X25519
- Key derivation: HKDF
- Password hashing: PBKDF2
- Signature algorithms: ECDSA (P-256, P-384), Ed25519, RSA (PKCS#1v1.5, PSS)
- [RustCrypto GitHub Org]:
- AEAD algorithms: [`aes-gcm`], [`aes-gcm-siv`], [`aes-siv`], [`chacha20poly1305`], [`xsalsa20poly1305`]
- Block ciphers: [`aes`], [`cast5`], [`des`]
- Digest algorithms: [`sha2`], [`sha3`], [`blake2`], [`ripemd160`]
(legacy: [`sha-1`], [`md-5`])
- Key derivation: [`hkdf`]
- MACs: [`cmac`], [`hmac`], [`pmac`], [`poly1305`]
- Password hashing: [`pbkdf2`]
- Stream ciphers: [`aes-ctr`], [`chacha20`], [`hc-256`], [`salsa20`]
- [`secp256k1`]:
- Key agreement: ECDH (secp256k1 only)
- Signature algorithms: ECDSA (secp256k1 only)
- [`orion`]:
- AEAD algorithms: ChaCha20Poly1305 (IETF version), XChaCha20Poly1305
- Digest algorithms: SHA-512, BLAKE2b
- Key derivation: HKDF
- MACs: HMAC, Poly1305
- Password hashing: PBKDF2
- Stream ciphers: ChaCha20 (IETF version), XChaCha20
[dalek-cryptography GitHub Org]: https://github.com/dalek-cryptography
[RustCrypto GitHub Org]: https://github.com/RustCrypto
[`aes`]: https://crates.io/crates/aes
[`aes-ctr`]: https://crates.io/crates/aes-ctr
[`aes-gcm`]: https://crates.io/crates/aes-gcm
[`aes-gcm-siv`]: https://crates.io/crates/aes-gcm-siv
[`aes-siv`]: https://crates.io/crates/aes-siv
[`blake2`]: https://crates.io/crates/blake2
[`cast5`]: https://crates.io/crates/cast5
[`chacha20`]: https://crates.io/crates/chacha20
[`chacha20poly1305`]: https://crates.io/crates/chacha20poly1305
[`cmac`]: https://crates.io/crates/cmac
[`des`]: https://crates.io/crates/des
[`ed25519-dalek`]: https://crates.io/crates/ed25519-dalek
[`hc-256`]: https://crates.io/crates/hc-256
[`hkdf`]: https://crates.io/crates/hkdf
[`hmac`]: https://crates.io/crates/hmac
[`pbkdf2`]: https://crates.io/crates/pbkdf2
[`pmac`]: https://crates.io/crates/pmac
[`poly1305`]: https://crates.io/crates/poly1305
[`ring`]: https://crates.io/crates/ring
[`ripemd160`]: https://crates.io/crates/ripemd160
[`salsa20`]: https://crates.io/crates/salsa20
[`secp256k1`]: https://crates.io/crates/secp256k1
[`sha-1`]: https://crates.io/crates/sha-1
[`sha2`]: https://crates.io/crates/sha2
[`sha3`]: https://crates.io/crates/sha3
[`x25519-dalek`]: https://crates.io/crates/x25519-dalek
[`xsalsa20poly1305`]: https://crates.io/crates/xsalsa20poly1305
[`orion`]: https://crates.io/crates/orion
| null |
2022-01-09T20:07:15Z
|
2016-09-06T12:00:00Z
| null | null | null |
{'https://github.com/DaGenix/rust-crypto/issues/440', 'https://rustsec.org/advisories/RUSTSEC-2016-0005.html', 'https://crates.io/crates/rust-crypto'}
| null |
crates.io
|
RUSTSEC-2020-0085
|
crate has been renamed to `sn_node`
|
This crate has been renamed from `safe_vault` to `sn_node`.
The new repository location is:
<https://github.com/maidsafe/sn_node>
| null |
2020-12-07T17:22:02Z
|
2020-12-07T12:00:00Z
| null | null | null |
{'https://github.com/maidsafe/sn_node/pull/1116', 'https://rustsec.org/advisories/RUSTSEC-2020-0085.html', 'https://crates.io/crates/safe_vault'}
| null |
crates.io
|
GHSA-f6f2-3w33-54r9
|
Use After Free in rusqlite
|
An issue was discovered in the rusqlite crate 0.25.x before 0.25.4 and 0.26.x before 0.26.2 for Rust. create_aggregate_function has a use-after-free.
|
{'CVE-2021-45714'}
|
2022-01-07T16:14:05Z
|
2022-01-06T22:02:36Z
|
HIGH
| null |
{'CWE-416'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-45714', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/rusqlite/RUSTSEC-2021-0128.md', 'https://rustsec.org/advisories/RUSTSEC-2021-0128.html', 'https://github.com/rusqlite/rusqlite'}
| null |
crates.io
|
RUSTSEC-2019-0017
|
Panic during initialization of Lazy<T> might trigger undefined behavior
|
If during the first dereference of Lazy<T> the initialization function panics,
subsequent dereferences will execute `std::hints::unreachable_unchecked`.
Applications with `panic = "abort"` are not affected, as there will be no
subsequent dereferences.
|
{'CVE-2019-16141'}
|
2021-10-19T22:14:35Z
|
2019-09-01T12:00:00Z
| null | null | null |
{'https://github.com/matklad/once_cell/issues/46', 'https://rustsec.org/advisories/RUSTSEC-2019-0017.html', 'https://crates.io/crates/once_cell'}
| null |
crates.io
|
RUSTSEC-2021-0037
|
Fix a use-after-free bug in diesels Sqlite backend
|
We've misused `sqlite3_column_name`. The
[SQLite](https://www.sqlite.org/c3ref/column_name.html) documentation
states that the following:
> The returned string pointer is valid until either the prepared statement
> is destroyed by sqlite3_finalize() or until the statement is automatically
> reprepared by the first call to sqlite3_step() for a particular
> run or until the next call to sqlite3_column_name()
> or sqlite3_column_name16() on the same column.
As part of our `query_by_name` infrastructure we've first received all
field names for the prepared statement and stored them as string slices
for later use. After that we called `sqlite3_step()` for the first time,
which invalids the pointer and therefore the stored string slice.
|
{'CVE-2021-28305'}
|
2021-10-19T22:14:35Z
|
2021-03-05T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2021-0037.html', 'https://github.com/diesel-rs/diesel/pull/2663', 'https://crates.io/crates/diesel'}
| null |
crates.io
|
GHSA-3358-4f7f-p4j4
|
Use after free in generic-array
|
An issue was discovered in the generic-array crate before 0.13.3 for Rust. It violates soundness by using the arr! macro to extend lifetimes.
|
{'CVE-2020-36465'}
|
2021-08-18T21:16:25Z
|
2021-08-25T20:56:12Z
|
HIGH
| null |
{'CWE-416'}
|
{'https://github.com/fizyk20/generic-array', 'https://github.com/fizyk20/generic-array/issues/98', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36465', 'https://rustsec.org/advisories/RUSTSEC-2020-0146.html'}
| null |
crates.io
|
GHSA-6mv9-qcx2-3hh3
|
Memory exhaustion in routinator
|
NLnet Labs Routinator versions 0.9.0 up to and including 0.10.1, support the gzip transfer encoding when querying RRDP repositories. This encoding can be used by an RRDP repository to cause an out-of-memory crash in these versions of Routinator. RRDP uses XML which allows arbitrary amounts of white space in the encoded data. The gzip scheme compresses such white space extremely well, leading to very small compressed files that become huge when being decompressed for further processing, big enough that Routinator runs out of memory when parsing input data waiting for the next XML element.
|
{'CVE-2021-43174'}
|
2021-11-15T14:48:03Z
|
2021-11-11T00:55:08Z
|
HIGH
| null |
{'CWE-787'}
|
{'https://www.debian.org/security/2022/dsa-5041', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43174', 'https://www.nlnetlabs.nl/downloads/routinator/CVE-2021-43172_CVE-2021-43173_CVE-2021-43174.txt', 'https://github.com/NLnetLabs/routinator'}
| null |
crates.io
|
GHSA-r7rv-2rph-hvhj
|
Improper synchronization in buttplug
|
An issue was discovered in the buttplug crate before 1.0.4 for Rust. ButtplugFutureStateShared does not properly consider (!Send|!Sync) objects, leading to a data race.
|
{'CVE-2020-36218'}
|
2021-08-19T18:48:19Z
|
2021-08-25T20:51:45Z
|
MODERATE
| null |
{'CWE-662'}
|
{'https://github.com/buttplugio/buttplug-rs/issues/225', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36218', 'https://github.com/buttplugio/buttplug-rs', 'https://rustsec.org/advisories/RUSTSEC-2020-0112.html'}
| null |
crates.io
|
RUSTSEC-2020-0139
|
dces' World type can cause data races
|
The `World` type in `dces` is marked as `Send` without bounds on its
`EntityStore` and `ComponentStore`.
This allows non-thread safe `EntityStore` and `ComponentStore`s to be sent
across threads and cause data races.
|
{'CVE-2020-36459'}
|
2021-10-19T22:14:35Z
|
2020-12-09T12:00:00Z
| null | null | null |
{'https://crates.io/crates/dces', 'https://gitlab.redox-os.org/redox-os/dces-rust/-/issues/8', 'https://rustsec.org/advisories/RUSTSEC-2020-0139.html'}
| null |
crates.io
|
GHSA-v938-qcc9-rwv8
|
Use of Uninitialized Resource in buffoon.
|
An issue was discovered in the buffoon crate through 2020-12-31 for Rust. InputStream::read_exact may read from uninitialized memory locations.
|
{'CVE-2020-36512'}
|
2022-01-07T16:24:01Z
|
2022-01-06T22:17:09Z
|
CRITICAL
| null |
{'CWE-908'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-36512', 'https://github.com/carllerche/buffoon', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/buffoon/RUSTSEC-2020-0154.md', 'https://rustsec.org/advisories/RUSTSEC-2020-0154.html'}
| null |
crates.io
|
RUSTSEC-2020-0093
|
Async-h1 request smuggling possible with long unread bodies
|
This vulnerability affects any webserver that uses async-h1 behind a reverse proxy, including all such Tide applications.
If the server does not read the body of a request which is longer than some buffer length, async-h1 will attempt to read a subsequent request from the body content starting at that offset into the body.
One way to exploit this vulnerability would be for an adversary to craft a request such that the body contains a request that would not be noticed by a reverse proxy, allowing it to forge forwarded/x-forwarded headers. If an application trusted the authenticity of these headers, it could be misled by the smuggled request.
Another potential concern with this vulnerability is that if a reverse proxy is sending multiple http clients' requests along the same keep-alive connection, it would be possible for the smuggled request to specify a long content and capture another user's request in its body. This content could be captured in a post request to an endpoint that allows the content to be subsequently retrieved by the adversary.
The flaw was corrected in commit [7df79f](https://github.com/http-rs/async-h1/commit/7df79f1d5d99fc0f492b315eebc7f0d301a85212) by ensuring that the request body is always consumed from the tcp stream before attempting to read subsequent keep-alive request headers from it.
|
{'GHSA-4vr9-8cjf-vf9c', 'CVE-2020-26281', 'CVE-2020-36202'}
|
2021-02-26T01:00:25Z
|
2020-12-17T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2020-0093.html', 'https://crates.io/crates/async-h1', 'https://github.com/http-rs/async-h1/releases/tag/v2.3.0'}
| null |
crates.io
|
RUSTSEC-2019-0001
|
Uncontrolled recursion leads to abort in HTML serialization
|
Affected versions of this crate did use recursion for serialization of HTML
DOM trees.
This allows an attacker to cause abort due to stack overflow by providing
a pathologically nested input.
The flaw was corrected by serializing the DOM tree iteratively instead.
|
{'CVE-2019-15542'}
|
2021-10-19T22:14:35Z
|
2019-04-27T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2019-0001.html', 'https://crates.io/crates/ammonia', 'https://github.com/rust-ammonia/ammonia/blob/master/CHANGELOG.md#210'}
| null |
crates.io
|
GHSA-6vmq-jh76-hq43
|
Uninitialized memory access in outer_cgi
|
An issue was discovered in the outer_cgi crate before 0.2.1 for Rust. A user-provided Read instance receives an uninitialized memory buffer from KeyValueReader.
|
{'CVE-2021-30454'}
|
2021-08-19T17:03:35Z
|
2021-08-25T20:55:25Z
|
CRITICAL
| null |
{'CWE-119'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-30454', 'https://github.com/SolraBizna/outer_cgi/issues/1', 'https://github.com/SolraBizna/outer_cgi', 'https://rustsec.org/advisories/RUSTSEC-2021-0051.html', 'https://github.com/SolraBizna/outer_cgi/commit/dd59b3066e616a08e756f72de8dc3ab11b7036c4'}
| null |
crates.io
|
GHSA-wgx2-6432-j3fw
|
Unsoundness in bigint
|
An issue was discovered in the bigint crate through 2020-05-07 for Rust. It allows a soundness violation.
|
{'CVE-2020-35880'}
|
2021-08-19T21:07:53Z
|
2021-08-25T20:48:04Z
|
CRITICAL
| null |
{'CWE-704'}
|
{'https://github.com/rustsec/advisory-db/pull/290', 'https://rustsec.org/advisories/RUSTSEC-2020-0025.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35880', 'https://github.com/paritytech/bigint', 'https://github.com/paritytech/bigint/commit/7e71521a61b009afc94c91135353102658550d42'}
| null |
crates.io
|
RUSTSEC-2021-0060
|
`aes-soft` has been merged into the `aes` crate
|
Please use the `aes` crate going forward. The new repository location is at:
<https://github.com/RustCrypto/block-ciphers/tree/master/aes>
AES-NI is now autodetected at runtime on `i686`/`x86-64` platforms.
If AES-NI is not present, the `aes` crate will fallback to a constant-time
portable software implementation.
To force the use of a constant-time portable implementation on these platforms,
even if AES-NI is available, use the new `force-soft` feature of the `aes`
crate to disable autodetection.
| null |
2021-05-04T01:28:43Z
|
2021-04-29T12:00:00Z
| null | null | null |
{'https://crates.io/crates/aes-soft', 'https://rustsec.org/advisories/RUSTSEC-2021-0060.html', 'https://github.com/RustCrypto/block-ciphers/pull/200'}
| null |
crates.io
|
RUSTSEC-2021-0125
|
Panic on incorrect date input to `simple_asn1`
|
Version 0.6.0 of the `simple_asn1` crate panics on certain malformed
inputs to its parsing functions, including `from_der` and `der_decode`.
Because this crate is frequently used with inputs from the network, this
should be considered a security vulnerability.
The issue occurs when parsing the old ASN.1 "UTCTime" time format. If an
attacker provides a UTCTime where the first character is ASCII but the
second character is above 0x7f, a string slice operation in the
`from_der_` function will try to slice into the middle of a UTF-8
character, and cause a panic.
This error was introduced in commit
[`d7d39d709577710e9dc8`](https://github.com/acw/simple_asn1/commit/d7d39d709577710e9dc8833ee57d200eef366db8),
which updated `simple_asn1` to use `time` instead of `chrono` because of
[`RUSTSEC-2020-159`](https://rustsec.org/advisories/RUSTSEC-2020-0159).
Versions of `simple_asn1` before 0.6.0 are not affected by this issue.
The [patch](https://github.com/acw/simple_asn1/pull/28) was applied in
`simple_asn1` version 0.6.1.
| null |
2021-11-18T00:32:59Z
|
2021-11-14T12:00:00Z
| null | null | null |
{'https://crates.io/crates/simple_asn1', 'https://github.com/acw/simple_asn1/issues/27', 'https://rustsec.org/advisories/RUSTSEC-2021-0125.html'}
| null |
crates.io
|
GHSA-pvh2-pj76-4m96
|
Specification non-compliance in JUMPI
|
### Impact
In `evm` crate `< 0.31.0`, `JUMPI` opcode's condition is checked after the destination validity check. However, according to Geth and OpenEthereum, the condition check should happen before the destination validity check.
### Patches
This is a **high** severity security advisory if you use `evm` crate for Ethereum mainnet. In this case, you should update your library dependency immediately to on or after `0.31.0`.
This is a **low** severity security advisory if you use `evm` crate in Frontier or in a standalone blockchain, because there's no security exploit possible with this advisory. It is **not** recommended to update to on or after `0.31.0` until all the normal chain upgrade preparations have been done. If you use Frontier or other `pallet-evm` based Substrate blockchain, please ensure to update your `spec_version` before updating this. For other blockchains, please make sure to follow a hard-fork process before you update this.
### Workarounds
If you are dependent on an older version of `evm` and cannot update due to API interface changes, please contact Wei by email (wei@that.world), who will be happy to help you to publish patch releases for older `evm` versions.
### References
Fix PR: https://github.com/rust-blockchain/evm/pull/67
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the `evm` repo.
### Special thanks
Special thanks to @rakita for reporting this issue.
|
{'CVE-2021-41153'}
|
2021-10-25T20:07:57Z
|
2021-10-19T15:28:35Z
|
HIGH
| null |
{'CWE-670'}
|
{'https://github.com/rust-blockchain/evm', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41153', 'https://github.com/rust-blockchain/evm/security/advisories/GHSA-pvh2-pj76-4m96', 'https://github.com/rust-blockchain/evm/pull/67'}
| null |
crates.io
|
GHSA-hv7x-f3pv-gpwr
|
Wrong memory orderings violates mutual exclusion in spin
|
An issue was discovered in the spin crate before 0.5.2 for Rust, when RwLock is used. Because memory ordering is mishandled, two writers can acquire the lock at the same time, violating mutual exclusion.
|
{'CVE-2019-16137'}
|
2021-08-19T21:22:40Z
|
2021-08-25T20:44:46Z
|
HIGH
| null |
{'CWE-662'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2019-16137', 'https://rustsec.org/advisories/RUSTSEC-2019-0013.html', 'https://github.com/mvdnes/spin-rs', 'https://github.com/mvdnes/spin-rs/issues/65'}
| null |
crates.io
|
GHSA-rpcm-whqc-jfw8
|
Use after free in libflate
|
An issue was discovered in the libflate crate before 0.1.25 for Rust. MultiDecoder::read has a use-after-free, leading to arbitrary code execution.
|
{'CVE-2019-15552'}
|
2021-08-19T21:22:31Z
|
2021-08-25T20:44:53Z
|
CRITICAL
| null |
{'CWE-416'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2019-15552', 'https://github.com/sile/libflate', 'https://github.com/sile/libflate/issues/35', 'https://rustsec.org/advisories/RUSTSEC-2019-0010.html'}
| null |
crates.io
|
RUSTSEC-2021-0061
|
`aes-ctr` has been merged into the `aes` crate
|
Please use the `aes` crate going forward. The new repository location is at:
<https://github.com/RustCrypto/block-ciphers/tree/master/aes>
The `aes` crate now has an optional `ctr` feature which autodetects SIMD
features on `i686`/`x86-64` targets and uses them if available, or otherwise
falls back to the implementation in the `ctr` crate.
If you would prefer not to have this autodetection performed, use the `aes`
crate directly with the `ctr` crate.
| null |
2021-05-04T01:28:43Z
|
2021-04-29T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2021-0061.html', 'https://crates.io/crates/aes-ctr', 'https://github.com/RustCrypto/block-ciphers/pull/200'}
| null |
crates.io
|
RUSTSEC-2021-0124
|
Data race when sending and receiving after closing a `oneshot` channel
|
If a `tokio::sync::oneshot` channel is closed (via the
[`oneshot::Receiver::close`] method), a data race may occur if the
`oneshot::Sender::send` method is called while the corresponding
`oneshot::Receiver` is `await`ed or calling `try_recv`.
When these methods are called concurrently on a closed channel, the two halves
of the channel can concurrently access a shared memory location, resulting in a
data race. This has been observed to [cause memory corruption][corruption].
Note that the race only occurs when **both** halves of the channel are used
after the `Receiver` half has called `close`. Code where `close` is not used, or where the
`Receiver` is not `await`ed and `try_recv` is not called after calling `close`,
is not affected.
See [tokio#4225][issue] for more details.
[corruption]: https://github.com/tokio-rs/tokio/issues/4225#issuecomment-967434847
[issue]: https://github.com/tokio-rs/tokio/issues/4225
[`oneshot::Receiver::close`]: https://docs.rs/tokio/1.14.0/tokio/sync/oneshot/struct.Receiver.html#method.close
|
{'CVE-2021-45710'}
|
2022-01-13T20:33:38Z
|
2021-11-16T12:00:00Z
| null | null | null |
{'https://github.com/tokio-rs/tokio/issues/4225', 'https://rustsec.org/advisories/RUSTSEC-2021-0124.html', 'https://crates.io/crates/tokio'}
| null |
crates.io
|
RUSTSEC-2020-0138
|
ReaderResult should be bounded by Sync
|
Affected versions of this crate implements `Sync` for `ReaderResult<T, E>` with the trait bound `T: Send, E: Send`.
Since matching on the public enum `ReaderResult<T, E>` provides access to `&T` & `&E`,
allowing data race to a non-Sync type `T` or `E`.
This can result in a memory corruption when multiple threads concurrently access `&T` or `&E`.
Suggested fix for the bug is change the trait bounds imposed on `T` & `E` to be `T: Sync, E: Sync`.
|
{'CVE-2020-36458'}
|
2021-10-19T22:14:35Z
|
2020-11-10T12:00:00Z
| null | null | null |
{'https://gitlab.com/nathanfaucett/rs-lexer/-/issues/2', 'https://crates.io/crates/lexer', 'https://rustsec.org/advisories/RUSTSEC-2020-0138.html'}
| null |
crates.io
|
RUSTSEC-2020-0092
|
Send/Sync bound needed on V in `impl Send/Sync for ARCache<K, V>`
|
Affected versions of this crate unconditionally implemented `Send`/`Sync` traits for `ARCache<K, V>` type.
This allows users to send/access types that do not implement `Send`/`Sync`, which can cause a data race.
The flaw was corrected in the 0.2.6 release by adding bounds `K: Send + Sync` & `V: Send + Sync` to affected `Send`/`Sync` trait implementations.
|
{'CVE-2020-35928'}
|
2021-10-19T22:14:35Z
|
2020-11-13T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2020-0092.html', 'https://github.com/kanidm/concread/issues/48', 'https://crates.io/crates/concread'}
| null |
crates.io
|
RUSTSEC-2021-0036
|
Intern<T>: Data race allowed on T
|
Affected versions of this crate unconditionally implements `Sync` for `Intern<T>`.
This allows users to create data race on `T: !Sync`, which may lead to undefined behavior
(for example, memory corruption).
The flaw was corrected in commit 2928a87 by adding the trait bound `T: Sync` in the `Sync` impl of `Intern<T>`.
|
{'CVE-2021-28037'}
|
2021-10-19T22:14:35Z
|
2021-03-03T12:00:00Z
| null | null | null |
{'https://github.com/droundy/internment/issues/20', 'https://crates.io/crates/internment', 'https://rustsec.org/advisories/RUSTSEC-2021-0036.html'}
| null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.