From bff18a269f8897b13a01fb78ac3b92a132a5184c Mon Sep 17 00:00:00 2001 From: "advisory-database[bot]" <45398580+advisory-database[bot]@users.noreply.github.com> Date: Tue, 3 Dec 2024 18:55:11 +0000 Subject: [PATCH] Publish Advisories GHSA-7q22-x757-cmgc GHSA-v5h2-q2w4-gpcx GHSA-wpvf-5mc3-hv6m GHSA-m7xq-9374-9rvx --- .../GHSA-7q22-x757-cmgc.json | 9 +++++++-- .../GHSA-v5h2-q2w4-gpcx.json | 17 +++++++++++++++-- .../GHSA-wpvf-5mc3-hv6m.json | 11 ++++++++--- .../GHSA-m7xq-9374-9rvx.json | 18 ++++++++++++++++-- 4 files changed, 46 insertions(+), 9 deletions(-) diff --git a/advisories/github-reviewed/2024/11/GHSA-7q22-x757-cmgc/GHSA-7q22-x757-cmgc.json b/advisories/github-reviewed/2024/11/GHSA-7q22-x757-cmgc/GHSA-7q22-x757-cmgc.json index 477213408f4..e1c11ad4595 100644 --- a/advisories/github-reviewed/2024/11/GHSA-7q22-x757-cmgc/GHSA-7q22-x757-cmgc.json +++ b/advisories/github-reviewed/2024/11/GHSA-7q22-x757-cmgc/GHSA-7q22-x757-cmgc.json @@ -1,7 +1,7 @@ { "schema_version": "1.4.0", "id": "GHSA-7q22-x757-cmgc", - "modified": "2024-12-03T16:07:27Z", + "modified": "2024-12-03T18:54:00Z", "published": "2024-11-29T21:31:03Z", "withdrawn": "2024-12-03T16:07:27Z", "aliases": [ @@ -10,6 +10,10 @@ "summary": "Withdrawn Advisory: Symfony http-security has authentication bypass", "details": "## Withdrawn Advisory\nThis advisory has been withdrawn because the report is not part of a valid vulnerability. This link is maintained to preserve external references. For more information, see advisory-database/pull/5046.\n\n## Original Description\nIn Symfony, a security vulnerability was identified in the FormLoginAuthenticator component, where it failed to adequately handle cases where the username or password field of a login request is empty. This flaw could lead to various security risks, including improper authentication logic handling or denial of service.", "severity": [ + { + "type": "CVSS_V3", + "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H" + }, { "type": "CVSS_V4", "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:U" @@ -60,7 +64,8 @@ ], "database_specific": { "cwe_ids": [ - "CWE-287" + "CWE-287", + "CWE-863" ], "severity": "MODERATE", "github_reviewed": true, diff --git a/advisories/github-reviewed/2024/11/GHSA-v5h2-q2w4-gpcx/GHSA-v5h2-q2w4-gpcx.json b/advisories/github-reviewed/2024/11/GHSA-v5h2-q2w4-gpcx/GHSA-v5h2-q2w4-gpcx.json index 64b28ba017c..3331a52f77c 100644 --- a/advisories/github-reviewed/2024/11/GHSA-v5h2-q2w4-gpcx/GHSA-v5h2-q2w4-gpcx.json +++ b/advisories/github-reviewed/2024/11/GHSA-v5h2-q2w4-gpcx/GHSA-v5h2-q2w4-gpcx.json @@ -1,13 +1,13 @@ { "schema_version": "1.4.0", "id": "GHSA-v5h2-q2w4-gpcx", - "modified": "2024-11-22T22:28:09Z", + "modified": "2024-12-03T18:53:35Z", "published": "2024-11-22T20:27:19Z", "aliases": [ "CVE-2024-53253" ], "summary": "Sentry improper error handling leaks Application Integration Client Secret", - "details": "### Impact\nDuring routine testing, we identified a scenario where a specific error message generated by our platform could include a plaintext Client ID and Client Secret for an application integration. The Client ID and Client Secret would not be displayed in the UI, but would be returned in the underlying HTTP response to the end user. This could occur under the following conditions:\n- An app installation made use of a [Search UI component](https://docs.sentry.io/organization/integrations/integration-platform/ui-components/formfield/#select) with the `async` flag set to true (default: true),\n- A user types types into the Search Component which creates a request to the third-party for search or query results, and\n- That third-party response may then fail validation and Sentry would return the `select-requester.invalid-response` error code along with a serialized version of a Sentry application containing the integration Client Secret.\n\nShould this error be found, it's reasonable to assume the potential exposure of an integration Client Secret. However, an ID and Secret pair alone does not provide direct access to any data. For that secret to be abused an attacker would also need to obtain a valid API token for a Sentry application. \n\n#### Impact for SaaS Users\nFor Sentry SaaS users, we have confirmed that only a single application integration was impacted and the owner has rotated their Client Secret. We have also confirmed that no abuse of the leaked Client Secret has occurred. \n\n#### Potential Impact for Self-Hosted Users\nSentry self-hosted does not ship with any application integrations. This could only impact self-hosted users that maintain their own integrations. In that case, search for a `select-requester.invalid-response` event. Please note that this error was also shared with another event unrelated to this advisory so you will also need to review the parameters logged for each named event. You may review [select_requester.py](https://github.com/getsentry/sentry/blob/4a448fbb0d0b416fef9ee0ab26579e0dc16f21b7/src/sentry/sentry_apps/external_requests/select_requester.py#L78-L123) for the instances where these errors can be generated. With the security fix this is no longer a shared event type.\n\n### Patches\n- Sentry SaaS users do not need to take any action.\n- The next release will include the fix for Sentry self-hosted users.\n\n### Workarounds\n- Sentry self-hosted users may not install version 24.11.0 and instead wait for the next release.\n- If your self-hosted instance is already running the affected version, consider downgrading to [24.10.0](https://github.com/getsentry/sentry/releases/tag/24.10.0).\n\n### References\n- Bug introduced in https://github.com/getsentry/sentry/pull/79377\n- Security fix in https://github.com/getsentry/sentry/pull/81038\n", + "details": "### Impact\nDuring routine testing, we identified a scenario where a specific error message generated by our platform could include a plaintext Client ID and Client Secret for an application integration. The Client ID and Client Secret would not be displayed in the UI, but would be returned in the underlying HTTP response to the end user. This could occur under the following conditions:\n- An app installation made use of a [Search UI component](https://docs.sentry.io/organization/integrations/integration-platform/ui-components/formfield/#select) with the `async` flag set to true (default: true),\n- A user types types into the Search Component which creates a request to the third-party for search or query results, and\n- That third-party response may then fail validation and Sentry would return the `select-requester.invalid-response` error code along with a serialized version of a Sentry application containing the integration Client Secret.\n\nShould this error be found, it's reasonable to assume the potential exposure of an integration Client Secret. However, an ID and Secret pair alone does not provide direct access to any data. For that secret to be abused an attacker would also need to obtain a valid API token for a Sentry application. \n\n#### Impact for SaaS Users\nFor Sentry SaaS users, we have confirmed that only a single application integration was impacted and the owner has rotated their Client Secret. We have also confirmed that no abuse of the leaked Client Secret has occurred. \n\n#### Potential Impact for Self-Hosted Users\nSentry self-hosted does not ship with any application integrations. This could only impact self-hosted users that maintain their own integrations. In that case, search for a `select-requester.invalid-response` event. Please note that this error was also shared with another event unrelated to this advisory so you will also need to review the parameters logged for each named event. You may review [select_requester.py](https://github.com/getsentry/sentry/blob/4a448fbb0d0b416fef9ee0ab26579e0dc16f21b7/src/sentry/sentry_apps/external_requests/select_requester.py#L78-L123) for the instances where these errors can be generated. With the security fix this is no longer a shared event type.\n\n### Patches\n- Sentry SaaS users do not need to take any action.\n- Sentry self-hosted users should upgrade to 24.11.1 or higher.\n\n### References\n- Bug introduced in https://github.com/getsentry/sentry/pull/79377\n- Security fix in https://github.com/getsentry/sentry/pull/81038\n", "severity": [ { "type": "CVSS_V3", @@ -20,6 +20,19 @@ "ecosystem": "PyPI", "name": "sentry" }, + "ranges": [ + { + "type": "ECOSYSTEM", + "events": [ + { + "introduced": "24.11.0" + }, + { + "fixed": "24.11.1" + } + ] + } + ], "versions": [ "24.11.0" ] diff --git a/advisories/github-reviewed/2024/11/GHSA-wpvf-5mc3-hv6m/GHSA-wpvf-5mc3-hv6m.json b/advisories/github-reviewed/2024/11/GHSA-wpvf-5mc3-hv6m/GHSA-wpvf-5mc3-hv6m.json index cc1fa2b54ea..b988bc13ae7 100644 --- a/advisories/github-reviewed/2024/11/GHSA-wpvf-5mc3-hv6m/GHSA-wpvf-5mc3-hv6m.json +++ b/advisories/github-reviewed/2024/11/GHSA-wpvf-5mc3-hv6m/GHSA-wpvf-5mc3-hv6m.json @@ -1,13 +1,18 @@ { "schema_version": "1.4.0", "id": "GHSA-wpvf-5mc3-hv6m", - "modified": "2024-11-27T17:20:58Z", + "modified": "2024-12-03T18:54:02Z", "published": "2024-11-20T21:30:50Z", "withdrawn": "2024-11-27T17:20:58Z", "aliases": [], "summary": "Duplicate Advisory: Querydsl SQL/HQL injection", "details": "## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-6q3q-6v5j-h6vg. This link is maintained to preserve external references.\n\n## Original Description\nQuerydsl 5.1.0 allows SQL/HQL injection in orderBy in JPAQuery.", - "severity": [], + "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": [ { "package": { @@ -120,7 +125,7 @@ "cwe_ids": [ "CWE-89" ], - "severity": "HIGH", + "severity": "CRITICAL", "github_reviewed": true, "github_reviewed_at": "2024-11-21T22:23:12Z", "nvd_published_at": "2024-11-20T21:15:08Z" diff --git a/advisories/github-reviewed/2024/12/GHSA-m7xq-9374-9rvx/GHSA-m7xq-9374-9rvx.json b/advisories/github-reviewed/2024/12/GHSA-m7xq-9374-9rvx/GHSA-m7xq-9374-9rvx.json index 559eb88031e..6566cfd85cb 100644 --- a/advisories/github-reviewed/2024/12/GHSA-m7xq-9374-9rvx/GHSA-m7xq-9374-9rvx.json +++ b/advisories/github-reviewed/2024/12/GHSA-m7xq-9374-9rvx/GHSA-m7xq-9374-9rvx.json @@ -1,7 +1,7 @@ { "schema_version": "1.4.0", "id": "GHSA-m7xq-9374-9rvx", - "modified": "2024-12-02T22:19:11Z", + "modified": "2024-12-03T18:54:33Z", "published": "2024-12-02T21:31:20Z", "aliases": [ "CVE-2024-53900" @@ -9,6 +9,10 @@ "summary": "Mongoose search injection vulnerability", "details": "Mongoose before 8.8.3 can improperly use $where in match.", "severity": [ + { + "type": "CVSS_V3", + "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H" + }, { "type": "CVSS_V4", "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N" @@ -51,10 +55,20 @@ { "type": "WEB", "url": "https://github.com/Automattic/mongoose/blob/master/CHANGELOG.md" + }, + { + "type": "WEB", + "url": "https://github.com/Automattic/mongoose/releases" + }, + { + "type": "WEB", + "url": "https://www.npmjs.com/package/mongoose?activeTab=versions" } ], "database_specific": { - "cwe_ids": [], + "cwe_ids": [ + "CWE-89" + ], "severity": "HIGH", "github_reviewed": true, "github_reviewed_at": "2024-12-02T22:19:11Z",