Quick answers
- Is CVE-2024-36128 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-36128 being exploited in the wild.
- How severe is CVE-2024-36128?
- Low severity, with a CVSS score of 3.1, published 4 June 2024.
- Which products and versions are affected?
- directus (npm) SEMVER:introduced=0,fixed=10.11.2.
- Is there a fix for CVE-2024-36128?
- Yes. directus (npm): upgrade to 10.11.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2024-36128 attacked?
- It is attacked over the network.
- Am I affected by CVE-2024-36128?
- Check whether you run directus (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- directus (npm): upgrade to 10.11.2 or later
npm install directus@10.11.2
Technical details
The vulnerability is a denial of service caused by improper input validation in the random string utility. When a non-numeric value is provided to the length parameter of the random string generation endpoint (GET /utils/random/string?length=foo), it creates a memory issue that corrupts the utility's state. Once triggered, the utility returns empty strings instead of random session IDs, causing all session refresh and authentication operations to fail. The vulnerability requires network access to the random string endpoint but no authentication or user interaction. The issue is fixed in Directus version 10.11.2 and later.
Affected products
- Directus Directus <=10.11.1
Identifiers
- CVE-2024-36128
- GHSA-632p-p495-25m5
Timeline
- 2024-06-03: disclosed
- 2024-06-04: patched: Fixed in version 10.11.2