Directus up to 10.13.2 OpenId/Oauth2 cache containing sensitive information

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.0$0-$5k0.00

Summaryinfo

A vulnerability described as problematic has been identified in Directus up to 10.13.2. This affects an unknown part of the component OpenId/Oauth2. Executing a manipulation can lead to use of cache containing sensitive information. The identification of this vulnerability is CVE-2024-45596. The attack may be launched remotely. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability has been found in Directus up to 10.13.2 and classified as problematic. This vulnerability affects an unknown code block of the component OpenId/Oauth2. The manipulation with an unknown input leads to a use of cache containing sensitive information vulnerability. The CWE definition for the vulnerability is CWE-524. The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere. As an impact it is known to affect confidentiality. CVE summarizes:

Directus is a real-time API and App dashboard for managing SQL database content. An unauthenticated user can access credentials of last authenticated user via OpenID or OAuth2 where the authentication URL did not include redirect query string. This happens because on that endpoint for both OpenId and Oauth2 Directus is using the respond middleware, which by default will try to cache GET requests that met some conditions. Although, those conditions do not include this scenario, when an unauthenticated request returns user credentials. This vulnerability is fixed in 10.13.3 and 11.1.0.

The advisory is available at github.com. This vulnerability was named CVE-2024-45596 since 09/02/2024. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1592 by the MITRE ATT&CK project.

Upgrading to version 10.13.3 or 11.1.0 eliminates this vulnerability. Applying the patch 4aace0bbe57232e38cd6a287ee475293e46dc91b is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.1
VulDB Meta Temp Score: 6.0

VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 6.5
NVD Vector: 🔍

CNA Base Score: 7.4
CNA Vector (GitHub_M): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Use of cache containing sensitive information
CWE: CWE-524
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Directus 10.13.3/11.1.0
Patch: 4aace0bbe57232e38cd6a287ee475293e46dc91b

Timelineinfo

09/02/2024 🔍
09/11/2024 +9 days 🔍
09/11/2024 +0 days 🔍
11/17/2025 +432 days 🔍

Sourcesinfo

Product: github.com

Advisory: GHSA-cff8-x7jv-4fm8
Status: Confirmed

CVE: CVE-2024-45596 (🔍)
GCVE (CVE): GCVE-0-2024-45596
GCVE (VulDB): GCVE-100-277114

Entryinfo

Created: 09/11/2024 06:18
Updated: 11/17/2025 20:51
Changes: 09/11/2024 06:18 (65), 09/12/2024 08:27 (1), 03/10/2025 18:31 (3), 11/17/2025 20:51 (11)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to stay up to date on a daily basis?

Enable the mail alert feature now!