Data GridApplication · Redhat
CVE-2020-25711
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 flaw was found in infinispan 10 REST API, where authorization permissions are not checked while performing some server management operations. When authz is enabled, any user with authentication can perform operations like shutting down the server without the ADMIN role.
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 REST API fails to enforce authorization checks for certain server management operations when authorization (authz) is enabled. Any user with valid authentication can perform privileged operations like server shutdown without possessing the required ADMIN role, resulting in an authorization bypass vulnerability.
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
Data GridApplication
= 8.0
Active Iq Unified ManagerApplication
all versions< 11.0.6CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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 installed Infinispan versionCheck the Infinispan server version by inspecting the startup logs, the lib directory, or by querying the REST API endpoint /rest/server metadata if availableAffected if The installed version is below 11.0.6, or is Red Hat Data Grid 8.0, or is any version of NetApp Active IQ Unified Manager
-
Locate the Infinispan configuration fileFind the infinispan.xml or cloud.xml configuration file typically located in the server/conf directory of the Infinispan installationAffected if Configuration file exists and the server is running with that configuration
-
Verify if authorization is enabledInspect the configuration XML for the <authorization> element or the security authorization configuration section - look for enabled="true" or similar authz settingsAffected if Authorization is explicitly enabled in the configuration (the vulnerability only applies when authz is enabled)
-
Confirm REST API endpoint exposureCheck if the REST connector is configured and exposed - look for <rest-connector> or <endpoint> configuration with REST protocol enabled, typically on port 8080 or 8443Affected if REST API endpoint is listening and accessible (the vulnerability affects REST API operations)
-
Review user role assignmentsExamine the users.properties or security REALM configuration to see what roles are assigned to authenticated users, specifically checking if non-admin users exist with valid credentialsAffected if Any authenticated user exists who does not have ADMIN role but could potentially access the REST API
You are affected if your Infinispan version is below 11.0.6 (or is Red Hat Data Grid 8.0 or NetApp Active IQ Unified Manager), authorization is enabled in configuration, and the REST API is exposed - then any authenticated user could potentially perform admin operations without proper role verification.
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 data11.0.6
Apply the vendor patch/upgrade to the fixed Infinispan version. As a defensive control, restrict network access to the Infinispan REST API to trusted users and networks until the patch is applied.
Fix this in Data Grid
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25711 — 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-2020-25711 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