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-8m49-2xj8-67v9
|
Data Loss/Denial of Service in SWHKD
|
SWHKD 1.1.5 unsafely uses the /tmp/swhks.pid pathname. There can be data loss or a denial of service. A patch is available on the `1.1.0` branch of the repository.
|
{'CVE-2022-27816'}
|
2022-04-28T18:02:03Z
|
2022-03-31T00:00:24Z
|
HIGH
| null |
{'CWE-59'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2022-27816', 'http://www.openwall.com/lists/oss-security/2022/04/14/1', 'https://github.com/waycrate/swhkd/commit/0b620a09605afb815c6d8d8953bbb7a10a8c0575', 'https://github.com/waycrate/swhkd'}
| null |
crates.io
|
RUSTSEC-2020-0108
|
Soundness issue: Input<R> can be misused to create data race to an object
|
`Input<R>` implements `Send` without requiring `R: Send`.
Affected versions of this crate allows users to send non-Send types to other threads,
which can lead to undefined behavior such as data race and memory corruption.
The flaw was corrected in version 0.5.1 by adding `R: Send` bound to the `Send` impl of `Input<R>`.
|
{'CVE-2020-36216'}
|
2021-10-19T22:14:35Z
|
2020-12-20T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2020-0108.html', 'https://github.com/petabi/eventio/issues/33', 'https://crates.io/crates/eventio'}
| null |
crates.io
|
RUSTSEC-2021-0114
|
Aliased mutable references from `tls_rand` & `TlsWyRand`
|
`TlsWyRand`'s implementation of `Deref` unconditionally dereferences a raw pointer, and returns
multiple mutable references to the same object, which is undefined behavior.
| null |
2021-09-23T20:26:20Z
|
2021-09-23T12:00:00Z
| null | null | null |
{'https://github.com/Absolucy/nanorand-rs/issues/28', 'https://crates.io/crates/nanorand', 'https://rustsec.org/advisories/RUSTSEC-2021-0114.html'}
| null |
crates.io
|
GHSA-c8hq-x4mm-p6q6
|
Memory handling issues in xcb
|
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur.
|
{'CVE-2020-36205'}
|
2021-08-19T18:50:43Z
|
2021-08-25T20:50:54Z
|
MODERATE
| null |
{'CWE-416', 'CWE-415'}
|
{'https://github.com/rtbo/rust-xcb/issues/93', 'https://rustsec.org/advisories/RUSTSEC-2020-0097.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36205', 'https://github.com/rtbo/rust-xcb'}
| null |
crates.io
|
RUSTSEC-2021-0051
|
KeyValueReader passes uninitialized memory to Read instance
|
The `KeyValueReader` type in affected versions of this crate set up an
uninitialized memory buffer and passed them to be read in to a user-provided
`Read` instance.
The `Read` instance could read uninitialized memory and cause undefined
behavior and miscompilations.
This issue was fixed in commit [dd59b30](https://github.com/SolraBizna/outer_cgi/commit/dd59b3066e616a08e756f72de8dc3ab11b7036c4)
by zero-initializing the buffers before passing them.
|
{'CVE-2021-30454'}
|
2021-10-19T22:14:35Z
|
2021-01-31T12:00:00Z
| null | null | null |
{'https://crates.io/crates/outer_cgi', 'https://github.com/SolraBizna/outer_cgi/issues/1', 'https://rustsec.org/advisories/RUSTSEC-2021-0051.html'}
| null |
crates.io
|
RUSTSEC-2022-0004
|
Stack overflow in rustc_serialize when parsing deeply nested JSON
|
When parsing JSON using `json::Json::from_str`, there is no limit to the depth of the stack, therefore deeply nested objects can cause a stack overflow, which aborts the process.
Example code that triggers the vulnerability is
```rust
fn main() {
let _ = rustc_serialize::json::Json::from_str(&"[0,[".repeat(10000));
}
```
[serde](https://crates.io/crates/serde) is recommended as a replacement to rustc_serialize.
| null |
2022-01-21T18:16:26Z
|
2022-01-01T12:00:00Z
| null | null | null |
{'https://crates.io/crates/rustc-serialize', 'https://rustsec.org/advisories/RUSTSEC-2022-0004.html'}
| null |
crates.io
|
GHSA-xwqr-xmgg-j69q
|
Integer overflow in solana_rbpf
|
From version 0.2.14 to 0.2.16 for Solana rBPF, function "relocate" in the file src/elf.rs has an integer overflow bug because the sym.st_value is read directly from ELF file without checking. If the sym.st_value is rather large, an integer overflow is triggered while calculating the variable "addr" via "addr = (sym.st_value + refd_pa) as u64";
|
{'CVE-2021-46102'}
|
2022-02-08T19:45:10Z
|
2022-01-28T22:59:28Z
|
HIGH
| null |
{'CWE-190'}
|
{'https://github.com/solana-labs/rbpf/pull/200', 'https://blocksecteam.medium.com/new-integer-overflow-bug-discovered-in-solana-rbpf-7729717159ee', 'https://github.com/solana-labs/rbpf/releases/tag/v0.2.17', 'https://github.com/solana-labs/rbpf/pull/236', 'https://github.com/solana-labs/rbpf/blob/c14764850f0b83b58aa013248eaf6d65836c1218/src/elf.rs#L609-L630', 'https://nvd.nist.gov/vuln/detail/CVE-2021-46102', 'https://github.com/solana-labs/rbpf'}
| null |
crates.io
|
GHSA-45w3-v3g4-54pm
|
Potential segfault in SPIFFE authenticator
|
### Impact
Several vulnerabilities have been reported in the `time` and `chrono` crates related to handling of calls to `localtime_r`. You can follow some of the discussions [here](https://github.com/chronotope/chrono/issues/602) and [here](https://github.com/time-rs/time/issues/293), and the associated CVE [here](https://nvd.nist.gov/vuln/detail/CVE-2020-26235). In our case, the issue with the dependency was flagged by our nightly CI build running [`cargo-audit`](https://github.com/parallaxsecond/parsec/issues/544).
The vulnerability leads to a segfault in specific circumstances - namely, when one of a number of functions in the `time` crate is called while any other thread is setting an environment variable. Given that in the case of the Parsec service this affects the SPIFFE authenticator, Parsec service users can encounter the issue only when the JWT SVID authenticator is enabled and being used. We have not undergone any manual tracing to understand if the vulnerable methods are called anywhere in our stack, however it seems reasonable to expect that if that were to be the case, the issue would lie in JWT validation (i.e. when handling the dates found within a Json Web Token). JWT validation could thus fail, bringing down the thread in which the request happens. The rest of the threads continue to work. Since the threadpool implementation that we use [continues replenishing the pool](https://docs.rs/threadpool/latest/threadpool/) when one thread panics, the impact on the service should be minimal.
### Patches
No current patches exist as the problems lie in a number of dependencies that are not under our control (see more details [here](https://github.com/parallaxsecond/parsec/issues/544#issuecomment-1024185688)).
The issue tracking the required change in the `rust-spiffe` crate (through which the vulnerable dependencies are imported in Parsec) can be seen [here](https://github.com/maxlambrecht/rust-spiffe/issues/17). Once updates happen in our dependency chain that allow us to update beyond the vulnerable versions of `time` and `chrono`, a new version of the Parsec service will be tagged and released with the appropriate notifications.
### Workarounds
The only complete workaround is to use a different type of authenticator with the Parsec service.
### References
As quoted in the initial paragraph, you can find out more information:
* in the `chrono` repo issue [here](https://github.com/chronotope/chrono/issues/602)
* in the `time` repo issue [here](https://github.com/time-rs/time/issues/293)
* in the official CVE report [here](https://nvd.nist.gov/vuln/detail/CVE-2020-26235)
* in our tracking issue [here](https://github.com/parallaxsecond/parsec/issues/544)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the Parsec service repo](https://github.com/parallaxsecond/parsec)
* Email us at [cncf-parsec-maintainers@lists.cncf.io](mailto:cncf-parsec-maintainers@lists.cncf.io)
| null |
2022-02-11T19:11:36Z
|
2022-02-11T19:11:36Z
|
LOW
| null |
{'CWE-476'}
|
{'https://github.com/chronotope/chrono/issues/602', 'https://github.com/time-rs/time/issues/293', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26235', 'https://github.com/parallaxsecond/parsec/security/advisories/GHSA-45w3-v3g4-54pm', 'https://github.com/parallaxsecond/parsec/issues/544#issuecomment-1024185688', 'https://github.com/parallaxsecond/parsec/issues/544', 'https://github.com/parallaxsecond/parsec'}
| null |
crates.io
|
RUSTSEC-2021-0102
|
Permissions bypass in pleaser
|
pleaseedit in pleaser before 0.4 uses predictable temporary filenames in /tmp and the target directory. This allows a local attacker to gain full root privileges by staging a symlink attack.
|
{'CVE-2021-31154', 'GHSA-pp74-39w2-v4w9'}
|
2021-09-10T15:58:05Z
|
2021-05-27T12:00:00Z
| null | null | null |
{'https://crates.io/crates/pleaser', 'https://nvd.nist.gov/vuln/detail/CVE-2021-31154', 'https://rustsec.org/advisories/RUSTSEC-2021-0102.html'}
| null |
crates.io
|
RUSTSEC-2022-0012
|
Arrow2 allows double free in `safe` code
|
The struct `Ffi_ArrowArray` implements `#derive(Clone)` that is inconsistent with
its custom implementation of `Drop`, resulting in a double free when cloned.
Cloning this struct in `safe` results in a segmentation fault, which is unsound.
This derive was removed from this struct. All users are advised to either:
* bump the patch version of this crate (for versions `v0.7,v0.8,v0.9`), or
* migrate to a more recent version of the crate (when using `<0.7`).
Doing so elimitates this vulnerability (code no longer compiles).
| null |
2022-04-05T15:24:42Z
|
2022-03-04T12:00:00Z
| null | null | null |
{'https://crates.io/crates/arrow2', 'https://rustsec.org/advisories/RUSTSEC-2022-0012.html', 'https://github.com/jorgecarleitao/arrow2/issues/880'}
| null |
crates.io
|
RUSTSEC-2021-0047
|
SliceDeque::drain_filter can double drop an element if the predicate panics
|
Affected versions of the crate incremented the current index of the drain filter
iterator *before* calling the predicate function `self.pred`.
If the predicate function panics, it is possible for the last element in the
iterator to be dropped twice.
|
{'CVE-2021-29938'}
|
2021-10-19T22:14:35Z
|
2021-02-19T12:00:00Z
| null | null | null |
{'https://github.com/gnzlbg/slice_deque/issues/90', 'https://rustsec.org/advisories/RUSTSEC-2021-0047.html', 'https://crates.io/crates/slice-deque'}
| null |
crates.io
|
RUSTSEC-2020-0149
|
Data race and memory safety issue in `Index`
|
The `appendix` crate implements a key-value mapping data structure called
`Index<K, V>` that is stored on disk. The crate allows for any type to inhabit
the generic `K` and `V` type parameters and implements Send and Sync for them
unconditionally.
Using a type that is not marked as `Send` or `Sync` with `Index` can allow it
to be used across multiple threads leading to data races. Additionally using
reference types for the keys or values will lead to the segmentation faults
in the crate's code.
|
{'CVE-2020-36469'}
|
2021-10-19T22:14:35Z
|
2020-11-15T12:00:00Z
| null | null | null |
{'https://github.com/krl/appendix/issues/6', 'https://crates.io/crates/appendix', 'https://rustsec.org/advisories/RUSTSEC-2020-0149.html'}
| null |
crates.io
|
GHSA-qg24-8xj4-gj2h
|
Unaligned memory allocation in chunky
|
An issue was discovered in the chunky crate through 2020-08-25 for Rust. The Chunk API does not honor an alignment requirement.
|
{'CVE-2020-36433'}
|
2021-08-18T20:17:28Z
|
2021-08-25T20:58:13Z
|
HIGH
| null |
{'CWE-758'}
|
{'https://rustsec.org/advisories/RUSTSEC-2020-0035.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36433', 'https://github.com/aeplay/chunky', 'https://github.com/aeplay/chunky/issues/2'}
| null |
crates.io
|
RUSTSEC-2021-0010
|
panic safety: double drop may happen within `util::{mutate, mutate2}`
|
Upon panic in a user-provided function `f`, `fn mutate()` & `fn mutate2` drops twice a same object.
Affected versions of this crate did not guard against double drop while temporarily duplicating an object's ownership with `ptr::read()`.
Dropping a same object can result in memory corruption.
The flaw was corrected in version "0.9.11" by fixing the code to abort upon panic.
|
{'CVE-2021-25907'}
|
2021-10-19T22:14:35Z
|
2021-01-12T12:00:00Z
| null | null | null |
{'https://github.com/strake/containers.rs/issues/2', 'https://crates.io/crates/containers', 'https://rustsec.org/advisories/RUSTSEC-2021-0010.html'}
| null |
crates.io
|
RUSTSEC-2019-0026
|
generichash::Digest::eq always return true
|
PartialEq implementation for generichash::Digest has compared itself to itself.
Digest::eq always returns true and Digest::ne always returns false.
|
{'CVE-2019-25002'}
|
2021-10-19T22:14:35Z
|
2019-10-11T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2019-0026.html', 'https://github.com/sodiumoxide/sodiumoxide/pull/381', 'https://crates.io/crates/sodiumoxide'}
| null |
crates.io
|
GHSA-438g-fx34-4h9m
|
Out of bounds read in simple-slab
|
An issue was discovered in the simple-slab crate before 0.3.3 for Rust. index() allows an out-of-bounds read.
|
{'CVE-2020-35892'}
|
2021-08-19T21:06:40Z
|
2021-08-25T20:48:38Z
|
CRITICAL
| null |
{'CWE-125'}
|
{'https://rustsec.org/advisories/RUSTSEC-2020-0039.html', 'https://github.com/nathansizemore/simple-slab', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35892', 'https://github.com/nathansizemore/simple-slab/issues/2'}
| null |
crates.io
|
GHSA-rpxm-vmr7-5f5f
|
Data races in convec
|
Affected versions of this crate unconditionally implement Send/Sync for `ConVec<T>`.
This allows users to insert `T` that is not Send or not Sync.
This allows users to create data races by using non-Send types like `Arc<Cell<_>>` or `Rc<_>` as `T` in `ConVec<T>`. It is also possible to create data races by using types like `Cell<_>` or `RefCell<_>` as `T` (types that are `Send` but not `Sync`).
Such data races can lead to memory corruption.
|
{'CVE-2020-36445'}
|
2021-08-24T18:24:04Z
|
2021-08-25T20:59:15Z
|
HIGH
| null |
{'CWE-119', 'CWE-362'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-36445', 'https://github.com/krl/convec', 'https://rustsec.org/advisories/RUSTSEC-2020-0125.html'}
| null |
crates.io
|
GHSA-5q2r-92f9-4m49
|
Improper verification of signature threshold in tough
|
## Impact
The tough library, prior to 0.7.1, does not properly verify the uniqueness of keys in the signatures provided to meet the threshold of cryptographic signatures. It allows someone with access to a valid signing key to create multiple valid signatures in order to circumvent TUF requiring a minimum threshold of unique keys before the metadata is considered valid.
AWS would like to thank Erick Tryzelaar of the Google Fuchsia Team for reporting this issue.
## Patches
A fix is available in version 0.7.1.
## Workarounds
No workarounds to this issue are known.
## References
CVE-2020-6174 is assigned to the same issue in the TUF reference implementation.
https://github.com/theupdateframework/tuf/pull/974
https://nvd.nist.gov/vuln/detail/CVE-2020-6174
## For more information
If you have any questions or comments about this advisory, [contact AWS Security](https://aws.amazon.com/security/vulnerability-reporting/) at [aws-security@amazon.com](mailto:aws-security@amazon.com).
|
{'CVE-2020-15093'}
|
2021-10-27T17:03:38Z
|
2021-08-25T20:56:55Z
|
HIGH
| null |
{'CWE-347'}
|
{'https://github.com/awslabs/tough', 'https://github.com/theupdateframework/tuf/commit/2977188139d065ff3356c3cb4aec60c582b57e0e', 'https://github.com/awslabs/tough/security/advisories/GHSA-5q2r-92f9-4m49', 'https://github.com/theupdateframework/tuf/pull/974', 'https://rustsec.org/advisories/RUSTSEC-2020-0024.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15093'}
| null |
crates.io
|
GHSA-q89x-f52w-6hj2
|
Headers containing newline characters can split messages in hyper
|
An issue was discovered in the hyper crate before 0.9.18 for Rust. It mishandles newlines in headers.
|
{'CVE-2017-18587'}
|
2021-08-19T21:25:19Z
|
2021-08-25T20:43:04Z
|
MODERATE
| null |
{'CWE-93'}
|
{'https://rustsec.org/advisories/RUSTSEC-2017-0002.html', 'https://github.com/hyperium/hyper', 'https://nvd.nist.gov/vuln/detail/CVE-2017-18587'}
| null |
crates.io
|
GHSA-g7r5-x7cr-vm3v
|
Buffer overflow and format vulnerabilities in ncurses
|
An issue was discovered in the ncurses crate for Rust. There are instr and mvwinstr buffer overflows because interaction with C functions is mishandled.
|
{'CVE-2019-15548'}
|
2021-08-18T17:45:15Z
|
2021-08-25T20:58:29Z
|
CRITICAL
| null |
{'CWE-119'}
|
{'https://github.com/jeaye/ncurses-rs/issues/172', 'https://rustsec.org/advisories/RUSTSEC-2019-0006.html', 'https://nvd.nist.gov/vuln/detail/CVE-2019-15548', 'https://github.com/RustSec/advisory-db/issues/106', 'https://github.com/jeaye/ncurses-rs'}
| null |
crates.io
|
RUSTSEC-2021-0067
|
Memory access due to code generation flaw in Cranelift module
|
There is a bug in 0.73.0 of the Cranelift x64 backend that can create a
scenario that could result in a potential sandbox escape in a WebAssembly
module. Users of versions 0.73.0 of Cranelift should upgrade to either 0.73.1
or 0.74 to remediate this vulnerability. Users of Cranelift prior to 0.73.0
should update to 0.73.1 or 0.74 if they were not using the old default backend.
More details can be found in the GitHub Security Advisory at:
<https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-hpqh-2wqx-7qp5>
|
{'CVE-2021-32629', 'GHSA-hpqh-2wqx-7qp5'}
|
2021-10-19T22:14:35Z
|
2021-05-21T12:00:00Z
| null | null | null |
{'https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-hpqh-2wqx-7qp5', 'https://rustsec.org/advisories/RUSTSEC-2021-0067.html', 'https://crates.io/crates/cranelift-codegen'}
| null |
crates.io
|
GHSA-qc4m-gc8r-mg8m
|
Double free in alpm-rs
|
An issue was discovered in the alpm-rs crate through 2020-08-20 for Rust. StrcCtx performs improper memory deallocation.
|
{'CVE-2020-35885'}
|
2021-08-19T20:56:12Z
|
2021-08-25T20:48:59Z
|
CRITICAL
| null |
{'CWE-415'}
|
{'https://rustsec.org/advisories/RUSTSEC-2020-0032.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35885', 'https://github.com/pigeonhands/rust-arch/issues/2', 'https://github.com/BahNahNah/rust-arch/tree/master/alpm-rs'}
| null |
crates.io
|
GHSA-85j6-f8j6-q26x
|
Unaligned references in Obstack
|
An issue was discovered in the obstack crate before 0.1.4 for Rust. Unaligned references can occur.
|
{'CVE-2020-35894'}
|
2021-08-19T21:06:51Z
|
2021-08-25T20:48:12Z
|
HIGH
| null |
{'CWE-706'}
|
{'https://github.com/petertodd/rust-obstack/issues/4', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35894', 'https://rustsec.org/advisories/RUSTSEC-2020-0040.html', 'https://github.com/petertodd/rust-obstack'}
| null |
crates.io
|
RUSTSEC-2021-0122
|
Generated code can read and write out of bounds in safe code
|
Code generated by flatbuffers' compiler is `unsafe` but not marked as such.
See https://github.com/google/flatbuffers/issues/6627 for details.
All users that use generated code by `flatbuffers` compiler are recommended to:
1. not expose flatbuffer generated code as part of their public APIs
2. audit their code and look for any usage of `follow`, `push`, or any method that uses them
(e.g. `self_follow`).
3. Carefuly go through the crates' documentation to understand which "safe" APIs are not
intended to be used.
| null |
2021-11-07T17:53:20Z
|
2021-10-31T12:00:00Z
| null | null | null |
{'https://crates.io/crates/flatbuffers', 'https://github.com/google/flatbuffers/issues/6627', 'https://rustsec.org/advisories/RUSTSEC-2021-0122.html'}
| null |
crates.io
|
RUSTSEC-2021-0088
|
`Read` on uninitialized memory may cause UB (fn preamble_skipcount())
|
Affected versions of this crate passes an uninitialized buffer to a user-provided `Read` implementation (within `fn preamble_skipcount()`).
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:34:42Z
|
2021-01-05T12:00:00Z
| null | null | null |
{'https://github.com/jblondin/csv-sniffer/issues/1', 'https://rustsec.org/advisories/RUSTSEC-2021-0088.html', 'https://crates.io/crates/csv-sniffer'}
| null |
crates.io
|
RUSTSEC-2020-0094
|
Unsound: can make `ARefss` contain a !Send, !Sync object.
|
`ARefss<'a, V>` is a type that is assumed to contain objects that are `Send + Sync`.
In the affected versions of this crate,
`Send`/`Sync` traits are unconditionally implemented for `ARefss<'a, V>`.
By using the `ARefss::map()` API, we can insert a `!Send` or `!Sync` object into `ARefss<'a, V>`. After that, it is possible to create a data race to the inner object of `ARefss<'a, V>`, which can lead to undefined behavior & memory corruption.
The flaw was corrected in commit 6dd7ca0 (https://github.com/diwic/reffers-rs/commit/6dd7ca0d50f2464df708975cdafcfaeeb6d41c66) by adding trait bound `V: Send + Sync` to `ARefss::map()` API.
|
{'CVE-2020-36203'}
|
2021-10-19T22:14:35Z
|
2020-12-01T12:00:00Z
| null | null | null |
{'https://crates.io/crates/reffers', 'https://rustsec.org/advisories/RUSTSEC-2020-0094.html', 'https://github.com/diwic/reffers-rs/issues/7'}
| null |
crates.io
|
GHSA-f997-8gxg-r354
|
Data races in lexer
|
lexer is a plugin based lexical reader.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'}
|
2022-05-05T18:16:25Z
|
2021-08-25T20:58:09Z
|
HIGH
| null |
{'CWE-77', 'CWE-362'}
|
{'https://rustsec.org/advisories/RUSTSEC-2020-0138.html', 'https://gitlab.com/nathanfaucett/rs-lexer', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/lexer/RUSTSEC-2020-0138.md', 'https://gitlab.com/nathanfaucett/rs-lexer/-/issues/2', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36458'}
| null |
crates.io
|
GHSA-q948-x8rf-888m
|
os_str_bytes relies on undefined behavior of `char::from_u32_unchecked`
|
An issue was discovered in the os_str_bytes crate before 2.0.0 for Rust. It has false expectations about char::from_u32_unchecked behavior.
|
{'CVE-2020-35865'}
|
2021-08-19T21:08:17Z
|
2021-08-25T20:47:55Z
|
HIGH
| null |
{'CWE-704'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-35865', 'https://rustsec.org/advisories/RUSTSEC-2020-0012.html', 'https://github.com/dylni/os_str_bytes/pull/1', 'https://github.com/dylni/os_str_bytes'}
| null |
crates.io
|
GHSA-r56q-vv3c-6g9c
|
Improper sanitization of delegated role names
|
### Impact
The tough library, prior to 0.12.0, does not properly sanitize delegated role names when caching a repository, or when loading a repository from the filesystem. When the repository is cached or loaded, files ending with the .json extension could be overwritten with role metadata anywhere on the system.
AWS would like to thank https://github.com/jku for reporting this issue.
### Patches
A fix is available in version 0.12.0.
### Workarounds
No workarounds to this issue are known.
### References
https://github.com/theupdateframework/python-tuf/security/advisories/GHSA-wjw6-2cqr-j4qr
|
{'CVE-2021-41150'}
|
2021-10-19T18:06:09Z
|
2021-10-19T20:16:26Z
|
HIGH
| null |
{'CWE-22'}
|
{'https://github.com/awslabs/tough/commit/1809b9bd1106d78a51fbea3071aa97a3530bac9a', 'https://github.com/awslabs/tough/security/advisories/GHSA-r56q-vv3c-6g9c', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41150', 'https://github.com/theupdateframework/python-tuf/security/advisories/GHSA-wjw6-2cqr-j4qr ', 'https://github.com/awslabs/tough'}
| null |
crates.io
|
GHSA-ff2r-xpwq-6whj
|
Use of Uninitialized Resource in gfx-auxil
|
An issue was discovered in the gfx-auxil crate through 2021-01-07 for Rust. gfx_auxil::read_spirv may read from uninitialized memory locations.
|
{'CVE-2021-45689'}
|
2022-01-07T17:18:43Z
|
2022-01-06T22:12:14Z
|
CRITICAL
| null |
{'CWE-908'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-45689', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/gfx-auxil/RUSTSEC-2021-0091.md', 'https://github.com/gfx-rs/gfx', 'https://rustsec.org/advisories/RUSTSEC-2021-0091.html'}
| null |
crates.io
|
RUSTSEC-2019-0006
|
Buffer overflow and format vulnerabilities in functions exposed without unsafe
|
`ncurses` exposes functions from the ncurses library which:
- Pass buffers without length to C functions that may write an arbitrary amount of
data, leading to a buffer overflow. (`instr`, `mvwinstr`, etc)
- Passes rust &str to strings expecting C format arguments, allowing hostile
input to execute a format string attack, which trivially allows writing
arbitrary data to stack memory (functions in the `printw` family).
|
{'CVE-2019-15548', 'CVE-2019-15547'}
|
2020-10-02T01:29:11Z
|
2019-06-15T12:00:00Z
| null | null | null |
{'https://github.com/RustSec/advisory-db/issues/106', 'https://crates.io/crates/ncurses', 'https://rustsec.org/advisories/RUSTSEC-2019-0006.html'}
| null |
crates.io
|
GHSA-cjg2-2fjg-fph4
|
Integer underflow in Frontier
|
### Impact
A bug in Frontier's MODEXP precompile implementation can cause an integer underflow in certain conditions. This will cause a node crash for debug builds. For release builds (and production WebAssembly binaries), the impact is limited as it can only cause a normal EVM out-of-gas. It is recommended that you apply the patch as soon as possible.
If you do not use MODEXP precompile in your runtime, then you are not impacted.
### Patches
Patches are applied in PR #549.
### Workarounds
None.
### References
Patch PR: #549
### Credits
Thanks to SR-Labs for discovering the security vulnerability, and thanks to PureStake team for the patches.
### 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-2022-21685'}
|
2022-01-14T19:58:51Z
|
2022-01-14T21:03:36Z
|
MODERATE
| null |
{'CWE-191'}
|
{'https://github.com/paritytech/frontier', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21685', 'https://github.com/paritytech/frontier/commit/8a93fdc6c9f4eb1d2f2a11b7ff1d12d70bf5a664', 'https://github.com/paritytech/frontier/pull/549', 'https://github.com/paritytech/frontier/security/advisories/GHSA-cjg2-2fjg-fph4'}
| null |
crates.io
|
GHSA-352p-rhvq-7g78
|
Null pointer deference in av-data
|
An issue was discovered in the av-data crate before 0.3.0 for Rust. A raw pointer is dereferenced, leading to a read of an arbitrary memory address, sometimes causing a segfault.
|
{'CVE-2021-25904'}
|
2021-08-19T18:45:49Z
|
2021-08-25T20:52:55Z
|
HIGH
| null |
{'CWE-476'}
|
{'https://rustsec.org/advisories/RUSTSEC-2021-0007.html', 'https://github.com/rust-av/rust-av/issues/136', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25904', 'https://github.com/rust-av/rust-av'}
| null |
crates.io
|
GHSA-g4rw-8m5q-6453
|
Out of bounds access in rgb
|
A safety violation was discovered in the rgb crate before 0.8.20 for Rust, leading to (for example) dereferencing of arbitrary pointers or disclosure of uninitialized memory. This occurs because structs can be treated as bytes for read and write operations.
|
{'CVE-2020-25016'}
|
2021-08-19T21:21:37Z
|
2021-08-25T20:45:12Z
|
CRITICAL
| null |
{'CWE-843', 'CWE-119'}
|
{'https://github.com/kornelski/rust-rgb/issues/35', 'https://nvd.nist.gov/vuln/detail/CVE-2020-25016', 'https://github.com/kornelski/rust-rgb', 'https://rustsec.org/advisories/RUSTSEC-2020-0029.html'}
| null |
crates.io
|
RUSTSEC-2021-0030
|
move_elements can double-free objects on panic
|
Affected versions of `scratchpad` used `ptr::read` to read elements while
calling a user provided function `f` on them.
Since the pointer read duplicates ownership, a panic inside the user provided
`f` function could cause a double free when unwinding.
The flaw was fixed in commit `891561bea` by removing the unsafe block and using
a plain iterator.
|
{'CVE-2021-28031'}
|
2021-10-19T22:14:35Z
|
2021-02-18T12:00:00Z
| null | null | null |
{'https://crates.io/crates/scratchpad', 'https://github.com/okready/scratchpad/issues/1', 'https://rustsec.org/advisories/RUSTSEC-2021-0030.html'}
| null |
crates.io
|
GHSA-jwfh-j623-m97h
|
Use of Uninitialized Resource in messagepack-rs
|
An issue was discovered in the messagepack-rs crate through 2021-01-26 for Rust. deserialize_string may read from uninitialized memory locations.
|
{'CVE-2021-45691'}
|
2022-01-07T17:12:54Z
|
2022-01-06T22:12:35Z
|
CRITICAL
| null |
{'CWE-908'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-45691', 'https://rustsec.org/advisories/RUSTSEC-2021-0092.html', 'https://github.com/otake84/messagepack-rs', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/messagepack-rs/RUSTSEC-2021-0092.md'}
| null |
crates.io
|
GHSA-vj62-g63v-f8mf
|
Validity check missing in Frontier
|
### Impact
In the newly introduced signed Frontier-specific extrinsic for `pallet-ethereum`, a large part of transaction validation logic was only called in transaction pool validation, but not in block execution. Malicious validators can take advantage of this to put invalid transactions into a block.
The attack is limited in that the signature is always validated, and the majority of the validation is done again in the subsequent `pallet-evm` execution logic. However, do note that a chain ID replay attack was possible. In addition, spamming attacks are of main concerns, while they are limited by Substrate block size limits and other factors.
### Patches
The issue is patched in commit 146bb48849e5393004be5c88beefe76fdf009aba.
### References
Patch PR: https://github.com/paritytech/frontier/pull/495
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Frontier repo](https://github.com/paritytech/frontier/issues)
### Special thanks
Special thanks to @librelois, @nanocryk and the Moonbeam team for reporting and fixing this security vulnerability.
|
{'CVE-2021-41138'}
|
2021-10-13T17:34:31Z
|
2021-10-13T18:53:38Z
|
MODERATE
| null |
{'CWE-20'}
|
{'https://github.com/paritytech/frontier/commit/146bb48849e5393004be5c88beefe76fdf009aba', 'https://github.com/paritytech/frontier', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41138', 'https://github.com/paritytech/frontier/security/advisories/GHSA-vj62-g63v-f8mf', 'https://github.com/paritytech/frontier/pull/497', 'https://github.com/paritytech/frontier/pull/495'}
| null |
crates.io
|
GHSA-x3r5-q6mj-m485
|
Improper sanitization of target names
|
### Impact
The tough library, prior to 0.12.0, does not properly sanitize target names when caching a repository, or when saving specific targets to an output directory. When targets are cached or saved, files could be overwritten with arbitrary content anywhere on the system.
AWS would like to thank https://github.com/jku for reporting this issue.
### Patches
A fix is available in version 0.12.0.
### Workarounds
No workarounds to this issue are known.
|
{'CVE-2021-41149'}
|
2021-10-19T18:04:34Z
|
2021-10-19T20:16:15Z
|
HIGH
| null |
{'CWE-22'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-41149', 'https://github.com/awslabs/tough/commit/1809b9bd1106d78a51fbea3071aa97a3530bac9a', 'https://github.com/awslabs/tough', 'https://github.com/awslabs/tough/security/advisories/GHSA-x3r5-q6mj-m485'}
| null |
crates.io
|
RUSTSEC-2020-0082
|
ordered_float:NotNan may contain NaN after panic in assignment operators
|
After using an assignment operators such as `NotNan::add_assign`, `NotNan::mul_assign`, etc., it was possible for the resulting `NotNan` value to contain a `NaN`. This could cause undefined behavior in safe code, because the safe `NotNan::cmp` method contains internal unsafe code that assumes the value is never `NaN`. (It could also cause undefined behavior in third-party unsafe code that makes the same assumption, as well as logic errors in safe code.)
This was mitigated starting in version 0.4.0, by panicking if the assigned value is NaN. However, in affected versions from 0.4.0 onward, code that uses the `NotNan` value during unwinding, or that continues after catching the panic, could still observe the invalid value and trigger undefined behavior.
The flaw is fully corrected in versions 1.1.1 and 2.0.1, by ensuring that the assignment operators panic without modifying the operand, if the result would be `NaN`.
|
{'CVE-2020-35923'}
|
2021-10-19T22:14:35Z
|
2020-12-06T12:00:00Z
| null | null | null |
{'https://crates.io/crates/ordered-float', 'https://github.com/reem/rust-ordered-float/pull/71', 'https://rustsec.org/advisories/RUSTSEC-2020-0082.html'}
| null |
crates.io
|
RUSTSEC-2020-0128
|
Cache<K>: Send/Sync impls needs trait bounds on `K`
|
Affected versions of this crate unconditionally implement Send/Sync for `Cache<K>`.
This allows users to insert `K` that is not Send or not Sync.
This allows users to create data races by using non-Send types like `Arc<Cell<T>>` or `Rc<T>` as `K` in `Cache<K>`. It is also possible to create data races by using types like `Cell<T>` or `RefCell<T>` (types that are `Send` but not `Sync`).
Such data races can lead to memory corruption.
|
{'CVE-2020-36448'}
|
2021-10-19T22:14:35Z
|
2020-11-24T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2020-0128.html', 'https://crates.io/crates/cache', 'https://github.com/krl/cache/issues/1'}
| null |
crates.io
|
RUSTSEC-2019-0010
|
MultiDecoder::read() drops uninitialized memory of arbitrary type on panic in client code
|
Affected versions of libflate have set a field of an internal structure with a generic type to an uninitialized value in `MultiDecoder::read()` and reverted it to the original value after the function completed. However, execution of `MultiDecoder::read()` could be interrupted by a panic in caller-supplied `Read` implementation. This would cause `drop()` to be called on uninitialized memory of a generic type implementing `Read`.
This is equivalent to a use-after-free vulnerability and could allow an attacker to gain arbitrary code execution.
The flaw was corrected by aborting immediately instead of unwinding the stack in case of panic within `MultiDecoder::read()`. The issue was discovered and fixed by Shnatsel.
|
{'CVE-2019-15552'}
|
2021-10-19T22:14:35Z
|
2019-07-04T12:00:00Z
| null | null | null |
{'https://github.com/sile/libflate/issues/35', 'https://crates.io/crates/libflate', 'https://rustsec.org/advisories/RUSTSEC-2019-0010.html'}
| null |
crates.io
|
GHSA-hv87-47h9-jcvq
|
Uncontrolled recursion in rust-yaml
|
An issue was discovered in the yaml-rust crate before 0.4.1 for Rust. There is uncontrolled recursion during deserialization.
|
{'CVE-2018-20993'}
|
2021-08-19T21:24:44Z
|
2021-08-25T20:43:13Z
|
HIGH
| null |
{'CWE-674'}
|
{'https://rustsec.org/advisories/RUSTSEC-2018-0006.html', 'https://github.com/chyh1990/yaml-rust/pull/109', 'https://github.com/chyh1990/yaml-rust', 'https://nvd.nist.gov/vuln/detail/CVE-2018-20993'}
| null |
crates.io
|
RUSTSEC-2021-0026
|
XSS in `comrak`
|
The [comrak](https://github.com/kivikakk/comrak) we were matching unsafe URL prefixes, such as `data:` or `javascript:` , in a case-sensitive manner. This meant prefixes like `Data:` were untouched.
|
{'CVE-2021-27671'}
|
2021-10-19T22:14:35Z
|
2021-02-21T12:00:00Z
| null | null | null |
{'https://github.com/kivikakk/comrak/releases/tag/0.9.1', 'https://crates.io/crates/comrak', 'https://rustsec.org/advisories/RUSTSEC-2021-0026.html'}
| null |
crates.io
|
GHSA-fjr6-hm39-4cf9
|
Double free in basic_dsp_matrix
|
An issue was discovered in the basic_dsp_matrix crate before 0.9.2 for Rust. When a TransformContent panic occurs, a double drop can be performed.
|
{'CVE-2021-25906'}
|
2021-08-19T18:46:23Z
|
2021-08-25T20:52:50Z
|
HIGH
| null |
{'CWE-415'}
|
{'https://rustsec.org/advisories/RUSTSEC-2021-0009.html', 'https://github.com/liebharc/basic_dsp/issues/47', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25906', 'https://github.com/liebharc/basic_dsp'}
| null |
crates.io
|
GHSA-g78p-g85h-q6ww
|
Data races in cache
|
An issue was discovered in the cache crate through 2020-11-24 for Rust.
Affected versions of this crate unconditionally implement Send/Sync for `Cache<K>`.
This allows users to insert `K` that is not Send or not Sync.
This allows users to create data races by using non-Send types like `Arc<Cell<T>>` or `Rc<T>` as `K` in `Cache<K>`. It is also possible to create data races by using types like `Cell<T>` or `RefCell<T>` (types that are `Send` but not `Sync`).
Such data races can lead to memory corruption.
|
{'CVE-2020-36448'}
|
2021-08-24T18:31:50Z
|
2021-08-25T20:57:12Z
|
HIGH
| null |
{'CWE-77', 'CWE-362'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-36448', 'https://github.com/krl/cache/issues/1', 'https://github.com/krl/cache', 'https://rustsec.org/advisories/RUSTSEC-2020-0128.html'}
| null |
crates.io
|
GHSA-qwvx-c8j7-5g75
|
Use of Uninitialized Resource in tectonic_xdv
|
An issue was discovered in the tectonic_xdv crate before 0.1.12 for Rust. XdvParser::<T>::process may read from uninitialized memory locations.
|
{'CVE-2021-45703'}
|
2022-01-07T17:40:42Z
|
2022-01-06T22:09:19Z
|
CRITICAL
| null |
{'CWE-908'}
|
{'https://rustsec.org/advisories/RUSTSEC-2021-0112.html', 'https://github.com/tectonic-typesetting/tectonic/', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/tectonic_xdv/RUSTSEC-2021-0112.md', 'https://nvd.nist.gov/vuln/detail/CVE-2021-45703'}
| null |
crates.io
|
RUSTSEC-2016-0002
|
HTTPS MitM vulnerability due to lack of hostname verification
|
When used on Windows platforms, all versions of Hyper prior to 0.9.4 did not
perform hostname verification when making HTTPS requests.
This allows an attacker to perform MitM attacks by preventing any valid
CA-issued certificate, even if there's a hostname mismatch.
The problem was addressed by leveraging rust-openssl's built-in support for
hostname verification.
|
{'CVE-2016-10932'}
|
2021-10-19T22:14:35Z
|
2016-05-09T12:00:00Z
| null | null | null |
{'https://github.com/hyperium/hyper/blob/master/CHANGELOG.md#v094-2016-05-09', 'https://rustsec.org/advisories/RUSTSEC-2016-0002.html', 'https://crates.io/crates/hyper'}
| null |
crates.io
|
GHSA-82hm-vh7g-hrh9
|
Partial read is incorrect in molecule
|
### Impact
Anyone who uses `total_size(..)` function to partial read the length of any `FixVec` will get an incorrect result, due to an incorrect implementation. This has been resolved in the 0.7.2 release.
### Workarounds
If you already have the whole `FixVec` `A`, you can use `A.as_slice().len()` to get the total size of the `FixVec`.
### For more information
If you have any questions or comments about this advisory:
- [Open an issue to ask use directly](https://github.com/nervosnetwork/molecule/issues/new).
| null |
2021-09-09T17:55:10Z
|
2021-08-25T21:01:25Z
|
MODERATE
| null | null |
{'https://github.com/nervosnetwork/molecule/security/advisories/GHSA-82hm-vh7g-hrh9', 'https://github.com/nervosnetwork/molecule', 'https://github.com/nervosnetwork/molecule/pull/49'}
| null |
crates.io
|
RUSTSEC-2021-0071
|
`grep-cli` may run arbitrary executables on Windows
|
On Windows in versions of `grep-cli` prior to `0.1.6`, it's possible for some
of the routines to execute arbitrary executables. In particular, a quirk of
the Windows process execution API is that it will automatically consider the
current directory before other directories when resolving relative binary
names. Therefore, if you use `grep-cli` to read decompressed files in an
untrusted directory with that directory as the CWD, a malicious actor to could
put, e.g., a `gz.exe` binary in that directory and `grep-cli` will use the
malicious actor's version of `gz.exe` instead of the system's.
This is also technically possible on Unix as well, but only if the `PATH`
variable contains `.`. Conventionally, they do not.
A `DecompressionReader` has been fixed to automatically resolve binary names
using `PATH`, instead of relying on the Windows API to do it.
If you use `grep-cli`'s `CommandReader` with a `std::process::Command` value
on Windows, then it is recommended to either construct the `Command` with an
absolute binary name, or use `grep-cli`'s new
[`resolve_binary`](https://docs.rs/grep-cli/0.1.6/grep_cli/fn.resolve_binary.html)
helper function.
To be clear, `grep-cli 0.1.6` mitigates this issue in two ways:
* A `DecompressionReader` will resolve decompression programs to absolute
paths automatically using the `PATH` environment variable, instead of relying
on Windows APIs to do it (which would result in the undesirable behavior of
checking the CWD for a program first).
* A new function, `resolve_binary`, was added to help users of this crate
mitigate this behavior when they need to create their own
`std::process::Command`. For example,
[ripgrep uses `grep_cli::resolve_binary`](https://github.com/BurntSushi/ripgrep/blob/7ce66f73cf7e76e9f2557922ac8e650eb02cf4ed/crates/core/search.rs#L119-L122)
on the argument given to its `--pre` flag.
While the first mitigation fixes this issue for sensible values of `PATH`
when doing decompression search, the second mitigation is imperfect. The more
fundamental issue is that `std::process::Command` is itself vulnerable to this.
|
{'CVE-2021-3013'}
|
2021-10-19T22:14:35Z
|
2021-06-12T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2021-0071.html', 'https://github.com/BurntSushi/ripgrep/issues/1773', 'https://crates.io/crates/grep-cli'}
| null |
crates.io
|
RUSTSEC-2021-0134
|
rental is unmaintained, author has moved on
|
The author encourages users to explore other solutions, or maintain a fork.
Maintained alternatives include:
* [`ouroboros`](https://crates.io/crates/ouroboros)
* [`fortify`](https://crates.io/crates/fortify)
* [`escher`](https://crates.io/crates/escher)
| null |
2022-03-06T11:02:04Z
|
2021-12-27T12:00:00Z
| null | null | null |
{'https://github.com/jpernst/rental/commit/213671ab3aab3452efd7e2290c6bb714ee327014', 'https://rustsec.org/advisories/RUSTSEC-2021-0134.html', 'https://crates.io/crates/rental'}
| null |
crates.io
|
GHSA-r3r5-jhw6-4634
|
Insecure temporary file usage in SWHKD
|
SWHKD 1.1.5 unsafely uses the /tmp/swhkd.sock pathname. There can be an information leak or denial of service.
|
{'CVE-2022-27818'}
|
2022-04-19T18:16:59Z
|
2022-04-08T00:00:24Z
|
CRITICAL
| null |
{'CWE-668'}
|
{'http://www.openwall.com/lists/oss-security/2022/04/14/1', 'https://nvd.nist.gov/vuln/detail/CVE-2022-27818', 'https://github.com/waycrate/swhkd', 'https://github.com/waycrate/swhkd/releases/tag/1.1.7', 'https://github.com/waycrate/swhkd/commit/f70b99dd575fab79d8a942111a6980431f006818', 'https://github.com/waycrate/swhkd/releases'}
| null |
crates.io
|
RUSTSEC-2020-0041
|
Multiple soundness issues in Chunk and InlineArray
|
Chunk:
* Array size is not checked when constructed with `unit()` and `pair()`.
* Array size is not checked when constructed with `From<InlineArray<A, T>>`.
* `Clone` and `insert_from` are not panic-safe; A panicking iterator causes memory safety issues with them.
InlineArray:
* Generates unaligned references for types with a large alignment requirement.
|
{'CVE-2020-25792', 'CVE-2020-25794', 'CVE-2020-25793', 'CVE-2020-25795', 'CVE-2020-25796', 'CVE-2020-25791'}
|
2021-10-19T22:14:35Z
|
2020-09-06T12:00:00Z
| null | null | null |
{'https://crates.io/crates/sized-chunks', 'https://rustsec.org/advisories/RUSTSEC-2020-0041.html', 'https://github.com/bodil/sized-chunks/issues/11'}
| null |
crates.io
|
RUSTSEC-2020-0104
|
ImageChunkMut needs bounds on its Send and Sync traits
|
In the affected versions of this crate, `ImageChunkMut<'_, T>` unconditionally implements `Send` and `Sync`, allowing to create data races.
This can result in a memory corruption or undefined behavior when non thread-safe types are moved and referenced across thread boundaries.
The flaw was corrected in commit e7fb2f5 by adding `T: Send` bound to the `Send` impl and adding `T: Sync` bound to the `Sync` impl.
|
{'CVE-2020-36211'}
|
2021-10-19T22:14:35Z
|
2020-12-08T12:00:00Z
| null | null | null |
{'https://rustsec.org/advisories/RUSTSEC-2020-0104.html', 'https://github.com/Devolutions/gfwx-rs/issues/7', 'https://crates.io/crates/gfwx'}
| null |
crates.io
|
GHSA-qgwf-r2jj-2ccv
|
Use after free in heapless
|
An issue was discovered in the heapless crate before 0.6.1 for Rust. The IntoIter Clone implementation clones an entire underlying Vec without considering whether it has already been partially consumed.
|
{'CVE-2020-36464'}
|
2021-08-18T21:16:38Z
|
2021-08-25T20:56:09Z
|
HIGH
| null |
{'CWE-416'}
|
{'https://github.com/japaric/heapless', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36464', 'https://rustsec.org/advisories/RUSTSEC-2020-0145.html', 'https://github.com/japaric/heapless/issues/181'}
| null |
crates.io
|
GHSA-x76r-966h-5qv9
|
Out-of-bounds Write in vec-const
|
An issue was discovered in the vec-const crate before 2.0.0 for Rust. It tries to construct a Vec from a pointer to a const slice, leading to memory corruption.
|
{'CVE-2021-45680'}
|
2022-01-07T16:19:25Z
|
2022-01-06T22:15:56Z
|
HIGH
| null |
{'CWE-787'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-45680', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/vec-const/RUSTSEC-2021-0082.md', 'https://rustsec.org/advisories/RUSTSEC-2021-0082.html', 'https://github.com/Eolu/vec-const/'}
| null |
crates.io
|
GHSA-8892-84wf-cg8f
|
SyncChannel<T> can move 'T: !Send' to other threads
|
Affected versions of this crate unconditionally implement Send/Sync for `SyncChannel<T>`.
`SyncChannel<T>` doesn't provide access to `&T` but merely serves as a channel that consumes and returns owned `T`.
Users can create UB in safe Rust by sending `T: !Send` to other threads with `SyncChannel::send/recv` APIs. Using `T = Arc<Cell<_>` allows to create data races (which can lead to memory corruption), and using `T = MutexGuard<T>` allows to unlock a mutex from a thread that didn't lock the mutex.
| null |
2021-08-06T18:04:55Z
|
2021-08-25T21:00:16Z
|
MODERATE
| null |
{'CWE-362'}
|
{'https://github.com/kitsuneninetails/signal-rust/issues/2', 'https://github.com/kitsuneninetails/signal-rust/', 'https://rustsec.org/advisories/RUSTSEC-2020-0126.html'}
| null |
crates.io
|
GHSA-9cg2-2j2h-59v9
|
Data races in atom
|
An issue was discovered in the atom crate before 0.3.6 for Rust. An unsafe Send implementation allows a cross-thread data race.
|
{'CVE-2020-35897'}
|
2021-08-19T20:53:48Z
|
2021-08-25T20:49:11Z
|
MODERATE
| null |
{'CWE-362'}
|
{'https://github.com/slide-rs/atom', 'https://github.com/slide-rs/atom/issues/13', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35897', 'https://rustsec.org/advisories/RUSTSEC-2020-0044.html'}
| null |
crates.io
|
RUSTSEC-2020-0016
|
`net2` crate has been deprecated; use `socket2` instead
|
The [`net2`](https://crates.io/crates/net2) crate has been deprecated
and users are encouraged to considered [`socket2`](https://crates.io/crates/socket2) instead.
| null |
2020-10-02T01:29:11Z
|
2020-05-01T12:00:00Z
| null | null | null |
{'https://github.com/deprecrated/net2-rs/commit/3350e3819adf151709047e93f25583a5df681091', 'https://crates.io/crates/net2', 'https://rustsec.org/advisories/RUSTSEC-2020-0016.html'}
| null |
crates.io
|
GHSA-f3fg-5j9p-vchc
|
File exposure in pleaser
|
pleaser before 0.4 allows a local unprivileged attacker to gain knowledge about the existence of files or directories in privileged locations via the search_path function, the --check option, or the -d option.
|
{'CVE-2021-31153'}
|
2021-06-01T19:35:31Z
|
2021-08-25T21:01:41Z
|
MODERATE
| null |
{'CWE-200', 'CWE-668'}
|
{'https://crates.io/crates/pleaser', 'https://nvd.nist.gov/vuln/detail/CVE-2021-31153', 'http://www.openwall.com/lists/oss-security/2021/05/18/1', 'https://gitlab.com/edneville/please/-/tree/master/src/bin'}
| null |
crates.io
|
RUSTSEC-2020-0153
|
`read` on uninitialized buffer may cause UB (bite::read::BiteReadExpandedExt::read_framed_max)
|
Affected versions of this crate calls a user provided `Read` implementation on an uninitialized buffer.
`Read` on uninitialized buffer is defined as undefined behavior in Rust.
| null |
2021-08-22T01:15:34Z
|
2020-12-31T12:00:00Z
| null | null | null |
{'https://crates.io/crates/bite', 'https://github.com/hinaria/bite/issues/1', 'https://rustsec.org/advisories/RUSTSEC-2020-0153.html'}
| null |
crates.io
|
RUSTSEC-2021-0118
|
`FixedSizeBinaryArray` does not perform bound checks on accessing values and offsets
|
`FixedSizeBinaryArray` performs insufficient bounds checks, which allows out-of-bounds reads in safe code.
| null |
2021-12-22T21:15:54Z
|
2021-09-14T12:00:00Z
| null | null | null |
{'https://github.com/apache/arrow-rs/issues/774', 'https://rustsec.org/advisories/RUSTSEC-2021-0118.html', 'https://crates.io/crates/arrow'}
| null |
crates.io
|
RUSTSEC-2022-0008
|
Delegate functions are missing `Send` bound
|
Affected versions of this crate did not require event handlers to have `Send` bound despite there being no guarantee of them being called on any particular thread, which can potentially lead to data races and undefined behavior.
The flaw was corrected in commit [afe3252](https://github.com/microsoft/windows-rs/commit/afe32525c22209aa8f632a0f4ad607863b51796a) by adding `Send` bounds.
| null |
2022-02-04T15:22:53Z
|
2022-01-02T12:00:00Z
| null | null | null |
{'https://crates.io/crates/windows', 'https://github.com/microsoft/windows-rs/issues/1409', 'https://rustsec.org/advisories/RUSTSEC-2022-0008.html'}
| null |
crates.io
|
RUSTSEC-2018-0020
|
Possible use-after-free with `proplist::Iterator`
|
Affected versions contained a possible use-after-free issue with property list iteration
due to a lack of a lifetime constraint tying the lifetime of a `proplist::Iterator` to the
`Proplist` object for which it was created. This made it possible for users, without
experiencing a compiler error/warning, to destroy the `Proplist` object before the iterator,
thus destroying the underlying C object the iterator works upon, before the iterator may be
finished with it.
This impacts all versions of the crate before `2.5.0` back to `1.0.5`. Before version
`1.0.5` the function that produces the iterator was broken to the point of being useless.
|
{'CVE-2018-25001', 'GHSA-6gvc-4jvj-pwq4'}
|
2021-10-19T22:14:35Z
|
2018-12-22T12:00:00Z
| null | null | null |
{'https://github.com/advisories/GHSA-6gvc-4jvj-pwq4', 'https://crates.io/crates/libpulse-binding', 'https://rustsec.org/advisories/RUSTSEC-2018-0020.html'}
| null |
crates.io
|
RUSTSEC-2020-0145
|
Use-after-free when cloning a partially consumed `Vec` iterator
|
The `IntoIter` `Clone` implementation clones the whole underlying `Vec`.
If the iterator is partially consumed the consumed items will be copied, thus creating a use-after-free access.
A proof of concept is available in the original bug report.
|
{'CVE-2020-36464'}
|
2021-10-19T22:14:35Z
|
2020-11-02T12:00:00Z
| null | null | null |
{'https://github.com/japaric/heapless/issues/181', 'https://rustsec.org/advisories/RUSTSEC-2020-0145.html', 'https://crates.io/crates/heapless'}
| null |
crates.io
|
GHSA-6wj2-g87r-pm62
|
Cross-site Scripting in comrak
|
An issue was discovered in the comrak crate before 0.10.1 for Rust. It mishandles & characters, leading to XSS via &# HTML entities.
|
{'CVE-2021-38186'}
|
2021-08-18T21:33:18Z
|
2021-08-25T20:55:43Z
|
MODERATE
| null |
{'CWE-79'}
|
{'https://github.com/kivikakk/comrak/releases/tag/0.10.1', 'https://nvd.nist.gov/vuln/detail/CVE-2021-38186', 'https://github.com/kivikakk/comrak', 'https://rustsec.org/advisories/RUSTSEC-2021-0063.html'}
| null |
crates.io
|
GHSA-9f5r-vqm5-m342
|
Use of Uninitialized Resource in ms3d
|
An issue was discovered in the ms3d crate before 0.1.3 for Rust. It might allow attackers to obtain sensitive information from uninitialized memory locations via IoReader::read.
|
{'CVE-2021-26952'}
|
2021-08-19T17:44:22Z
|
2021-08-25T20:53:16Z
|
HIGH
| null |
{'CWE-908'}
|
{'https://github.com/andrewhickman/ms3d/issues/1', 'https://nvd.nist.gov/vuln/detail/CVE-2021-26952', 'https://github.com/andrewhickman/ms3d', 'https://rustsec.org/advisories/RUSTSEC-2021-0016.html'}
| null |
crates.io
|
RUSTSEC-2020-0057
|
crate has been renamed to `cipher`
|
This crate has been renamed from `block-cipher` to `cipher`.
The new repository location is at:
<https://github.com/RustCrypto/traits/tree/master/cipher>
| null |
2020-10-25T19:05:32Z
|
2020-10-15T12:00:00Z
| null | null | null |
{'https://github.com/RustCrypto/traits/pull/337', 'https://crates.io/crates/block-cipher', 'https://rustsec.org/advisories/RUSTSEC-2020-0057.html'}
| null |
crates.io
|
GHSA-9frf-r7c7-j2vg
|
Out of bounds write in stackvector
|
An issue was discovered in the stackvector crate before 1.0.9 for Rust. There is an out-of-bounds write in StackVec::extend if size_hint provides certain anomalous data.
|
{'CVE-2021-29939'}
|
2021-08-19T17:15:11Z
|
2021-08-25T20:54:14Z
|
HIGH
| null |
{'CWE-787'}
|
{'https://rustsec.org/advisories/RUSTSEC-2021-0048.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29939', 'https://github.com/Alexhuszagh/rust-stackvector/issues/2', 'https://github.com/Alexhuszagh/rust-stackvector'}
| null |
crates.io
|
RUSTSEC-2020-0112
|
ButtplugFutureStateShared allows data race to (!Send|!Sync) objects
|
`ButtplugFutureStateShared<T>` implements `Send` & `Sync` regardless of `T`.
If `T: !Send` for `ButtplugFutureStateShared<T>`, it is possible to move non-Send types across thread boundaries (e.g. `T`=`Rc<T>`) and lead to undefined behavior.
If `T: !Sync` for `ButtplugFutureStateShared<T>`, it is possible to cause data race to `T` (e.g. `T`=`Arc<Cell<_>>`) and lead to undefined behavior.
The flaw was corrected in version 1.0.4 by removing manual implementations of `Send`/`Sync` for `ButtplugFutureStateShared<T>` to let rustc generate auto trait implementations with correct trait bounds on `T`.
|
{'CVE-2020-36218'}
|
2021-10-19T22:14:35Z
|
2020-12-18T12:00:00Z
| null | null | null |
{'https://github.com/buttplugio/buttplug-rs/issues/225', 'https://rustsec.org/advisories/RUSTSEC-2020-0112.html', 'https://crates.io/crates/buttplug'}
| null |
crates.io
|
GHSA-jh37-772x-4hpw
|
Double free in algorithmica
|
An issue was discovered in the algorithmica crate through 2021-03-07 for Rust. In the affected versions of this crate, `merge_sort::merge()` wildly duplicates and drops ownership of `T` without guarding against double-free. Due to such implementation, simply invoking `merge_sort::merge()` on `Vec<T: Drop>` can cause **double free** bugs.
|
{'CVE-2021-31996'}
|
2021-08-24T19:12:12Z
|
2021-08-25T21:01:52Z
|
HIGH
| null |
{'CWE-415'}
|
{'https://github.com/AbrarNitk/algorithmica/issues/1', 'https://nvd.nist.gov/vuln/detail/CVE-2021-31996', 'https://rustsec.org/advisories/RUSTSEC-2021-0053.html'}
| null |
crates.io
|
GHSA-pp74-39w2-v4w9
|
Permissions bypass in pleaser
|
pleaseedit in pleaser before 0.4 uses predictable temporary filenames in /tmp and the target directory. This allows a local attacker to gain full root privileges by staging a symlink attack.
|
{'CVE-2021-31154'}
|
2021-06-08T17:14:10Z
|
2021-08-25T21:01:44Z
|
HIGH
| null |
{'CWE-59', 'CWE-340'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-31154', '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 |
npm
|
GHSA-p6j9-7xhc-rhwp
|
Hostname spoofing via backslashes in URL
|
### Impact
If using affected versions to determine a URL's hostname, the hostname can be spoofed by using a backslash (`\`) character as part of the scheme delimiter, e.g. `scheme:/\hostname`. If the hostname is used in security decisions, the decision may be incorrect.
Depending on library usage and attacker intent, impacts may include allow/block list bypasses, SSRF attacks, open redirects, or other undesired behavior.
Example URL: `https:/\expected-example.com/path`
Escaped string: `https:/\\expected-example.com/path` (JavaScript strings must escape backslash)
Affected versions incorrectly return no hostname. Patched versions correctly return `expected-example.com`. Patched versions match the behavior of other parsers which implement the [WHATWG URL specification](https://url.spec.whatwg.org/), including web browsers and [Node's built-in URL class](https://nodejs.org/api/url.html).
### Patches
Version 1.19.6 is patched against all known payload variants.
### References
https://github.com/medialize/URI.js/releases/tag/v1.19.6 (fix for this particular bypass)
https://github.com/medialize/URI.js/releases/tag/v1.19.4 (fix for related bypass)
https://github.com/medialize/URI.js/releases/tag/v1.19.3 (fix for related bypass)
[PR #233](https://github.com/medialize/URI.js/pull/233) (initial fix for backslash handling)
### For more information
If you have any questions or comments about this advisory, open an issue in https://github.com/medialize/URI.js
### Reporter credit
[Yaniv Nizry](https://twitter.com/ynizry) from the CxSCA AppSec team at Checkmarx
|
{'CVE-2021-27516'}
|
2021-02-26T21:37:41Z
|
2021-03-01T20:03:53Z
|
MODERATE
| null |
{'CWE-20'}
|
{'https://github.com/medialize/URI.js/security/advisories/GHSA-p6j9-7xhc-rhwp', 'https://advisory.checkmarx.net/advisory/CX-2021-4305', 'https://github.com/medialize/URI.js/commit/a1ad8bcbc39a4d136d7e252e76e957f3ece70839', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27516', 'https://github.com/medialize/URI.js/releases/tag/v1.19.6'}
| null |
npm
|
GHSA-vpch-rxw3-fgx8
|
Cross-Site Scripting in @risingstack/protect
|
All versions of `@risingstack/protect` are vulnerable to Cross-Site Scripting. The `isXss()` XSS validator has several bypasses that may allow attackers to execute arbitrary JavaScript in a victim's browser.
## Recommendation
No fix is currently available. Consider using an alternative package. The package is not actively maintained and will not be patched.
|
{'CVE-2018-1000160'}
|
2021-09-20T22:10:09Z
|
2018-04-25T14:30:43Z
|
MODERATE
| null |
{'CWE-79'}
|
{'http://embed.plnkr.co/xHbhB29JWWyMUMeHsLrm', 'https://nvd.nist.gov/vuln/detail/CVE-2018-1000160', 'https://github.com/advisories/GHSA-vpch-rxw3-fgx8', 'https://snyk.io/vuln/SNYK-JS-RISINGSTACKPROTECT-455402', 'https://github.com/RisingStack/protect/blob/60b0c91e86686d34e5202419ce9ae7e8dc08edcd/lib/rules/xss.js#L4-L13', 'https://github.com/RisingStack/protect/issues/16', 'https://www.npmjs.com/advisories/1116', 'https://github.com/RisingStack/protect'}
| null |
npm
|
GHSA-9v62-24cr-58cx
|
Denial of Service in node-sass
|
Affected versions of `node-sass` are vulnerable to Denial of Service (DoS). Crafted objects passed to the `renderSync` function may trigger C++ assertions in `CustomImporterBridge::get_importer_entry` and `CustomImporterBridge::post_process_return_value` that crash the Node process. This may allow attackers to crash the system's running Node process and lead to Denial of Service.
## Recommendation
Upgrade to version 4.13.1 or later
| null |
2021-09-28T16:08:17Z
|
2020-09-11T21:12:39Z
|
MODERATE
| null |
{'CWE-400'}
|
{'https://github.com/sass/node-sass', 'https://www.npmjs.com/advisories/961', 'https://github.com/sass/node-sass/commit/338fd7a14d3b8bd374a382336df16f9c6792b884'}
| null |
npm
|
GHSA-4mvj-rq4v-2fxw
|
Prototype Pollution in x-assign
|
This affects all versions of package x-assign. The global proto object can be polluted using the __proto__ object.
|
{'CVE-2021-23452'}
|
2021-10-21T14:54:57Z
|
2021-10-21T17:50:44Z
|
HIGH
| null |
{'CWE-915', 'CWE-1321'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-23452', 'https://snyk.io/vuln/SNYK-JS-XASSIGN-1759314', 'https://github.com/mvoorberg/x-assign', 'https://runkit.com/embed/sq8qjwemyn8t'}
| null |
npm
|
GHSA-mf22-92pm-m8p8
|
Cross site scripting in @awsui/components-react
|
### Impact
Components could potentially allow cross-site scripting (XSS) in certain circumstances. These components could render content without adequate neutralization.
### Patches
Fixed in 3.0.367.
|
{'CVE-2022-24709'}
|
2022-03-09T21:12:59Z
|
2022-02-25T15:36:47Z
|
HIGH
| null |
{'CWE-79'}
|
{'https://www.npmjs.com/package/@awsui/components-react', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24709', 'https://github.com/aws/awsui-documentation/security/advisories/GHSA-mf22-92pm-m8p8', 'https://github.com/aws/awsui-documentation/'}
| null |
npm
|
GHSA-4x5j-v9v9-w8gw
|
Downloads Resources over HTTP in httpsync
|
Affected versions of `httpsync` insecurely download an executable over an unencrypted HTTP connection.
In scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running `httpsync`.
## Recommendation
No patch is currently available for this vulnerability.
The best mitigation is currently to avoid using this package, using a different package if available.
Alternatively, the risk of exploitation can be reduced by ensuring that this package is not installed while connected to a public network. If the package is installed on a private network, the only people who can exploit this vulnerability are those who have compromised your network or those who have privileged access to your ISP, such as Nation State Actors or Rogue ISP Employees.
|
{'CVE-2016-10614'}
|
2021-01-08T19:52:32Z
|
2019-02-18T23:47:40Z
|
HIGH
| null |
{'CWE-311'}
|
{'https://nodesecurity.io/advisories/210', 'https://github.com/advisories/GHSA-4x5j-v9v9-w8gw', 'https://www.npmjs.com/advisories/210', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10614'}
| null |
npm
|
GHSA-36rh-ggpr-j3gj
|
Azure DevOps token leakage in logs
|
### Impact
Applies to Azure DevOps users only. The bot's token may be exposed in server or pipeline logs due to the `http.extraheader=AUTHORIZATION` parameter being logged without redaction. It is recommended that Azure DevOps users revoke their existing bot credentials and generate new ones after upgrading if there's a potential that logs have been saved to a location that others can view.
### Patches
Fixed in 23.25.1
### Workarounds
Do not share Renovate logs with anyone who cannot be trusted with access to the token.
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@renovatebot.com](mailto:security@renovatebot.com)
| null |
2020-09-14T16:38:10Z
|
2020-09-14T16:38:40Z
|
MODERATE
| null | null |
{'https://github.com/renovatebot/renovate/security/advisories/GHSA-36rh-ggpr-j3gj'}
| null |
npm
|
GHSA-gqf6-75v8-vr26
|
Arbitrary File Write in bin-links
|
Versions of `bin-links` prior to 1.1.5 are vulnerable to an Arbitrary File Write. The package fails to restrict access to folders outside of the intended `node_modules` folder through the `bin` field. This allows attackers to create arbitrary files in the system. Note it is not possible to overwrite files that already exist.
## Recommendation
Upgrade to version 1.1.5 or later.
| null |
2020-08-31T18:58:56Z
|
2020-09-04T16:56:11Z
|
LOW
| null | null |
{'https://www.npmjs.com/advisories/1427'}
| null |
npm
|
GHSA-jhq3-57xh-6643
|
Privilege Escalation due to Blind NoSQL Injection in flintcms
|
Versions of `flintcms` before version 1.1.10 are vulnerable to account takeover due to blind MongoDB injection in the password reset.
## Recommendation
Update to version 1.1.10 or later.
|
{'CVE-2018-3783'}
|
2021-09-14T19:42:55Z
|
2018-08-21T17:03:59Z
|
CRITICAL
| null |
{'CWE-89'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2018-3783', 'https://hackerone.com/reports/386807', 'https://github.com/advisories/GHSA-jhq3-57xh-6643', 'https://www.npmjs.com/advisories/689'}
| null |
npm
|
GHSA-r4m5-47cq-6qg8
|
Server-Side Request Forgery in ftp-srv
|
All versions of `ftp-srv` are vulnerable to Server-Side Request Forgery (SSRF). The package fails to prevent remote clients to access other resources in the network, for example when connecting to the server through telnet. This allows attackers to access any network resources available to the server, including private resources in the hosting environment.
## Recommendation
No fix is currently available. Consider using an alternative package until a fix is made available.
| null |
2020-08-31T18:59:34Z
|
2020-09-04T17:25:13Z
|
HIGH
| null |
{'CWE-918'}
|
{'https://www.npmjs.com/advisories/1445'}
| null |
npm
|
GHSA-q6pj-jh94-5fpr
|
OS Command Injection in docker-compose-remote-api
|
docker-compose-remote-api through 0.1.4 allows execution of arbitrary commands. Within 'index.js' of the package, the function 'exec(serviceName, cmd, fnStdout, fnStderr, fnExit)' uses the variable 'serviceName' which can be controlled by users without any sanitization.
|
{'CVE-2020-7606'}
|
2021-07-28T21:23:11Z
|
2021-05-07T16:14:39Z
|
CRITICAL
| null |
{'CWE-78'}
|
{'https://snyk.io/vuln/SNYK-JS-DOCKERCOMPOSEREMOTEAPI-560125', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7606'}
| null |
npm
|
GHSA-5c8j-xr24-2665
|
Potential Command Injection in printer
|
Versions 0.0.1 and earlier of `printer` are affected by a command injection vulnerability resulting from a failure to sanitize command arguments properly in the `printDirect()` function.
## Recommendation
Update to version 0.0.2 or later.
|
{'CVE-2014-3741'}
|
2021-09-01T21:34:20Z
|
2017-11-28T22:44:52Z
|
CRITICAL
| null |
{'CWE-77'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2014-3741', 'http://www.openwall.com/lists/oss-security/2014/05/15/2', 'https://github.com/tojocky/node-printer', 'http://www.openwall.com/lists/oss-security/2014/05/13/1', 'https://www.npmjs.com/advisories/27', 'https://github.com/advisories/GHSA-5c8j-xr24-2665', 'https://nodesecurity.io/advisories/printer_potential_command_injection', 'https://github.com/tojocky/node-printer/commit/e001e38738c17219a1d9dd8c31f7d82b9c0013c7'}
| null |
npm
|
GHSA-5xf4-f2fq-f69j
|
Improper link resolution before file access (Link Following)
|
In Yarn before 1.21.1, the package install functionality can be abused to generate arbitrary symlinks on the host filesystem by using specially crafted "bin" keys. Existing files could be overwritten depending on the current user permission set.
|
{'CVE-2019-10773'}
|
2021-08-19T17:16:27Z
|
2020-02-14T23:10:16Z
|
HIGH
| null |
{'CWE-78'}
|
{'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ITY5BC63CCC647DFNUQRQ5AJDKUKUNBI/', 'https://github.com/yarnpkg/yarn/issues/7761#issuecomment-565493023', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10773', 'https://github.com/yarnpkg/yarn/commit/039bafd74b7b1a88a53a54f8fa6fa872615e90e7', 'https://blog.daniel-ruf.de/critical-design-flaw-npm-pnpm-yarn/', 'https://snyk.io/vuln/SNYK-JS-YARN-537806,', 'https://github.com/yarnpkg/yarn/pull/7755', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3HIZW4NZVV5QY5WWGW2JRP3FHYKZ6ZJ5/', 'https://access.redhat.com/errata/RHSA-2020:0475'}
| null |
npm
|
GHSA-4363-x42f-xph6
|
Malicious Package in hw-trnasport-u2f
|
All versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.
## Recommendation
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer.
The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
| null |
2021-10-01T21:03:00Z
|
2020-09-03T17:05:14Z
|
CRITICAL
| null |
{'CWE-506'}
|
{'https://www.npmjs.com/advisories/1400'}
| null |
npm
|
GHSA-hf8c-xr89-vfm5
|
Command Injection in ungit
|
The package ungit before 1.5.20 are vulnerable to Remote Code Execution (RCE) via argument injection. The issue occurs when calling the /api/fetch endpoint. User controlled values (remote and ref) are passed to the git fetch command. By injecting some git options it was possible to get arbitrary command execution.
|
{'CVE-2022-25766'}
|
2022-03-28T18:26:27Z
|
2022-03-22T00:00:41Z
|
HIGH
| null |
{'CWE-77'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2022-25766', 'https://github.com/FredrikNoren/ungit/pull/1511', 'https://github.com/FredrikNoren/ungit/pull/1510', 'https://github.com/FredrikNoren/ungit/blob/master/CHANGELOG.md%231520', 'https://snyk.io/vuln/SNYK-JS-UNGIT-2414099', 'https://github.com/FredrikNoren/ungit'}
| null |
npm
|
GHSA-c3hr-wwh3-qm54
|
Directory Traversal in fsk-server
|
Affected versions of `fsk-server` resolve relative file paths, resulting in a directory traversal vulnerability. A malicious actor can use this vulnerability to access files outside of the intended directory root, which may result in the disclosure of private files on the vulnerable system.
Example request:
```
GET /../../../../../../../../../../etc/passwd HTTP/1.1
host:foo
```
## Recommendation
No patch is available for this vulnerability.
It is recommended that the package is only used for local development, and if the functionality is needed for production, a different package is used instead.
|
{'CVE-2017-16090'}
|
2020-08-31T18:20:05Z
|
2020-09-01T16:47:09Z
|
HIGH
| null |
{'CWE-22'}
|
{'https://github.com/JacksonGL/NPM-Vuln-PoC/tree/master/directory-traversal/fsk-server', 'https://www.npmjs.com/advisories/345', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16090', 'https://nodesecurity.io/advisories/345'}
| null |
npm
|
GHSA-g78m-2chm-r7qv
|
Regular Expression Denial of Service in websocket-extensions (NPM package)
|
### Impact
The ReDoS flaw allows an attacker to exhaust the server's capacity to process
incoming requests by sending a WebSocket handshake request containing a header
of the following form:
Sec-WebSocket-Extensions: a; b="\c\c\c\c\c\c\c\c\c\c ...
That is, a header containing an unclosed string parameter value whose content is
a repeating two-byte sequence of a backslash and some other character. The
parser takes exponential time to reject this header as invalid, and this will
block the processing of any other work on the same thread. Thus if you are
running a single-threaded server, such a request can render your service
completely unavailable.
### Patches
Users should upgrade to version 0.1.4.
### Workarounds
There are no known work-arounds other than disabling any public-facing
WebSocket functionality you are operating.
### References
- https://blog.jcoglan.com/2020/06/02/redos-vulnerability-in-websocket-extensions/
|
{'CVE-2020-7662'}
|
2021-08-25T21:51:05Z
|
2020-06-05T16:16:12Z
|
HIGH
| null |
{'CWE-400'}
|
{'https://blog.jcoglan.com/2020/06/02/redos-vulnerability-in-websocket-extensions', 'https://snyk.io/vuln/SNYK-JS-WEBSOCKETEXTENSIONS-570623', 'https://github.com/faye/websocket-extensions-node/security/advisories/GHSA-g78m-2chm-r7qv', 'https://github.com/faye/websocket-extensions-node/commit/29496f6838bfadfe5a2f85dff33ed0ba33873237', 'https://github.com/faye/websocket-extensions-node', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7662'}
| null |
npm
|
GHSA-xw22-wv29-3299
|
ApiKey secret could be revelated on network issue
|
### Impact
_What kind of vulnerability is it? Who is impacted?_
Applications that are using node-etsy-client and reporting client error to the end user will offer api key value too
### Patches
_Has the problem been patched? What versions should users upgrade to?_
creharmony/node-etsy-client#18 fixes this issue. This is fixed in [node-etsy-client v0.3.0](https://github.com/creharmony/node-etsy-client/tree/v0.3.0) and later.
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
Do not report or log etsy client error if you are using version <= v0.2.0
Update your version of node-etsy-client
### References
_Are there any links users can visit to find out more?_
- https://github.com/creharmony/node-etsy-client/issues/17 : On connect error secret appears in error #17
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [github.com/creharmony/node-etsy-client/issues](https://github.com/creharmony/node-etsy-client/issues/)
|
{'CVE-2021-21421'}
|
2021-04-02T17:05:21Z
|
2021-04-06T17:29:52Z
|
HIGH
| null |
{'CWE-200'}
|
{'https://github.com/creharmony/node-etsy-client/commit/b4beb8ef080366c1a87dbf9e163051a446acaa7d', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21421', 'https://github.com/creharmony/node-etsy-client/security/advisories/GHSA-xw22-wv29-3299'}
| null |
npm
|
GHSA-5fw9-fq32-wv5p
|
OS Command Injection in node-notifier
|
This affects the package node-notifier before 8.0.1. It allows an attacker to run arbitrary commands on Linux machines due to the options params not being sanitised when being passed an array.
|
{'CVE-2020-7789'}
|
2020-12-21T16:03:51Z
|
2020-12-21T16:04:07Z
|
MODERATE
| null |
{'CWE-78'}
|
{'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1050371', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7789', 'https://github.com/mikaelbr/node-notifier/blob/master/lib/utils.js%23L303', 'https://snyk.io/vuln/SNYK-JS-NODENOTIFIER-1035794', 'https://github.com/mikaelbr/node-notifier/commit/5d62799dab88505a709cd032653b2320c5813fce'}
| null |
npm
|
GHSA-754x-4jwp-cqp6
|
Cross-Site Scripting in http_server
|
All versions of `http_server` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.
## Recommendation
No fix is currently available. Consider using an alternative package until a fix is made available.
|
{'CVE-2019-15600'}
|
2020-08-31T18:49:49Z
|
2020-03-31T17:02:26Z
|
HIGH
| null |
{'CWE-22'}
|
{'https://hackerone.com/reports/692262', 'https://hackerone.com/reports/578138', 'https://nvd.nist.gov/vuln/detail/CVE-2019-15600', 'https://www.npmjs.com/advisories/1170'}
| null |
npm
|
GHSA-8r98-rqg5-4vm3
|
Downloads Resources over HTTP in node-browser
|
Affected versions of `node-browser` insecurely downloads resources over HTTP.
In scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.
## Recommendation
No patch is currently available for this vulnerability.
The best mitigation is currently to avoid using this package, using a different package if available.
Alternatively, the risk of exploitation can be reduced by ensuring that this package is not installed while connected to a public network. If the package is installed on a private network, the only people who can exploit this vulnerability are those who have compromised your network or those who have privileged access to your ISP, such as Nation State Actors or Rogue ISP Employees.
|
{'CVE-2016-10618'}
|
2021-01-08T20:58:04Z
|
2019-02-18T23:56:50Z
|
HIGH
| null |
{'CWE-311'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2016-10618', 'https://github.com/advisories/GHSA-8r98-rqg5-4vm3', 'https://www.npmjs.com/advisories/214', 'https://nodesecurity.io/advisories/214'}
| null |
npm
|
GHSA-rvww-x6m4-4vc2
|
Malicious Package in blubird
|
Version 3.5.0 of `blubird` contains malicious code . The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. Upon require the package attempts to start a cryptocurrency miner using coin-hive.
## Recommendation
Remove the package from your environment and verify whether your system is running the cryptocurrency miner.
| null |
2021-09-30T22:00:23Z
|
2020-09-11T21:12:39Z
|
CRITICAL
| null |
{'CWE-506'}
|
{'https://www.npmjs.com/advisories/921'}
| null |
npm
|
GHSA-fm93-fhh2-cg2c
|
Prototype Pollution in min-dash
|
The package min-dash before 3.8.1 are vulnerable to Prototype Pollution via the set method due to missing enforcement of key types.
|
{'CVE-2021-23460'}
|
2022-01-27T14:11:41Z
|
2022-01-27T14:21:53Z
|
HIGH
| null |
{'CWE-1321'}
|
{'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-2342127', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23460', 'https://github.com/bpmn-io/min-dash/pull/21/commits/5ab05cbc4fd8d5eafb7db540c491ed0906b9d320', 'https://github.com/bpmn-io/min-dash/blob/c4d579c0eb2ed0739592111c3906b198921d3f52/lib/object.js%23L32', 'https://github.com/bpmn-io/min-dash/pull/21', 'https://github.com/bpmn-io/min-dash', 'https://snyk.io/vuln/SNYK-JS-MINDASH-2340605'}
| null |
npm
|
GHSA-2xwv-3cc9-fp7c
|
Sensitive Data Exposure in seneca
|
Versions of `seneca` prior to 3.9.0 are vulnerable to Sensitive Data Exposure. When a process using the package crashes all environment variables are printed. This may leak sensitive data such as access keys, especially given scenarios when log-monitoring systems store the error output.
## Recommendation
Upgrade to version 3.9.0 or later.
|
{'CVE-2019-5483'}
|
2020-08-31T18:49:15Z
|
2019-09-11T23:07:57Z
|
LOW
| null |
{'CWE-209'}
|
{'https://www.npmjs.com/advisories/1155', 'https://github.com/nodejs/security-wg/blob/master/vuln/npm/501.json', 'https://nvd.nist.gov/vuln/detail/CVE-2019-5483', 'https://hackerone.com/reports/526258'}
| null |
npm
|
GHSA-5w25-hxp5-h8c9
|
Improper Verification of Cryptographic Signature
|
tEnvoy contains the PGP, NaCl, and PBKDF2 in node.js and the browser (hashing, random, encryption, decryption, signatures, conversions), used by TogaTech.org. In versions prior to 7.0.3, the `verifyWithMessage` method of `tEnvoyNaClSigningKey` always returns `true` for any signature that has a SHA-512 hash matching the SHA-512 hash of the message even if the signature was invalid. This issue is patched in version 7.0.3. As a workaround: In `tenvoy.js` under the `verifyWithMessage` method definition within the `tEnvoyNaClSigningKey` class, ensure that the return statement call to `this.verify` ends in `.verified`.
|
{'CVE-2021-32685'}
|
2021-06-17T18:47:52Z
|
2021-06-21T17:12:13Z
|
CRITICAL
| null |
{'CWE-347'}
|
{'https://github.com/TogaTech/tEnvoy/commit/a121b34a45e289d775c62e58841522891dee686b', 'https://github.com/TogaTech/tEnvoy/releases/tag/v7.0.3', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32685', 'https://github.com/TogaTech/tEnvoy/security/advisories/GHSA-7r96-8g3x-g36m'}
| null |
npm
|
GHSA-65p8-3hm4-h9h8
|
Denial of Service in rgb2hex
|
All versions of `rgb2hex` are vulnerable to Regular Expression Denial of Service (ReDoS) when an attacker can pass in a specially crafted invalid color value.
## Recommendation
Update to version 0.1.6 or later.
| null |
2021-08-17T21:23:49Z
|
2019-08-23T00:04:48Z
|
MODERATE
| null |
{'CWE-400'}
|
{'https://snyk.io/vuln/npm:rgb2hex:20180429', 'https://hackerone.com/reports/319629', 'https://www.npmjs.com/advisories/647', 'https://github.com/christian-bromann/rgb2hex/blob/v0.1.0/index.js#L25', 'https://nodesecurity.io/advisories/647'}
| null |
npm
|
GHSA-6q48-vjq2-mwcj
|
Command Injection in umount
|
All versions of `umount ` are vulnerable to Command Injection. The package fails to sanitize input rules and passes it directly to an `exec` call on the `umount` function . This may allow attackers to execute arbitrary code in the system if the `device` value passed to the function is user-controlled.
## Recommendation
No fix is currently available. Consider using an alternative package until a fix is made available.
|
{'CVE-2020-7628'}
|
2021-07-28T22:37:17Z
|
2020-06-10T20:28:03Z
|
CRITICAL
| null |
{'CWE-78'}
|
{'https://www.npmjs.com/advisories/1512', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7628', 'https://snyk.io/vuln/SNYK-JS-UMOUNT-564265'}
| null |
npm
|
GHSA-23cm-x6j7-6hq3
|
matrix-js-sdk can be tricked into disclosing E2EE room keys to a participating homeserver
|
### Impact
A logic error in the room key sharing functionality of matrix-js-sdk before 12.4.1 allows a malicious Matrix homeserver† participating in an encrypted room to steal room encryption keys from affected Matrix clients participating in that room. This allows the homeserver to decrypt end-to-end encrypted messages sent by affected clients.
† Or anyone with access to the account of the original recipient of an encrypted message.
Known clients affected (via their use of vulnerable versions of matrix-js-sdk):
- Element Web (1.8.2 and earlier)
- Element Desktop (1.8.2 and earlier)
- SchildiChat Web (1.7.32-sc1 and earlier)
- SchildiChat Desktop (1.7.32-sc1 and earlier)
- Cinny (1.2.0 and earlier)
### Patch
This was fixed in https://github.com/matrix-org/matrix-js-sdk/commit/894c24880da0e1cc81818f51c0db80e3c9fb2be9.
### Workarounds
To prevent a homeserver from being able to steal the room keys, vulnerable clients can be taken offline or signed out. If signing out, care should be taken to either set up Secure Backup or export E2E room keys in order to preserve access to past messages.
|
{'CVE-2021-40823'}
|
2021-10-21T14:27:03Z
|
2021-09-14T20:24:18Z
|
MODERATE
| null |
{'CWE-200'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-40823', 'https://github.com/matrix-org/matrix-js-sdk/commit/894c24880da0e1cc81818f51c0db80e3c9fb2be9', 'https://github.com/matrix-org/matrix-js-sdk/security/advisories/GHSA-23cm-x6j7-6hq3', 'https://github.com/matrix-org/matrix-js-sdk/releases/tag/v12.4.1', 'https://matrix.org/blog/2021/09/13/vulnerability-disclosure-key-sharing', 'https://github.com/matrix-org/matrix-js-sdk'}
| null |
npm
|
GHSA-mvjj-gqq2-p4hw
|
Cross-Site Scripting in react-dom
|
Affected versions of `react-dom` are vulnerable to Cross-Site Scripting (XSS). The package fails to validate attribute names in HTML tags which may lead to Cross-Site Scripting in specific scenarios. This may allow attackers to execute arbitrary JavaScript in the victim's browser. To be affected by this vulnerability, the application needs to:
- be a server-side React app
- be rendered to HTML using `ReactDOMServer`
- include an attribute name from user input in an HTML tag
## Recommendation
If you are using `react-dom` 16.0.x, upgrade to 16.0.1 or later.
If you are using `react-dom` 16.1.x, upgrade to 16.1.2 or later.
If you are using `react-dom` 16.2.x, upgrade to 16.2.1 or later.
If you are using `react-dom` 16.3.x, upgrade to 16.3.3 or later.
If you are using `react-dom` 16.4.x, upgrade to 16.4.2 or later.
|
{'CVE-2018-6341'}
|
2020-08-31T18:58:44Z
|
2019-01-04T19:05:35Z
|
LOW
| null |
{'CWE-79'}
|
{'https://www.npmjs.com/advisories/1421', 'https://twitter.com/reactjs/status/1024745321987887104', 'https://github.com/advisories/GHSA-mvjj-gqq2-p4hw', 'https://reactjs.org/blog/2018/08/01/react-v-16-4-2.html', 'https://snyk.io/vuln/npm:react-dom:20180802', 'https://nvd.nist.gov/vuln/detail/CVE-2018-6341'}
| null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.