CVE-2022-23532: org.neo4j.procedure:apoc Path Traversal Vulnerability

CVE-2022-23532 · Severity: low · CVSS 3.1 · Published 2023-01-13

org.neo4j.procedure:apoc Path Traversal Vulnerability

Technologies: org.neo4j.procedure:apoc (Maven). Vendors: Maven.

Quick answers

Is CVE-2022-23532 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-23532 being exploited in the wild.
How severe is CVE-2022-23532?
Low severity, with a CVSS score of 3.1, published 13 January 2023.
Which products and versions are affected?
org.neo4j.procedure:apoc (Maven) ECOSYSTEM:introduced=0,fixed=4.3.0.12.
Is there a fix for CVE-2022-23532?
Yes. org.neo4j.procedure:apoc (Maven): upgrade to 4.3.0.12 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-23532?
Check whether you run org.neo4j.procedure:apoc (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.neo4j.procedure:apoc (Maven): upgrade to 4.3.0.12 or later
    # set org.neo4j.procedure:apoc to 4.3.0.12 in your pom.xml or build.gradle

Affected products

  • org.neo4j.procedure:apoc (Maven) ECOSYSTEM:introduced=0,fixed=4.3.0.12

Identifiers

  • CVE-2022-23532
  • GHSA-5v8v-gwmw-qw97

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.