Advisory Database Sync

2026-05-22 18:04:22 -07:00 · 2024-11-29 05:18:00 +00:00
parent 472df6496e
commit e90eeb517a
907 changed files with 1672 additions and 5016 deletions
@@ -8,9 +8,7 @@
  ],
  "summary": "File Descriptor Leak Can Cause DoS Vulnerability in hapi",
  "details": "Versions 2.0.x and 2.1.x of hapi are vulnerable to a denial of service attack via a file descriptor leak. \n\nWhen triggered repeatedly, this leak will cause the server to run out of file descriptors and the node process to die. The effort required to take down a server depends on the process file descriptor limit. No other side effects or exploits have been identified.\n\n\n\n## Recommendation\n\n- Please upgrade to version 2.2.x or above as soon as possible.",
-  "severity": [
-
-  ],
+  "severity": [],
  "affected": [
    {
      "package": {
@@ -3,14 +3,10 @@
  "id": "GHSA-8w57-jfpm-945m",
  "modified": "2023-04-11T00:26:58Z",
  "published": "2019-06-11T16:16:07Z",
-  "aliases": [
-
-  ],
+  "aliases": [],
  "summary": "Denial of Service in http-proxy-agent",
  "details": "Versions of `http-proxy-agent` before 2.1.0 are vulnerable to denial of service and uninitialized memory leak when unsanitized options are passed to `Buffer`. An attacker may leverage these unsanitized options to consume system resources.\n\n\n## Recommendation\n\nUpdate to version 2.1.0 or later.",
-  "severity": [
-
-  ],
+  "severity": [],
  "affected": [
    {
      "package": {
@@ -3,14 +3,10 @@
  "id": "GHSA-wxhq-pm8v-cw75",
  "modified": "2020-08-31T18:35:40Z",
  "published": "2019-06-05T20:50:16Z",
-  "aliases": [
-
-  ],
+  "aliases": [],
  "summary": "Regular Expression Denial of Service in clean-css",
  "details": "Version of `clean-css` prior to 4.1.11 are vulnerable to Regular Expression Denial of Service (ReDoS). Untrusted input may cause catastrophic backtracking while matching regular expressions. This can cause the application to be unresponsive leading to Denial of Service.\n\n\n## Recommendation\n\nUpgrade to version 4.1.11 or higher.",
-  "severity": [
-
-  ],
+  "severity": [],
  "affected": [
    {
      "package": {
@@ -3,14 +3,10 @@
  "id": "GHSA-39vw-qp34-rmwf",
  "modified": "2023-06-13T21:03:35Z",
  "published": "2021-08-25T21:00:18Z",
-  "aliases": [
-
-  ],
+  "aliases": [],
  "summary": "Uncontrolled recursion leads to abort in deserialization",
  "details": "Affected versions of this crate did not properly check for recursion while deserializing aliases. This allows an attacker to make a YAML file with an alias referring to itself causing an abort. The flaw was corrected by checking the recursion depth.\n",
-  "severity": [
-
-  ],
+  "severity": [],
  "affected": [
    {
      "package": {
@@ -3,14 +3,10 @@
  "id": "GHSA-66p5-j55p-32r9",
  "modified": "2021-08-06T16:36:54Z",
  "published": "2021-08-25T21:00:25Z",
-  "aliases": [
-
-  ],
+  "aliases": [],
  "summary": "smallvec creates uninitialized value of any type",
  "details": "Affected versions of this crate called `mem::uninitialized()` to create values of a user-supplied type `T`.\nThis is unsound e.g. if `T` is a reference type (which must be non-null and thus may not remain uninitialized).\n \nThe flaw was corrected by avoiding the use of `mem::uninitialized()`, using `MaybeUninit` instead.\n",
-  "severity": [
-
-  ],
+  "severity": [],
  "affected": [
    {
      "package": {
@@ -3,14 +3,10 @@
  "id": "GHSA-82hm-vh7g-hrh9",
  "modified": "2021-09-09T17:55:10Z",
  "published": "2021-08-25T21:01:25Z",
-  "aliases": [
-
-  ],
+  "aliases": [],
  "summary": "Partial read is incorrect in molecule",
  "details": "### Impact\n\nAnyone 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.\n\n### Workarounds\n\nIf you already have the whole `FixVec` `A`, you can use `A.as_slice().len()` to get the total size of the `FixVec`.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- [Open an issue to ask use directly](https://github.com/nervosnetwork/molecule/issues/new).",
-  "severity": [
-
-  ],
+  "severity": [],
  "affected": [
    {
      "package": {
@@ -51,9 +47,7 @@
    }
  ],
  "database_specific": {
-    "cwe_ids": [
-
-    ],
+    "cwe_ids": [],
    "severity": "MODERATE",
    "github_reviewed": true,
    "github_reviewed_at": "2021-08-02T18:10:49Z",
@@ -3,9 +3,7 @@
  "id": "GHSA-83r8-p8v6-6gfm",
  "modified": "2022-06-14T20:53:20Z",
  "published": "2021-08-25T21:00:20Z",
-  "aliases": [
-
-  ],
+  "aliases": [],
  "summary": "Slock<T> allows sending non-Send types across thread boundaries",
  "details": "`Slock<T>` unconditionally implements `Send`/`Sync`.\n\nAffected versions of this crate allows sending non-Send types to other threads,\nwhich can lead to data races and memory corruption due to the data race.\n",
  "severity": [
@@ -3,9 +3,7 @@
  "id": "GHSA-8892-84wf-cg8f",
  "modified": "2023-06-13T21:01:55Z",
  "published": "2021-08-25T21:00:16Z",
-  "aliases": [
-
-  ],
+  "aliases": [],
  "summary": "SyncChannel<T> can move 'T: !Send' to other threads",
  "details": "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.\n",
  "severity": [
@@ -3,14 +3,10 @@
  "id": "GHSA-ghpq-vjxw-ch5w",
  "modified": "2021-08-18T20:41:10Z",
  "published": "2021-08-25T20:56:52Z",
-  "aliases": [
-
-  ],
+  "aliases": [],
  "summary": "Use after free in libpulse-binding",
  "details": "### Overview\n\nVersion 1.2.1 of the `libpulse-binding` Rust crate, released on the 15th of June 2018, fixed a pair of use-after-free issues with the objects returned by the `get_format_info` and `get_context` methods of `Stream` objects. These objects were mistakenly being constructed without setting an important flag to prevent destruction of the underlying C objects they reference upon their own destruction.\n\nThis advisory is being written retrospectively, having previously only been noted in the changelog. No CVE assignment was sought.\n\n### Patches\n\nUsers are required to update to version 1.2.1 or newer.\n\nVersions older than 1.2.1 have been yanked from crates.io. This was believed to have already been done at the time of the 1.2.1 release, but upon double checking now they were found to still be available, so has been done now (22nd October 2020).",
-  "severity": [
-
-  ],
+  "severity": [],
  "affected": [
    {
      "package": {
@@ -3,9 +3,7 @@
  "id": "GHSA-gq4h-f254-7cw9",
  "modified": "2023-06-13T21:53:00Z",
  "published": "2021-08-25T21:00:34Z",
-  "aliases": [
-
-  ],
+  "aliases": [],
  "summary": "Data races in ticketed_lock",
  "details": "Affected versions of this crate unconditionally implemented `Send` for `ReadTicket<T>` & `WriteTicket<T>`.\nThis allows to send non-Send `T` to other threads.\n\nThis can allows creating data races by cloning types with internal mutability and sending them to other threads (as `T` of `ReadTicket<T>`/`WriteTicket<T>`). Such data races can cause memory corruption or other undefined behavior.\n\nThe flaw was corrected in commit `a986a93` by adding `T: Send` bounds to `Send` impls of `ReadTicket<T>`/`WriteTicket<T>`.\n",
  "severity": [
@@ -3,9 +3,7 @@
  "id": "GHSA-m296-j53x-xv95",
  "modified": "2023-06-13T21:47:59Z",
  "published": "2021-08-25T21:00:32Z",
-  "aliases": [
-
-  ],
+  "aliases": [],
  "summary": "Data races in tiny_future",
  "details": "`tiny_future` contains a light-weight implementation of `Future`s. The `Future` type it has lacked bound on its `Send` and `Sync` traits. This allows for a bug where non-thread safe types such as `Cell` can be used in `Future`s and cause data races in concurrent programs. The flaw was corrected in commit `c791919` by adding trait bounds to `Future`'s `Send` and `Sync`.\n",
  "severity": [
@@ -3,14 +3,10 @@
  "id": "GHSA-mcrf-7hf9-f6q5",
  "modified": "2023-06-13T20:48:55Z",
  "published": "2021-08-25T21:00:09Z",
-  "aliases": [
-
-  ],
+  "aliases": [],
  "summary": "Unchecked vector pre-allocation",
  "details": "Affected versions of this crate pre-allocate memory on deserializing raw buffers without checking whether there is sufficient data available. This allows an attacker to do denial-of-service attacks by sending small msgpack messages that allocate gigabytes of memory.\n",
-  "severity": [
-
-  ],
+  "severity": [],
  "affected": [
    {
      "package": {
@@ -3,9 +3,7 @@
  "id": "GHSA-pfjq-935c-4895",
  "modified": "2023-06-13T22:27:40Z",
  "published": "2021-08-25T21:00:37Z",
-  "aliases": [
-
-  ],
+  "aliases": [],
  "summary": "Data races in v9",
  "details": "Affected versions of this crate unconditionally implement `Sync` for `SyncRef<T>`. This definition allows data races if `&T` is accessible through `&SyncRef`.\n\n`SyncRef<T>` derives `Clone` and `Debug`, and the default implementations of those traits access `&T` by invoking `T::clone()` & `T::fmt()`. It is possible to create data races & undefined behavior by concurrently invoking `SyncRef<T>::clone()` or `SyncRef<T>::fmt()` from multiple threads with `T: !Sync`.\n",
  "severity": [
@@ -3,9 +3,7 @@
  "id": "GHSA-r88h-6987-g79f",
  "modified": "2023-06-13T21:54:46Z",
  "published": "2021-08-25T21:00:28Z",
-  "aliases": [
-
-  ],
+  "aliases": [],
  "summary": "Data races on syncpool",
  "details": "Affected versions of this crate unconditionally implements `Send` for `Bucket2`. This allows sending non-Send types to other threads.\n\nThis 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).\n\nThe flaw was corrected in commit `15b2828` by adding a `T: Send` bound to the `Send` impl of `Bucket2<T>`.\n",
  "severity": [
@@ -3,14 +3,10 @@
  "id": "GHSA-w65j-g6c7-g3m4",
  "modified": "2021-08-24T19:13:30Z",
  "published": "2021-08-25T20:42:50Z",
-  "aliases": [
-
-  ],
+  "aliases": [],
  "summary": "Multiple memory safety issues in actix-web",
  "details": "Affected versions contain multiple memory safety issues, such as:\n\n - Unsoundly coercing immutable references to mutable references\n - Unsoundly extending lifetimes of strings\n - Adding the `Send` marker trait to objects that cannot be safely sent between threads\n\nThis may result in a variety of memory corruption scenarios, most likely use-after-free.\n \nA signficant refactoring effort has been conducted to resolve these issues.\n",
-  "severity": [
-
-  ],
+  "severity": [],
  "affected": [
    {
      "package": {
@@ -3,14 +3,10 @@
  "id": "GHSA-wcxc-jf6c-8rx9",
  "modified": "2021-08-18T20:24:24Z",
  "published": "2021-08-25T20:57:21Z",
-  "aliases": [
-
-  ],
+  "aliases": [],
  "summary": " Uncaught Exception in libpulse-binding",
  "details": "Affected versions of this crate failed to catch panics crossing FFI boundaries via callbacks, which\nis a form of UB. This flaw was corrected by [this commit][1] which was included in version 2.6.0.",
-  "severity": [
-
-  ],
+  "severity": [],
  "affected": [
    {
      "package": {
@@ -3,9 +3,7 @@
  "id": "GHSA-xwxc-j97j-84gf",
  "modified": "2023-06-13T20:35:51Z",
  "published": "2021-08-25T21:00:03Z",
-  "aliases": [
-
-  ],
+  "aliases": [],
  "summary": "Race condition in Parc",
  "details": "In the affected versions of this crate, `LockWeak<T>` unconditionally implemented `Send` with no trait bounds on `T`. `LockWeak<T>` doesn't own `T` and only provides `&T`. This allows concurrent access to a non-Sync `T`, which can cause undefined behavior like data races.\n",
  "severity": [
@@ -58,9 +58,7 @@
    }
  ],
  "database_specific": {
-    "cwe_ids": [
-
-    ],
+    "cwe_ids": [],
    "severity": "CRITICAL",
    "github_reviewed": true,
    "github_reviewed_at": "2022-01-05T23:45:58Z",
@@ -325,9 +325,7 @@
    }
  ],
  "database_specific": {
-    "cwe_ids": [
-
-    ],
+    "cwe_ids": [],
    "severity": "HIGH",
    "github_reviewed": true,
    "github_reviewed_at": "2022-07-07T23:06:40Z",
@@ -8,9 +8,7 @@
  ],
  "summary": "Strapi does not verify the access or ID tokens issued during the OAuth flow",
  "details": "Strapi 3.2.1 until 4.6.0 does not verify the access or ID tokens issued during the OAuth flow when the AWS Cognito login provider is used for authentication. A remote attacker could forge an ID token that is signed using the 'None' type algorithm to bypass authentication and impersonate any user that use AWS Cognito for authentication.",
-  "severity": [
-
-  ],
+  "severity": [],
  "affected": [
    {
      "package": {
@@ -71,9 +69,7 @@
    }
  ],
  "database_specific": {
-    "cwe_ids": [
-
-    ],
+    "cwe_ids": [],
    "severity": "MODERATE",
    "github_reviewed": true,
    "github_reviewed_at": "2023-04-24T18:43:51Z",
--- a/Show More
+++ b/Show More