LiveActive security incident?Get immediate response
CVE Record

CVE-2018-1000820: neo4j-contrib neo4j-apoc-procedures version before commit 45bc09c contains a XML External Entity (XXE) vuln...

neo4j-contrib neo4j-apoc-procedures version before commit 45bc09c contains a XML External Entity (XXE) vulnerability in XML Parser that can result in Disclosure of confidential data, denial of service, SSRF, port scanning. This vulnerability appears to have been fixed in after commit 45bc09c.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-1000820 is an XXE flaw in neo4j-contrib neo4j-apoc-procedures before commit 45bc09c. If vulnerable XML parsing is reachable, it may expose confidential data, cause denial of service, or enable server-side requests and internal port scanning. Public severity and CVSS data are not provided.

Executive priority

Prioritize systems where Neo4j processes untrusted XML or can reach sensitive internal services. Business urgency is moderate because the reported impacts include data disclosure and SSRF, but the public record lacks CVSS, precise affected versions, and confirmed active exploitation.

Technical view

The CVE describes an XML External Entity vulnerability in the XML parser used by neo4j-apoc-procedures before commit 45bc09c. Reported outcomes include data disclosure, denial of service, SSRF, and port scanning. The source bundle says the issue was fixed after commit 45bc09c, but does not provide a precise version mapping.

Likely exposure

Exposure is most likely in Neo4j environments using the affected APOC procedures and accepting or processing XML input. The provided record lists affected vendor and product fields as n/a, so asset matching should use repository, dependency, and commit evidence.

Exploitation context

The sources describe potential impact but do not show confirmed active exploitation. The CVE is not listed as KEV in the bundle. Treat public exploitability evidence as incomplete unless your own threat intelligence or vendor advisories add more detail.

Researcher notes

The record is sparse: no CVSS, CWE, CPE, or exact release range is included. The strongest anchors are the affected project name, the XXE class, the stated impact set, and the fix reference to commit 45bc09c. Avoid over-claiming exploit status.

Mitigation direction

  • Check whether neo4j-apoc-procedures is present in Neo4j deployments.
  • Upgrade or rebuild from a revision after commit 45bc09c.
  • Review vendor or project guidance for exact fixed release mapping.
  • Restrict untrusted XML processing where APOC procedures are exposed.
  • Limit outbound network access from Neo4j hosts where possible.

Validation and detection

  • Inventory Neo4j servers and installed APOC procedure versions.
  • Confirm whether the deployed code predates commit 45bc09c.
  • Review application paths that pass XML into APOC procedures.
  • Check logs for unexpected outbound requests from Neo4j hosts.
  • Document uncertainty where exact version mapping is unavailable.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-1000820 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.