# CVE-2017-7686: Apache Ignite communicates to an external PHP server where sensitive information is sent

> Apache Ignite's update notifier sends sensitive system properties to an external server, potentially exposing user information.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/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:** 28 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8p83-68cw-943f

## What is CVE-2017-7686?

CVE-2017-7686 is a high-severity vulnerability in Apache Ignite, published on 28 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Apache Ignite 1.0.0-RC3 to 2.0 uses an update notifier component to update the users about new project releases that include additional functionality, bug fixes and performance improvements. To do that the component communicates to an external PHP server (http://ignite.run) where it needs to send some system properties like Apache Ignite or Java version. Some of the properties might contain user sensitive information.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-7686?

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 | 2.1 |
| `org.apache.ignite:ignite-core` | Maven | All versions | 2.1 |

Products: Apache Ignite.

## How do I fix CVE-2017-7686?

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

## Is CVE-2017-7686 being exploited?

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

## Other vulnerabilities in Apache Ignite

- [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-2017-7686 and fix it if it is affected.

What it is: CVE-2017-7686 is a high-severity vulnerability in Apache Ignite, published on 28 Jun 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-2017-7686 in the wild and no public exploit code.

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

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

## Sources

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

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