CVE-2023-5256 Drupal core - Critical - Cache poisoning - SA-CORE-2023-006
Drupal core leaks sensitive error backtraces via JSON:API, allowing anonymous users to gain privileged access.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2023-5256?
CVE-2023-5256 is a high-severity vulnerability in Drupal Drupal, published on 28 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
In certain scenarios, Drupal's JSON:API module will output error backtraces. With some configurations, this may cause sensitive information to be cached and made available to anonymous users, leading to privilege escalation.
This vulnerability only affects sites with the JSON:API module enabled, and can be mitigated by uninstalling JSON:API.
The core REST and contributed GraphQL modules are not affected.
Weakness: CWE-200
Which versions are affected by CVE-2023-5256?
8 open source packages ship an affected version, including drupal/core and drupal. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
drupal/core Packagist | From 10.0.0 | 10.0.11 |
drupal/core Packagist | From 10.0.0 | 10.0.11 |
drupal/core Packagist | From 10.1.0 | 10.1.4 |
drupal/core Packagist | From 10.1.0 | 10.1.4 |
drupal/core Packagist | From 8.7.0 | 9.5.11, 10.0.11, 10.1.4 |
drupal/core Packagist | From 8.7.0 | 9.5.11 |
2 more packages
drupal/core Packagist | From 8.7.0 | 9.5.11 |
drupal Bitnami | From 8.7.0 | 9.5.11, 10.0.11, 10.1.4 |
Products include Drupal Drupal.
How do I fix CVE-2023-5256?
Upgrade drupal/core to a fixed version for your release line: 10.0.11, 10.1.4 or 9.5.11.
Is CVE-2023-5256 being exploited?
There is no known exploitation of CVE-2023-5256 in the wild and no public exploit code.
Other vulnerabilities in Drupal Drupal
Sources
Also known as BIT-drupal-2023-5256, DRUPAL-CORE-2023-006, GHSA-rjqg-3h9m-fx5x, UBUNTU-CVE-2023-5256.