Advisory details:
github_osv / GHSA-hxgm-ghmv-xjjm
| Advisory ID | github_osv/GHSA-hxgm-ghmv-xjjm |
| Aliases |
CVE-2024-39701
|
| Summary | Directus incorrectly handles `_in` filter ### Summary Directus >=9.23.0, <=v10.5.3 improperly handles _in, _nin operators. It evaluates empty arrays as valid so expressions like {"role": {"_in": $CURRENT_USER.some_field}} would evaluate to true allowing the request to pass. ### Details This results in Broken Access Control because the rule fails to do what it was intended to do: Pass rule if **field** matches any of the **values**. ref: https://docs.directus.io/reference/filter-rules.html#filter-operators In my example this would translate to "Pass rule if **<collection>.role** matches any of **[]**". Which should fail. This instead passes in Directus <= v10.5.3, >=v9.23.0 ### PoC {"role": {"_in": $CURRENT_USER.some_field}} field validation would pass if $CURRENT_USER.some_field is null. Real scenario: Using https://github.com/u12206050/directus-extension-role-chooser with the specified versions of Directus (I tested on 10.0.0) allows users with access to this feature set their role to whatever role if they don't have any roles assigned (user_roles.role is left with the default value, null) despite the validation rule being ```yaml validation: role: _in: $CURRENT_USER.user_roles.role ``` Latest version of Directus (v10.8.3 and above) handles the above validation rule correctly. ### Impact Permissions fail to open for setups relying on this filter and can lead to users getting access to things they're not supposed to. |
| Status | Published |
| Exploitability | 0.5 |
| Weighted Severity | 6.3 |
| Risk | 3.1 |
| Affected and Fixed Packages | Package Details |
| Introduced and Fixed Package Commit Patches | Package Commit Patches Details |
| CWE-284 | Improper Access Control |
| System | Score | Found at |
|---|---|---|
| cvssv3.1 | 6.3 | https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/07/GHSA-hxgm-ghmv-xjjm/GHSA-hxgm-ghmv-xjjm.json |
| cvssv4 | 7.0 | https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/07/GHSA-hxgm-ghmv-xjjm/GHSA-hxgm-ghmv-xjjm.json |
| generic_textual | HIGH |
| Reference id | Reference type | URL |
|---|---|---|
| https://github.com/directus/directus | ||
| CVE-2024-39701 | https://nvd.nist.gov/vuln/detail/CVE-2024-39701 | |
| GHSA-hxgm-ghmv-xjjm | https://github.com/directus/directus/security/advisories/GHSA-hxgm-ghmv-xjjm |
No EPSS data available for this advisory.
| Patch URL | |
|---|---|
| There are no known patches. | |
| Attack Vector (AV) | Attack Complexity (AC) | Privileges Required (PR) | User Interaction (UI) | Scope (S) | Confidentiality Impact (C) | Integrity Impact (I) | Availability Impact (A) |
|---|---|---|---|---|---|---|---|
network adjacent_network local physical |
low high |
none low high |
none required |
unchanged changed |
high low none |
high low none |
high low none |
| Attack Vector (AV) | Attack Complexity (AC) | Attack Requirements (AT) | Privileges Required (PR) | User Interaction (UI) | Vulnerable System Impact Confidentiality (VC) | Vulnerable System Impact Integrity (VI) | Vulnerable System Impact Availability (VA) | Subsequent System Impact Confidentiality (SC) | Subsequent System Impact Integrity (SI) | Subsequent System Impact Availability (SA) |
|---|---|---|---|---|---|---|---|---|---|---|
network adjacent local physical |
low high |
none present |
none low high |
none passive active |
high low none |
high low none |
high low none |
high low none |
high low none |
high low none |
There are no SSVC decisions available.