Unsafe Deserialization in org.neo4j:neo4j (CVE-2021-34371)
Summary
Vulnerability in org.neo4j:neo4j (CVE-2021-34371). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.5.0 or later.
Original description
The description as published by the source.
Neo4j through 3.4.18 (with the shell server enabled) exposes an RMI service that arbitrarily deserializes Java objects, e.g., through setSessionVariable. An attacker can abuse this for remote code execution because there are dependencies with exploitable gadget chains.
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-2021-34371 has been found in org.neo4j:neo4j.
Successful exploitation can lead to full system takeover.
What to do: upgrade org.neo4j:neo4j to 3.5.0 or later.
If unsure, ask your IT team or search "org.neo4j:neo4j CVE-2021-34371" on the vendor's site.
CVE-2021-34371 (org.neo4j:neo4j) — CWE-502
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.5.0 — 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.
Unsafe deserialization (CWE-502) exists in org.neo4j:neo4j.
Check the vendor advisory for the affected versions of org.neo4j:neo4j.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 3.5.0.
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:neo4j を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.neo4j:neo4j to 3.5.0ステージング環境で 3.5.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory exploit-db.com
- package github.com
- web nvd.nist.gov