Skip to content
Fencer Intel
critical 9.1

CVE-2021-42767 json

Neo4j Graph Database vulnerable to Path Traversal

published 4y ago modified 4mo ago also GHSA-4mpj-488r-vh6m , EUVD-2022-0817

cvss
9.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits
0
none known

Summary

A directory traversal vulnerability in the apoc plugins in Neo4J Graph database before 4.4.0.1 allows attackers to read local files, and sometimes create local files. This is fixed in 3.5.17, 4.2.10, 4.3.0.4, and 4.4.0.1.

Patch / fix

  • maven org.neo4j.procedure:apoc 3.5.17, 4.2.10, 4.3.0.4, 4.4.0.1
  • neo4j awesome_procedures 3.5.0.17, 4.2.10, 4.3.0.4, 4.4.0.1

Is CVE-2021-42767 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.53% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD 2.0 6.4 AV:N/AC:L/Au:N/C:P/I:P/A:N
GitHub 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven org.neo4j.procedure:apoc
<3.5.17
>=4.2.0, <4.2.10
>=4.3.0.0, <4.3.0.4
>=4.4.0.0, <4.4.0.1
3.5.17
4.2.10
4.3.0.4
4.4.0.1

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.