dbcve.org
Jboss Data GridApplication · Redhat

CVE-2018-1131

HIGH · 8.8 CVSS v3.0 Published 2018-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Infinispan permits improper deserialization of trusted data via XML and JSON transcoders under certain server configurations. A user with authenticated access to the server could send a malicious object to a cache configured to accept certain types of objects, achieving code execution and possible further attacks. Versions 9.0.3.Final, 9.1.7.Final, 8.2.10.Final, 9.2.2.Final, 9.3.0.Alpha1 are believed to be affected.

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

Infinispan contains an improper deserialization vulnerability in its XML and JSON transcoders. An authenticated attacker can send specially crafted serialized objects to caches configured to accept certain object types, potentially achieving arbitrary code execution on the server.

MitigationUpgrade Infinispan to a patched version or disable/restrict the XML and JSON transcoders for untrusted cache entries. If upgrading is not immediately possible, ensure caches are not configured to accept deserialized Java objects from user input.

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
Jboss Data GridApplication
Affected:= 7.2
InfinispanApplication
Affected:= 8.2.10= 9.0.3= 9.1.7= 9.2.2= 9.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/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 Infinispan or JBoss Data Grid version
    Locate the JAR file (infinispan-core.jar, jboss-datagrid-*.jar) or check the server startup logs for the exact version string. If using Maven, inspect the dependency tree for org.infinispan:infinispan-core with version 8.2.10, 9.0.3, 9.1.7, 9.2.2, or 9.3.0. For JBoss Data Grid, check for version 7.2.
    Affected if The installed version exactly matches 8.2.10, 9.0.3, 9.1.7, 9.2.2, 9.3.0 (Infinispan) or 7.2 (JBoss Data Grid)
  2. Locate XML transcoder configuration
    Search configuration files (infinispan.xml, standalone.xml, domain.xml) for the element <serialization> with <transcoders> or look for the class org.infinispan.server.core.security.sasl.Jboss SaslSupport. Also inspect any cache definitions with marshaller settings.
    Affected if XML transcoding is explicitly enabled and caches accept XML-encoded content from untrusted network sources
  3. Locate JSON transcoder configuration
    Search for JSON serialization configuration in Infinispan cache definitions or the presence of org.infinispan.query.json and related JSON transcoder classes on the classpath. Check for REST endpoints exposing caches.
    Affected if JSON transcoding is enabled and REST/Hot Rod endpoints expose caches that accept JSON input from clients
  4. Verify cache authorization and authentication settings
    Examine cache configuration XML or programmatic setup for <authorization> roles, <security> elements, or authentication domain settings. Determine if unauthenticated or low-privilege users can invoke cache operations.
    Affected if Caches are accessible to authenticated but low-privilege users who can trigger deserialization through XML or JSON inputs
  5. Inspect cache type configuration for Java object acceptance
    Review cache definitions for <type> handlers, custom serializers, or any configuration allowing Java objects to be deserialized. Check for <advanced- externalizers> or any registration of Java serialization handlers.
    Affected if Caches are configured to accept, store, or deserialize Java objects from user-supplied serialized content

Your environment is affected if you run any of the exact version matches (8.2.10, 9.0.3, 9.1.7, 9.2.2, 9.3.0 or 7.2) AND have XML or JSON transcoders exposed to untrusted inputs with caches accepting deserialized Java objects.

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

Upgrade Infinispan to a patched version or disable/restrict the XML and JSON transcoders for untrusted cache entries. If upgrading is not immediately possible, ensure caches are not configured to accept deserialized Java objects from user input.

Fix this in Jboss Data Grid Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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