# CVE-2016-6805: Moderate severity vulnerability that affects org.apache.ignite:ignite-core

> Man-in-the-middle attackers can read arbitrary files via XXE in modified update-notifier documents in Apache Ignite.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8qfc-cvjp-mgpq

## What is CVE-2016-6805?

CVE-2016-6805 is a medium-severity vulnerability in n/a, published on 7 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Apache Ignite before 1.9 allows man-in-the-middle attackers to read arbitrary files via XXE in modified update-notifier documents.

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

## Which versions are affected by CVE-2016-6805?

2 open source packages ship an affected version, including org.apache.ignite:ignite-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.ignite:ignite-core` | Maven | All versions | 1.9 |
| `org.apache.ignite:ignite-core` | Maven | All versions | 1.9 |

Products: Apache Ignite.

## How do I fix CVE-2016-6805?

Upgrade org.apache.ignite:ignite-core to 1.9 or later.

## Is CVE-2016-6805 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-1273](https://insights.sbomify.com/CVE-2018-1273/): VMware Tanzu Spring Data Commons Property Binder (critical 9.8, exploited in the wild)
- [CVE-2018-8018](https://insights.sbomify.com/CVE-2018-8018/): Code execution via deserialization in org.apache.ignite:ignite-core (critical 9.8)
- [CVE-2018-1295](https://insights.sbomify.com/CVE-2018-1295/): Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization (critical 9.8)
- [CVE-2024-52577](https://insights.sbomify.com/CVE-2024-52577/): Apache Ignite: Possible RCE when deserializing incoming messages by the server node (critical 9.5)
- [CVE-2020-1963](https://insights.sbomify.com/CVE-2020-1963/): File system access via H2 in Apache Ignite (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6805 and fix it if it is affected.

What it is: CVE-2016-6805 is a medium-severity vulnerability in n/a, published on 7 Apr 2017. 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-2016-6805 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.ignite:ignite-core (Maven): affected all versions; fixed in 1.9
- org.apache.ignite:ignite-core (Maven): affected all versions; fixed in 1.9

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-2016-6805/ (Markdown: https://insights.sbomify.com/CVE-2016-6805/index.md)
```

## Sources

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

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