Path Traversal in org.neo4j.procedure:apoc (CVE-2022-37423)
Summary
Path traversal in org.neo4j.procedure:apoc (CVE-2022-37423). Risk of unauthorized operations or information disclosure. Exploitable via apoc.log.stream. Mitigation: upgrade to 4.3.0.7 or later.
Original description
The description as published by the source.
Neo4j APOC (Awesome Procedures on Cypher) before 4.3.0.7 and 4.x before 4.4.0.8 allows Directory Traversal to sibling directories via apoc.log.stream.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2022-37423 has been found in org.neo4j.procedure:apoc.
Attackers can target a specific entry point like apoc.log.stream over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade org.neo4j.procedure:apoc to 4.3.0.7 or later.
If unsure, ask your IT team or search "org.neo4j.procedure:apoc CVE-2022-37423" on the vendor's site.
CVE-2022-37423 (org.neo4j.procedure:apoc) — CWE-22
Attack surface: apoc.log.stream
Patched: 4.3.0.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in org.neo4j.procedure:apoc. Attackers reach the vulnerable code path via apoc.log.stream.
Check the vendor advisory for the affected versions of org.neo4j.procedure:apoc. Attack surface: apoc.log.stream.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.3.0.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.neo4j.procedure:apoc を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.neo4j.procedure:apoc to 4.3.0.7ステージング環境で 4.3.0.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com
- web neo4j.com
- web neo4j.com