Vulnerability from drupal
Published
2019-12-11 18:32
Modified
2023-08-11 18:16
Summary
Details
This module extends access handling of Drupal Core's Taxonomy module.
The module doesn't sufficiently check,
- if a given entity should be access controlled, defaulting to allowing access even to unpublished Taxonomy Terms.
- if certain administrative routes should be access controlled, defaulting to allowing access even to users without permission to access these administrative routes.
The vulnerability is mitigated by the facts, that
- the user interface to change the status of Taxonomy Terms has been released in Drupal Core 8.8 and a custom or contributed module is required in earlier versions of Drupal Core to mark Taxonomy Terms as unpublished.
- all entity operations (except the view operation) available on affected administrative routes still require appropriate permissions.
- an attacker must have a role with permission to either access content or view a Taxonomy Term in a vocabulary.
Credits
guedressel
www.drupal.org/user/266710
{
"affected": [
{
"database_specific": {
"affected_versions": "\u003c2.7.0"
},
"package": {
"ecosystem": "Packagist:https://packages.drupal.org/8",
"name": "drupal/taxonomy_access_fix"
},
"ranges": [
{
"database_specific": {
"constraint": "\u003c2.7.0"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "2.7.0"
}
],
"type": "ECOSYSTEM"
}
],
"severity": []
}
],
"aliases": [],
"credits": [
{
"contact": [
"https://www.drupal.org/user/266710"
],
"name": "guedressel"
}
],
"details": "This module extends access handling of Drupal Core\u0027s Taxonomy module.\n\nThe module doesn\u0027t sufficiently check,\n\n* if a given entity should be access controlled, defaulting to allowing access even to unpublished Taxonomy Terms.\n* if certain administrative routes should be access controlled, defaulting to allowing access even to users without permission to access these administrative routes.\n\nThe vulnerability is mitigated by the facts, that\n\n* the user interface to change the status of Taxonomy Terms has been released in Drupal Core 8.8 and a custom or contributed module is required in earlier versions of Drupal Core to mark Taxonomy Terms as unpublished.\n* all entity operations (except the view operation) available on affected administrative routes still require appropriate permissions.\n* an attacker must have a role with permission to either access content or view a Taxonomy Term in a vocabulary.",
"id": "DRUPAL-CONTRIB-2019-093",
"modified": "2023-08-11T18:16:07.000Z",
"published": "2019-12-11T18:32:17.000Z",
"references": [
{
"type": "WEB",
"url": "https://www.drupal.org/sa-contrib-2019-093"
}
],
"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…