GHSA-9vx8-f5c4-862x json
XML External Entity (XXE) vulnerability in apoc.import.graphml
published 3y ago modified last yr.
- cvss
- 5.9
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
### Impact A XML External Entity (XXE) vulnerability found in the apoc.import.graphml procedure of APOC core plugin in Neo4j graph database. XML External Entity (XXE) injection occurs when the XML parser allows external entities to be resolved. The XML parser used by the apoc.import.graphml procedure was not configured in a secure way and therefore allowed this.
External entities can be used to read local files, send HTTP requests, and perform denial-of-service attacks on the application.
Abusing the XXE vulnerability enabled assessors to read local files remotely. Although with the level of privileges assessors had this was limited to one-line files. With the ability to write to the database, any file could have been read. Additionally, assessors noted, with local testing, the server could be crashed by passing in improperly formatted XML.
### Patches The users should aim to use the latest released version compatible with their Neo4j version. The minimum versions containing patch for this vulnerability is 4.4.0.14.
### Workarounds If you cannot upgrade the library, you can control the [allowlist](https://neo4j.com/docs/operations-manual/current/reference/configuration-settings/#config_dbms.security.procedures.allowlist) of the procedures that can be used in your system.
### For more information If you have any questions or comments about this advisory: * Open an issue in [neo4j-apoc-procedures](https://github.com/neo4j-contrib/neo4j-apoc-procedures) * Email us at [security@neo4j.com](mailto:security@neo4j.com)
### Credits We want to publicly recognise the contribution of Christopher Schneider – State Farm.
Patch / fix
- maven org.neo4j.procedure:apoc 4.4.0.14, 5.5.0
Is GHSA-9vx8-f5c4-862x 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 FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.neo4j.procedure:apoc | <4.4.0.14 >=5.0.0, <5.5.0 |
4.4.0.14 5.5.0 |
Classification
- Weakness
-
- CWE-611 Improper Restriction of XML External Entity Reference
References
-
github.com
/neo4j-contrib/neo4j-apoc-procedures/commit/c3e2a29020497acf9417879f38e8af4e8c6d5783
web
-
github.com
/neo4j-contrib/neo4j-apoc-procedures/security/advisories/GHSA-9vx8-f5c4-862x
web
-
github.com
/neo4j/apoc/security/advisories/GHSA-6wxg-wh7f-rqpr
web
-
nvd.nist.gov
/vuln/detail/CVE-2023-23926
advisory
-
github.com
/neo4j-contrib/neo4j-apoc-procedures
package
-
github.com
/neo4j-contrib/neo4j-apoc-procedures/releases/tag/4.4.0.14
web
Sources
- GitHub Advisory GHSA-9vx8-f5c4-862x
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.