First published: Wed Jun 28 2017(Updated: )
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.
Credit: security@apache.org security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache Ignite | =1.0.0 | |
Apache Ignite | =1.0.0-rc3 | |
Apache Ignite | =1.1.0 | |
Apache Ignite | =1.2.0 | |
Apache Ignite | =1.3.0 | |
Apache Ignite | =1.4.0 | |
Apache Ignite | =1.5.0-b1 | |
Apache Ignite | =1.5.0-final | |
Apache Ignite | =1.6.0 | |
Apache Ignite | =1.7.0 | |
Apache Ignite | =1.8.0 | |
Apache Ignite | =1.9.0 | |
Apache Ignite | =2.0.0 | |
maven/org.apache.ignite:ignite-core | <2.1 | 2.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-7686 is classified as a moderate severity vulnerability due to potential information disclosure issues.
To mitigate CVE-2017-7686, it is recommended to upgrade to Apache Ignite version 2.1 or later.
CVE-2017-7686 affects Apache Ignite versions from 1.0.0-RC3 to 2.0.0.
CVE-2017-7686 is an information disclosure vulnerability related to the update notifier component in Apache Ignite.
There are no effective workarounds for CVE-2017-7686, so upgrading is strongly recommended.