Vulnerability from drupal
Published
2021-09-22 16:43
Modified
2023-08-11 17:03
Summary
Details
This module enables you to create an individual hash for each user. These hashes can be used for authentication instead of the user's password, e.g. for views exporters.
The module doesn't sufficiently invalidate page output when the page_cache module is used.
This vulnerability is mitigated by the fact that an attacker must have a user hash that grants access to specific content and the attack must be timed to the reset of the page cache.
Credits
Jürgen Haas
www.drupal.org/user/168924
Lee Rowlands
www.drupal.org/user/395439
{
"affected": [
{
"database_specific": {
"affected_versions": "\u003c2.0.1"
},
"package": {
"ecosystem": "Packagist:https://packages.drupal.org/8",
"name": "drupal/user_hash"
},
"ranges": [
{
"database_specific": {
"constraint": "\u003c2.0.1"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "2.0.1"
}
],
"type": "ECOSYSTEM"
}
],
"severity": []
}
],
"aliases": [],
"credits": [
{
"contact": [
"https://www.drupal.org/user/168924"
],
"name": "J\u00fcrgen Haas"
},
{
"contact": [
"https://www.drupal.org/user/395439"
],
"name": "Lee Rowlands"
}
],
"details": "This module enables you to create an individual hash for each user. These hashes can be used for authentication instead of the user\u0027s password, e.g. for views exporters.\n\nThe module doesn\u0027t sufficiently invalidate page output when the page\\_cache module is used.\n\nThis vulnerability is mitigated by the fact that an attacker must have a user hash that grants access to specific content and the attack must be timed to the reset of the page cache.",
"id": "DRUPAL-CONTRIB-2021-030",
"modified": "2023-08-11T17:03:36.000Z",
"published": "2021-09-22T16:43:17.000Z",
"references": [
{
"type": "WEB",
"url": "https://www.drupal.org/sa-contrib-2021-030"
}
],
"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…