dbcve.org
IgniteApplication · Apache

CVE-2018-1295

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-02
Fix available
A fix is available. Upgrade to after 2.3.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
In Apache Ignite 2.3 or earlier, the serialization mechanism does not have a list of classes allowed for serialization/deserialization, which makes it possible to run arbitrary code when 3-rd party vulnerable classes are present in Ignite classpath. The vulnerability can be exploited if the one sends a specially prepared form of a serialized object to one of the deserialization endpoints of some Ignite components - discovery SPI, Ignite persistence, Memcached endpoint, socket steamer.

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

In Apache Ignite 2.3 and earlier, the serialization mechanism lacks a whitelist of allowed classes, enabling remote code execution via malicious serialized objects sent to deserialization endpoints (discovery SPI, Ignite persistence, Memcached, socket streamer).

MitigationUpgrade to Apache Ignite 2.4 or later which implements class whitelisting for serialization; if immediate upgrade is not feasible, restrict network access to Ignite deserialization endpoints and audit the classpath for vulnerable serializable classes.

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:<= 2.3.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
High
Availability
High

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

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 version
    Locate the ignite-core JAR file in your deployment and check its version number, or run: java -cp ignite-core-*.jar org.apache.ignite.Ignition 2>&1 | grep -i version
    Affected if The installed version is 2.3.0 or earlier
  2. Verify deserialization endpoints are exposed
    Review your Ignite configuration (XML files or programmatic config) for enabled SPI implementations: DiscoverySpi, Memcached communication, or socket streaming. Check for open network listeners on ports used by these services (typically 47100 for discovery, 11211 for Memcached, or custom streamer ports)
    Affected if Any of these SPI endpoints are enabled and accessible on the network
  3. Confirm Ignite persistence is in use
    Examine your Ignite configuration for DataStorageConfiguration with persistence enabled, or check for 'setPersistenceEnabled(true)' in programmatic config
    Affected if Ignite native persistence is enabled and storing data to disk
  4. Check for deserialization consumer configurations
    Inspect your ignite.xml or configuration beans for 'TcpDiscoverySpi', 'TcpCommunicationSpi', or custom serializer settings that handle incoming serialized objects
    Affected if Any SPI or component is configured to accept and deserialize objects from untrusted sources

You are affected if Apache Ignite version is 2.3.0 or earlier AND any deserialization endpoint (discovery SPI, Memcached, socket streamer) or Ignite persistence is enabled and accessible on the network.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.3.0
Interim mitigation

Upgrade to Apache Ignite 2.4 or later which implements class whitelisting for serialization; if immediate upgrade is not feasible, restrict network access to Ignite deserialization endpoints and audit the classpath for vulnerable serializable classes.

Recommended fix High confidence

Apache Ignite 2.4.0 or later

  1. Download Apache Ignite 2.4.0 or later from the official Apache Ignite releases repository
  2. Stop all Ignite nodes and services that use the affected version
  3. Backup your existing Ignite configuration files and any persisted data
  4. Install the new Ignite 2.4.0+ binaries on all nodes
  5. Review and update Ignite configuration to ensure compatibility with 2.4.0+ (check XML configs, Spring beans, and programmatic configurations)
  6. Test the upgrade in a staging environment before deploying to production
  7. Deploy the upgraded Ignite nodes and restart services
  8. Verify that all deserialization endpoints (discovery SPI, persistence, Memcached, socket streamer) are functioning correctly
Caveat Upgrading may require review of custom serialization code and configuration changes; verify that any user-defined serialized objects remain compatible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ignite Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1295 — 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-2018-1295 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