User impersonation via unredacted refresh-token cookies
Published Mar 23, 2023 · Updated Feb 21, 2025
Sensitive-data logging in Directus before 9.23.3 allows local users with log access to obtain refresh tokens and impersonate users. The HTTP logger serializes Cookie and Set-Cookie headers without removing the directus_refresh_token value, placing reusable credentials in log output. Access to shared cloud or log-aggregation output is required; exchanging a captured refresh token at /auth/refresh yields an access token for actions as the affected user.
Summary
What happened
Sensitive-data logging in Directus before 9.23.3 allows local users with log access to obtain refresh tokens and impersonate users. The HTTP logger serializes Cookie and Set-Cookie headers without removing the directus_refresh_token value, placing reusable credentials in log output. Access to shared cloud or log-aggregation output is required; exchanging a captured refresh token at /auth/refresh yields an access token for actions as the affected user.
The record
- CVE
- CVE-2023-28443
- Published
- Mar 23, 2023
- Updated
- Feb 21, 2025
- Vendor
- Directus
- Product
- Directus
- Classifications
- CWE-532, CWE-284, T1552.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 23, 2023CVE publishedPublication date reported by the CVE source.
- Feb 21, 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=< 9.23.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Vendor refresh-token log exposure demonstrationproof of concept · demonstrated
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