Operation on a Resource after Expiration or Release Affecting @directus/api package, versions >=18.0.0 <25.0.0
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JS-DIRECTUSAPI-9535117
- published27 Mar 2025
- disclosed26 Mar 2025
- creditUnknown
Introduced: 26 Mar 2025
CVE-2025-30351 (opens in a new tab)How to fix?
Upgrade @directus/api to version 25.0.0 or higher.
Overview
@directus/api is a real-time API and App dashboard for managing SQL database content
Affected versions of this package are vulnerable to Operation on a Resource after Expiration or Release due to a missing check in verifySessionJWT. An attacker can continue to access the API using a session token even after the user has been suspended by using the token obtained prior to suspension.
Note:
This is only exploitable if the /auth/refresh call is not triggered, as that would invalidate the session token.
PoC
Create an active user
Log in with that user and note the session cookie
Suspend the user (and don't trigger an
/auth/refreshcall, as that invalidates the sessionAccess the API with
Authorization: Bearer <token>