CVE-2023-3629
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, Cache retrieval endpoints do not properly evaluate the necessary admin 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 and cache retrieval endpoints fail to properly evaluate admin permissions required for certain operations. This authorization bypass allows authenticated users to access data or endpoints outside their intended permission scope, potentially exposing sensitive cached information to unauthorized users.
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< 8.4.4all versions= 6all 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 application server installation directory or identify running Java processes containing 'infinispan', 'datagrid', or 'jboss' in the process arguments. Check common paths such as /opt/jboss/, /opt/infinispan/, or the application's lib directory.Affected if Infinispan, Red Hat Data Grid, or JBoss Data Grid is installed and running
-
Determine the installed versionCheck the version manifest or version file in the installation directory. For Red Hat Data Grid, look for a version file or check the RPM package version. For Infinispan, check the JAR manifest or pom.xml if available in the distribution.Affected if Version is Infinispan all versions, Red Hat Data Grid < 8.4.4, or any version of Red Hat JBoss Data Grid or JBoss EAP 6
-
Verify REST or cache retrieval endpoints are exposedCheck server configuration files (such as server.conf, web.xml, or the Infinispan server.xml) for REST connector definitions or cache endpoint configurations. Look for lines containing 'rest-connector', 'restEndpoint', or similar REST-related settings.Affected if REST endpoints or cache retrieval endpoints are enabled in the server configuration
-
Confirm endpoint accessibility from networkAttempt a local curl or HTTP request to common REST endpoints such as /rest/v2/cache/{cacheName} or /api/v2/caches to verify the endpoints are reachable and responding.Affected if REST or cache retrieval endpoints respond to HTTP requests without requiring explicit admin authorization checks
-
Review role-based access control configurationInspect the authorization configuration files (often in infinispan.xml, jboss-web.xml, or the security subsystem configuration) to determine what roles are assigned to the REST endpoint operations and whether permission checks are enforced.Affected if Authorization roles are defined but not properly enforced on REST cache retrieval operations, or admin permissions are not required for sensitive cache access
Your environment is affected if Infinispan, Red Hat Data Grid, or JBoss Data Grid is running with REST endpoints enabled and the installed version falls within the affected ranges, particularly if role-based access control may not be properly enforcing admin permissions on cache retrieval operations.
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
Upgrade to the patched version of Infinispan that properly enforces permission checks on REST cache retrieval endpoints. Review and configure role-based access control (RBAC) settings to ensure users have only the minimum necessary permissions.
Infinispan: 14.0.21+ or latest stable | Red Hat Data Grid: 8.4.4+
- 1. Identify the current version of Infinispan or Red Hat Data Grid in use
- 2. For Data Grid users: Upgrade to version 8.4.4 or later which contains the fix for proper admin permission evaluation
- 3. For Infinispan users: Upgrade to version 14.0.21 or later (or the latest stable release) which addresses the permission evaluation issue
- 4. Verify the upgrade by testing cache retrieval operations with non-admin users to confirm proper permission enforcement
- 5. Review role-based access control (RBAC) configurations to ensure they align with the fixed version's security model
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3629 — 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-3629 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