# CVE-2018-1000652: XML external entity in n/a

> An attacker can exploit an XML External Entity vulnerability in JabRef's MsBib importer to disclose confidential data or cause denial of service.

- **Severity:** Critical 10.0 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Aug 2018
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2018-1000652, GHSA-x4cf-86pp-49rw, UBUNTU-CVE-2018-1000652

## What is CVE-2018-1000652?

CVE-2018-1000652 is a critical vulnerability in n/a, published on 20 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

JabRef version <=4.3.1 contains a XML External Entity (XXE) vulnerability in MsBibImporter XML Parser that can result in disclosure of confidential data, denial of service, server side request forgery, port scanning. This attack appear to be exploitable via Specially crafted MsBib file. This vulnerability appears to have been fixed in after commit 89f855d.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

## Which versions are affected by CVE-2018-1000652?

It affects 1 product.


Products: Jabref Jabref.

## How do I fix CVE-2018-1000652?

Apply the vendor's patch.

## Is CVE-2018-1000652 being exploited?

There is no known exploitation of CVE-2018-1000652 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1000652 and fix it if it is affected.

What it is: CVE-2018-1000652 is a critical vulnerability in n/a, published on 20 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1000652 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-1000652/ (Markdown: https://insights.sbomify.com/CVE-2018-1000652/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1000652
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1000652
- OSV: https://osv.dev/vulnerability/CVE-2018-1000652

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-1000652/
Summaries are generated and may contain mistakes; the official description above is the record.