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.
7172 vulnerabilities reference this CWE, most recent first.
GHSA-F74R-H7QJ-C63F
Vulnerability from github – Published: 2026-08-19 18:32 – Updated: 2026-08-19 18:32Summary
An authenticated organization user who can create or edit alert rules in a folder can query a datasource for which they do not have datasources:query permission. The attacker sets the client-controlled query field queryType to expr while retaining the UID of a real datasource.
The alert-rule authorization path treats the query as a server-side expression and skips datasource permission enforcement, while the evaluator subsequently resolves and executes the query against the real datasource identified by datasourceUid.
Impact
This bypass can expose data accessible through Grafana's configured datasource credentials to a low-privileged user who is not authorized to query that datasource directly. Confidentiality impact is High.
Integrity impact is Low because some datasource backends and configured credentials may permit state-changing queries. No availability impact has been demonstrated.
Attack prerequisites
- Authenticated, low-privileged user in the same Grafana organization
- Permission to create or edit alert rules in an accessible folder
- No datasources:query permission for the targeted datasource
- Knowledge or discovery of the targeted datasource UID
- No user interaction required
Technical details / root cause
- The attacker submits an alert-rule query with queryType: "expr" and the UID of a real datasource.
- The datasource authorization helper skips permission enforcement when query.QueryType == "expr".
- queryType is client-controlled and is not validated against the referenced datasource.
- During evaluation, Grafana selects and loads the actual datasource using DatasourceUID, not the spoofed queryType.
- The query therefore executes using Grafana's datasource credentials despite the caller lacking datasources:query.
The root cause is inconsistent query classification between authorization and execution: authorization trusts queryType, while execution trusts DatasourceUID.
Affected product / component
- Product: Grafana OSS
- Component: Unified Alerting / ngalert
- Area: Alert-rule datasource authorization and query evaluation
- Confirmed version: Grafana OSS 13.0.1
- Affected version range: not yet assessed
Severity
- CVSS 3.1: 7.1 High
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
- CWE-863: Incorrect Authorization
Scope is Unchanged because the vulnerable authorization decision and resulting impact remain within Grafana's security authority.
Source
- Researcher: czarflix
- Intigriti report: GRAFANALABS-F996ATD7
- Report URL: https://app.intigriti.com/company/submissions/GRAFANALABS-F996ATD7
Related report / duplicate assessment
This is a default-Grafana-OSS reproduction of the root cause previously reported in GRAFANALABS-IAQAFIXI. The earlier submission was archived as Not Applicable because its proof of concept depended on Cloud/Enterprise-specific permission mechanisms, and the researcher was invited to demonstrate the issue under default OSS permissions. This report establishes that missing prerequisite and should be treated as the actionable OSS submission, not dismissed as a duplicate.
VUL-2026-0095 and VUL-2026-0126 concern Enterprise Recorded Queries and have different components, endpoints, and root causes; they are related authorization issues but not duplicates.
Recommended remediation
- Do not exempt a query from datasource authorization based solely on client-controlled queryType.
- Resolve the referenced datasource server-side before authorization and apply datasources:query whenever the resolved UID represents a real datasource.
- Require expression queries to reference only the canonical server-side expression datasource and reject mismatches such as queryType: "expr" paired with a real datasource UID.
- Ensure authorization and evaluation use the same canonical datasource identity and fail closed when fields conflict.
- Add regression coverage for an OSS user with folder-level alert-rule edit permission but without datasource query permission, including mismatched queryType and datasourceUid values.
{
"affected": [],
"aliases": [
"CVE-2026-17183"
],
"database_specific": {
"cwe_ids": [
"CWE-863"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-19T18:16:35Z",
"severity": "HIGH"
},
"details": "Summary\n\nAn authenticated organization user who can create or edit alert rules in a folder can query a datasource for which they do not have datasources:query permission. The attacker sets the client-controlled query field queryType to __expr__ while retaining the UID of a real datasource.\n\nThe alert-rule authorization path treats the query as a server-side expression and skips datasource permission enforcement, while the evaluator subsequently resolves and executes the query against the real datasource identified by datasourceUid.\n\n## Impact\n\nThis bypass can expose data accessible through Grafana\u0027s configured datasource credentials to a low-privileged user who is not authorized to query that datasource directly. Confidentiality impact is High.\n\nIntegrity impact is Low because some datasource backends and configured credentials may permit state-changing queries. No availability impact has been demonstrated.\n\n## Attack prerequisites\n\n- Authenticated, low-privileged user in the same Grafana organization\n- Permission to create or edit alert rules in an accessible folder\n- No datasources:query permission for the targeted datasource\n- Knowledge or discovery of the targeted datasource UID\n- No user interaction required\n\n## Technical details / root cause\n\n1. The attacker submits an alert-rule query with queryType: \"__expr__\" and the UID of a real datasource.\n2. The datasource authorization helper skips permission enforcement when query.QueryType == \"__expr__\".\n3. queryType is client-controlled and is not validated against the referenced datasource.\n4. During evaluation, Grafana selects and loads the actual datasource using DatasourceUID, not the spoofed queryType.\n5. The query therefore executes using Grafana\u0027s datasource credentials despite the caller lacking datasources:query.\n\nThe root cause is inconsistent query classification between authorization and execution: authorization trusts queryType, while execution trusts DatasourceUID.\n\n## Affected product / component\n\n- Product: Grafana OSS\n- Component: Unified Alerting / ngalert\n- Area: Alert-rule datasource authorization and query evaluation\n- Confirmed version: Grafana OSS 13.0.1\n- Affected version range: not yet assessed\n\n## Severity\n\n- CVSS 3.1: 7.1 High\n- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N\n- CWE-863: Incorrect Authorization\n\nScope is Unchanged because the vulnerable authorization decision and resulting impact remain within Grafana\u0027s security authority.\n\n## Source\n\n- Researcher: czarflix\n- Intigriti report: GRAFANALABS-F996ATD7\n- Report URL: https://app.intigriti.com/company/submissions/GRAFANALABS-F996ATD7\n\n## Related report / duplicate assessment\n\nThis is a default-Grafana-OSS reproduction of the root cause previously reported in GRAFANALABS-IAQAFIXI. The earlier submission was archived as Not Applicable because its proof of concept depended on Cloud/Enterprise-specific permission mechanisms, and the researcher was invited to demonstrate the issue under default OSS permissions. This report establishes that missing prerequisite and should be treated as the actionable OSS submission, not dismissed as a duplicate.\n\nVUL-2026-0095 and VUL-2026-0126 concern Enterprise Recorded Queries and have different components, endpoints, and root causes; they are related authorization issues but not duplicates.\n\n## Recommended remediation\n\n- Do not exempt a query from datasource authorization based solely on client-controlled queryType.\n- Resolve the referenced datasource server-side before authorization and apply datasources:query whenever the resolved UID represents a real datasource.\n- Require expression queries to reference only the canonical server-side expression datasource and reject mismatches such as queryType: \"__expr__\" paired with a real datasource UID.\n- Ensure authorization and evaluation use the same canonical datasource identity and fail closed when fields conflict.\n- Add regression coverage for an OSS user with folder-level alert-rule edit permission but without datasource query permission, including mismatched queryType and datasourceUid values.",
"id": "GHSA-f74r-h7qj-c63f",
"modified": "2026-08-19T18:32:52Z",
"published": "2026-08-19T18:32:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-17183"
},
{
"type": "WEB",
"url": "https://grafana.com/security/security-advisories/cve-2026-17183"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-F76V-RQVC-F4RW
Vulnerability from github – Published: 2021-11-30 00:00 – Updated: 2022-10-24 19:00The Bulk Datetime Change WordPress plugin before 1.12 does not enforce capability checks which allows users with Contributor roles to 1) list private post titles of other users and 2) change the posted date of other users' posts.
{
"affected": [],
"aliases": [
"CVE-2021-24842"
],
"database_specific": {
"cwe_ids": [
"CWE-862",
"CWE-863"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-11-29T09:15:00Z",
"severity": "MODERATE"
},
"details": "The Bulk Datetime Change WordPress plugin before 1.12 does not enforce capability checks which allows users with Contributor roles to 1) list private post titles of other users and 2) change the posted date of other users\u0027 posts.",
"id": "GHSA-f76v-rqvc-f4rw",
"modified": "2022-10-24T19:00:20Z",
"published": "2021-11-30T00:00:50Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-24842"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/2618982"
},
{
"type": "WEB",
"url": "https://wpscan.com/vulnerability/054bd981-dbdd-47dd-bad0-fa327e5860a2"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-F79P-HQ3G-PRJW
Vulnerability from github – Published: 2022-05-24 17:05 – Updated: 2022-05-24 17:05An Improper Authorization - CWE-285 vulnerability exists in EcoStruxure? Control Expert V14.0 and all versions of Unity Pro (previously calledEcoStruxure? Control Expert), which could allow a bypass of the authentication process between EcoStruxure Control Expert and the controller.
{
"affected": [],
"aliases": [
"CVE-2019-6855"
],
"database_specific": {
"cwe_ids": [
"CWE-863"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2020-01-06T23:15:00Z",
"severity": "HIGH"
},
"details": "An Improper Authorization - CWE-285 vulnerability exists in EcoStruxure? Control Expert V14.0 and all versions of Unity Pro (previously calledEcoStruxure? Control Expert), which could allow a bypass of the authentication process between EcoStruxure Control Expert and the controller.",
"id": "GHSA-f79p-hq3g-prjw",
"modified": "2022-05-24T17:05:44Z",
"published": "2022-05-24T17:05:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-6855"
},
{
"type": "WEB",
"url": "https://www.se.com/ww/en/download/document/SEVD-2019-344-02"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-F7GR-QGV6-M73R
Vulnerability from github – Published: 2026-01-13 15:37 – Updated: 2026-01-13 15:37The CP Image Store with Slideshow plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.1.9 due to a logic error in the 'cpis_admin_init' function's permission check. This makes it possible for authenticated attackers, with Contributor-level access and above, to import arbitrary products via XML, if the XML file has already been uploaded to the server.
{
"affected": [],
"aliases": [
"CVE-2026-0684"
],
"database_specific": {
"cwe_ids": [
"CWE-863"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-01-13T14:16:38Z",
"severity": "MODERATE"
},
"details": "The CP Image Store with Slideshow plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.1.9 due to a logic error in the \u0027cpis_admin_init\u0027 function\u0027s permission check. This makes it possible for authenticated attackers, with Contributor-level access and above, to import arbitrary products via XML, if the XML file has already been uploaded to the server.",
"id": "GHSA-f7gr-qgv6-m73r",
"modified": "2026-01-13T15:37:04Z",
"published": "2026-01-13T15:37:04Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-0684"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/cp-image-store/tags/1.1.9/cp-image-store.php#L826"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/3434716"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/28e48604-2aaf-4e02-9b1e-cebf5f0bfcf7?source=cve"
}
],
"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-F7H3-XRJ3-8HHR
Vulnerability from github – Published: 2023-05-16 00:30 – Updated: 2024-04-04 04:11In verifyReplacingVersionCode of InstallPackageHelper.java, there is a possible way to downgrade system apps below system image version due to a logic error in the code. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11 Android-12 Android-12L Android-13Android ID: A-256202273
{
"affected": [],
"aliases": [
"CVE-2023-21116"
],
"database_specific": {
"cwe_ids": [
"CWE-863"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-05-15T22:15:12Z",
"severity": "MODERATE"
},
"details": "In verifyReplacingVersionCode of InstallPackageHelper.java, there is a possible way to downgrade system apps below system image version due to a logic error in the code. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11 Android-12 Android-12L Android-13Android ID: A-256202273",
"id": "GHSA-f7h3-xrj3-8hhr",
"modified": "2024-04-04T04:11:45Z",
"published": "2023-05-16T00:30:17Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-21116"
},
{
"type": "WEB",
"url": "https://source.android.com/security/bulletin/2023-05-01"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-F7P4-692G-F4W7
Vulnerability from github – Published: 2022-05-13 01:21 – Updated: 2022-05-13 01:21A security feature bypass vulnerability exists when Microsoft browsers improperly handle requests of different origins, aka 'Microsoft Browsers Security Feature Bypass Vulnerability'.
{
"affected": [],
"aliases": [
"CVE-2019-0762"
],
"database_specific": {
"cwe_ids": [
"CWE-863"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2019-04-09T02:29:00Z",
"severity": "MODERATE"
},
"details": "A security feature bypass vulnerability exists when Microsoft browsers improperly handle requests of different origins, aka \u0027Microsoft Browsers Security Feature Bypass Vulnerability\u0027.",
"id": "GHSA-f7p4-692g-f4w7",
"modified": "2022-05-13T01:21:32Z",
"published": "2022-05-13T01:21:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-0762"
},
{
"type": "WEB",
"url": "https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0762"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-F7WF-M2QG-R9RX
Vulnerability from github – Published: 2025-08-29 18:30 – Updated: 2026-10-07 18:31Incomplete authorization of linked device synchronization messages in WhatsApp for iOS prior to v2.25.21.73, WhatsApp Business for iOS v2.25.21.78, and WhatsApp for Mac v2.25.21.78 could have allowed an unrelated user to trigger processing of content from an arbitrary URL on a target’s device. We assess that this vulnerability, in combination with an OS-level vulnerability on Apple platforms (CVE-2025-43300), may have been exploited in a sophisticated attack against specific targeted users.
{
"affected": [],
"aliases": [
"CVE-2025-55177"
],
"database_specific": {
"cwe_ids": [
"CWE-863"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-08-29T16:15:36Z",
"severity": "HIGH"
},
"details": "Incomplete authorization of linked device synchronization messages in WhatsApp for iOS prior to v2.25.21.73, WhatsApp Business for iOS v2.25.21.78, and WhatsApp for Mac v2.25.21.78 could have allowed an unrelated user to trigger processing of content from an arbitrary URL on a target\u2019s device. We assess that this vulnerability, in combination with an OS-level vulnerability on Apple platforms (CVE-2025-43300), may have been exploited in a sophisticated attack against specific targeted users.",
"id": "GHSA-f7wf-m2qg-r9rx",
"modified": "2026-10-07T18:31:54Z",
"published": "2025-08-29T18:30:50Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-55177"
},
{
"type": "WEB",
"url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-55177"
},
{
"type": "WEB",
"url": "https://www.facebook.com/security/advisories/cve-2025-55177"
},
{
"type": "WEB",
"url": "https://www.whatsapp.com/security/advisories/2025"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-F82V-JWR5-MFFW
Vulnerability from github – Published: 2025-03-21 15:20 – Updated: 2026-03-02 16:59Impact
It is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware.
Patches
- For Next.js 15.x, this issue is fixed in
15.2.3 - For Next.js 14.x, this issue is fixed in
14.2.25 - For Next.js 13.x, this issue is fixed in 13.5.9
- For Next.js 12.x, this issue is fixed in 12.3.5
- For Next.js 11.x, consult the below workaround.
Note: Next.js deployments hosted on Vercel are automatically protected against this vulnerability.
Workaround
If patching to a safe version is infeasible, we recommend that you prevent external user requests which contain the x-middleware-subrequest header from reaching your Next.js application.
Credits
- Allam Rachid (zhero;)
- Allam Yasser (inzo_)
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "next"
},
"ranges": [
{
"events": [
{
"introduced": "13.0.0"
},
{
"fixed": "13.5.9"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "next"
},
"ranges": [
{
"events": [
{
"introduced": "14.0.0"
},
{
"fixed": "14.2.25"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "next"
},
"ranges": [
{
"events": [
{
"introduced": "15.0.0"
},
{
"fixed": "15.2.3"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "next"
},
"ranges": [
{
"events": [
{
"introduced": "12.0.0"
},
{
"fixed": "12.3.5"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-29927"
],
"database_specific": {
"cwe_ids": [
"CWE-285",
"CWE-863"
],
"github_reviewed": true,
"github_reviewed_at": "2025-03-21T15:20:12Z",
"nvd_published_at": "2025-03-21T15:15:42Z",
"severity": "CRITICAL"
},
"details": "# Impact\nIt is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware.\n\n# Patches\n* For Next.js 15.x, this issue is fixed in `15.2.3`\n* For Next.js 14.x, this issue is fixed in `14.2.25`\n* For Next.js 13.x, this issue is fixed in 13.5.9\n* For Next.js 12.x, this issue is fixed in 12.3.5\n* For Next.js 11.x, consult the below workaround.\n\n_Note: Next.js deployments hosted on Vercel are automatically protected against this vulnerability._\n\n# Workaround\nIf patching to a safe version is infeasible, we recommend that you prevent external user requests which contain the `x-middleware-subrequest` header from reaching your Next.js application.\n\n## Credits\n\n- Allam Rachid (zhero;)\n- Allam Yasser (inzo_)",
"id": "GHSA-f82v-jwr5-mffw",
"modified": "2026-03-02T16:59:03Z",
"published": "2025-03-21T15:20:12Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/vercel/next.js/security/advisories/GHSA-f82v-jwr5-mffw"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-29927"
},
{
"type": "WEB",
"url": "https://github.com/vercel/next.js/commit/52a078da3884efe6501613c7834a3d02a91676d2"
},
{
"type": "WEB",
"url": "https://github.com/vercel/next.js/commit/5fd3ae8f8542677c6294f32d18022731eab6fe48"
},
{
"type": "PACKAGE",
"url": "https://github.com/vercel/next.js"
},
{
"type": "WEB",
"url": "https://github.com/vercel/next.js/releases/tag/v12.3.5"
},
{
"type": "WEB",
"url": "https://github.com/vercel/next.js/releases/tag/v13.5.9"
},
{
"type": "WEB",
"url": "https://security.netapp.com/advisory/ntap-20250328-0002"
},
{
"type": "WEB",
"url": "https://vercel.com/changelog/vercel-firewall-proactively-protects-against-vulnerability-with-middleware"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2025/03/23/3"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2025/03/23/4"
}
],
"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"
}
],
"summary": "Authorization Bypass in Next.js Middleware"
}
GHSA-F834-HXF4-WMXM
Vulnerability from github – Published: 2022-05-24 19:04 – Updated: 2022-05-24 19:04Multiple vulnerabilities in the authorization process of Cisco ASR 5000 Series Software (StarOS) could allow an authenticated, remote attacker to bypass authorization and execute a subset of CLI commands on an affected device. For more information about these vulnerabilities, see the Details section of this advisory.
{
"affected": [],
"aliases": [
"CVE-2021-1540"
],
"database_specific": {
"cwe_ids": [
"CWE-863"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-06-04T17:15:00Z",
"severity": "HIGH"
},
"details": "Multiple vulnerabilities in the authorization process of Cisco ASR 5000 Series Software (StarOS) could allow an authenticated, remote attacker to bypass authorization and execute a subset of CLI commands on an affected device. For more information about these vulnerabilities, see the Details section of this advisory.",
"id": "GHSA-f834-hxf4-wmxm",
"modified": "2022-05-24T19:04:04Z",
"published": "2022-05-24T19:04:04Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-1540"
},
{
"type": "WEB",
"url": "https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-asr5k-autho-bypass-mJDF5S7n"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-F842-4GQM-2CPG
Vulnerability from github – Published: 2023-04-28 15:30 – Updated: 2024-04-04 03:43Insecure Permissions vulnerability found in MagicJack A921 USB Phone Jack Rev 3.0 v.1.4 allows a physically proximate attacker to escalate privileges and gain access to sensitive information via the NAND flash memory.
{
"affected": [],
"aliases": [
"CVE-2023-30024"
],
"database_specific": {
"cwe_ids": [
"CWE-269",
"CWE-863"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-04-28T13:15:13Z",
"severity": "MODERATE"
},
"details": "Insecure Permissions vulnerability found in MagicJack A921 USB Phone Jack Rev 3.0 v.1.4 allows a physically proximate attacker to escalate privileges and gain access to sensitive information via the NAND flash memory.",
"id": "GHSA-f842-4gqm-2cpg",
"modified": "2024-04-04T03:43:33Z",
"published": "2023-04-28T15:30:18Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-30024"
},
{
"type": "WEB",
"url": "https://drive.google.com/drive/folders/1cKd8hksThK610GPtBQ3du8DEkwKywlAi?usp=sharing"
},
{
"type": "WEB",
"url": "https://pastebin.com/raw/irWcawp8"
},
{
"type": "WEB",
"url": "https://samuraisecurity.co.uk/red-teaming-0x01-click-rce-via-voip-usb"
},
{
"type": "WEB",
"url": "https://www.magicjack.com"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"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.