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.
20387 vulnerabilities reference this CWE, most recent first.
GHSA-QW47-MCM5-934W
Vulnerability from github – Published: 2026-10-20 21:05 – Updated: 2026-10-20 21:05Draft text for GHSA-qw47-mcm5-934w. The body below drops into the GitHub advisory description field; the metadata block maps to the form fields. Set the patched version at release; publish when the fix ships._
- Ecosystem: Maven
- Affected package:
org.a2aproject.sdk:a2a-java-sdk-server-common(task store / authorization) - Affected versions:
<= 1.2.0.Final(and1.2.1.Final-SNAPSHOTonmainprior to the fix) - Patched version: (the release that carries the fix, e.g. 1.2.1.Final)
- CWE: CWE-1188 (Insecure Default Initialization), CWE-862 (Missing Authorization)
- Severity: High
- CVSS v3.1:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N(7.5, High)
Details
The default task store performs no authorization on task reads. InMemoryTaskStore's no-arg
constructor sets authorizationProvider = null, and InMemoryTaskStore.get(String taskId) is a
bare map lookup with no authorization check regardless of provider:
public InMemoryTaskStore() {
this.authorizationProvider = null; // default wiring
}
@Override
public @Nullable Task get(String taskId) {
return tasks.get(taskId); // no owner / caller check
}
Authorization is enforced only when the application both supplies a TaskAuthorizationProvider
and routes requests through AuthorizationRequestHandlerDecorator (via CDI), which checks
ownership before delegating. A server that uses the default store, or wires
DefaultRequestHandler.builder().build() manually, or integrates through a non-CDI stack (e.g.
Spring), never reaches that check. The safe posture is therefore opt-in and the shipped default is
the unsafe one. A caller can read a task created by another caller simply by knowing or guessing
its id.
Summary
With the SDK's default configuration, task reads are not authorized: any caller can retrieve a task (including its status, context, message history, and artifacts) created by another caller, by supplying the task id.
PoC
Using only the real production classes wired the default way (no mocks):
- Construct the default store:
InMemoryTaskStore store = new InMemoryTaskStore();(no-arg constructor, so no authorization provider). - As one caller, save a task:
store.save(victimTask, false);with idvictim-task-42. - As a second, unrelated caller with no auth context, read it back:
store.get("victim-task-42").
The second caller receives the first caller's task in full, with no authorization check:
unauthenticated get(victim-task-42) returned task owned by nobody-checked: victim-task-42 / ctx=victim-ctx
Verified on main (commit 72d220c, JDK 21) and reproduces unchanged on 1.2.0.Final.
Impact
Task data crosses caller boundaries with no authorization. In any multi-caller deployment built on
the default wiring, one caller can enumerate and read another caller's tasks, including task status,
context id, the message history, and any artifacts the task carries, which for agent workloads is
frequently sensitive input and generated content. Because the insecure behaviour is the default
rather than a misconfiguration, it is easy to ship unintentionally, and in the default/reference
deployment the transport endpoints are served without authentication enforced, so the read is
reachable by an unauthenticated caller (PR:N). CVSS is scored against the default configuration
as shipped.
Remediation
Fail closed by default: deny task reads when no authorization provider is configured, rather than
treating a missing provider as allow-all, and apply the authorization check in the store's get
path (not only in list and the CDI decorator) so it holds regardless of how the handler is
wired. If the current permissive default is retained for single-user/testing scenarios, emit a
prominent startup warning when the server comes up with no authorization provider so it cannot be
shipped by accident.
Workarounds
Until a fixed release, configure a TaskAuthorizationProvider and ensure requests are routed
through the authorization decorator (CDI wiring), rather than relying on the default no-arg store
or a manually built handler.
References
- CWE-1188: Insecure Default Initialization of Resource: https://cwe.mitre.org/data/definitions/1188.html
- CWE-862: Missing Authorization: https://cwe.mitre.org/data/definitions/862.html
{
"affected": [
{
"package": {
"ecosystem": "Maven",
"name": "org.a2aproject.sdk:a2a-java-sdk-server-common"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.3.0.Final"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-111764"
],
"database_specific": {
"cwe_ids": [
"CWE-1188",
"CWE-862"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-20T21:05:09Z",
"nvd_published_at": "2026-10-20T16:17:00Z",
"severity": "HIGH"
},
"details": "Draft text for GHSA-qw47-mcm5-934w. The body below drops into the GitHub advisory description\nfield; the metadata block maps to the form fields. Set the patched version at release; publish\nwhen the fix ships._\n\n---\n\n- **Ecosystem:** Maven\n- **Affected package:** `org.a2aproject.sdk:a2a-java-sdk-server-common` (task store / authorization)\n- **Affected versions:** `\u003c= 1.2.0.Final` (and `1.2.1.Final-SNAPSHOT` on `main` prior to the fix)\n- **Patched version:** _(the release that carries the fix, e.g. 1.2.1.Final)_\n- **CWE:** CWE-1188 (Insecure Default Initialization), CWE-862 (Missing Authorization)\n- **Severity:** High\n- **CVSS v3.1:** `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N` (7.5, High)\n\n---\n\n## Details\n\nThe default task store performs no authorization on task reads. `InMemoryTaskStore`\u0027s no-arg\nconstructor sets `authorizationProvider = null`, and `InMemoryTaskStore.get(String taskId)` is a\nbare map lookup with no authorization check regardless of provider:\n\n```java\npublic InMemoryTaskStore() {\n this.authorizationProvider = null; // default wiring\n}\n\n@Override\npublic @Nullable Task get(String taskId) {\n return tasks.get(taskId); // no owner / caller check\n}\n```\n\nAuthorization is enforced only when the application both supplies a `TaskAuthorizationProvider`\n*and* routes requests through `AuthorizationRequestHandlerDecorator` (via CDI), which checks\nownership before delegating. A server that uses the default store, or wires\n`DefaultRequestHandler.builder().build()` manually, or integrates through a non-CDI stack (e.g.\nSpring), never reaches that check. The safe posture is therefore opt-in and the shipped default is\nthe unsafe one. A caller can read a task created by another caller simply by knowing or guessing\nits id.\n\n## Summary\n\nWith the SDK\u0027s default configuration, task reads are not authorized: any caller can retrieve a\ntask (including its status, context, message history, and artifacts) created by another caller,\nby supplying the task id.\n\n## PoC\n\nUsing only the real production classes wired the default way (no mocks):\n\n1. Construct the default store: `InMemoryTaskStore store = new InMemoryTaskStore();` (no-arg\n constructor, so no authorization provider).\n2. As one caller, save a task: `store.save(victimTask, false);` with id `victim-task-42`.\n3. As a second, unrelated caller with no auth context, read it back: `store.get(\"victim-task-42\")`.\n\nThe second caller receives the first caller\u0027s task in full, with no authorization check:\n\n```\nunauthenticated get(victim-task-42) returned task owned by nobody-checked: victim-task-42 / ctx=victim-ctx\n```\n\nVerified on `main` (commit `72d220c`, JDK 21) and reproduces unchanged on `1.2.0.Final`.\n\n## Impact\n\nTask data crosses caller boundaries with no authorization. In any multi-caller deployment built on\nthe default wiring, one caller can enumerate and read another caller\u0027s tasks, including task status,\ncontext id, the message history, and any artifacts the task carries, which for agent workloads is\nfrequently sensitive input and generated content. Because the insecure behaviour is the default\nrather than a misconfiguration, it is easy to ship unintentionally, and in the default/reference\ndeployment the transport endpoints are served without authentication enforced, so the read is\nreachable by an unauthenticated caller (`PR:N`). CVSS is scored against the default configuration\nas shipped.\n\n## Remediation\n\nFail closed by default: deny task reads when no authorization provider is configured, rather than\ntreating a missing provider as allow-all, and apply the authorization check in the store\u0027s `get`\npath (not only in `list` and the CDI decorator) so it holds regardless of how the handler is\nwired. If the current permissive default is retained for single-user/testing scenarios, emit a\nprominent startup warning when the server comes up with no authorization provider so it cannot be\nshipped by accident.\n\n## Workarounds\n\nUntil a fixed release, configure a `TaskAuthorizationProvider` and ensure requests are routed\nthrough the authorization decorator (CDI wiring), rather than relying on the default no-arg store\nor a manually built handler.\n\n## References\n\n- CWE-1188: Insecure Default Initialization of Resource: https://cwe.mitre.org/data/definitions/1188.html\n- CWE-862: Missing Authorization: https://cwe.mitre.org/data/definitions/862.html",
"id": "GHSA-qw47-mcm5-934w",
"modified": "2026-10-20T21:05:09Z",
"published": "2026-10-20T21:05:09Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/a2aproject/a2a-java/security/advisories/GHSA-qw47-mcm5-934w"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-111764"
},
{
"type": "WEB",
"url": "https://github.com/a2aproject/a2a-java/pull/1095"
},
{
"type": "WEB",
"url": "https://github.com/a2aproject/a2a-java/commit/efb4e985e99390c4fc1f78c0a187a4254c0a2553"
},
{
"type": "PACKAGE",
"url": "https://github.com/a2aproject/a2a-java"
},
{
"type": "WEB",
"url": "https://github.com/a2aproject/a2a-java/releases/tag/v1.3.0.Final"
}
],
"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": "A2A Java SDK has a fail-open default task authorization"
}
GHSA-QW4X-6R3W-Q94X
Vulnerability from github – Published: 2026-10-24 06:30 – Updated: 2026-10-24 15:32The News Kit Addons For Elementor WordPress plugin through 1.4.7 does not perform capability or ownership checks before updating post metadata in one of its authenticated AJAX actions, allowing users with subscriber-level access and above to write arbitrary post meta, under attacker-chosen keys, to any post including those owned by other users. This can be used to overwrite protected core metadata and tamper with content created by higher-privileged users.
{
"affected": [],
"aliases": [
"CVE-2026-97353"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-24T06:16:37Z",
"severity": "MODERATE"
},
"details": "The News Kit Addons For Elementor WordPress plugin through 1.4.7 does not perform capability or ownership checks before updating post metadata in one of its authenticated AJAX actions, allowing users with subscriber-level access and above to write arbitrary post meta, under attacker-chosen keys, to any post including those owned by other users. This can be used to overwrite protected core metadata and tamper with content created by higher-privileged users.",
"id": "GHSA-qw4x-6r3w-q94x",
"modified": "2026-10-24T15:32:53Z",
"published": "2026-10-24T06:30:29Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-97353"
},
{
"type": "WEB",
"url": "https://wpscan.com/vulnerability/4114e6a4-d8ed-4456-a15f-4d47034ae75f"
}
],
"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:L",
"type": "CVSS_V3"
}
]
}
GHSA-QW52-QMWQ-9MJQ
Vulnerability from github – Published: 2024-02-06 00:30 – Updated: 2025-05-15 21:31The Active Products Tables for WooCommerce. Professional products tables for WooCommerce store plugin for WordPress is vulnerable to unauthorized access of functionality due to a missing capability check on several functions in all versions up to, and including, 1.0.6.1. This makes it possible for subscribers and higher to execute functions intended for admin use.
{
"affected": [],
"aliases": [
"CVE-2024-0797"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-02-05T22:16:05Z",
"severity": "MODERATE"
},
"details": "The Active Products Tables for WooCommerce. Professional products tables for WooCommerce store plugin for WordPress is vulnerable to unauthorized access of functionality due to a missing capability check on several functions in all versions up to, and including, 1.0.6.1. This makes it possible for subscribers and higher to execute functions intended for admin use.",
"id": "GHSA-qw52-qmwq-9mjq",
"modified": "2025-05-15T21:31:18Z",
"published": "2024-02-06T00:30:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-0797"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/3029488/profit-products-tables-for-woocommerce/trunk?contextall=1\u0026old=3005088\u0026old_path=%2Fprofit-products-tables-for-woocommerce%2Ftrunk"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/3029488/profit-products-tables-for-woocommerce/trunk?contextall=1\u0026old=3005088\u0026old_path=/profit-products-tables-for-woocommerce/trunk"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/0a94841f-b1dd-44f4-b7a1-65a9fdf7b18d?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-QW58-MHG6-Q49H
Vulnerability from github – Published: 2026-04-16 12:31 – Updated: 2026-04-16 12:31The OneSignal – Web Push Notifications plugin for WordPress is vulnerable to authorization bypass in versions up to, and including, 3.8.0. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete OneSignal metadata for arbitrary posts.
{
"affected": [],
"aliases": [
"CVE-2026-3155"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-04-16T12:16:07Z",
"severity": "LOW"
},
"details": "The OneSignal \u2013 Web Push Notifications plugin for WordPress is vulnerable to authorization bypass in versions up to, and including, 3.8.0. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete OneSignal metadata for arbitrary posts.",
"id": "GHSA-qw58-mhg6-q49h",
"modified": "2026-04-16T12:31:41Z",
"published": "2026-04-16T12:31:41Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-3155"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/3501190/onesignal-free-web-push-notifications"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/58337bbc-ba10-4876-b91c-78657afc67d1?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-QW5F-5RGP-5CG9
Vulnerability from github – Published: 2026-03-25 18:31 – Updated: 2026-03-27 15:30Missing Authorization vulnerability in Arni Cinco WPCargo Track & Trace wpcargo allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WPCargo Track & Trace: from n/a through <= 8.0.2.
{
"affected": [],
"aliases": [
"CVE-2026-25401"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-03-25T17:16:49Z",
"severity": "HIGH"
},
"details": "Missing Authorization vulnerability in Arni Cinco WPCargo Track \u0026 Trace wpcargo allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WPCargo Track \u0026 Trace: from n/a through \u003c= 8.0.2.",
"id": "GHSA-qw5f-5rgp-5cg9",
"modified": "2026-03-27T15:30:25Z",
"published": "2026-03-25T18:31:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-25401"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/Wordpress/Plugin/wpcargo/vulnerability/wordpress-wpcargo-track-trace-plugin-8-0-2-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:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-QW9P-RFPX-FXH5
Vulnerability from github – Published: 2026-02-18 06:30 – Updated: 2026-02-18 06:30The Order Splitter for WooCommerce plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'wos_troubleshooting' AJAX endpoint in all versions up to, and including, 5.3.5. This makes it possible for authenticated attackers, with Subscriber-level access and above, to view information pertaining to other user's orders.
{
"affected": [],
"aliases": [
"CVE-2025-12075"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-02-18T05:16:17Z",
"severity": "MODERATE"
},
"details": "The Order Splitter for WooCommerce plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the \u0027wos_troubleshooting\u0027 AJAX endpoint in all versions up to, and including, 5.3.5. This makes it possible for authenticated attackers, with Subscriber-level access and above, to view information pertaining to other user\u0027s orders.",
"id": "GHSA-qw9p-rfpx-fxh5",
"modified": "2026-02-18T06:30:19Z",
"published": "2026-02-18T06:30:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-12075"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset?sfp_email=\u0026sfph_mail=\u0026reponame=\u0026old=3387820%40woo-order-splitter\u0026new=3387820%40woo-order-splitter\u0026sfp_email=\u0026sfph_mail="
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/627eb000-086e-408a-8123-063fed6364be?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-QW9X-8R88-2MFQ
Vulnerability from github – Published: 2025-01-21 18:31 – Updated: 2026-04-01 18:33Missing Authorization vulnerability in Farhan Noor ApplyOnline – Application Form Builder and Manager allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects ApplyOnline – Application Form Builder and Manager: from n/a through 2.6.7.1.
{
"affected": [],
"aliases": [
"CVE-2025-22721"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-01-21T18:15:15Z",
"severity": "MODERATE"
},
"details": "Missing Authorization vulnerability in Farhan Noor ApplyOnline \u2013 Application Form Builder and Manager allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects ApplyOnline \u2013 Application Form Builder and Manager: from n/a through 2.6.7.1.",
"id": "GHSA-qw9x-8r88-2mfq",
"modified": "2026-04-01T18:33:18Z",
"published": "2025-01-21T18:31:07Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-22721"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/apply-online/vulnerability/wordpress-applyonline-plugin-2-6-7-1-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-QWFF-3J78-F8JM
Vulnerability from github – Published: 2024-02-16 03:30 – Updated: 2024-11-26 18:38In applyCustomDescription of SaveUi.java, there is a possible way to view images belonging to a different user due to a missing permission check. This could lead to local information disclosure with User execution privileges needed. User interaction is not needed for exploitation.
{
"affected": [],
"aliases": [
"CVE-2024-0037"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-02-16T02:15:51Z",
"severity": "LOW"
},
"details": "In applyCustomDescription of SaveUi.java, there is a possible way to view images belonging to a different user due to a missing permission check. This could lead to local information disclosure with User execution privileges needed. User interaction is not needed for exploitation.",
"id": "GHSA-qwff-3j78-f8jm",
"modified": "2024-11-26T18:38:46Z",
"published": "2024-02-16T03:30:51Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-0037"
},
{
"type": "WEB",
"url": "https://android.googlesource.com/platform/frameworks/base/+/55fc00a0788ea0995fe0851616b9ac21710a2931"
},
{
"type": "WEB",
"url": "https://source.android.com/security/bulletin/2024-02-01"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-QWG6-XHP2-3C8Q
Vulnerability from github – Published: 2025-01-31 09:31 – Updated: 2026-04-01 18:33Missing Authorization vulnerability in mgplugin EMI Calculator allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects EMI Calculator: from n/a through 1.1.
{
"affected": [],
"aliases": [
"CVE-2025-22265"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-01-31T09:15:07Z",
"severity": "MODERATE"
},
"details": "Missing Authorization vulnerability in mgplugin EMI Calculator allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects EMI Calculator: from n/a through 1.1.",
"id": "GHSA-qwg6-xhp2-3c8q",
"modified": "2026-04-01T18:33:30Z",
"published": "2025-01-31T09:31:50Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-22265"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/emi-calculator/vulnerability/wordpress-emi-calculator-plugin-1-1-settings-change-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:L",
"type": "CVSS_V3"
}
]
}
GHSA-QWH2-6H9R-J729
Vulnerability from github – Published: 2022-05-24 16:49 – Updated: 2024-04-04 01:13MailEnable Enterprise Premium 10.23 did not use appropriate access control checks in a number of areas. As a result, it was possible to perform a number of actions, when logged in as a user, that that user should not have had permission to perform. It was also possible to gain access to areas within the application for which the accounts used were supposed to have insufficient access.
{
"affected": [],
"aliases": [
"CVE-2019-12926"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2019-07-08T22:15:00Z",
"severity": "HIGH"
},
"details": "MailEnable Enterprise Premium 10.23 did not use appropriate access control checks in a number of areas. As a result, it was possible to perform a number of actions, when logged in as a user, that that user should not have had permission to perform. It was also possible to gain access to areas within the application for which the accounts used were supposed to have insufficient access.",
"id": "GHSA-qwh2-6h9r-j729",
"modified": "2024-04-04T01:13:14Z",
"published": "2022-05-24T16:49:48Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-12926"
},
{
"type": "WEB",
"url": "https://www.nccgroup.trust/uk/our-research/technical-advisory-multiple-vulnerabilities-in-mailenable"
},
{
"type": "WEB",
"url": "http://www.mailenable.com/Premium-ReleaseNotes.txt"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/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.
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.