Skip to content
Fencer Intel
no cvss —

DRUPAL-CONTRIB-2019-093 json

This module extends access handling of Drupal Core's Taxonomy module.

published 6y ago modified 2mo ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

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.

Patch / fix

  • packagist drupal/taxonomy_access_fix 2.7.0

Is DRUPAL-CONTRIB-2019-093 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
packagist drupal/taxonomy_access_fix
<2.7.0
2.7.0

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.