Directus up to 10.9.x /files get request method with sensitive query strings
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Directus up to 10.9.x and classified as problematic. Affected by this issue is some unknown functionality of the file /files. This manipulation causes use of get request method with sensitive query strings. The identification of this vulnerability is CVE-2024-28238. The attack can only be executed locally. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability classified as problematic was found in Directus up to 10.9.x. Affected by this vulnerability is an unknown part of the file /files. The manipulation with an unknown input leads to a use of get request method with sensitive query strings vulnerability. The CWE definition for the vulnerability is CWE-598. The web application uses the HTTP GET method to process a request and includes sensitive information in the query string of that request. As an impact it is known to affect confidentiality. The summary by CVE is:
Directus is a real-time API and App dashboard for managing SQL database content. When reaching the /files page, a JWT is passed via GET request. Inclusion of session tokens in URLs poses a security risk as URLs are often logged in various places (e.g., web server logs, browser history). Attackers gaining access to these logs may hijack active user sessions, leading to unauthorized access to sensitive information or actions on behalf of the user. This issue has been addressed in version 10.10.0. Users are advised to upgrade. There are no known workarounds for this vulnerability.
The weakness was shared 03/12/2024 as GHSA-2ccr-g2rv-h677. The advisory is shared at github.com. This vulnerability is known as CVE-2024-28238 since 03/07/2024. Technical details are known, but no exploit is available.
Upgrading to version 10.10.0 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.3VulDB Meta Temp Score: 2.3
VulDB Base Score: 2.3
VulDB Temp Score: 2.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 2.3
NVD Vector: 🔍
CNA Base Score: 2.3
CNA Vector (GitHub, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Use of get request method with sensitive query stringsCWE: CWE-598
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Directus 10.10.0
Timeline
03/07/2024 🔍03/12/2024 🔍
03/12/2024 🔍
01/03/2025 🔍
Sources
Product: github.comAdvisory: GHSA-2ccr-g2rv-h677
Status: Confirmed
CVE: CVE-2024-28238 (🔍)
GCVE (CVE): GCVE-0-2024-28238
GCVE (VulDB): GCVE-100-256609
Entry
Created: 03/12/2024 22:24Updated: 01/03/2025 18:40
Changes: 03/12/2024 22:24 (49), 01/03/2025 18:40 (26)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.