dbcve.org
IgniteApplication · Apache

CVE-2017-7686

HIGH · 7.5 CVSS v3.0 Published 2017-06-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Ignite versions 1.0.0-RC3 through 2.0 include an update notifier component that communicates with an external PHP server (http://ignite.run) to notify users of new releases. During this communication, the component transmits system properties including Apache Ignite and Java version information, some of which may contain user-sensitive data, resulting in unintended information disclosure to a third-party external host.

MitigationDisable or remove the update notifier component in Apache Ignite configurations, or block outbound network access to the external host ignite.run at the network perimeter to prevent sensitive data exfiltration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IgniteApplication
Affected:= 1.0.0= 1.1.0= 1.2.0= 1.3.0= 1.4.0= 1.5.0= 1.6.0= 1.7.0= 1.8.0= 1.9.0= 2.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Ignite installation and version
    Locate the Apache Ignite installation directory and check the version. Run 'java -jar ignite-core-{version}.jar' or check the ignite-core-{version}.jar filename in the lib folder. Alternatively, check pom.xml dependencies if built from source.
    Affected if The installed version matches any of: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0, or 2.0.0
  2. Locate update notifier configuration
    Search for XML configuration files in the Ignite installation directory or config folder. Look for 'UpdateNotifier' or related configuration elements in ignite.xml, ignite-default.xml, or similar configuration files.
    Affected if An update notifier component is explicitly configured in any Ignite configuration XML file
  3. Check for update notifier bean in code
    Search the codebase for 'UpdateNotifier' class usage. In Java deployments, grep for 'org.apache.ignite.internal.UpdateNotifier' or inspect the classpath for update-notifier*.jar files.
    Affected if The UpdateNotifier class is loaded or referenced in the application configuration
  4. Detect outbound network traffic to ignite.run
    Monitor network connections using tcpdump, Wireshark, or netstat while Ignite is starting or running. Run 'tcpdump host ignite.run' or 'netstat -an | grep ignite.run' to capture any outbound connections.
    Affected if Network traffic to the host 'ignite.run' on ports 80 or 443 is observed from the Ignite process
  5. Inspect Java system properties being transmitted
    Enable Java debug logging or network packet capture to inspect the payload sent to ignite.run. Review HTTP headers and POST data for exposed system properties such as 'java.version', 'os.name', or custom user properties.
    Affected if HTTP requests to ignite.run contain system property data that includes sensitive information beyond basic version numbers

A user is affected if they run a vulnerable Apache Ignite version (1.0.0 through 2.0.0) with the update notifier component enabled, resulting in outbound connections to ignite.run that exfiltrate system properties.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable or remove the update notifier component in Apache Ignite configurations, or block outbound network access to the external host ignite.run at the network perimeter to prevent sensitive data exfiltration.

Fix this in Ignite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-7686 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-7686 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data