diff --git a/advisories/github-reviewed/2024/11/GHSA-4gmq-m9vp-jrwg/GHSA-4gmq-m9vp-jrwg.json b/advisories/github-reviewed/2024/11/GHSA-4gmq-m9vp-jrwg/GHSA-4gmq-m9vp-jrwg.json index 0228a14b007..db1495ede9e 100644 --- a/advisories/github-reviewed/2024/11/GHSA-4gmq-m9vp-jrwg/GHSA-4gmq-m9vp-jrwg.json +++ b/advisories/github-reviewed/2024/11/GHSA-4gmq-m9vp-jrwg/GHSA-4gmq-m9vp-jrwg.json @@ -1,13 +1,12 @@ { "schema_version": "1.4.0", "id": "GHSA-4gmq-m9vp-jrwg", - "modified": "2025-01-22T17:36:32Z", + "modified": "2025-02-19T17:47:37Z", "published": "2024-11-04T06:30:30Z", - "aliases": [ - "CVE-2024-10761" - ], - "summary": "Umbraco CMS Cross-site Scripting vulnerability", - "details": "A vulnerability was found in Umbraco CMS 12.3.6. It has been classified as problematic. Affected is an unknown function of the file /Umbraco/preview/frame?id{} of the component Dashboard. The manipulation of the argument culture leads to cross site scripting. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.", + "withdrawn": "2025-02-19T17:47:37Z", + "aliases": [], + "summary": "Duplicate Advisory: Umbraco CMS Cross-site Scripting vulnerability", + "details": "# Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-69cg-w8vm-h229. This link is maintained to preserve external references.\n\n# Original Description\n\nA vulnerability was found in Umbraco CMS 12.3.6. It has been classified as problematic. Affected is an unknown function of the file /Umbraco/preview/frame?id{} of the component Dashboard. The manipulation of the argument culture leads to cross site scripting. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.", "severity": [ { "type": "CVSS_V3", diff --git a/advisories/github-reviewed/2025/02/GHSA-99vm-5v2h-h6r6/GHSA-99vm-5v2h-h6r6.json b/advisories/github-reviewed/2025/02/GHSA-99vm-5v2h-h6r6/GHSA-99vm-5v2h-h6r6.json new file mode 100644 index 00000000000..23677031c5d --- /dev/null +++ b/advisories/github-reviewed/2025/02/GHSA-99vm-5v2h-h6r6/GHSA-99vm-5v2h-h6r6.json @@ -0,0 +1,78 @@ +{ + "schema_version": "1.4.0", + "id": "GHSA-99vm-5v2h-h6r6", + "modified": "2025-02-19T17:46:27Z", + "published": "2025-02-19T17:46:27Z", + "aliases": [ + "CVE-2025-27089" + ], + "summary": "Directus allows updates to non-allowed fields due to overlapping policies", + "details": "### Summary\nIf there are two overlapping policies for the `update` action that allow access to different fields, instead of correctly checking access permissions against the item they apply for the user is allowed to update the superset of fields allowed by any of the policies. \n\nE.g. have one policy allowing update access to `field_a` if the `id == 1` and one policy allowing update access to `field_b` if the `id == 2`. The user with both these policies is allowed to update both `field_a` and `field_b` for the items with ids `1` and `2`. \n\n### Details\nBefore v11, if a user was allowed to update an item they were allowed to update the fields that the single permission, that applied to that item, listed. With overlapping permissions this isn't as clear cut anymore and the union of fields might not be the fields the user is allowed to update for that specific item.\n\nThe solution that this PR introduces is to evaluate the permissions for each field that the user tries to update in the validateItemAccess DB query, instead of only verifying access to the item as a whole. This is done by, instead of returning the actual field value, returning a flag that indicates if the user has access to that field. This uses the same case/when mechanism that is used for stripping out non permitted field that is at the core of the permissions engine.\n\nAs a result, for every item that the access is validated for, the expected result is an item that has either 1 or null for all the \"requested\" fields instead of any of the actual field values. These results are not useful for anything other than verifying the field level access permissions.\n\nThe final check in validateItemAccess can either fail if the number of items does not match the number of items the access is checked for (ie. the user does not have access to the item at all) or if not all of the passed in fields have access permissions for any of the returned items.\n\n### Impact\nThis is a vulnerability that allows update access to unintended fields, potentially impacting the password field for user accounts.", + "severity": [ + { + "type": "CVSS_V3", + "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N" + } + ], + "affected": [ + { + "package": { + "ecosystem": "npm", + "name": "directus" + }, + "ranges": [ + { + "type": "ECOSYSTEM", + "events": [ + { + "introduced": "11.0.0" + }, + { + "fixed": "11.1.2" + } + ] + } + ] + }, + { + "package": { + "ecosystem": "npm", + "name": "@directus/api" + }, + "ranges": [ + { + "type": "ECOSYSTEM", + "events": [ + { + "introduced": "22.0.0" + }, + { + "fixed": "23.1.0" + } + ] + } + ] + } + ], + "references": [ + { + "type": "WEB", + "url": "https://github.com/directus/directus/security/advisories/GHSA-99vm-5v2h-h6r6" + }, + { + "type": "WEB", + "url": "https://github.com/directus/directus/commit/a7ea67783b060d0d6fc964d71c2d4575d5eee4e2" + }, + { + "type": "PACKAGE", + "url": "https://github.com/directus/directus" + } + ], + "database_specific": { + "cwe_ids": [], + "severity": "MODERATE", + "github_reviewed": true, + "github_reviewed_at": "2025-02-19T17:46:27Z", + "nvd_published_at": null + } +} \ No newline at end of file diff --git a/advisories/github-reviewed/2025/02/GHSA-qxj7-2x7w-3mpp/GHSA-qxj7-2x7w-3mpp.json b/advisories/github-reviewed/2025/02/GHSA-qxj7-2x7w-3mpp/GHSA-qxj7-2x7w-3mpp.json new file mode 100644 index 00000000000..2d1edd881b1 --- /dev/null +++ b/advisories/github-reviewed/2025/02/GHSA-qxj7-2x7w-3mpp/GHSA-qxj7-2x7w-3mpp.json @@ -0,0 +1,65 @@ +{ + "schema_version": "1.4.0", + "id": "GHSA-qxj7-2x7w-3mpp", + "modified": "2025-02-19T17:47:19Z", + "published": "2025-02-19T17:47:19Z", + "aliases": [ + "CVE-2025-26620" + ], + "summary": "Duende.AccessTokenManagement race condition when concurrently retrieving customized Client Credentials Access Tokens", + "details": "### Summary\nDuende.AccessTokenManagement contains a race condition when requesting access tokens using the client credentials flow. Concurrent requests to obtain an access token using differing protocol parameters can return access tokens obtained with the wrong scope, resource indicator, or other protocol parameters. Such usage is somewhat atypical, and only a small percentage of users are likely to be affected.\n\n### Details\nDuende.AccessTokenManagement can request access tokens using the client credentials flow in several ways. In basic usage, the client credentials flow is configured once and the parameters do not vary. In more advanced situations, requests with varying protocol parameters may be made by calling specific overloads of these methods:\n\n- `HttpContext.GetClientAccessTokenAsync()`\n- `IClientCredentialsTokenManagementService.GetAccessTokenAsync()`\n\nThere are overloads of both of these methods that accept a `TokenRequestParameters` object that customizes token request parameters. However, concurrent requests with varying `TokenRequestParameters` will result in the same token for all concurrent calls.\n\n\n### Upgrading\nMost users can simply update the NuGet package to the latest version. Customizations of the `IClientCredentialsTokenCache` that derive from the default implementation (`DistributedClientCredentialsTokenCache`) will require a small code change, as its constructor was changed to add a dependency on the `ITokenRequestSynchronization` service. The synchronization service will need to be injected into the derived class and passed to the base constructor.\n\n### Impact\nThe impact of this vulnerability depends on how Duende.AccessTokenManagement is used and on the security architecture of the solution. Most users will not be vulnerable to this issue. More advanced users may run into this issue by calling the methods specified above with customized token request parameters. The impact of obtaining an access token with different than intended protocol parameters will vary depending on application logic, security architecture, and the authorization policy of the resource servers.\n\nThank you to **Michael Dimoudis** of **PageUp** for finding this issue and responsibly disclosing it!", + "severity": [ + { + "type": "CVSS_V4", + "score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N" + } + ], + "affected": [ + { + "package": { + "ecosystem": "NuGet", + "name": "Duende.AccessTokenManagement" + }, + "ranges": [ + { + "type": "ECOSYSTEM", + "events": [ + { + "introduced": "0" + }, + { + "fixed": "3.2.0" + } + ] + } + ] + } + ], + "references": [ + { + "type": "WEB", + "url": "https://github.com/DuendeSoftware/foss/security/advisories/GHSA-qxj7-2x7w-3mpp" + }, + { + "type": "ADVISORY", + "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-26620" + }, + { + "type": "WEB", + "url": "https://github.com/DuendeSoftware/foss/commit/a33332ddec0ebf3c048ba85427e3c77d47c68dac" + }, + { + "type": "PACKAGE", + "url": "https://github.com/DuendeSoftware/foss" + } + ], + "database_specific": { + "cwe_ids": [ + "CWE-367" + ], + "severity": "MODERATE", + "github_reviewed": true, + "github_reviewed_at": "2025-02-19T17:47:19Z", + "nvd_published_at": "2025-02-18T18:15:36Z" + } +} \ No newline at end of file