dbcve.org
Data GridApplication · Redhat

CVE-2020-10771

HIGH · 7.1 CVSS v3.1 Published 2021-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
A flaw was found in Infinispan version 10, where it is possible to perform various actions that could have side effects using GET requests. This flaw allows an attacker to perform a cross-site request forgery (CSRF) attack.

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 confidence

Infinispan version 10 contains a CSRF vulnerability where attackers can trigger side effects via GET requests, allowing malicious cross-site request forgery attacks against authenticated users.

MitigationImplement anti-CSRF tokens, change state-changing GET endpoints to require POST requests, and enable Infinispan's built-in CSRF protection mechanisms.

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
Affected:= 8.0
Infinispan Server RestApplication
Affected:= 10.0.0
Oncommand InsightApplication
Affected:all versions

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
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/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 installed Infinispan or Red Hat Data Grid version
    Check the version of Infinispan Server or Red Hat Data Grid installed in your environment. For Infinispan, this may be visible in server logs, startup output, or the 'org.infinispan.core.version' property in the server's manifest. For Red Hat Data Grid, check via the management console or rpm/dpkg package manager.
    Affected if The installed version is 10.0.0.x for Infinispan Server Rest, or version 8.0 for Red Hat Data Grid.
  2. Verify REST endpoint exposure
    Check if the Infinispan/Red Hat Data Grid REST endpoint is exposed and accessible. Look for network listeners configured for port 8080 (default REST port) or custom REST connector configurations in the server.xml or infinispan.xml configuration files.
    Affected if The REST interface is exposed and reachable over HTTP/HTTPS without additional network segmentation.
  3. Confirm authentication is in use for REST API
    Determine if the REST API is configured to require authentication. Check server authentication configuration files for BASIC, DIGEST, or Bearer token authentication setup for the REST connector.
    Affected if Users authenticate to the REST API, because the CSRF attack targets authenticated sessions.
  4. Check for CSRF protection configuration
    Inspect the server security configuration for CSRF protection settings. In Infinispan, look for 'csrf' or 'cross-site' protection settings in the security configuration XML or the management console security settings.
    Affected if CSRF protection is NOT explicitly configured or is disabled, meaning the server relies on default vulnerable behavior.
  5. Identify NetApp OnCommand Insight installation
    Determine if NetApp OnCommand Insight software is installed in the environment. Check for the OCI installation directory, service processes, or installed software listings.
    Affected if NetApp OnCommand Insight is present in any version - all versions are affected by this CVE.

Your environment is affected if you have Infinispan Server REST 10.0.0.x, Red Hat Data Grid 8.0, or any version of NetApp OnCommand Insight exposed via REST without explicit CSRF protection, and users authenticate to these interfaces.

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

Implement anti-CSRF tokens, change state-changing GET endpoints to require POST requests, and enable Infinispan's built-in CSRF protection mechanisms.

Fix this in Data Grid Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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