CWE-863
Allowed-with-ReviewIncorrect Authorization
Abstraction: Class · Status: Incomplete
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
8386 vulnerabilities reference this CWE, most recent first.
GHSA-R7GH-2W8P-P7Q9
Vulnerability from github – Published: 2026-11-17 03:31 – Updated: 2026-11-17 03:31phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an improper authorization vulnerability in updateUserRights that lets USER_EDIT admins drop category restrictions on group rights. Attackers can re-save rights through the user update-rights API to convert category-restricted group rights into global direct rights, then edit, publish or delete FAQs in withheld categories.
{
"affected": [],
"aliases": [
"CVE-2026-130357"
],
"database_specific": {
"cwe_ids": [
"CWE-863"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-17T02:17:18Z",
"severity": "HIGH"
},
"details": "phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an improper authorization vulnerability in updateUserRights that lets USER_EDIT admins drop category restrictions on group rights. Attackers can re-save rights through the user update-rights API to convert category-restricted group rights into global direct rights, then edit, publish or delete FAQs in withheld categories.",
"id": "GHSA-r7gh-2w8p-p7q9",
"modified": "2026-11-17T03:31:43Z",
"published": "2026-11-17T03:31:43Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-cg5x-q2hj-hw3j"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-130357"
},
{
"type": "WEB",
"url": "https://github.com/thorsten/phpMyFAQ/releases/tag/4.2.0-RC.2"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/phpmyfaq-4.2.0-alpha.2-before-4.2.0-rc.2-privilege-escalation-via-updateuserrights"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-R7HQ-Q2XM-6C5M
Vulnerability from github – Published: 2026-11-12 23:21 – Updated: 2026-11-12 23:21Summary
The StringMatcher/PathMatcher for safe_regex builds its RE2 as ^${regex}$ with no surrounding group. Because alternation has the lowest precedence, a pattern "a|b|c" compiles to /^a|b|c$/ -- "starts with a" OR "contains b" OR "ends with c" instead of a full match of the whole value. Configurations with safe_regex matchers that use a regex alternation (a natural way to list methods or service identities) therefore apply partial string matches. This impacts route selection, xDS credentials, and RBAC.
Details
src/matcher.ts: SafeRegexValueMatcher and PathSafeRegexValueMatcher both do
this.targetRegexImpl = new RE2(`^${targetRegex}$`, 'u');
and apply() returns targetRegexImpl.test(value). With a top-level alternation the anchors bind only to the first/last branch.
https://github.com/grpc/grpc-node/blob/e742b11bd8039f3dbea4cd29afdf5d95a8ba6b92/packages/grpc-js-xds/src/matcher.ts#L59
https://github.com/grpc/grpc-node/blob/e742b11bd8039f3dbea4cd29afdf5d95a8ba6b92/packages/grpc-js-xds/src/matcher.ts#L232
src/route.ts (getPredicateForStringMatcher / getPredicateForHeaderMatcher) builds these for every safe_regex StringMatcher/HeaderMatcher, and src/rbac.ts uses them for RBAC url_path permissions/principals, authenticated.principal_name (mTLS SAN/CN), requested_server_name and header rules. So an ALLOW rule written with an alternation grants access to method names, certificate identities or header values that extend an intended one. DENY policies only become broader (fail-safe).
https://github.com/grpc/grpc-node/blob/e742b11bd8039f3dbea4cd29afdf5d95a8ba6b92/packages/grpc-js-xds/src/route.ts#L28
https://github.com/grpc/grpc-node/blob/e742b11bd8039f3dbea4cd29afdf5d95a8ba6b92/packages/grpc-js-xds/src/route.ts#L47
Proof of concept
In a scratch directory:
npm init -y
npm i @grpc/grpc-js-xds@1.14.1 @grpc/grpc-js
node poc.cjs
poc.cjs calls the exported RBAC engine directly (the functions grpc-js uses to make the authorization decision); no server or network:
const { parseConfig } = require('@grpc/grpc-js-xds/build/src/rbac.js')
const { SafeRegexValueMatcher } = require('@grpc/grpc-js-xds/build/src/matcher.js')
const { Metadata } = require('@grpc/grpc-js')
console.log(new SafeRegexValueMatcher('admin|editor').toString()) // SafeRegex(/^admin|editor$/u)
const sr = regex => ({ match_pattern: 'safe_regex', safe_regex: { regex } })
const info = urlPath => ({ urlPath, headers: new Metadata(), tls: true, peerCertificate: null,
destinationIp: '10.0.0.1', destinationPort: 443, sourceIp: '10.0.0.2' })
const g = parseConfig({ action: 'ALLOW', policies: { p: {
permissions: [{ rule: 'url_path', url_path: { path: sr('/acme.Users/GetUser|/acme.Users/ListUsers') } }],
principals: [{ identifier: 'any', any: true }] } } })
console.log('GetUser ', g.apply(info('/acme.Users/GetUser'))) // true (intended)
console.log('DeleteUser ', g.apply(info('/acme.Users/DeleteUser'))) // false (control)
console.log('GetUserSecrets', g.apply(info('/acme.Users/GetUserSecrets'))) // true <-- BYPASS
Observed (grpc-js-xds 1.14.1, grpc-js 1.14.6):
matcher "admin|editor" -> SafeRegex(/^admin|editor$/u);
apply("administrator")=true, apply("not-an-editor")=true
ALLOW url_path /acme.Users/GetUser|/acme.Users/ListUsers:
/acme.Users/GetUser -> ALLOWED (intended)
/acme.Users/DeleteUser -> denied (control)
/acme.Users/GetUserSecrets -> ALLOWED <-- bypass (policy intends deny)
control, same regex as (?:...|...): /acme.Users/GetUserSecrets -> denied
ALLOW authenticated principal_name spiffe://prod/ns/web/sa/frontend|...ops/sa/admin:
spiffe://prod/ns/web/sa/frontend-batch -> ALLOWED <-- bypass
Impact
Users of @grpc/grpc-js-xds who are using safe_regex matchers with alternation for route selection, xDS credentials SAN matchers, or RBAC rules may see incorrectly permissive behavior.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "@grpc/grpc-js-xds"
},
"ranges": [
{
"events": [
{
"introduced": "1.14.0"
},
{
"fixed": "1.14.2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "@grpc/grpc-js-xds"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.13.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-126367"
],
"database_specific": {
"cwe_ids": [
"CWE-625",
"CWE-863"
],
"github_reviewed": true,
"github_reviewed_at": "2026-11-12T23:21:57Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "### Summary\n\nThe StringMatcher/PathMatcher for `safe_regex` builds its RE2 as `^${regex}$` with no surrounding group. Because alternation has the lowest precedence, a pattern `\"a|b|c\"` compiles to `/^a|b|c$/` -- \"starts with a\" OR \"contains b\" OR \"ends with c\" instead of a full match of the whole value. Configurations with `safe_regex` matchers that use a regex alternation (a natural way to list methods or service identities) therefore apply partial string matches. This impacts route selection, xDS credentials, and RBAC.\n\n### Details\n\n`src/matcher.ts`: `SafeRegexValueMatcher` and `PathSafeRegexValueMatcher` both do\n```ts\nthis.targetRegexImpl = new RE2(`^${targetRegex}$`, \u0027u\u0027);\n```\n\nand `apply()` returns `targetRegexImpl.test(value)`. With a top-level alternation the anchors bind only to the first/last branch.\n\nhttps://github.com/grpc/grpc-node/blob/e742b11bd8039f3dbea4cd29afdf5d95a8ba6b92/packages/grpc-js-xds/src/matcher.ts#L59\n\nhttps://github.com/grpc/grpc-node/blob/e742b11bd8039f3dbea4cd29afdf5d95a8ba6b92/packages/grpc-js-xds/src/matcher.ts#L232\n\n`src/route.ts` (`getPredicateForStringMatcher` / `getPredicateForHeaderMatcher`) builds these for every `safe_regex` `StringMatcher`/`HeaderMatcher`, and src/rbac.ts uses them for RBAC `url_path` `permissions`/`principals`, `authenticated.principal_name` (mTLS SAN/CN), `requested_server_name` and `header rules`. So an ALLOW rule written with an alternation grants access to method names, certificate identities or header values that extend an intended one. DENY policies only become broader (fail-safe).\n\nhttps://github.com/grpc/grpc-node/blob/e742b11bd8039f3dbea4cd29afdf5d95a8ba6b92/packages/grpc-js-xds/src/route.ts#L28\n\nhttps://github.com/grpc/grpc-node/blob/e742b11bd8039f3dbea4cd29afdf5d95a8ba6b92/packages/grpc-js-xds/src/route.ts#L47\n\n### Proof of concept\n\nIn a scratch directory:\n\n```\nnpm init -y\nnpm i @grpc/grpc-js-xds@1.14.1 @grpc/grpc-js\nnode poc.cjs\n```\n\n`poc.cjs` calls the exported RBAC engine directly (the functions grpc-js uses to make the authorization decision); no server or network:\n\n```js\nconst { parseConfig } = require(\u0027@grpc/grpc-js-xds/build/src/rbac.js\u0027)\nconst { SafeRegexValueMatcher } = require(\u0027@grpc/grpc-js-xds/build/src/matcher.js\u0027)\nconst { Metadata } = require(\u0027@grpc/grpc-js\u0027)\n\nconsole.log(new SafeRegexValueMatcher(\u0027admin|editor\u0027).toString()) // SafeRegex(/^admin|editor$/u)\n\nconst sr = regex =\u003e ({ match_pattern: \u0027safe_regex\u0027, safe_regex: { regex } })\nconst info = urlPath =\u003e ({ urlPath, headers: new Metadata(), tls: true, peerCertificate: null,\n destinationIp: \u002710.0.0.1\u0027, destinationPort: 443, sourceIp: \u002710.0.0.2\u0027 })\nconst g = parseConfig({ action: \u0027ALLOW\u0027, policies: { p: {\n permissions: [{ rule: \u0027url_path\u0027, url_path: { path: sr(\u0027/acme.Users/GetUser|/acme.Users/ListUsers\u0027) } }],\n principals: [{ identifier: \u0027any\u0027, any: true }] } } })\n\nconsole.log(\u0027GetUser \u0027, g.apply(info(\u0027/acme.Users/GetUser\u0027))) // true (intended)\nconsole.log(\u0027DeleteUser \u0027, g.apply(info(\u0027/acme.Users/DeleteUser\u0027))) // false (control)\nconsole.log(\u0027GetUserSecrets\u0027, g.apply(info(\u0027/acme.Users/GetUserSecrets\u0027))) // true \u003c-- BYPASS\n```\n\nObserved (grpc-js-xds 1.14.1, grpc-js 1.14.6):\n\n```\nmatcher \"admin|editor\" -\u003e SafeRegex(/^admin|editor$/u);\n apply(\"administrator\")=true, apply(\"not-an-editor\")=true\nALLOW url_path /acme.Users/GetUser|/acme.Users/ListUsers:\n /acme.Users/GetUser -\u003e ALLOWED (intended)\n /acme.Users/DeleteUser -\u003e denied (control)\n /acme.Users/GetUserSecrets -\u003e ALLOWED \u003c-- bypass (policy intends deny)\ncontrol, same regex as (?:...|...): /acme.Users/GetUserSecrets -\u003e denied\nALLOW authenticated principal_name spiffe://prod/ns/web/sa/frontend|...ops/sa/admin:\n spiffe://prod/ns/web/sa/frontend-batch -\u003e ALLOWED \u003c-- bypass\n```\n\n### Impact\n\nUsers of `@grpc/grpc-js-xds` who are using `safe_regex` matchers with alternation for route selection, xDS credentials SAN matchers, or RBAC rules may see incorrectly permissive behavior.",
"id": "GHSA-r7hq-q2xm-6c5m",
"modified": "2026-11-12T23:21:57Z",
"published": "2026-11-12T23:21:57Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/grpc/grpc-node/security/advisories/GHSA-r7hq-q2xm-6c5m"
},
{
"type": "WEB",
"url": "https://github.com/grpc/grpc-node/commit/3fc3b0ebf7a89d64843a73679951142d33b40cb1"
},
{
"type": "WEB",
"url": "https://github.com/grpc/grpc-node/commit/57a67e96babcb29b6eabc1833221ccf2fa152d43"
},
{
"type": "PACKAGE",
"url": "https://github.com/grpc/grpc-node"
},
{
"type": "WEB",
"url": "https://github.com/grpc/grpc-node/releases/tag/@grpc/grpc-js-xds@1.13.2"
},
{
"type": "WEB",
"url": "https://github.com/grpc/grpc-node/releases/tag/@grpc/grpc-js-xds@1.14.2"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "@grpc/grpc-js: safe_regex incorrectly applies partial string matching for patterns with alternation"
}
GHSA-R7HV-2FGC-3QJ2
Vulnerability from github – Published: 2024-09-19 18:30 – Updated: 2024-09-19 18:30In JetBrains YouTrack before 2024.3.44799 user without appropriate permissions could restore workflows attached to a project
{
"affected": [],
"aliases": [
"CVE-2024-47159"
],
"database_specific": {
"cwe_ids": [
"CWE-863"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-09-19T18:15:09Z",
"severity": "MODERATE"
},
"details": "In JetBrains YouTrack before 2024.3.44799 user without appropriate permissions could restore workflows attached to a project",
"id": "GHSA-r7hv-2fgc-3qj2",
"modified": "2024-09-19T18:30:52Z",
"published": "2024-09-19T18:30:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47159"
},
{
"type": "WEB",
"url": "https://www.jetbrains.com/privacy-security/issues-fixed"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-R7MC-98MX-P9M8
Vulnerability from github – Published: 2026-09-09 03:30 – Updated: 2026-09-09 18:31Incorrect authorization in ServiceWorker in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to bypass web origin policy via a crafted HTML page. (Chromium security severity: Low)
{
"affected": [],
"aliases": [
"CVE-2026-87598"
],
"database_specific": {
"cwe_ids": [
"CWE-863"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-09T01:17:17Z",
"severity": "MODERATE"
},
"details": "Incorrect authorization in ServiceWorker in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to bypass web origin policy via a crafted HTML page. (Chromium security severity: Low)",
"id": "GHSA-r7mc-98mx-p9m8",
"modified": "2026-09-09T18:31:51Z",
"published": "2026-09-09T03:30:43Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-87598"
},
{
"type": "WEB",
"url": "https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_0808145027.html"
},
{
"type": "WEB",
"url": "https://issues.chromium.org/issues/499218516"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-R7MM-GRF3-5FJV
Vulnerability from github – Published: 2022-08-17 00:00 – Updated: 2024-01-11 19:35Adobe Commerce versions 2.4.3-p2 (and earlier), 2.3.7-p3 (and earlier) and 2.4.4 (and earlier) are affected by an Improper Authorization vulnerability that could result in Privilege escalation. An attacker could leverage this vulnerability to access other user's data. Exploitation of this issue does not require user interaction.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "magento/community-edition"
},
"ranges": [
{
"events": [
{
"introduced": "2.3.0"
},
{
"fixed": "2.3.7-p4"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Packagist",
"name": "magento/community-edition"
},
"ranges": [
{
"events": [
{
"introduced": "2.4.4"
},
{
"fixed": "2.4.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Packagist",
"name": "magento/community-edition"
},
"ranges": [
{
"events": [
{
"introduced": "2.4.0"
},
{
"fixed": "2.4.3-p3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2022-34256"
],
"database_specific": {
"cwe_ids": [
"CWE-285",
"CWE-863"
],
"github_reviewed": true,
"github_reviewed_at": "2024-01-11T19:35:36Z",
"nvd_published_at": "2022-08-16T21:15:00Z",
"severity": "HIGH"
},
"details": "Adobe Commerce versions 2.4.3-p2 (and earlier), 2.3.7-p3 (and earlier) and 2.4.4 (and earlier) are affected by an Improper Authorization vulnerability that could result in Privilege escalation. An attacker could leverage this vulnerability to access other user\u0027s data. Exploitation of this issue does not require user interaction.",
"id": "GHSA-r7mm-grf3-5fjv",
"modified": "2024-01-11T19:35:36Z",
"published": "2022-08-17T00:00:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-34256"
},
{
"type": "WEB",
"url": "https://github.com/magento/magento2/commit/246d524b7586af2245092008e0d92b8d6fdd8523"
},
{
"type": "WEB",
"url": "https://github.com/magento/magento2/commit/5548bc64b5bc904346c0af9193a7fbb5274b4efa"
},
{
"type": "WEB",
"url": "https://github.com/magento/magento2/commit/5f07eba878296a37bd5c3a2baecad48948547594"
},
{
"type": "PACKAGE",
"url": "https://github.com/magento/magento2"
},
{
"type": "WEB",
"url": "https://helpx.adobe.com/security/products/magento/apsb22-38.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "Magento Improper Authorization vulnerability"
}
GHSA-R7PF-569H-JFW3
Vulnerability from github – Published: 2026-09-22 18:33 – Updated: 2026-09-22 18:33Adobe Campaign Classic (ACC) is affected by an Incorrect Authorization vulnerability that could result in arbitrary code execution in the context of the current user. An attacker could exploit this vulnerability to execute arbitrary code. Exploitation of this issue does not require user interaction.
{
"affected": [],
"aliases": [
"CVE-2026-75728"
],
"database_specific": {
"cwe_ids": [
"CWE-863"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-22T18:17:16Z",
"severity": "CRITICAL"
},
"details": "Adobe Campaign Classic (ACC) is affected by an Incorrect Authorization vulnerability that could result in arbitrary code execution in the context of the current user. An attacker could exploit this vulnerability to execute arbitrary code. Exploitation of this issue does not require user interaction.",
"id": "GHSA-r7pf-569h-jfw3",
"modified": "2026-09-22T18:33:33Z",
"published": "2026-09-22T18:33:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-75728"
},
{
"type": "WEB",
"url": "https://helpx.adobe.com/security/products/campaign/apsb26-142.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-R7R2-M3VR-C8QC
Vulnerability from github – Published: 2025-05-15 12:30 – Updated: 2025-05-17 14:02Mattermost versions 10.6.x <= 10.6.1, 10.5.x <= 10.5.2, 10.4.x <= 10.4.4, 9.11.x <= 9.11.11 fail to check the correct permissions which allows authenticated users who only have permission to invite non-guest users to a team to add guest users to that team via the API to add a single user to a team.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 10.6.1"
},
"package": {
"ecosystem": "Go",
"name": "github.com/mattermost/mattermost/server/v8"
},
"ranges": [
{
"events": [
{
"introduced": "10.6.0"
},
{
"fixed": "10.6.2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 10.5.2"
},
"package": {
"ecosystem": "Go",
"name": "github.com/mattermost/mattermost/server/v8"
},
"ranges": [
{
"events": [
{
"introduced": "10.5.0"
},
{
"fixed": "10.5.3"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 10.4.4"
},
"package": {
"ecosystem": "Go",
"name": "github.com/mattermost/mattermost/server/v8"
},
"ranges": [
{
"events": [
{
"introduced": "10.4.0"
},
{
"fixed": "10.4.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 9.11.11"
},
"package": {
"ecosystem": "Go",
"name": "github.com/mattermost/mattermost/server/v8"
},
"ranges": [
{
"events": [
{
"introduced": "9.11.0"
},
{
"fixed": "9.11.12"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "github.com/mattermost/mattermost/server/v8"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "8.0.0-20250415054241-76ab3867b785"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-3446"
],
"database_specific": {
"cwe_ids": [
"CWE-863"
],
"github_reviewed": true,
"github_reviewed_at": "2025-05-17T14:02:03Z",
"nvd_published_at": "2025-05-15T11:15:48Z",
"severity": "MODERATE"
},
"details": "Mattermost versions 10.6.x \u003c= 10.6.1, 10.5.x \u003c= 10.5.2, 10.4.x \u003c= 10.4.4, 9.11.x \u003c= 9.11.11 fail to check the correct permissions which allows authenticated users who only have permission to invite non-guest users to a team to add guest users to that team via the API to add a single user to a team.",
"id": "GHSA-r7r2-m3vr-c8qc",
"modified": "2025-05-17T14:02:03Z",
"published": "2025-05-15T12:30:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-3446"
},
{
"type": "PACKAGE",
"url": "https://github.com/mattermost/mattermost"
},
{
"type": "WEB",
"url": "https://mattermost.com/security-updates"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "Mattermost Fails to Validate Team Invite Permissions"
}
GHSA-R7RH-G777-G5GX
Vulnerability from github – Published: 2021-10-12 18:49 – Updated: 2021-10-18 14:34Default SilverStripe GraphQL Server (aka silverstripe/graphql) 3.x through 3.4.1 permission checker not inherited by query subclass.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "silverstripe/graphql"
},
"ranges": [
{
"events": [
{
"introduced": "3.0.0"
},
{
"fixed": "3.5.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2021-28661"
],
"database_specific": {
"cwe_ids": [
"CWE-863"
],
"github_reviewed": true,
"github_reviewed_at": "2021-10-08T21:35:47Z",
"nvd_published_at": "2021-10-07T15:15:00Z",
"severity": "MODERATE"
},
"details": "Default SilverStripe GraphQL Server (aka silverstripe/graphql) 3.x through 3.4.1 permission checker not inherited by query subclass.",
"id": "GHSA-r7rh-g777-g5gx",
"modified": "2021-10-18T14:34:41Z",
"published": "2021-10-12T18:49:23Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-28661"
},
{
"type": "WEB",
"url": "https://github.com/silverstripe/silverstripe-graphql/pull/407/commits/16961459f681f7b32145296189dfdbcc7715e6ed"
},
{
"type": "WEB",
"url": "https://github.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/graphql/CVE-2021-28661.yaml"
},
{
"type": "PACKAGE",
"url": "https://github.com/silverstripe/silverstripe-graphql"
},
{
"type": "WEB",
"url": "https://github.com/silverstripe/silverstripe-graphql/releases"
},
{
"type": "WEB",
"url": "https://github.com/silverstripe/silverstripe-graphql/releases/tag/3.5.2"
},
{
"type": "WEB",
"url": "https://www.silverstripe.org/download/security-releases/CVE-2021-28661"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "SilverStripe GraphQL Server permission checker not inherited by query subclass."
}
GHSA-R7RH-JWW5-5FJR
Vulnerability from github – Published: 2024-10-02 21:33 – Updated: 2024-10-09 22:47Impact
We've identified a vulnerability in the Pomerium databroker service API that may grant unintended access under specific conditions. This affects only certain Pomerium Zero and Pomerium Enterprise deployments.
Who is affected?
A Pomerium deployment is susceptible to this issue if all of the following conditions are met: - You have issued a service account access token using Pomerium Zero or Pomerium Enterprise. - The access token has an explicit expiration date in the future. - The core Pomerium databroker gRPC API is not otherwise secured by network access controls.
If your deployment does not meet all of these conditions, you are not affected by this vulnerability.
Details
The Pomerium databroker service is responsible for managing all persistent Pomerium application state. Requests to the databroker service API are authorized by the presence of a JSON Web Token (JWT) signed by a key known by all Pomerium services in the same deployment. However, incomplete validation of this JWT meant that some service account access tokens would incorrectly be treated as valid for the purpose of databroker API authorization.
Improper access to the databroker API could allow exfiltration of user info, spoofing of user sessions, or tampering with Pomerium routes, policies, and other settings.
Discovery
This issue was discovered during internal review. At this time we have no evidence to suggest that this vulnerability has been exploited in the wild.
Patches
We have released Pomerium v0.27.1 which includes a fix for the JWT validation logic. All affected users are strongly encouraged to upgrade to this version.
Workarounds
If you cannot upgrade immediately, consider the following mitigations:
-
Network access controls: Restrict access to the Pomerium internal gRPC API by configuring your network firewall or security groups to limit access to trusted sources only. Ensure that the port specified in the
grpc_addresssetting is not exposed to unauthorized networks. -
For Pomerium Zero deployments only: As of Pomerium v0.26.0, you can disable the gRPC API listener by setting
grpc_address: ""in your YAML configuration file. In all-in-one mode, Pomerium does not require the internal gRPC API to be exposed beyond localhost.
For more information
If you have questions or need further assistance:
- Open an issue in the pomerium/pomerium repository.
- Contact us at security@pomerium.com.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/pomerium/pomerium"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.27.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2024-47616"
],
"database_specific": {
"cwe_ids": [
"CWE-863"
],
"github_reviewed": true,
"github_reviewed_at": "2024-10-02T21:33:11Z",
"nvd_published_at": "2024-10-02T22:15:03Z",
"severity": "HIGH"
},
"details": "### Impact\n\nWe\u0027ve identified a vulnerability in the Pomerium databroker service API that may grant unintended access under specific conditions. This affects only certain Pomerium Zero and Pomerium Enterprise deployments.\n\n#### Who is affected?\n\nA Pomerium deployment is susceptible to this issue if _all_ of the following conditions are met:\n- You have issued a [service account](https://www.pomerium.com/docs/capabilities/service-accounts) access token using Pomerium Zero or Pomerium Enterprise.\n- The access token has an explicit expiration date in the future.\n- The core Pomerium databroker gRPC API is not otherwise secured by network access controls.\n\nIf your deployment does not meet _all_ of these conditions, you are not affected by this vulnerability.\n\n#### Details\n\nThe Pomerium databroker service is responsible for managing all persistent Pomerium application state. Requests to the databroker service API are authorized by the presence of a JSON Web Token (JWT) signed by a key known by all Pomerium services in the same deployment. However, incomplete validation of this JWT meant that some service account access tokens would incorrectly be treated as valid for the purpose of databroker API authorization.\n\nImproper access to the databroker API could allow exfiltration of user info, spoofing of user sessions, or tampering with Pomerium routes, policies, and other settings.\n\n#### Discovery\n\nThis issue was discovered during internal review. At this time we have no evidence to suggest that this vulnerability has been exploited in the wild.\n\n### Patches\n\nWe have released [Pomerium v0.27.1](https://github.com/pomerium/pomerium/releases/tag/v0.27.1) which includes a fix for the JWT validation logic. All affected users are strongly encouraged to upgrade to this version.\n\n### Workarounds\n\nIf you cannot upgrade immediately, consider the following mitigations:\n\n- Network access controls: Restrict access to the Pomerium internal gRPC API by configuring your network firewall or security groups to limit access to trusted sources only. Ensure that the port specified in the [`grpc_address`](https://www.pomerium.com/docs/reference/grpc#grpc-address) setting is not exposed to unauthorized networks.\n\n- _For Pomerium Zero deployments only:_ As of Pomerium v0.26.0, you can disable the gRPC API listener by setting `grpc_address: \"\"` in your YAML configuration file. In all-in-one mode, Pomerium does not require the internal gRPC API to be exposed beyond localhost.\n\n### For more information\nIf you have questions or need further assistance:\n\n- Open an issue in the [pomerium/pomerium](https://github.com/pomerium/pomerium/issues) repository.\n- Contact us at [security@pomerium.com](mailto:security@pomerium.com).\n",
"id": "GHSA-r7rh-jww5-5fjr",
"modified": "2024-10-09T22:47:38Z",
"published": "2024-10-02T21:33:11Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/pomerium/pomerium/security/advisories/GHSA-r7rh-jww5-5fjr"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47616"
},
{
"type": "WEB",
"url": "https://github.com/pomerium/pomerium/commit/e018cf0fc0979d2abe25ff705db019feb7523444"
},
{
"type": "PACKAGE",
"url": "https://github.com/pomerium/pomerium"
},
{
"type": "WEB",
"url": "https://github.com/pomerium/pomerium/releases/tag/v0.27.1"
},
{
"type": "WEB",
"url": "https://pkg.go.dev/vuln/GO-2024-3179"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Pomerium service account access token may grant unintended access to databroker API"
}
GHSA-R7RR-GHH8-J4P9
Vulnerability from github – Published: 2022-05-24 17:45 – Updated: 2022-09-25 00:00Improper Access Control in EmailValidationView in Samsung Account prior to version 10.7.0.7 and 12.1.1.3 allows physically proximate attackers to log out user account on device without user password.
{
"affected": [],
"aliases": [
"CVE-2021-25351"
],
"database_specific": {
"cwe_ids": [
"CWE-863"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-03-25T17:15:00Z",
"severity": "LOW"
},
"details": "Improper Access Control in EmailValidationView in Samsung Account prior to version 10.7.0.7 and 12.1.1.3 allows physically proximate attackers to log out user account on device without user password.",
"id": "GHSA-r7rr-ghh8-j4p9",
"modified": "2022-09-25T00:00:18Z",
"published": "2022-05-24T17:45:24Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-25351"
},
{
"type": "WEB",
"url": "https://security.samsungmobile.com"
},
{
"type": "WEB",
"url": "https://security.samsungmobile.com/serviceWeb.smsb"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
]
}
Mitigation
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries.
- Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
Mitigation
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].
Mitigation MIT-4.4
Strategy: Libraries or Frameworks
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
Mitigation
- For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page.
- One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
Mitigation
Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.
No CAPEC attack patterns related to this CWE.