Common Weakness Enumeration

CWE-862

Allowed-with-Review

Missing 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.

20277 vulnerabilities reference this CWE, most recent first.

GHSA-WQ67-359W-GV3W

Vulnerability from github – Published: 2025-09-22 21:30 – Updated: 2026-04-01 18:36
VLAI
Details

Missing Authorization vulnerability in MantraBrain Ultimate Watermark allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Ultimate Watermark: from n/a through 1.1.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2025-57985"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-09-22T19:15:58Z",
    "severity": "MODERATE"
  },
  "details": "Missing Authorization vulnerability in MantraBrain Ultimate Watermark allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Ultimate Watermark: from n/a through 1.1.",
  "id": "GHSA-wq67-359w-gv3w",
  "modified": "2026-04-01T18:36:12Z",
  "published": "2025-09-22T21:30:24Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-57985"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/wordpress/plugin/ultimate-watermark/vulnerability/wordpress-ultimate-watermark-plugin-1-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:N/I:L/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-WQ68-P5V9-GCVX

Vulnerability from github – Published: 2026-11-10 21:32 – Updated: 2026-11-10 21:32
VLAI
Details

Missing authorization in Microsoft Office SharePoint allows an authorized attacker to elevate privileges over a network.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-109495"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-11-10T19:18:18Z",
    "severity": "MODERATE"
  },
  "details": "Missing authorization in Microsoft Office SharePoint allows an authorized attacker to elevate privileges over a network.",
  "id": "GHSA-wq68-p5v9-gcvx",
  "modified": "2026-11-10T21:32:30Z",
  "published": "2026-11-10T21:32:30Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-109495"
    },
    {
      "type": "WEB",
      "url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-109495"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-WQ6V-6PCM-FP8R

Vulnerability from github – Published: 2025-12-31 21:30 – Updated: 2026-04-01 18:36
VLAI
Details

Missing Authorization vulnerability in merkulove Logger for Elementor allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Logger for Elementor: from n/a through 1.0.9.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2025-66146"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-12-31T20:15:43Z",
    "severity": "MODERATE"
  },
  "details": "Missing Authorization vulnerability in merkulove Logger for Elementor allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Logger for Elementor: from n/a through 1.0.9.",
  "id": "GHSA-wq6v-6pcm-fp8r",
  "modified": "2026-04-01T18:36:31Z",
  "published": "2025-12-31T21:30:59Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-66146"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/wordpress/plugin/logger-elementor/vulnerability/wordpress-logger-for-elementor-plugin-1-0-9-broken-access-control-vulnerability?_s_id=cve"
    },
    {
      "type": "WEB",
      "url": "https://vdp.patchstack.com/database/wordpress/plugin/logger-elementor/vulnerability/wordpress-logger-for-elementor-plugin-1-0-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:N/I:L/A:L",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-WQ78-VXP9-QCFF

Vulnerability from github – Published: 2026-06-02 15:32 – Updated: 2026-06-02 15:32
VLAI
Details

Missing Authorization vulnerability in Sekander Badsha Crew HRM allows Exploiting Incorrectly Configured Access Control Security Levels.

This issue affects Crew HRM: from n/a through 1.2.2.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-27351"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-06-02T14:16:50Z",
    "severity": "MODERATE"
  },
  "details": "Missing Authorization vulnerability in Sekander Badsha Crew HRM allows Exploiting Incorrectly Configured Access Control Security Levels.\n\nThis issue affects Crew HRM: from n/a through 1.2.2.",
  "id": "GHSA-wq78-vxp9-qcff",
  "modified": "2026-06-02T15:32:12Z",
  "published": "2026-06-02T15:32:12Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27351"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/wordpress/plugin/hr-management/vulnerability/wordpress-crew-hrm-plugin-1-2-2-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:L",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-WQ7X-7X4J-792V

Vulnerability from github – Published: 2026-08-26 00:31 – Updated: 2026-08-26 21:31
VLAI
Details

Missing Authorization vulnerability in Drupal PhotoSwipe - Responsive JavaScript Modal Image Gallery allows Forceful Browsing. This issue affects PhotoSwipe - Responsive JavaScript Modal Image Gallery versions: from 0.0.0 to 3.2.0.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-16645"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-25T23:16:57Z",
    "severity": "CRITICAL"
  },
  "details": "Missing Authorization vulnerability in Drupal PhotoSwipe - Responsive JavaScript Modal Image Gallery allows Forceful Browsing. This issue affects PhotoSwipe - Responsive JavaScript Modal Image Gallery versions: from 0.0.0 to 3.2.0.",
  "id": "GHSA-wq7x-7x4j-792v",
  "modified": "2026-08-26T21:31:40Z",
  "published": "2026-08-26T00:31:02Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-16645"
    },
    {
      "type": "WEB",
      "url": "https://www.drupal.org/sa-contrib-2026-088"
    }
  ],
  "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-WQ8G-F6R3-3M8C

Vulnerability from github – Published: 2023-02-08 03:30 – Updated: 2026-04-08 21:31
VLAI
Details

The Wicked Folders plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the ajax_clone_folder function in versions up to, and including, 2.18.16. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to invoke this function and perform actions intended for administrators such as modifying the folder structure maintained by the plugin.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2023-0715"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2023-02-08T02:15:00Z",
    "severity": "MODERATE"
  },
  "details": "The Wicked Folders plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the ajax_clone_folder function in versions up to, and including, 2.18.16. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to invoke this function and perform actions intended for administrators such as modifying the folder structure maintained by the plugin.",
  "id": "GHSA-wq8g-f6r3-3m8c",
  "modified": "2026-04-08T21:31:48Z",
  "published": "2023-02-08T03:30:25Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-0715"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/wicked-folders/tags/2.18.16/lib/class-wicked-folders-ajax.php"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/changeset?sfp_email=\u0026sfph_mail=\u0026reponame=\u0026new=2860994%40wicked-folders%2Ftrunk\u0026old=2805161%40wicked-folders%2Ftrunk\u0026sfp_email=\u0026sfph_mail="
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/c3728280-3487-4cb2-8e37-f33811bc0a22"
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/c3728280-3487-4cb2-8e37-f33811bc0a22?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-WQ8H-VPFM-4FRM

Vulnerability from github – Published: 2025-11-06 18:32 – Updated: 2026-01-20 15:31
VLAI
Details

Missing Authorization vulnerability in ThemeNectar Salient salient.This issue affects Salient: from n/a through < 17.4.0.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2025-62028"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-11-06T16:16:08Z",
    "severity": "MODERATE"
  },
  "details": "Missing Authorization vulnerability in ThemeNectar Salient salient.This issue affects Salient: from n/a through \u003c 17.4.0.",
  "id": "GHSA-wq8h-vpfm-4frm",
  "modified": "2026-01-20T15:31:52Z",
  "published": "2025-11-06T18:32:56Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-62028"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/Wordpress/Theme/salient/vulnerability/wordpress-salient-theme-17-4-0-broken-access-control-vulnerability?_s_id=cve"
    },
    {
      "type": "WEB",
      "url": "https://vdp.patchstack.com/database/Wordpress/Theme/salient/vulnerability/wordpress-salient-theme-17-4-0-broken-access-control-vulnerability"
    },
    {
      "type": "WEB",
      "url": "https://vdp.patchstack.com/database/Wordpress/Theme/salient/vulnerability/wordpress-salient-theme-17-4-0-broken-access-control-vulnerability?_s_id=cve"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-WQ9H-H745-R69V

Vulnerability from github – Published: 2024-11-16 06:30 – Updated: 2024-11-16 06:30
VLAI
Details

The WP Log Viewer plugin for WordPress is vulnerable to unauthorized use of functionality due to a missing capability check on several AJAX actions in all versions up to, and including, 1.2.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to access logs, update plugin-related user settings and general plugin settings.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2024-11085"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-11-16T04:15:05Z",
    "severity": "MODERATE"
  },
  "details": "The WP Log Viewer plugin for WordPress is vulnerable to unauthorized use of functionality due to a missing capability check on several AJAX actions in all versions up to, and including, 1.2.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to access logs, update plugin-related user settings and general plugin settings.",
  "id": "GHSA-wq9h-h745-r69v",
  "modified": "2024-11-16T06:30:40Z",
  "published": "2024-11-16T06:30:40Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-11085"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/wp-log-viewer/trunk/libs/Ajax.php"
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/e27bd526-1a5f-4628-8bb2-1741496f897f?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:L/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-WQC4-CWR9-MWW9

Vulnerability from github – Published: 2025-08-28 06:30 – Updated: 2025-08-28 06:30
VLAI
Details

Multiple plugins and/or themes for WordPress by LiquidThemes are vulnerable to unauthorized access due to a missing capability check on the liquid_reset_wordpress_before AJAX in various versions. This makes it possible for authenticated attackers, with Subscriber-level access and above, to deactivate all of a site's plugins. While we escalated this to Envato after not being able to establish contact, it appears the developer added a nonce check, however that is not sufficient protection as the nonce is exposed to all users with access to the dashboard.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2025-0951"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-08-28T04:15:56Z",
    "severity": "MODERATE"
  },
  "details": "Multiple plugins and/or themes for WordPress by LiquidThemes are vulnerable to unauthorized access due to a missing capability check on the liquid_reset_wordpress_before AJAX in various versions. This makes it possible for authenticated attackers, with Subscriber-level access and above, to deactivate all of a site\u0027s plugins. While we escalated this to Envato after not being able to establish contact, it appears the developer added a nonce check, however that is not sufficient protection as the nonce is exposed to all users with access to the dashboard.",
  "id": "GHSA-wqc4-cwr9-mww9",
  "modified": "2025-08-28T06:30:57Z",
  "published": "2025-08-28T06:30:57Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-0951"
    },
    {
      "type": "WEB",
      "url": "https://themeforest.net/user/liquidthemes"
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/0099c700-e1af-4d97-a518-151a9139ea35?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-WQCW-G35J-J578

Vulnerability from github – Published: 2026-05-05 21:49 – Updated: 2026-05-13 16:27
VLAI
Summary
Kubewarden vulnerable to RBAC Reconnaissance via unchecked can_i host capability call
Details

Impact

Kubewarden is a policy engine for Kubernetes. Kubewarden cluster operators can grant permissions to users to deploy namespaced AdmissionPolicies and AdmissionPolicyGroups in their Namespaces. One of Kubewarden promises is that configured users can deploy namespaced policies in a safe manner, without privilege escalation.

An attacker with privileged AdmissionPolicy or AdmissionPolicyGroup create permissions (which isn't the default) can craft a policy that makes use of the can_i host callback. The callback issues a SubjectAccessReview (SAR) requests to enumerate RBAC permissions of any user or service account across the cluster. Three operations on the host capabilities kubewarden/kubernetes binding enforce the context-aware allow-list via can_access_kubernetes_resource():

  • list_resources_by_namespace
  • list_resources_all
  • get_resource

However, can_i does not perform that check and forwards the request directly to the callback handler, which executes a real SubjectAccessReview using policy-server privileges. This creates a policy-level authorization gap: can_i is effectively usable even when the policy has no context-aware resource grant.

This is an information disclosure / reconnaissance issue, and not direct workload data exfiltration. The attacker learns permission information, such as whether specific service accounts can "get secrets", "create pods", or "bind clusterroles" in chosen namespaces.

Patches

Cluster Operators, if providing their users with privileges to deploy AdmissionPolicies or AdmissionPolicygroups (which isn't the default), must then also deploy PolicyServers with reduced permissions for host capability calls. This includes the PolicyServer default. For that, make use of the new feature in v1.35: - For custom PolicyServers: Set the new PolicyServer.spec.namespacedPoliciesCapabilities , for example to an empty list [] which doesn't allow any capability. - For the default PolicyServer, set the .Values.policyServer.namespacedPoliciesCapabilities , for example to an empty list [] which doesn't allow any capability.

Also, if needed, they must ensure that those namespaced AdmissionPolicies or AdmissionPolicygroups are scheduled in the PolicyServers with reduced permissions. For that, they could make use of the new ns-policyserver-mapper policy, their own policy or other means, such as GitOps.

See: https://docs.kubewarden.io/howtos/policy-servers/namespaced-policies-capabilities

Workarounds

Cluster Operators can opt for: - Not allowing users to create namespaced policies (AdmissionPolicies, AdmissionPolicyGroups). - Removing SubjectAccessReview "create" permissions for the PolicyServer ServiceAccount RBAC being used, in custom PolicyServers and the PolicyServer default.

Resources

  • Code changes, with new security feature: https://github.com/kubewarden/kubewarden-controller/pull/1693
  • Documentation changes: https://github.com/kubewarden/docs/pull/737
  • Explained new feature on 1.35.0
  • Updated Threat model assessment
Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/kubewarden/kubewarden-controller"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.35.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-42541"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-05-05T21:49:03Z",
    "nvd_published_at": "2026-05-12T18:17:24Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\nKubewarden is a policy engine for Kubernetes. Kubewarden cluster operators can grant permissions to users to deploy namespaced AdmissionPolicies and AdmissionPolicyGroups in their Namespaces. One of Kubewarden promises is that configured users can deploy namespaced policies in a safe manner, without privilege escalation.\n\nAn attacker with privileged AdmissionPolicy or AdmissionPolicyGroup create permissions (which isn\u0027t the default) can craft a policy that makes use of the `can_i` host callback. The callback issues a SubjectAccessReview (SAR) requests to enumerate RBAC permissions of any user or service account across the cluster. Three operations on the host capabilities `kubewarden/kubernetes` binding enforce the context-aware allow-list via `can_access_kubernetes_resource()`:\n\n- `list_resources_by_namespace`\n- `list_resources_all`\n- `get_resource`\n\nHowever, `can_i` does not perform that check and forwards the request directly to the callback handler, which executes a real SubjectAccessReview using policy-server privileges. This creates a policy-level authorization gap: `can_i` is effectively usable even when the policy has no context-aware resource grant.\n\nThis is an information disclosure / reconnaissance issue, and not direct workload data exfiltration. The attacker learns permission information, such as whether specific service accounts can \"get secrets\", \"create pods\", or \"bind clusterroles\" in chosen namespaces.\n\n### Patches\n\nCluster Operators, if providing their users with privileges to deploy AdmissionPolicies or AdmissionPolicygroups (which isn\u0027t the default), must then also deploy PolicyServers with reduced permissions for host capability calls. This includes the PolicyServer `default`. \nFor that, make use of the new feature in v1.35:\n- For custom PolicyServers: Set the new `PolicyServer.spec.namespacedPoliciesCapabilities` , for example to an empty list `[]` which doesn\u0027t allow any capability.\n- For the `default` PolicyServer, set the `.Values.policyServer.namespacedPoliciesCapabilities` , for example to an empty list `[]` which doesn\u0027t allow any capability. \n\nAlso, if needed, they must ensure that those namespaced AdmissionPolicies or AdmissionPolicygroups are scheduled in the PolicyServers with reduced permissions.\nFor that, they could make use of the new [ns-policyserver-mapper](https://artifacthub.io/packages/kubewarden/kubewarden-policy-library/ns-policyserver-mapper) policy, their own policy or other means, such as GitOps.\n\nSee: https://docs.kubewarden.io/howtos/policy-servers/namespaced-policies-capabilities\n\n### Workarounds\n\nCluster Operators can opt for:\n- Not allowing users to create namespaced policies (AdmissionPolicies, AdmissionPolicyGroups).\n- Removing SubjectAccessReview \"create\" permissions for the PolicyServer ServiceAccount RBAC being used, in custom PolicyServers and the  PolicyServer `default`.\n\n### Resources\n\n- Code changes, with new security feature: https://github.com/kubewarden/kubewarden-controller/pull/1693\n- Documentation changes: https://github.com/kubewarden/docs/pull/737\n  - Explained new feature on 1.35.0\n  - Updated Threat model assessment",
  "id": "GHSA-wqcw-g35j-j578",
  "modified": "2026-05-13T16:27:04Z",
  "published": "2026-05-05T21:49:03Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/kubewarden/adm-controller/security/advisories/GHSA-wqcw-g35j-j578"
    },
    {
      "type": "WEB",
      "url": "https://github.com/kubewarden/kubewarden-controller/security/advisories/GHSA-wqcw-g35j-j578"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42541"
    },
    {
      "type": "WEB",
      "url": "https://github.com/kubewarden/docs/pull/737"
    },
    {
      "type": "WEB",
      "url": "https://github.com/kubewarden/kubewarden-controller/pull/1693"
    },
    {
      "type": "WEB",
      "url": "https://docs.kubewarden.io/howtos/policy-servers/namespaced-policies-capabilities"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/kubewarden/kubewarden-controller"
    }
  ],
  "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": "Kubewarden vulnerable to RBAC Reconnaissance via unchecked can_i host capability call"
}

Mitigation
Architecture and Design
  • 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
Architecture and Design

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
Architecture and Design

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
Architecture and Design
  • 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
System Configuration Installation

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.