# CVE-2022-23532: neo4j-apoc-procedures is vulnerable to path traversal

> Attackers with query execution access can create files outside intended directories via path traversal in Neo4j APOC export procedures.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Jan 2023
- **Updated:** 10 Mar 2025
- **Also known as:** GHSA-5v8v-gwmw-qw97

## What is CVE-2022-23532?

CVE-2022-23532 is a high-severity path traversal vulnerability in neo4j-contrib neo4j-apoc-procedures, published on 14 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

APOC (Awesome Procedures on Cypher) is an add-on library for Neo4j that provides hundreds of procedures and functions. A path traversal vulnerability found in the apoc.export.* procedures of apoc plugins in Neo4j Graph database. The issue allows a malicious actor to potentially break out of the expected directory. The vulnerability is such that files could only be created but not overwritten. For the vulnerability to be exploited, an attacker would need access to execute an arbitrary query, either by having access to an authenticated Neo4j client, or a Cypher injection vulnerability in an application. The minimum versions containing patch for this vulnerability are 4.4.0.12 and 4.3.0.12 and 5.3.1. As a workaround, you can control the allowlist of the procedures that can be used in your system, and/or turn off local file access by setting apoc.export.file.enabled=false.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2022-23532?

4 open source packages ship an affected version, including org.neo4j.procedure:apoc. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.neo4j.procedure:apoc` | Maven | All versions | 4.3.0.12 |
| `org.neo4j.procedure:apoc` | Maven | All versions | 4.3.0.12 |
| `org.neo4j.procedure:apoc` | Maven | From 4.4.0.0 | 4.4.0.12 |
| `org.neo4j.procedure:apoc` | Maven | From 4.4.0.0 | 4.4.0.12 |

Products: Neo4j Awesome Procedures on Cyper.

## How do I fix CVE-2022-23532?

Upgrade org.neo4j.procedure:apoc to a fixed version for your release line: 4.3.0.12 or 4.4.0.12.

## Is CVE-2022-23532 being exploited?

There is no known exploitation of CVE-2022-23532 in the wild and no public exploit code.

## Other vulnerabilities in neo4j-contrib neo4j-apoc-procedures

- [CVE-2018-1000820](https://insights.sbomify.com/CVE-2018-1000820/): XML External Entity (XXE) vulnerability in neo4j.procedure:apoc (critical 10.0)
- [CVE-2023-23926](https://insights.sbomify.com/CVE-2023-23926/): XML External Entity (XXE) vulnerability in apoc.import.graphml (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-23532 and fix it if it is affected.

What it is: CVE-2022-23532 is a high-severity path traversal vulnerability in neo4j-contrib neo4j-apoc-procedures, published on 14 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-23532 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.neo4j.procedure:apoc (Maven): affected all versions; fixed in 4.3.0.12
- org.neo4j.procedure:apoc (Maven): affected all versions; fixed in 4.3.0.12
- org.neo4j.procedure:apoc (Maven): affected from 4.4.0.0; fixed in 4.4.0.12
- org.neo4j.procedure:apoc (Maven): affected from 4.4.0.0; fixed in 4.4.0.12

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-23532/ (Markdown: https://insights.sbomify.com/CVE-2022-23532/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-23532
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-23532
- OSV: https://osv.dev/vulnerability/CVE-2022-23532

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-23532/
Summaries are generated and may contain mistakes; the official description above is the record.