CWE-862
Allowed-with-ReviewMissing Authorization
Abstraction: Class · Status: Incomplete
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
14693 vulnerabilities reference this CWE, most recent first.
GHSA-QMFX-54PC-298P
Vulnerability from github – Published: 2025-12-31 18:30 – Updated: 2026-04-01 18:36Missing Authorization vulnerability in Web Builder 143 Sticky Notes for WP Dashboard allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Sticky Notes for WP Dashboard: from n/a through 1.2.4.
{
"affected": [],
"aliases": [
"CVE-2025-62087"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-12-31T16:15:44Z",
"severity": "MODERATE"
},
"details": "Missing Authorization vulnerability in Web Builder 143 Sticky Notes for WP Dashboard allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Sticky Notes for WP Dashboard: from n/a through 1.2.4.",
"id": "GHSA-qmfx-54pc-298p",
"modified": "2026-04-01T18:36:28Z",
"published": "2025-12-31T18:30:23Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-62087"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/wb-sticky-notes/vulnerability/wordpress-sticky-notes-for-wp-dashboard-plugin-1-2-4-broken-access-control-vulnerability?_s_id=cve"
},
{
"type": "WEB",
"url": "https://vdp.patchstack.com/database/wordpress/plugin/wb-sticky-notes/vulnerability/wordpress-sticky-notes-for-wp-dashboard-plugin-1-2-4-broken-access-control-vulnerability?_s_id=cve"
}
],
"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"
}
]
}
GHSA-QMH6-M8QQ-5H2C
Vulnerability from github – Published: 2025-03-28 12:31 – Updated: 2026-04-01 18:34Missing Authorization vulnerability in webrangers Clear Sucuri Cache allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Clear Sucuri Cache: from n/a through 1.4.
{
"affected": [],
"aliases": [
"CVE-2025-31469"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-03-28T12:15:19Z",
"severity": "MODERATE"
},
"details": "Missing Authorization vulnerability in webrangers Clear Sucuri Cache allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Clear Sucuri Cache: from n/a through 1.4.",
"id": "GHSA-qmh6-m8qq-5h2c",
"modified": "2026-04-01T18:34:14Z",
"published": "2025-03-28T12:31:38Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-31469"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/clear-sucuri-cache/vulnerability/wordpress-clear-sucuri-cache-1-4-broken-access-control-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-QMH9-PQQV-CWMX
Vulnerability from github – Published: 2026-02-03 15:30 – Updated: 2026-02-03 18:30Missing Authorization vulnerability in ILLID Share This Image share-this-image allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Share This Image: from n/a through <= 2.09.
{
"affected": [],
"aliases": [
"CVE-2026-25010"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-02-03T15:16:19Z",
"severity": "MODERATE"
},
"details": "Missing Authorization vulnerability in ILLID Share This Image share-this-image allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Share This Image: from n/a through \u003c= 2.09.",
"id": "GHSA-qmh9-pqqv-cwmx",
"modified": "2026-02-03T18:30:43Z",
"published": "2026-02-03T15:30:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-25010"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/Wordpress/Plugin/share-this-image/vulnerability/wordpress-share-this-image-plugin-2-09-broken-access-control-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-QMJJ-P7M9-WJRV
Vulnerability from github – Published: 2026-02-27 19:29 – Updated: 2026-02-27 19:29In multi-user mode (OpenID), the sync API endpoints (/sync/*) don't verify that the authenticated user owns or has access to the file being operated on. Any authenticated user can read, modify, and overwrite any other user's budget files by providing their file ID.
Affected Code
File: packages/sync-server/src/app-sync.ts
The validateSessionMiddleware on line 31 confirms the user is authenticated, but individual endpoints only check that the file exists (via verifyFileExists), never that the requesting user owns or has access to the file.
Compare with POST /sync/delete-user-file (lines 394-430) which correctly checks:
const isOwner = file.owner === userId;
const isServerAdmin = isAdmin(userId);
if (!isOwner && !isServerAdmin) { ... }
This check is missing from all other endpoints.
Affected Endpoints
GET /sync/download-user-file- download any budget filePOST /sync/upload-user-file- overwrite any budget filePOST /sync/sync- read/write sync messages of any filePOST /sync/user-get-key- read encryption key infoPOST /sync/user-create-key- change encryption keyPOST /sync/reset-user-file- reset sync statePOST /sync/update-user-filename- rename fileGET /sync/get-user-file-info- read file metadata
PoC
Setup: Two users (Alice, Bob) authenticated via OpenID on the same Actual server. Alice has a budget with fileId abc-123.
Bob downloads Alice's budget:
curl -X GET 'https://actual.example.com/sync/download-user-file' \
-H 'X-Actual-Token: <bob-session-token>' \
-H 'X-Actual-File-Id: abc-123' \
-o stolen-budget.blob
Bob reads Alice's file metadata:
curl -X GET 'https://actual.example.com/sync/get-user-file-info' \
-H 'X-Actual-Token: <bob-session-token>' \
-H 'X-Actual-File-Id: abc-123'
Bob renames Alice's budget:
curl -X POST 'https://actual.example.com/sync/update-user-filename' \
-H 'X-Actual-Token: <bob-session-token>' \
-H 'Content-Type: application/json' \
-d '{"fileId": "abc-123", "name": "pwned"}'
Bob resets Alice's sync state (destructive):
curl -X POST 'https://actual.example.com/sync/reset-user-file' \
-H 'X-Actual-Token: <bob-session-token>' \
-H 'Content-Type: application/json' \
-d '{"fileId": "abc-123"}'
File IDs can be discovered by admin users via GET /sync/list-user-files (admins see all files), through user_access sharing, or by guessing.
Impact
In multi-user deployments (OpenID mode), any authenticated user can steal other users' complete financial data (transactions, accounts, balances, payees), modify or destroy their budgets, and tamper with encryption keys. This is a personal finance app, so the data is highly sensitive.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 26.2.0"
},
"package": {
"ecosystem": "npm",
"name": "@actual-app/sync-server"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "26.2.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-27638"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": true,
"github_reviewed_at": "2026-02-27T19:29:46Z",
"nvd_published_at": "2026-02-26T23:16:34Z",
"severity": "MODERATE"
},
"details": "In multi-user mode (OpenID), the sync API endpoints (`/sync/*`) don\u0027t verify that the authenticated user owns or has access to the file being operated on. Any authenticated user can read, modify, and overwrite any other user\u0027s budget files by providing their file ID.\n\n## Affected Code\n\nFile: `packages/sync-server/src/app-sync.ts`\n\nThe `validateSessionMiddleware` on line 31 confirms the user is authenticated, but individual endpoints only check that the file *exists* (via `verifyFileExists`), never that the requesting user *owns* or *has access to* the file.\n\nCompare with `POST /sync/delete-user-file` (lines 394-430) which correctly checks:\n```js\nconst isOwner = file.owner === userId;\nconst isServerAdmin = isAdmin(userId);\nif (!isOwner \u0026\u0026 !isServerAdmin) { ... }\n```\n\nThis check is missing from all other endpoints.\n\n## Affected Endpoints\n\n- `GET /sync/download-user-file` - download any budget file\n- `POST /sync/upload-user-file` - overwrite any budget file\n- `POST /sync/sync` - read/write sync messages of any file\n- `POST /sync/user-get-key` - read encryption key info\n- `POST /sync/user-create-key` - change encryption key\n- `POST /sync/reset-user-file` - reset sync state\n- `POST /sync/update-user-filename` - rename file\n- `GET /sync/get-user-file-info` - read file metadata\n\n## PoC\n\nSetup: Two users (Alice, Bob) authenticated via OpenID on the same Actual server. Alice has a budget with fileId `abc-123`.\n\nBob downloads Alice\u0027s budget:\n```bash\ncurl -X GET \u0027https://actual.example.com/sync/download-user-file\u0027 \\\n -H \u0027X-Actual-Token: \u003cbob-session-token\u003e\u0027 \\\n -H \u0027X-Actual-File-Id: abc-123\u0027 \\\n -o stolen-budget.blob\n```\n\nBob reads Alice\u0027s file metadata:\n```bash\ncurl -X GET \u0027https://actual.example.com/sync/get-user-file-info\u0027 \\\n -H \u0027X-Actual-Token: \u003cbob-session-token\u003e\u0027 \\\n -H \u0027X-Actual-File-Id: abc-123\u0027\n```\n\nBob renames Alice\u0027s budget:\n```bash\ncurl -X POST \u0027https://actual.example.com/sync/update-user-filename\u0027 \\\n -H \u0027X-Actual-Token: \u003cbob-session-token\u003e\u0027 \\\n -H \u0027Content-Type: application/json\u0027 \\\n -d \u0027{\"fileId\": \"abc-123\", \"name\": \"pwned\"}\u0027\n```\n\nBob resets Alice\u0027s sync state (destructive):\n```bash\ncurl -X POST \u0027https://actual.example.com/sync/reset-user-file\u0027 \\\n -H \u0027X-Actual-Token: \u003cbob-session-token\u003e\u0027 \\\n -H \u0027Content-Type: application/json\u0027 \\\n -d \u0027{\"fileId\": \"abc-123\"}\u0027\n```\n\nFile IDs can be discovered by admin users via `GET /sync/list-user-files` (admins see all files), through `user_access` sharing, or by guessing.\n\n## Impact\n\nIn multi-user deployments (OpenID mode), any authenticated user can steal other users\u0027 complete financial data (transactions, accounts, balances, payees), modify or destroy their budgets, and tamper with encryption keys. This is a personal finance app, so the data is highly sensitive.",
"id": "GHSA-qmjj-p7m9-wjrv",
"modified": "2026-02-27T19:29:46Z",
"published": "2026-02-27T19:29:46Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/actualbudget/actual/security/advisories/GHSA-qmjj-p7m9-wjrv"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27638"
},
{
"type": "WEB",
"url": "https://github.com/actualbudget/actual/commit/9966c024cb75f57943193cac8e42f401efed9d08"
},
{
"type": "PACKAGE",
"url": "https://github.com/actualbudget/actual"
},
{
"type": "WEB",
"url": "https://github.com/actualbudget/actual/releases/tag/v26.2.1"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P",
"type": "CVSS_V4"
}
],
"summary": "@actual-app/sync-server: Missing authorization in sync endpoints allows cross-user budget file access in multi-user mode"
}
GHSA-QMJQ-QM3J-H6V3
Vulnerability from github – Published: 2024-11-01 15:31 – Updated: 2024-11-01 15:31Missing Authorization vulnerability in BracketSpace Advanced Cron Manager allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Advanced Cron Manager – debug & control: from n/a through 2.5.9.
{
"affected": [],
"aliases": [
"CVE-2024-43154"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-11-01T15:15:39Z",
"severity": "MODERATE"
},
"details": "Missing Authorization vulnerability in BracketSpace Advanced Cron Manager allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Advanced Cron Manager \u2013 debug \u0026 control: from n/a through 2.5.9.",
"id": "GHSA-qmjq-qm3j-h6v3",
"modified": "2024-11-01T15:31:59Z",
"published": "2024-11-01T15:31:59Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43154"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/vulnerability/advanced-cron-manager/wordpress-advanced-cron-manager-debug-control-plugin-2-5-9-broken-access-control-vulnerability?_s_id=cve"
}
],
"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"
}
]
}
GHSA-QMMQ-R82H-32QV
Vulnerability from github – Published: 2026-02-05 15:31 – Updated: 2026-04-08 18:34The Greenshift – animation and page builder blocks plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the greenshift_app_pass_validation() function in all versions up to, and including, 12.5.7. This makes it possible for authenticated attackers, with Subscriber-level access and above, to retrieve global plugin settings including stored AI API keys.
{
"affected": [],
"aliases": [
"CVE-2026-1927"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-02-05T14:16:04Z",
"severity": "MODERATE"
},
"details": "The Greenshift \u2013 animation and page builder blocks plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the greenshift_app_pass_validation() function in all versions up to, and including, 12.5.7. This makes it possible for authenticated attackers, with Subscriber-level access and above, to retrieve global plugin settings including stored AI API keys.",
"id": "GHSA-qmmq-r82h-32qv",
"modified": "2026-04-08T18:34:02Z",
"published": "2026-02-05T15:31:14Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-1927"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/3441535/greenshift-animation-and-page-builder-blocks/trunk/init.php"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/3441609/greenshift-animation-and-page-builder-blocks"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/6e2128db-ca9f-4211-8bc5-01a2cc1cba64?source=cve"
}
],
"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"
}
]
}
GHSA-QMP5-2J86-R93W
Vulnerability from github – Published: 2025-03-05 12:31 – Updated: 2025-03-05 12:31The Hero Mega Menu - Responsive WordPress Menu Plugin plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the hmenu_delete_menu() function in all versions up to, and including, 1.16.5. This makes it possible for unauthenticated attackers to delete arbitrary directories on the server.
{
"affected": [],
"aliases": [
"CVE-2024-13780"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-03-05T10:15:16Z",
"severity": "MODERATE"
},
"details": "The Hero Mega Menu - Responsive WordPress Menu Plugin plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the hmenu_delete_menu() function in all versions up to, and including, 1.16.5. This makes it possible for unauthenticated attackers to delete arbitrary directories on the server.",
"id": "GHSA-qmp5-2j86-r93w",
"modified": "2025-03-05T12:31:10Z",
"published": "2025-03-05T12:31:10Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-13780"
},
{
"type": "WEB",
"url": "https://codecanyon.net/item/hero-menu-responsive-wordpress-mega-menu-plugin/10324895"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/17872fe4-b566-44ca-8218-3677fb75cb1c?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:N/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-QMPJ-CVWJ-R2M8
Vulnerability from github – Published: 2026-02-19 18:31 – Updated: 2026-02-19 21:30Missing Authorization vulnerability in sparklewpthemes Fitness FSE fitness-fse allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Fitness FSE: from n/a through <= 1.0.6.
{
"affected": [],
"aliases": [
"CVE-2026-25394"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-02-19T09:16:21Z",
"severity": "MODERATE"
},
"details": "Missing Authorization vulnerability in sparklewpthemes Fitness FSE fitness-fse allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Fitness FSE: from n/a through \u003c= 1.0.6.",
"id": "GHSA-qmpj-cvwj-r2m8",
"modified": "2026-02-19T21:30:45Z",
"published": "2026-02-19T18:31:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-25394"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/Wordpress/Theme/fitness-fse/vulnerability/wordpress-fitness-fse-theme-1-0-6-broken-access-control-vulnerability?_s_id=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-QMQJ-CP2V-2Q9P
Vulnerability from github – Published: 2025-03-14 06:30 – Updated: 2025-03-14 06:30The Search & Filter Pro plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'get_meta_values' function in all versions up to, and including, 2.5.19. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read the values of arbitrary post meta.
{
"affected": [],
"aliases": [
"CVE-2025-1528"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-03-14T05:15:42Z",
"severity": "MODERATE"
},
"details": "The Search \u0026 Filter Pro plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the \u0027get_meta_values\u0027 function in all versions up to, and including, 2.5.19. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read the values of arbitrary post meta.",
"id": "GHSA-qmqj-cp2v-2q9p",
"modified": "2025-03-14T06:30:42Z",
"published": "2025-03-14T06:30:42Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-1528"
},
{
"type": "WEB",
"url": "https://searchandfilter.com/search-filter-2-5-20-security-release"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/47adb5fe-534f-48a9-81a3-883e1d2cda7f?source=cve"
}
],
"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"
}
]
}
GHSA-QMQW-R4X6-3W2Q
Vulnerability from github – Published: 2023-05-09 06:30 – Updated: 2023-05-12 15:24A missing authorization in GitHub repository answerdev/answer prior to 1.0.9 can lead to a user rating their own answer as the best answer.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/answerdev/answer"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.0.9"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2023-2590"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": true,
"github_reviewed_at": "2023-05-11T20:36:13Z",
"nvd_published_at": "2023-05-09T06:15:08Z",
"severity": "LOW"
},
"details": "A missing authorization in GitHub repository answerdev/answer prior to 1.0.9 can lead to a user rating their own answer as the best answer.",
"id": "GHSA-qmqw-r4x6-3w2q",
"modified": "2023-05-12T15:24:21Z",
"published": "2023-05-09T06:30:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-2590"
},
{
"type": "WEB",
"url": "https://github.com/answerdev/answer/commit/51ac1e6b76ae9ab3ca2008ca4819c0cc3bd2fcd3"
},
{
"type": "PACKAGE",
"url": "https://github.com/answerdev/answer"
},
{
"type": "WEB",
"url": "https://huntr.dev/bounties/a4238a30-3ddb-4415-9055-e179c3d4dea7"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "Answer Missing Authorization vulnerability"
}
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.
CAPEC-665: Exploitation of Thunderbolt Protection Flaws
An adversary leverages a firmware weakness within the Thunderbolt protocol, on a computing device to manipulate Thunderbolt controller firmware in order to exploit vulnerabilities in the implementation of authorization and verification schemes within Thunderbolt protection mechanisms. Upon gaining physical access to a target device, the adversary conducts high-level firmware manipulation of the victim Thunderbolt controller SPI (Serial Peripheral Interface) flash, through the use of a SPI Programing device and an external Thunderbolt device, typically as the target device is booting up. If successful, this allows the adversary to modify memory, subvert authentication mechanisms, spoof identities and content, and extract data and memory from the target device. Currently 7 major vulnerabilities exist within Thunderbolt protocol with 9 attack vectors as noted in the Execution Flow.