Advisory Database Sync

This commit is contained in:
advisory-database[bot]
2024-04-10 18:40:54 +00:00
parent f53a890c76
commit 90cf0ad854
999 changed files with 9323 additions and 1886 deletions
@@ -1,13 +1,13 @@
{
"schema_version": "1.4.0",
"id": "GHSA-6xrf-q977-5vgc",
"modified": "2023-01-06T03:21:28Z",
"modified": "2024-04-04T13:49:56Z",
"published": "2022-12-26T09:30:25Z",
"aliases": [
"CVE-2022-4742"
],
"summary": "json-pointer vulnerable to Prototype Pollution",
"details": "A vulnerability, which was classified as critical, has been found in json-pointer. Affected by this issue is the function set of the file index.js. The manipulation leads to improperly controlled modification of object prototype attributes ('prototype pollution'). The attack may be launched remotely. The name of the patch is 859c9984b6c407fc2d5a0a7e47c7274daa681941. It is recommended to apply a patch to fix this issue. VDB-216794 is the identifier assigned to this vulnerability.",
"details": "A vulnerability, which was classified as critical, has been found in json-pointer up to 0.6.1. Affected by this issue is the function set of the file index.js. The manipulation leads to improperly controlled modification of object prototype attributes ('prototype pollution'). The attack may be launched remotely. Upgrading to version 0.6.2 is able to address this issue. The patch is identified as 859c9984b6c407fc2d5a0a7e47c7274daa681941. It is recommended to upgrade the affected component. VDB-216794 is the identifier assigned to this vulnerability.",
"severity": [
{
"type": "CVSS_V3",
@@ -1,7 +1,7 @@
{
"schema_version": "1.4.0",
"id": "GHSA-9jfx-84v9-2rr2",
"modified": "2024-04-01T18:30:58Z",
"modified": "2024-04-05T15:08:07Z",
"published": "2023-07-20T00:30:24Z",
"aliases": [
"CVE-2023-3299"
@@ -70,6 +70,10 @@
{
"type": "PACKAGE",
"url": "https://github.com/hashicorp/nomad"
},
{
"type": "WEB",
"url": "https://pkg.go.dev/vuln/GO-2024-2669"
}
],
"database_specific": {
@@ -1,7 +1,7 @@
{
"schema_version": "1.4.0",
"id": "GHSA-rpvr-38xv-xvxq",
"modified": "2024-04-01T18:33:25Z",
"modified": "2024-04-05T15:34:23Z",
"published": "2023-07-20T00:30:24Z",
"aliases": [
"CVE-2023-3072"
@@ -66,6 +66,10 @@
{
"type": "PACKAGE",
"url": "https://github.com/hashicorp/nomad"
},
{
"type": "WEB",
"url": "https://pkg.go.dev/vuln/GO-2024-2670"
}
],
"database_specific": {
@@ -1,7 +1,7 @@
{
"schema_version": "1.4.0",
"id": "GHSA-v5fm-hr72-27hx",
"modified": "2024-04-01T19:17:38Z",
"modified": "2024-04-05T15:34:59Z",
"published": "2023-07-20T00:30:25Z",
"aliases": [
"CVE-2023-3300"
@@ -70,6 +70,10 @@
{
"type": "PACKAGE",
"url": "https://github.com/hashicorp/nomad"
},
{
"type": "WEB",
"url": "https://pkg.go.dev/vuln/GO-2024-2671"
}
],
"database_specific": {
@@ -1,7 +1,7 @@
{
"schema_version": "1.4.0",
"id": "GHSA-67hx-6x53-jw92",
"modified": "2023-10-16T13:55:36Z",
"modified": "2024-04-04T14:26:10Z",
"published": "2023-10-16T13:55:36Z",
"aliases": [
"CVE-2023-45133"
@@ -52,6 +52,25 @@
]
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "babel-traverse"
},
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
}
]
}
],
"database_specific": {
"last_known_affected_version_range": "< 7.23.2"
}
}
],
"references": [
@@ -1,7 +1,7 @@
{
"schema_version": "1.4.0",
"id": "GHSA-5667-3wch-7q7w",
"modified": "2024-04-03T15:30:41Z",
"modified": "2024-04-09T12:30:44Z",
"published": "2024-03-27T09:30:40Z",
"aliases": [
"CVE-2024-1023"
@@ -9,7 +9,10 @@
"summary": "Eclipse Vert.x memory leak",
"details": "A vulnerability in the Eclipse Vert.x toolkit results in a memory leak due to using Netty FastThreadLocal data structures. Specifically, when the Vert.x HTTP client establishes connections to different hosts, triggering the memory leak. The leak can be accelerated with intimate runtime knowledge, allowing an attacker to exploit this vulnerability. For instance, a server accepting arbitrary internet addresses could serve as an attack vector by connecting to these addresses, thereby accelerating the memory leak.",
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
@@ -80,6 +83,10 @@
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2024:1662"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2024:1706"
},
{
"type": "WEB",
"url": "https://access.redhat.com/security/cve/CVE-2024-1023"
@@ -95,6 +102,7 @@
],
"database_specific": {
"cwe_ids": [
"CWE-119",
"CWE-200"
],
"severity": "MODERATE",
@@ -0,0 +1,69 @@
{
"schema_version": "1.4.0",
"id": "GHSA-27jx-ffw8-xrqv",
"modified": "2024-04-04T17:01:56Z",
"published": "2024-04-04T15:30:34Z",
"aliases": [
"CVE-2024-3116"
],
"summary": "pgAdmin Remote Code Execution (RCE) vulnerability",
"details": "pgAdmin <= 8.4 is affected by a Remote Code Execution (RCE) vulnerability through the validate binary path API. This vulnerability allows attackers to execute arbitrary code on the server hosting PGAdmin, posing a severe risk to the database management system's integrity and the security of the underlying data.\n",
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L"
}
],
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "pgadmin4"
},
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "8.5"
}
]
}
]
}
],
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-3116"
},
{
"type": "WEB",
"url": "https://github.com/pgadmin-org/pgadmin4/issues/7326"
},
{
"type": "WEB",
"url": "https://github.com/pgadmin-org/pgadmin4/commit/fbbbfe22dd468bcfef1e1f833ec32289a6e56a8b"
},
{
"type": "WEB",
"url": "https://gist.github.com/aelmokhtar/689a8be7e3bd535ec01992d8ec7b2b98"
},
{
"type": "PACKAGE",
"url": "https://github.com/pgadmin-org/pgadmin4"
}
],
"database_specific": {
"cwe_ids": [
],
"severity": "HIGH",
"github_reviewed": true,
"github_reviewed_at": "2024-04-04T17:01:56Z",
"nvd_published_at": "2024-04-04T15:15:39Z"
}
}
@@ -1,7 +1,7 @@
{
"schema_version": "1.4.0",
"id": "GHSA-2q59-h24c-w6fg",
"modified": "2024-04-03T14:13:02Z",
"modified": "2024-04-04T13:37:56Z",
"published": "2024-04-03T14:13:02Z",
"aliases": [
"CVE-2024-30265"
@@ -97,6 +97,10 @@
"type": "WEB",
"url": "https://github.com/voila-dashboards/voila/security/advisories/GHSA-2q59-h24c-w6fg"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-30265"
},
{
"type": "WEB",
"url": "https://github.com/voila-dashboards/voila/commit/00d6362c237b6b4d466873535554d6076ead0c52"
@@ -129,6 +133,6 @@
"severity": "HIGH",
"github_reviewed": true,
"github_reviewed_at": "2024-04-03T14:13:02Z",
"nvd_published_at": null
"nvd_published_at": "2024-04-03T23:15:13Z"
}
}
File diff suppressed because one or more lines are too long
@@ -0,0 +1,65 @@
{
"schema_version": "1.4.0",
"id": "GHSA-4v52-7q2x-v4xj",
"modified": "2024-04-05T15:08:53Z",
"published": "2024-04-05T15:08:53Z",
"aliases": [
],
"summary": "eyre: Parts of Report are dropped as the wrong type during downcast",
"details": "In affected versions, after a `Report` is constructed using `wrap_err` or `wrap_err_with` to attach a message of type `D` onto an error of type `E`, then using `downcast` to recover ownership of either the value of type `D` or the value of type `E`, one of two things can go wrong:\n\n- If downcasting to `E`, there remains a value of type `D` to be dropped. It is incorrectly \"dropped\" by running `E`'s drop behavior, rather than `D`'s. For example if `D` is `&str` and `E` is `std::io::Error`, there would be a call of `std::io::Error::drop` in which the reference received by the `Drop` impl does not refer to a valid value of type `std::io::Error`, but instead to `&str`.\n\n- If downcasting to `D`, there remains a value of type `E` to be dropped. When `D` and `E` do not happen to be the same size, `E`'s drop behavior is incorrectly executed in the wrong location. The reference received by the `Drop` impl may point left or right of the real `E` value that is meant to be getting dropped.\n\nIn both cases, when the `Report` contains an error `E` that has nontrivial drop behavior, the most likely outcome is memory corruption.\n\nWhen the `Report` contains an error `E` that has trivial drop behavior (for example a `Utf8Error`) but where `D` has nontrivial drop behavior (such as `String`), the most likely outcome is that downcasting to `E` would leak `D`.",
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"package": {
"ecosystem": "crates.io",
"name": "eyre"
},
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0.6.9"
},
{
"fixed": "0.6.12"
}
]
}
]
}
],
"references": [
{
"type": "WEB",
"url": "https://github.com/eyre-rs/eyre/issues/141"
},
{
"type": "WEB",
"url": "https://github.com/eyre-rs/eyre/commit/770ac3fa1435eae3b166a4b072053360e38a0575"
},
{
"type": "PACKAGE",
"url": "https://github.com/eyre-rs/eyre"
},
{
"type": "WEB",
"url": "https://rustsec.org/advisories/RUSTSEC-2024-0021.html"
}
],
"database_specific": {
"cwe_ids": [
"CWE-843"
],
"severity": "HIGH",
"github_reviewed": true,
"github_reviewed_at": "2024-04-05T15:08:53Z",
"nvd_published_at": null
}
}
@@ -0,0 +1,111 @@
{
"schema_version": "1.4.0",
"id": "GHSA-4v7x-pqxf-cx7m",
"modified": "2024-04-04T23:02:57Z",
"published": "2024-04-04T21:30:32Z",
"aliases": [
"CVE-2023-45288"
],
"summary": "net/http, x/net/http2: close connections when receiving too many headers",
"details": "An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames. Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed. This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send. The fix sets a limit on the amount of excess header frames we will process before closing a connection.",
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"
}
],
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "net/http"
},
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "1.21.9"
}
]
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "golang.org/x/net/http2"
},
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "0.23.0"
}
]
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "net/http"
},
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "1.22.0-0"
},
{
"fixed": "1.22.2"
}
]
}
]
}
],
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-45288"
},
{
"type": "WEB",
"url": "https://go.dev/cl/576155"
},
{
"type": "WEB",
"url": "https://go.dev/issue/65051"
},
{
"type": "WEB",
"url": "https://groups.google.com/g/golang-announce/c/YgW0sx8mN3M"
},
{
"type": "WEB",
"url": "https://nowotarski.info/http2-continuation-flood-technical-details"
},
{
"type": "WEB",
"url": "https://pkg.go.dev/vuln/GO-2024-2687"
}
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"severity": "MODERATE",
"github_reviewed": true,
"github_reviewed_at": "2024-04-04T23:02:57Z",
"nvd_published_at": "2024-04-04T21:15:16Z"
}
}
@@ -0,0 +1,69 @@
{
"schema_version": "1.4.0",
"id": "GHSA-5pgg-2g8v-p4x9",
"modified": "2024-04-08T13:47:03Z",
"published": "2024-04-05T06:30:46Z",
"aliases": [
"CVE-2024-22363"
],
"summary": "SheetJS Regular Expression Denial of Service (ReDoS)",
"details": "SheetJS Community Edition before 0.20.2 is vulnerable.to Regular Expression Denial of Service (ReDoS).",
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "xlsx"
},
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "0.20.2"
}
]
}
]
}
],
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-22363"
},
{
"type": "WEB",
"url": "https://cdn.sheetjs.com/advisories/CVE-2024-22363"
},
{
"type": "WEB",
"url": "https://cwe.mitre.org/data/definitions/1333.html"
},
{
"type": "PACKAGE",
"url": "https://git.sheetjs.com/sheetjs/sheetjs"
},
{
"type": "WEB",
"url": "https://git.sheetjs.com/sheetjs/sheetjs/src/tag/v0.20.2"
}
],
"database_specific": {
"cwe_ids": [
"CWE-1333"
],
"severity": "HIGH",
"github_reviewed": true,
"github_reviewed_at": "2024-04-08T13:47:03Z",
"nvd_published_at": "2024-04-05T06:15:10Z"
}
}
@@ -0,0 +1,62 @@
{
"schema_version": "1.4.0",
"id": "GHSA-65pc-76pq-pvf5",
"modified": "2024-04-05T15:06:16Z",
"published": "2024-04-04T15:30:34Z",
"withdrawn": "2024-04-05T15:06:16Z",
"aliases": [
],
"summary": "Duplicate Advisory: Pebble service manager's file pull API allows access by any user",
"details": "## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-4685-2x5r-65pj. This link is maintained to preserve external references.\n\n## Original Description\nIt was discovered that Pebble's read-file API and the associated pebble pull command, before v1.10.2, allowed unprivileged local users to read files with root-equivalent permissions when Pebble was running as root. Fixes are also available as backports to v1.1.1, v1.4.2, and v1.7.4.",
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N"
}
],
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/canonical/pebble"
},
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "1.1.1"
}
]
}
]
}
],
"references": [
{
"type": "WEB",
"url": "https://github.com/canonical/pebble/security/advisories/GHSA-4685-2x5r-65pj"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-3250"
},
{
"type": "WEB",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-3250"
}
],
"database_specific": {
"cwe_ids": [
],
"severity": "MODERATE",
"github_reviewed": true,
"github_reviewed_at": "2024-04-05T15:06:16Z",
"nvd_published_at": "2024-04-04T15:15:39Z"
}
}
@@ -0,0 +1,82 @@
{
"schema_version": "1.4.0",
"id": "GHSA-6cf6-8hvr-r68w",
"modified": "2024-04-05T15:44:23Z",
"published": "2024-04-04T14:21:19Z",
"aliases": [
"CVE-2024-31206"
],
"summary": "dectalk-tts Uses Unencrypted HTTP Request",
"details": "### Impact\n\nIn `dectalk-tts@1.0.0`, network requests to the third-party API are sent over HTTP, which is unencrypted. Unencrypted traffic can be easily intercepted and modified by attackers. Anyone who uses the package could be the victim of a [man-in-the-middle (MITM)](https://en.wikipedia.org/wiki/Man-in-the-middle_attack) attack.\n\n<ins>Theft</ins>\n\nBecause `dectalk-tts` is a text-to-speech package, user requests are expected to only contain natural language. The package [README](https://github.com/JstnMcBrd/dectalk-tts/blob/main/README.md) warns that user input is sent to a third-party API, so users should not send sensitive information regardless.\n\nBut if users ignore the warnings and send sensitive information anyway, that information could be stolen by attackers.\n\n<ins>Modification</ins>\n\nAttackers could manipulate requests to the API. However, the worst a modified request could do is return an incorrect audio file or bad request rejection.\n\nAttackers could also manipulate responses from the API, returning malicious output to the user. Output is expected to be a wav-encoded buffer, which users will likely save to a file. This could be a dangerous entrypoint to the user's filesystem.\n\n### Patches\n\nThe network request was upgraded to HTTPS in version `1.0.1`. No other changes were made, so updating is risk-free.\n\n### Workarounds\n\nThere are no workarounds, but here are some precautions:\n\n- Do not send any sensitive information.\n\n- Carefully verify the API response before saving it.\n\n### References\n\n[Vulnerable code](https://github.com/JstnMcBrd/dectalk-tts/blob/b3e92156cbb699218ac9b9c7d8979abd0e635767/src/index.ts#L18)\n[Original report](https://github.com/JstnMcBrd/dectalk-tts/issues/3)\n[Patch pull request](https://github.com/JstnMcBrd/dectalk-tts/pull/4)\n",
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N"
}
],
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "dectalk-tts"
},
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "1.0.0"
},
{
"fixed": "1.0.1"
}
]
}
],
"versions": [
"1.0.0"
]
}
],
"references": [
{
"type": "WEB",
"url": "https://github.com/JstnMcBrd/dectalk-tts/security/advisories/GHSA-6cf6-8hvr-r68w"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-31206"
},
{
"type": "WEB",
"url": "https://github.com/JstnMcBrd/dectalk-tts/issues/3"
},
{
"type": "WEB",
"url": "https://github.com/JstnMcBrd/dectalk-tts/pull/4"
},
{
"type": "WEB",
"url": "https://github.com/JstnMcBrd/dectalk-tts/commit/3600d8ac156f27da553ac4ead46d16989a350105"
},
{
"type": "PACKAGE",
"url": "https://github.com/JstnMcBrd/dectalk-tts"
},
{
"type": "WEB",
"url": "https://github.com/JstnMcBrd/dectalk-tts/blob/b3e92156cbb699218ac9b9c7d8979abd0e635767/src/index.ts#L18"
}
],
"database_specific": {
"cwe_ids": [
"CWE-300",
"CWE-319",
"CWE-598"
],
"severity": "HIGH",
"github_reviewed": true,
"github_reviewed_at": "2024-04-04T14:21:19Z",
"nvd_published_at": "2024-04-04T23:15:15Z"
}
}
@@ -1,7 +1,7 @@
{
"schema_version": "1.4.0",
"id": "GHSA-75hq-h6g9-h4q5",
"modified": "2024-04-02T21:09:24Z",
"modified": "2024-04-04T20:24:14Z",
"published": "2024-04-02T21:09:23Z",
"aliases": [
"CVE-2024-30266"
@@ -43,6 +43,10 @@
"type": "WEB",
"url": "https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-75hq-h6g9-h4q5"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-30266"
},
{
"type": "WEB",
"url": "https://github.com/bytecodealliance/wasmtime/issues/8281"
@@ -71,6 +75,6 @@
"severity": "LOW",
"github_reviewed": true,
"github_reviewed_at": "2024-04-02T21:09:23Z",
"nvd_published_at": null
"nvd_published_at": "2024-04-04T16:15:09Z"
}
}
@@ -1,7 +1,7 @@
{
"schema_version": "1.4.0",
"id": "GHSA-9ph3-v2vh-3qx7",
"modified": "2024-04-03T15:30:41Z",
"modified": "2024-04-09T12:30:46Z",
"published": "2024-04-02T09:30:42Z",
"aliases": [
"CVE-2024-1300"
@@ -11,7 +11,7 @@
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L"
}
],
"affected": [
@@ -83,6 +83,10 @@
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2024:1662"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2024:1706"
},
{
"type": "WEB",
"url": "https://access.redhat.com/security/cve/CVE-2024-1300"
@@ -0,0 +1,92 @@
{
"schema_version": "1.4.0",
"id": "GHSA-9qxr-qj54-h672",
"modified": "2024-04-04T16:25:33Z",
"published": "2024-04-04T14:20:54Z",
"aliases": [
"CVE-2024-30261"
],
"summary": "Undici's fetch with integrity option is too lax when algorithm is specified but hash value is in incorrect",
"details": "### Impact\n\nIf an attacker can alter the `integrity` option passed to `fetch()`, they can let `fetch()` accept requests as valid even if they have been tampered.\n\n### Patches\n\nFixed in https://github.com/nodejs/undici/commit/d542b8cd39ec1ba303f038ea26098c3f355974f3.\nFixes has been released in v5.28.4 and v6.11.1.\n\n\n### Workarounds\n\nEnsure that `integrity` cannot be tampered with.\n\n### References\n\nhttps://hackerone.com/reports/2377760\n",
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N"
}
],
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "undici"
},
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "5.28.4"
}
]
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "undici"
},
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.0.0"
},
{
"fixed": "6.11.1"
}
]
}
]
}
],
"references": [
{
"type": "WEB",
"url": "https://github.com/nodejs/undici/security/advisories/GHSA-9qxr-qj54-h672"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-30261"
},
{
"type": "WEB",
"url": "https://github.com/nodejs/undici/commit/2b39440bd9ded841c93dd72138f3b1763ae26055"
},
{
"type": "WEB",
"url": "https://github.com/nodejs/undici/commit/d542b8cd39ec1ba303f038ea26098c3f355974f3"
},
{
"type": "WEB",
"url": "https://hackerone.com/reports/2377760"
},
{
"type": "PACKAGE",
"url": "https://github.com/nodejs/undici"
}
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"severity": "LOW",
"github_reviewed": true,
"github_reviewed_at": "2024-04-04T14:20:54Z",
"nvd_published_at": "2024-04-04T15:15:39Z"
}
}
@@ -1,13 +1,13 @@
{
"schema_version": "1.4.0",
"id": "GHSA-c33x-xqrf-c478",
"modified": "2024-04-02T14:16:05Z",
"modified": "2024-04-05T18:53:25Z",
"published": "2024-04-02T14:16:05Z",
"aliases": [
"CVE-2024-22189"
],
"summary": "QUIC's Connection ID Mechanism vulnerable to Memory Exhaustion Attack",
"details": "An attacker can cause its peer to run out of memory sending a large number of NEW_CONNECTION_ID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRE_CONNECTION_ID frame. The attacker can prevent the receiver from sending out (the vast majority of) these RETIRE_CONNECTION_ID frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate.\n\nI published a more detailed description of the attack and its mitigation in this blog post: https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-management/.\nI also presented this attack in the IETF QUIC working group session at IETF 119: https://youtu.be/JqXtYcZAtIA?si=nJ31QKLBSTRXY35U&t=3683\n\nThere's no way to mitigate this attack, please update quic-go to a version that contains the fix.",
"details": "An attacker can cause its peer to run out of memory by sending a large number of NEW_CONNECTION_ID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRE_CONNECTION_ID frame. The attacker can prevent the receiver from sending out (the vast majority of) these RETIRE_CONNECTION_ID frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate.\n\nI published a more detailed description of the attack and its mitigation in this blog post: https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-management/.\nI also presented this attack in the IETF QUIC working group session at IETF 119: https://youtu.be/JqXtYcZAtIA?si=nJ31QKLBSTRXY35U&t=3683\n\nThere's no way to mitigate this attack, please update quic-go to a version that contains the fix.",
"severity": [
{
"type": "CVSS_V3",
@@ -40,6 +40,10 @@
"type": "WEB",
"url": "https://github.com/quic-go/quic-go/security/advisories/GHSA-c33x-xqrf-c478"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-22189"
},
{
"type": "WEB",
"url": "https://github.com/quic-go/quic-go/commit/4a99b816ae3ab03ae5449d15aac45147c85ed47a"
@@ -59,11 +63,12 @@
],
"database_specific": {
"cwe_ids": [
"CWE-400"
"CWE-400",
"CWE-770"
],
"severity": "HIGH",
"github_reviewed": true,
"github_reviewed_at": "2024-04-02T14:16:05Z",
"nvd_published_at": null
"nvd_published_at": "2024-04-04T15:15:37Z"
}
}
@@ -1,7 +1,7 @@
{
"schema_version": "1.4.0",
"id": "GHSA-c4gr-q97g-ppwc",
"modified": "2024-04-01T20:33:53Z",
"modified": "2024-04-04T16:25:21Z",
"published": "2024-04-01T20:33:53Z",
"aliases": [
"CVE-2024-30250"
@@ -40,6 +40,10 @@
"type": "WEB",
"url": "https://github.com/kindspells/astro-shield/security/advisories/GHSA-c4gr-q97g-ppwc"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-30250"
},
{
"type": "WEB",
"url": "https://github.com/kindspells/astro-shield/commit/1221019306f501bf5fa9bcfb5a23a2321d34ba0a"
@@ -64,6 +68,6 @@
"severity": "HIGH",
"github_reviewed": true,
"github_reviewed_at": "2024-04-01T20:33:53Z",
"nvd_published_at": null
"nvd_published_at": "2024-04-04T15:15:39Z"
}
}
@@ -0,0 +1,72 @@
{
"schema_version": "1.4.0",
"id": "GHSA-f8h5-v2vg-46rr",
"modified": "2024-04-09T21:33:27Z",
"published": "2024-04-04T15:30:34Z",
"aliases": [
"CVE-2024-2700"
],
"summary": "quarkus-core leaks local environment variables from Quarkus namespace during application's build",
"details": "A vulnerability was found in the quarkus-core component. Quarkus captures the local environment variables from the Quarkus namespace during the application's build. Thus, running the resulting application inherits the values captured at build time. \n\nHowever, some local environment variables may have been set by the developer / CI environment for testing purposes, such as dropping the database during the application startup or trusting all TLS certificates to accept self-signed certificates. If these properties are configured using environment variables or the .env facility, they are captured into the built application. It leads to dangerous behavior if the application does not override these values.\n\nThis behavior only happens for configuration properties from the `quarkus.*` namespace. So, application-specific properties are not captured.",
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"package": {
"ecosystem": "Maven",
"name": "io.quarkus:quarkus-core"
},
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "3.9.2"
}
]
}
],
"database_specific": {
"last_known_affected_version_range": "<= 3.9.1"
}
}
],
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-2700"
},
{
"type": "WEB",
"url": "https://github.com/quarkusio/quarkus/issues/39927"
},
{
"type": "WEB",
"url": "https://access.redhat.com/security/cve/CVE-2024-2700"
},
{
"type": "WEB",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2273281"
},
{
"type": "PACKAGE",
"url": "https://github.com/quarkusio/quarkus"
}
],
"database_specific": {
"cwe_ids": [
"CWE-526"
],
"severity": "HIGH",
"github_reviewed": true,
"github_reviewed_at": "2024-04-04T17:01:45Z",
"nvd_published_at": "2024-04-04T14:15:09Z"
}
}

Some files were not shown because too many files have changed in this diff Show More