GHSA-5V8V-GWMW-QW97

Vulnerability from github – Published: 2023-01-13 21:28 – Updated: 2023-01-24 18:06
VLAI?
Summary
org.neo4j.procedure:apoc Path Traversal Vulnerability
Details

Impact

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 procedure would need to have been allow listed in the neo4j configuration as well as having the apoc config apoc.export.file.enabled set to true.

On a UNIX based system the following query allows arbitrary write access to the tmp folder:

CALL apoc.export.csv.query('RETURN 1', 'file:///..//..//..//..//tmp/test.txt', {})

Patches

The users should aim to use the latest released version compatible with their Neo4j version. The minimum versions containing patch for this vulnerability are 4.4.0.12 and 4.3.0.12.

Workarounds

If you cannot upgrade the library, 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

For more information

If you have any questions or comments about this advisory: * Open an issue in neo4j-apoc-procedures * Email us at security@neo4j.com

Credits

We want to publicly recognise the contribution Adam Reziouk - Airbus.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.neo4j.procedure:apoc"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "4.3.0.12"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.neo4j.procedure:apoc"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "4.4.0.0"
            },
            {
              "fixed": "4.4.0.12"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2022-23532"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2023-01-13T21:28:46Z",
    "nvd_published_at": "2023-01-14T01:15:00Z",
    "severity": "HIGH"
  },
  "details": "### Impact\nA Path Traversal Vulnerability found in the apoc.export.* procedures of apoc plugins in Neo4j Graph database.\nThe 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.\n\nFor 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 procedure would need to have been allow listed in the neo4j configuration as well as having the apoc config `apoc.export.file.enabled` set to true. \n\nOn a UNIX based system the following query allows arbitrary write access to the tmp folder:\n\nCALL apoc.export.csv.query(\u0027RETURN 1\u0027, \u0027file:///..//..//..//..//tmp/test.txt\u0027, {})\n\n### Patches\nThe users should aim to use the latest released version compatible with their Neo4j version. The minimum versions containing patch for this vulnerability are 4.4.0.12 and 4.3.0.12.\n\n### Workarounds\nIf you cannot upgrade the library, you can control the\u00a0[allowlist of the ](https://neo4j.com/docs/operations-manual/current/reference/configuration-settings/#config_dbms.security.procedures.allowlist)procedures\u00a0that can be used in your system, and/or turn off local file access by setting apoc.export.file.enabled=false\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in\u00a0[neo4j-apoc-procedures](https://github.com/neo4j-contrib/neo4j-apoc-procedures)\n* Email us at\u00a0[security@neo4j.com](mailto:security@neo4j.com)\n\n### Credits\nWe want to publicly recognise the contribution Adam Reziouk - Airbus.",
  "id": "GHSA-5v8v-gwmw-qw97",
  "modified": "2023-01-24T18:06:35Z",
  "published": "2023-01-13T21:28:46Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/neo4j-contrib/neo4j-apoc-procedures/security/advisories/GHSA-5v8v-gwmw-qw97"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-23532"
    },
    {
      "type": "WEB",
      "url": "https://github.com/neo4j-contrib/neo4j-apoc-procedures/commit/01e63ed2d187cd2a8aa1d78bf831ef0fdd69b522"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/neo4j-contrib/neo4j-apoc-procedures"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "org.neo4j.procedure:apoc Path Traversal Vulnerability"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…