CVE-2024-27295
Monospace Directus ≤ 10.8.3
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:NSummary
CVE-2024-27295 is a high-severity Use of Incorrectly-Resolved Name or Reference (CWE-706) vulnerability in Monospace Directus. Its CVSS base score is 8.2 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked at the 50th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-0993
Vulnerability Data
Directus is a real-time API and App dashboard for managing SQL database content. The password reset mechanism of the Directus backend allows attackers to receive a password reset email of a victim user, specifically having it arrive at a similar…
more
email address as the victim with a one or more characters changed to use accents. This is due to the fact that by default MySQL/MariaDB are configured for accent-insensitive and case-insensitive comparisons. This vulnerability is fixed in version 10.8.3.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement applies authorization checks to the resolved resource, blocking access outside the intended sphere.
Information flow enforcement can constrain flows that result from an incorrectly resolved name or reference.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices directly prevent incorrect name/reference resolution bugs during coding.
Enforced authorization boundaries limit damage from an incorrectly resolved reference.
Logical segmentation and access controls reduce the chance an out-of-sphere resolution succeeds.
Hardened configuration baselines can constrain allowable name-to-resource mappings.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect incorrect name or reference resolution through fuzzing and negative test cases.
Network segmentation and routing policies reduce the chance that a mis-resolved name leads to an unintended external resource.
Segregated networks limit the blast radius when a name or reference resolves outside the intended control sphere.
Secure SDLC practices include design reviews that can catch incorrect name or reference handling before deployment.
Application security requirements can mandate validation of all external references and names used at runtime.
Secure architecture principles discourage reliance on ambient or globally-resolvable names without explicit scoping.