diff --git a/advisories/github-reviewed/2024/03/GHSA-fqg8-vfv7-8fj8/GHSA-fqg8-vfv7-8fj8.json b/advisories/github-reviewed/2024/03/GHSA-fqg8-vfv7-8fj8/GHSA-fqg8-vfv7-8fj8.json index de9796dd1f6..38e01879eb8 100644 --- a/advisories/github-reviewed/2024/03/GHSA-fqg8-vfv7-8fj8/GHSA-fqg8-vfv7-8fj8.json +++ b/advisories/github-reviewed/2024/03/GHSA-fqg8-vfv7-8fj8/GHSA-fqg8-vfv7-8fj8.json @@ -1,7 +1,7 @@ { "schema_version": "1.4.0", "id": "GHSA-fqg8-vfv7-8fj8", - "modified": "2024-03-04T20:43:12Z", + "modified": "2024-03-06T21:36:55Z", "published": "2024-03-04T20:43:12Z", "aliases": [ "CVE-2024-27307" @@ -9,7 +9,10 @@ "summary": "JSONata expression can pollute the \"Object\" prototype", "details": "### Impact\n\nIn JSONata versions `>= 1.4.0, < 1.8.7` and `>= 2.0.0, < 2.0.4`, a malicious expression can use the [transform operator](https://docs.jsonata.org/other-operators#-------transform) to override properties on the `Object` constructor and prototype. This may lead to denial of service, remote code execution or other unexpected behavior in applications that evaluate user-provided JSONata expressions.\n\n### Patch\n\nThis issue has been fixed in JSONata versions `>= 1.8.7` and `>= 2.0.4`. Applications that evaluate user-provided expressions should update ASAP to prevent exploitation. The following patch can be applied if updating is not possible.\n\n```patch\n--- a/src/jsonata.js\n+++ b/src/jsonata.js\n@@ -1293,6 +1293,13 @@ var jsonata = (function() {\n }\n for(var ii = 0; ii < matches.length; ii++) {\n var match = matches[ii];\n+ if (match && (match.isPrototypeOf(result) || match instanceof Object.constructor)) {\n+ throw {\n+ code: \"D1010\",\n+ stack: (new Error()).stack,\n+ position: expr.position\n+ };\n+ }\n // evaluate the update value for each match\n var update = await evaluate(expr.update, match, environment);\n // update must be an object\n@@ -1539,7 +1546,7 @@ var jsonata = (function() {\n if (typeof err.token == 'undefined' && typeof proc.token !== 'undefined') {\n err.token = proc.token;\n }\n- err.position = proc.position;\n+ err.position = proc.position || err.position;\n }\n throw err;\n }\n@@ -1972,6 +1979,7 @@ var jsonata = (function() {\n \"T1007\": \"Attempted to partially apply a non-function. Did you mean ${{{token}}}?\",\n \"T1008\": \"Attempted to partially apply a non-function\",\n \"D1009\": \"Multiple key definitions evaluate to same key: {{value}}\",\n+ \"D1010\": \"Attempted to access the Javascript object prototype\", // Javascript specific \n \"T1010\": \"The matcher function argument passed to function {{token}} does not return the correct object structure\",\n \"T2001\": \"The left side of the {{token}} operator must evaluate to a number\",\n \"T2002\": \"The right side of the {{token}} operator must evaluate to a number\",\n```\n\n### References\n\nhttps://github.com/jsonata-js/jsonata/releases/tag/v2.0.4\n\n### Credit\n\nThank you to Albert Pedersen of Cloudflare for disclosing this issue.\n", "severity": [ - + { + "type": "CVSS_V3", + "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H" + } ], "affected": [ { @@ -56,6 +59,10 @@ "type": "WEB", "url": "https://github.com/jsonata-js/jsonata/security/advisories/GHSA-fqg8-vfv7-8fj8" }, + { + "type": "ADVISORY", + "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-27307" + }, { "type": "WEB", "url": "https://github.com/jsonata-js/jsonata/commit/1d579dbe99c19fbe509f5ba2c6db7959b0d456d1" @@ -79,11 +86,11 @@ ], "database_specific": { "cwe_ids": [ - + "CWE-1321" ], - "severity": "HIGH", + "severity": "CRITICAL", "github_reviewed": true, "github_reviewed_at": "2024-03-04T20:43:12Z", - "nvd_published_at": null + "nvd_published_at": "2024-03-06T20:15:47Z" } } \ No newline at end of file diff --git a/advisories/github-reviewed/2024/03/GHSA-jr83-m233-gg6p/GHSA-jr83-m233-gg6p.json b/advisories/github-reviewed/2024/03/GHSA-jr83-m233-gg6p/GHSA-jr83-m233-gg6p.json index 18cf6fe3537..b188b5e9f31 100644 --- a/advisories/github-reviewed/2024/03/GHSA-jr83-m233-gg6p/GHSA-jr83-m233-gg6p.json +++ b/advisories/github-reviewed/2024/03/GHSA-jr83-m233-gg6p/GHSA-jr83-m233-gg6p.json @@ -1,7 +1,7 @@ { "schema_version": "1.4.0", "id": "GHSA-jr83-m233-gg6p", - "modified": "2024-03-04T20:45:09Z", + "modified": "2024-03-06T21:37:49Z", "published": "2024-03-04T20:45:08Z", "aliases": [ "CVE-2024-27915" @@ -9,7 +9,10 @@ "summary": "Sulu grants access to pages regardless of role permissions", "details": "### Impact\n\n_What kind of vulnerability is it? Who is impacted?_\n\nAccess to pages is granted regardless of role permissions for webspaces which have a security system configured and permission check enabled. Webspaces without do not have this issue.\n\n### Patches\n\nHas the problem been patched? What versions should users upgrade to?\n\nThe problem is patched with Version `2.4.17` and `2.5.13`.\n\n### Workarounds\n\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nRemove following lines from `vendor/symfony/security-http/HttpUtils.php`:\n\n```\n- // Shortcut if request has already been matched before\n- if ($request->attributes->has('_route')) {\n- return $path === $request->attributes->get('_route');\n - }\n```\n\nOr do not install `symfony/security-http` versions greater equal than `v5.4.30` or `v6.3.6`.\n\n### References\n\n_Are there any links users can visit to find out more?_\n\nCurrently no references.\n", "severity": [ - + { + "type": "CVSS_V3", + "score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N" + } ], "affected": [ { @@ -56,6 +59,10 @@ "type": "WEB", "url": "https://github.com/sulu/sulu/security/advisories/GHSA-jr83-m233-gg6p" }, + { + "type": "ADVISORY", + "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-27915" + }, { "type": "WEB", "url": "https://github.com/sulu/sulu/commit/ec9c3f99e15336dc4f6877f512300f231c17c6da" @@ -67,11 +74,11 @@ ], "database_specific": { "cwe_ids": [ - + "CWE-863" ], "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2024-03-04T20:45:08Z", - "nvd_published_at": null + "nvd_published_at": "2024-03-06T20:15:47Z" } } \ No newline at end of file diff --git a/advisories/github-reviewed/2024/03/GHSA-r8w9-5wcg-vfj7/GHSA-r8w9-5wcg-vfj7.json b/advisories/github-reviewed/2024/03/GHSA-r8w9-5wcg-vfj7/GHSA-r8w9-5wcg-vfj7.json index f3ecdb286f6..a19a21f624f 100644 --- a/advisories/github-reviewed/2024/03/GHSA-r8w9-5wcg-vfj7/GHSA-r8w9-5wcg-vfj7.json +++ b/advisories/github-reviewed/2024/03/GHSA-r8w9-5wcg-vfj7/GHSA-r8w9-5wcg-vfj7.json @@ -1,7 +1,7 @@ { "schema_version": "1.4.0", "id": "GHSA-r8w9-5wcg-vfj7", - "modified": "2024-03-04T20:44:35Z", + "modified": "2024-03-06T21:37:37Z", "published": "2024-03-04T20:44:35Z", "aliases": [ "CVE-2024-27308" @@ -9,7 +9,10 @@ "summary": "Mio's tokens for named pipes may be delivered after deregistration", "details": "### Impact\n\nWhen using named pipes on Windows, mio will under some circumstances return invalid tokens that correspond to named pipes that have already been deregistered from the mio registry. The impact of this vulnerability depends on how mio is used. For some applications, invalid tokens may be ignored or cause a warning or a crash. On the other hand, for applications that store pointers in the tokens, this vulnerability may result in a use-after-free.\n\nFor users of Tokio, this vulnerability is serious and can result in a use-after-free in Tokio.\n\nThe vulnerability is Windows-specific, and can only happen if you are using named pipes. Other IO resources are not affected.\n\n### Affected versions\nThis vulnerability has been fixed in mio v0.8.11.\n\nAll versions of mio between v0.7.2 and v0.8.10 are vulnerable.\n\nTokio is vulnerable when you are using a vulnerable version of mio AND you are using at least Tokio v1.30.0. Versions of Tokio prior to v1.30.0 will ignore invalid tokens, so they are not vulnerable.\n\n### Workarounds\nVulnerable libraries that use mio can work around this issue by detecting and ignoring invalid tokens.\n\n### Technical details\n\nWhen an IO resource registered with mio has a readiness event, mio delivers that readiness event to the user using a user-specified token. Mio guarantees that when an IO resource is [deregistered](https://docs.rs/mio/latest/mio/struct.Registry.html#method.deregister), then it will never return the token for that IO resource again. However, for named pipes on windows, mio may sometimes deliver the token for a named pipe even though the named pipe has been previously deregistered.\n\nThis vulnerability was originally reported in the Tokio issue tracker: [tokio-rs/tokio#6369](https://github.com/tokio-rs/tokio/issues/6369)\nThis vulnerability was fixed in: [tokio-rs/mio#1760](https://github.com/tokio-rs/mio/pull/1760)\nThis vulnerability is also known as [RUSTSEC-2024-0019](https://rustsec.org/advisories/RUSTSEC-2024-0019.html).\n\nThank you to @rofoun and @radekvit for discovering and reporting this issue.", "severity": [ - + { + "type": "CVSS_V3", + "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N" + } ], "affected": [ { @@ -40,6 +43,10 @@ "type": "WEB", "url": "https://github.com/tokio-rs/mio/security/advisories/GHSA-r8w9-5wcg-vfj7" }, + { + "type": "ADVISORY", + "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-27308" + }, { "type": "WEB", "url": "https://github.com/tokio-rs/tokio/issues/6369" @@ -65,6 +72,6 @@ "severity": "HIGH", "github_reviewed": true, "github_reviewed_at": "2024-03-04T20:44:35Z", - "nvd_published_at": null + "nvd_published_at": "2024-03-06T20:15:47Z" } } \ No newline at end of file