CVE-2022-36084 is a critical-severity (CVSS 9.9) CWE-74 vulnerability in cruddl. A fix is available for cruddl — see the affected versions and patch details below.
cruddl vulnerable to AQL injection through flexSearch
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-36084.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2022-36084 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
cruddlnpmDescription
Impact
If a vunerable version of cruddl is used to generate a schema that uses @flexSearchFulltext, users of that schema may be able to inject arbitrary AQL queries that will be forwarded to and executed by ArangoDB.
Schemas that do not use @flexSearchFulltext are not affected.
The attacker needs to have READ permission to at least one root entity type that has @flexSearchFulltext enabled.
Patches
The issue has been fixed in version 3.0.2 and in version 2.7.0 of cruddl.
Workarounds
Users can temporarily remove @flexSearchFulltext from their schemas before they can update cruddl.
For more information
If you have any questions or comments about this advisory:
- Open an issue in cruddl
- Email us at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | cruddl | ≥ 3.0.0&&< 3.0.2 | 3.0.2npm install cruddl@3.0.2 |
| 📦npm | cruddl | ≥ 1.1.0&&< 2.7.0 | 2.7.0npm install cruddl@2.7.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cruddl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update cruddl to 3.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-36084 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-36084 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-36084. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-36084 in your dependencies?
O3 Security finds CVE-2022-36084 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.