CVE-2023-5256GHSA-RJQG-3H9M-FX5XBIT-DRUPAL-2023-5256DRUPAL-CORE-2023-006
Drupal core - Critical - Cache poisoning - SA-CORE-2023-006
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 9.5.11, 10.0.11, 10.1.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Drupal Core
From 10.1 · through 10.1.4; From 10.0 · through 10.0.11; From 9.5 · through 9.5.11
- drupal/corePackagist
From 8.7.0 · fixed in 9.5.11
- drupal/corePackagist
From 10.0.0 · fixed in 10.0.11
- drupal/corePackagist
From 10.1.0 · fixed in 10.1.4
- drupal/corePackagist
From 8.7.0 · fixed in 9.5.11; From 10.0.0 · fixed in 10.0.11; From 10.1.0 · fixed in 10.1.4