Vulnerability from drupal
Published
2024-10-09 15:48
Modified
2025-02-20 19:26
Summary
Details
This module enables you to manage blocks from specific modules in the specific themes.
The module doesn't sufficiently check permissions under the scenario when a block is added using the form "/admin/structure/block/add/{plugin_id}/{theme}" (route "block.admin_add"). The attacker can add the block to the theme where they can't manage blocks.
This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer blocks provided by [provider]".
Credits
Francesco Sardara
www.drupal.org/user/2353864
{
"affected": [
{
"database_specific": {
"affected_versions": "\u003e=1.0.0 \u003c1.2.0"
},
"package": {
"ecosystem": "Packagist:https://packages.drupal.org/8",
"name": "drupal/block_permissions"
},
"ranges": [
{
"database_specific": {
"constraint": "\u003e=1.0.0 \u003c1.2.0"
},
"events": [
{
"introduced": "1.0.0"
},
{
"fixed": "1.2.0"
}
],
"type": "ECOSYSTEM"
}
],
"severity": []
}
],
"aliases": [
"CVE-2024-13282"
],
"credits": [
{
"contact": [
"https://www.drupal.org/user/2353864"
],
"name": "Francesco Sardara"
}
],
"details": "This module enables you to manage blocks from specific modules in the specific themes.\n\nThe module doesn\u0027t sufficiently check permissions under the scenario when a block is added using the form \"/admin/structure/block/add/{plugin\\_id}/{theme}\" (route \"block.admin\\_add\"). The attacker can add the block to the theme where they can\u0027t manage blocks.\n\nThis vulnerability is mitigated by the fact that an attacker must have a role with the permission \"administer blocks provided by [provider]\".",
"id": "DRUPAL-CONTRIB-2024-046",
"modified": "2025-02-20T19:26:30.000Z",
"published": "2024-10-09T15:48:11.000Z",
"references": [
{
"type": "WEB",
"url": "https://www.drupal.org/sa-contrib-2024-046"
}
],
"schema_version": "1.7.0"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…