CVE-2022-37423 — apoc
Fix: neo4j-contrib/neo4j-apoc-procedures#3080CVE-2022-37423 is a Path Traversal vulnerability in org.neo4j.procedure:apoc. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.neo4j.procedure:apoc — see the affected versions and patch details below.
Neo4j Graph apoc plugins Partial Path Traversal Vulnerability
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.
Real-World Exposure
org.neo4j.procedure:apoc☕org.neo4j.procedure:apocReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Impact
A partial Directory Traversal Vulnerability found in apoc.log.stream function of apoc plugins in Neo4j Graph database.
This issue allows a malicious actor to potentially break out of the expected directory. The impact is limited to sibling directories. For example, userControlled.getCanonicalPath().startsWith("/usr/out") will allow an attacker to access a directory with a name like /usr/outnot.
Patches
The users should aim to use the latest released version compatible with their Neo4j version. The minimum versions containing patch for this vulnerability are 4.4.0.8 and 4.3.0.7
Workarounds
If you cannot upgrade the library, you can control the allowlist of the functions that can be used in your system
For more information
If you have any questions or comments about this advisory:
- Open an issue in neo4j-apoc-procedures
- Email us at [email protected]
Credits
We want to publicly recognise the contribution of Jonathan Leitschuh for reporting this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.neo4j.procedure:apoc | ≥ 4.4.0.0&&< 4.4.0.8 | 4.4.0.8org.neo4j.procedure:apoc:4.4.0.8 |
| ☕Maven | org.neo4j.procedure:apoc | all versions | 4.3.0.7org.neo4j.procedure:apoc:4.3.0.7 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.neo4j.procedure:apoc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.neo4j.procedure:apoc to 4.4.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-37423 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-37423 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-37423. 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-37423 in your dependencies?
O3 Security finds CVE-2022-37423 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.