CVE-2018-1000644 json
Eclipse RDF4j vulnerable to XML External Entity
published 2018-08-20 8 y ago modified 2026-06-17 4 mo ago also GHSA-6xq8-pvg4-3mf3 , EUVD-2018-0528
- cvss
- 10.0
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
Eclipse 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.
Patch / fix
- maven org.eclipse.rdf4j:rdf4j-runtime 2.4.0
- eclipse rdf4j 2.4.0
- rdf4j Debian 14 5.3.2-1
debian advisories DEBIAN-CVE-2018-1000644
- github.com/eclipse/rdf4j/issues/1056 advisory
Exploit prediction
1.75% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 10.0 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.0 | 10.0 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.eclipse.rdf4j:rdf4j-runtime | <2.4.0 |
2.4.0 |
Classification
- Weakness
-
- CWE-611 Improper Restriction of XML External Entity Reference
References
-
github.com
/eclipse/rdf4j/issues/1056
web, patch, third-party-advisory
-
0dd.zone
/2018/08/05/rdf4j-XXE/
third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-1000644
advisory
-
0dd.zone
/2018/08/05/rdf4j-XXE
web
-
github.com
/advisories/GHSA-6xq8-pvg4-3mf3
advisory
-
github.com
/eclipse/rdf4j
package
Sources
- CVE List CVE-2018-1000644
- GitHub Advisory GHSA-6xq8-pvg4-3mf3
- NVD CVE-2018-1000644
Fencer Vulns 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.