# CVE-2014-3682: XML external entity in n/a

> Remote attackers can read arbitrary files by importing a crafted BPMN2 file into the jBPM designer application.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p5xg-9chh-rh94

## What is CVE-2014-3682?

CVE-2014-3682 is a high-severity vulnerability in n/a, published on 20 Feb 2015. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

XML external entity (XXE) vulnerability in the JBPMBpmn2ResourceImpl function in designer/bpmn2/resource/JBPMBpmn2ResourceImpl.java in jbpm-designer 6.0.x and 6.2.x allows remote attackers to read arbitrary files and possibly have other unspecified impact by importing a crafted BPMN2 file.

## Which versions are affected by CVE-2014-3682?

It affects 1 product.


Products: Redhat Jbpm-Designer.

## How do I fix CVE-2014-3682?

No fix has been published for CVE-2014-3682 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-3682 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-3682 and fix it if it is affected.

What it is: CVE-2014-3682 is a high-severity vulnerability in n/a, published on 20 Feb 2015. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-3682 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-2014-3682/ (Markdown: https://insights.sbomify.com/CVE-2014-3682/index.md)
```

## Sources

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

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