Skip to content

Session Token in URL in directus

Low severity GitHub Reviewed Published Mar 12, 2024 in directus/directus • Updated Mar 13, 2024

Package

npm directus (npm)

Affected versions

< 10.10.0

Patched versions

10.10.0

Description

Impact

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.

Patches

Has the problem been patched? What versions should users upgrade to?

Workarounds

There's no workaround available.

References

Are there any links users can visit to find out more?

References

@rijkvanzanten rijkvanzanten published to directus/directus Mar 12, 2024
Published to the GitHub Advisory Database Mar 12, 2024
Reviewed Mar 12, 2024
Published by the National Vulnerability Database Mar 12, 2024
Last updated Mar 13, 2024

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N

EPSS score

0.043%
(11th percentile)

Weaknesses

CVE ID

CVE-2024-28238

GHSA ID

GHSA-2ccr-g2rv-h677

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.