Jboss Data GridApplication · Redhat
CVE-2023-3628
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's REST. Bulk read endpoints do not properly evaluate user permissions for the operation. This issue could allow an authenticated user to access information outside of their intended permissions.
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 REST API bulk read endpoints fail to properly evaluate authorization permissions, allowing authenticated users to access data outside their intended scope. This is an authorization bypass vulnerability where the permission check logic is missing or incorrect for bulk operations.
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
all versions
Jboss Enterprise Application PlatformApplication
= 6
Data GridApplication
< 8.4.4all versionsCVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 Infinispan or JBoss Data Grid installationLocate the Infinispan or JBoss Data Grid installation directory. Check for presence of infinispan-core.jar, standalone.xml, or the 'infinispan' service/process. Look for process names like 'infinispan', 'jdg', or 'jboss' running on typical ports (11222, 8080, 8443).Affected if The product is Infinispan Server, Red Hat JBoss Data Grid, Red Hat Data Grid, or Red Hat JBoss Enterprise Application Platform version 6, and REST API bulk read endpoints are accessible.
-
Determine installed versionCheck the version manifest or build information. For Infinispan, examine the 'org.infinispan.version' file in the server installation or run: bin/server.sh --version. For JBoss, check the version in the product.conf file or the JAR manifest files in the modules directory.Affected if The installed version matches one of the affected ranges: all versions of Redhat Jboss Data Grid, Redhat Jboss Enterprise Application Platform version 6 exactly, Redhat Data Grid versions before 8.4.4, or all versions of Infinispan.
-
Verify REST API bulk operations are enabledCheck the server configuration (typically standalone.xml, infinispan.xml, or boot.xml) for the presence and configuration of the REST endpoint. Look for <rest-connector> or <endpoints> configuration sections. Confirm whether the REST API is bound to a network-accessible interface.Affected if REST connector is enabled and bound to a non-localhost interface, allowing network access to bulk read endpoints such as /rest/v2/caches/{cacheName} with bulk read parameters.
-
Review authorization configuration for cache accessInspect the authorization configuration in the Infinispan/JBoss configuration file. Look for <authorization> sections within <cache> or <cache-container> definitions. Check if role mappings are properly defined for the security realm or authentication mechanism in use.Affected if Authorization is configured but the bulk operation permission checks are missing or incorrectly implemented, allowing authenticated users to read data from caches they should not have access to.
-
Audit access logs for unauthorized bulk data accessReview server access logs (typically in logs/ directory) for REST API requests to bulk endpoints. Look for patterns where authenticated users accessed multiple cache entries or caches outside their expected permissions. Search for requests to /rest/v2/caches/* with query parameters indicating bulk operations.Affected if Logs show authenticated users successfully retrieving data from caches or entries outside their assigned role permissions via bulk read operations.
The environment is affected if Infinispan Server, Red Hat JBoss Data Grid, Red Hat Data Grid (before 8.4.4), or Red Hat JBoss EAP 6 is running with the REST API bulk read endpoints enabled and accessible to authenticated users.
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.
dbcve · scoped8.4.4
Apply vendor-provided patches for Infinispan. Review and restrict user permissions to minimum required access. Audit access logs for unauthorized data access attempts.
Infinispan 14.0.21+ or JBoss Data Grid 8.4.4+
- 1. Identify the specific Infinispan or JBoss Data Grid version currently deployed
- 2. For Infinispan: Upgrade to version 14.0.21 or later which contains the security fix for this permission bypass vulnerability
- 3. For JBoss Data Grid: Upgrade to version 8.4.4 or later which includes the patched Infinispan libraries
- 4. For JBoss Enterprise Application Platform 6: Apply the appropriate RHSA security advisory patch from Red Hat
- 5. After upgrade, verify that REST bulk read operations properly enforce authorization checks
- 6. Test that users can only access data they are explicitly permitted to read
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jboss Data Grid
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3628 — 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-2023-3628 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