CVE-2018-1000644
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedEclipse RDF4j version < 2.4.0 Milestone 2 contains a XML External Entity (XXE) vulnerability in RDF4j XML parser parsing RDF files that can result in the disclosure of confidential data, denial of service, server side request forgery, port scanning. This attack appear to be exploitable via Specially crafted RDF file.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceEclipse RDF4j versions before 2.4.0 Milestone 2 contain an XML External Entity (XXE) vulnerability in the XML parser used to process RDF files. Attackers can exploit this by supplying specially crafted RDF/XML files to read local files from the server, cause denial of service, perform server-side request forgery, or conduct port scanning against internal infrastructure.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.4.0= 2.4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Eclipse RDF4j versionCheck the version of the Eclipse RDF4j library or application in your environment (check pom.xml, dependency management, or application metadata)Affected if The version is lower than 2.4.0 Milestone 2 or exactly 2.4.0
-
Determine if RDF/XML file processing is enabledIdentify whether your application or service uses RDF4j to parse RDF/XML files (review configuration, upload features, or data import functionality)Affected if RDF/XML parsing is actively used or can be triggered by user-supplied files
-
Inspect XML parser configuration for external entity settingsReview XML parser settings in your RDF4j configuration or underlying XML parser (look for features such as 'external-general-entities', 'external-parameter-entities', or DTD processing flags)Affected if External entity processing is enabled or not explicitly disabled
-
Check for unprotected XML input handlingExamine how RDF4j handles XML input streams and whether the underlying XMLReader has security restrictions appliedAffected if The XML parser allows DTD processing or external entity resolution without explicit disabling
You are affected if your Eclipse RDF4j version is less than 2.4.0 Milestone 2 or equals 2.4.0 AND your environment processes RDF/XML files with an XML parser that has external entity processing enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.4.0
Upgrade Eclipse RDF4j to version 2.4.0 Milestone 2 or later. Additionally, ensure XML parsers are configured with disabled external entity processing (DTD and external entity references disabled).
2.4.1 or later (preferably 2.5.x or 3.x)
- 1. Identify all dependencies on org.eclipse.rdf4j libraries in your project
- 2. Check current version of org.eclipse.rdf4j dependencies (e.g., rdf4j-core, rdf4j-server, rdf4j-workbench)
- 3. Upgrade to rdf4j version 2.4.1 or later (2.5.x or 3.x recommended for long-term stability)
- 4. Rebuild and test application to ensure XML parsing functionality works correctly
- 5. Verify XXE protection is in place by testing with crafted RDF files containing external entity references
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000644 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-1000644 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data