CVE-2019-10174
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 · uneditedA vulnerability was found in Infinispan such that the invokeAccessibly method from the public class ReflectionUtil allows any application class to invoke private methods in any class with Infinispan's privileges. The attacker can use reflection to introduce new, malicious behavior into the application.
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 · moderate confidenceInfinispan's ReflectionUtil class contains an invokeAccessibly method that allows any application class to bypass Java's access control mechanisms and invoke private methods in any class with Infinispan's privileges. This reflection-based authorization bypass enables attackers to call privileged methods and inject malicious behavior into the application.
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= 1.0all versionsall versions= 7.2all versionsall versionsall versions< 8.2.12>= 9.0.0, < 9.4.17CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Infinispan or affected Red Hat products are in useCheck for presence of Infinispan libraries (infinispan-core*.jar, infinispan-*.jar) in the application classpath or deployed modules. For Red Hat products, check installed product directories for JBoss Data Grid, JBoss EAP, Fuse, Openshift Application Runtimes, or Single Sign On installations.Affected if Infinispan libraries or any affected Red Hat product is deployed in the environment
-
Determine the installed Infinispan versionLocate the infinispan-core or infinispan JAR file in the classpath or module directory and check its version metadata (MANIFEST.MF or filename). For Red Hat products, check the version of the bundled Infinispan module in the product's lib or modules directory.Affected if The Infinispan version is < 8.2.12, OR >= 9.0.0 AND < 9.4.17, OR the product is any version of Red Hat JBoss Data Grid, JBoss EAP, Fuse 1.0, Openshift Application Runtimes, or Single Sign On
-
Check if the ReflectionUtil class is accessibleSearch for the ReflectionUtil class in the deployed Infinispan JAR files. Verify it contains the invokeAccessibly method by inspecting the compiled class or source if available.Affected if The ReflectionUtil class with invokeAccessibly method exists in the deployed Infinispan libraries
-
Verify the vulnerability is exploitableDetermine if the application exposes deserialization endpoints, allows user-controlled data to reach Infinispan's reflection mechanisms, or uses Infinispan's remote query/features that could invoke the vulnerable method. Check configuration files (infinispan.xml, standalone.xml) for exposed remoting or Hot Rod endpoints.Affected if The application has exposed network endpoints or data paths that could allow an attacker to trigger the invokeAccessibly method with malicious input
The environment is affected if Infinispan or any affected Red Hat product is deployed with a version in the vulnerable ranges and the application has attack surface that could reach the ReflectionUtil.invokeAccessibly method.
Generated from the published advisory. Verify against your own configuration.
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 data8.2.129.4.17
Upgrade to a patched version of Infinispan that properly restricts the invokeAccessibly method; apply vendor-supplied patches or updates as they become available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10174 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10174 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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