# DRUPAL-CONTRIB-2021-030: This module enables you to create an individual hash for each user.

> An attacker with a valid user hash can access cached content intended for other users if the page cache is not properly invalidated.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Sep 2021

## What is DRUPAL-CONTRIB-2021-030?

DRUPAL-CONTRIB-2021-030 is a vulnerability in drupal/user_hash, published on 22 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

## Which versions are affected by DRUPAL-CONTRIB-2021-030?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/user_hash` | Packagist:https://packages.drupal.org/8 | All versions | 2.0.1 |

## How do I fix DRUPAL-CONTRIB-2021-030?

Apply the vendor's patch.

## Is DRUPAL-CONTRIB-2021-030 being exploited?

There is no known exploitation of DRUPAL-CONTRIB-2021-030 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for DRUPAL-CONTRIB-2021-030 and fix it if it is affected.

What it is: DRUPAL-CONTRIB-2021-030 is a vulnerability in drupal/user_hash, published on 22 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2021-030 in the wild and no public exploit code.

Affected product: drupal/user_hash. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/DRUPAL-CONTRIB-2021-030/ (Markdown: https://insights.sbomify.com/DRUPAL-CONTRIB-2021-030/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2021-030

---
From sbomify Insights: https://insights.sbomify.com/DRUPAL-CONTRIB-2021-030/
Summaries are generated and may contain mistakes; the official description above is the record.