Unauthenticated service interruption via structural-element mishandling
Published Jan 16, 2024 · Updated Jun 20, 2025
Improper structural-element handling in Drupal core 9.3.6 allows remote attackers to interrupt the service via network requests. Drupal and JPCERT/CC have not published the affected parser, request structure, or incorrect code operation that exhausts resources. No authentication or user interaction is required; the documented consequence is reduced availability, and Drupal could not reproduce it in 9.5.x or 10.x.
Summary
What happened
Improper structural-element handling in Drupal core 9.3.6 allows remote attackers to interrupt the service via network requests. Drupal and JPCERT/CC have not published the affected parser, request structure, or incorrect code operation that exhausts resources. No authentication or user interaction is required; the documented consequence is reduced availability, and Drupal could not reproduce it in 9.5.x or 10.x.
The record
- CVE
- CVE-2024-22362
- Published
- Jan 16, 2024
- Updated
- Jun 20, 2025
- Vendor
- OAuth.js
- Product
- Drupal core
- Classifications
- CWE-237, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 16, 2024CVE publishedPublication date reported by the CVE source.
- Jun 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=prior to 9.5.x
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo