CVE-2024-6875: Infinispan: infinispan: rest compare api has buffer leak
A vulnerability was found in the Infinispan component in Red Hat Data Grid. The REST compare API may have a buffer leak and an out of memory error can occur when sending continual requests with large POST data to the REST API.
Security readout for executives and security teams
Plain-English summary
This issue can let an authenticated user exhaust memory in Red Hat Data Grid/JBoss Data Grid by repeatedly sending large POST requests to an affected REST compare API. The main business impact is service disruption, not data theft or tampering.
Executive priority
Treat as a service availability risk for systems relying on Red Hat Data Grid. It is not currently evidenced as exploited in the wild, but exposed authenticated REST APIs should be reviewed and patched on vendor guidance.
Technical view
CVE-2024-6875 is a CWE-401 memory leak in Infinispan’s REST compare API. The CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, reflecting network reachability, low complexity, required privileges, and high availability impact.
Likely exposure
Exposure is most likely where Red Hat Data Grid 8 or Red Hat JBoss Data Grid 7 exposes the Infinispan REST API to authenticated users or services. The source bundle does not identify exact fixed or vulnerable versions.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not listed as KEV. Abuse requires network access and some privileges, but the described failure mode can cause out-of-memory denial of service.
Researcher notes
Evidence identifies a buffer or memory leak in the REST compare API causing possible OOM under continual large POST data. Public source detail is limited; avoid assuming unauthenticated reachability, precise affected versions, or exploit maturity beyond the CVSS and description.
Mitigation direction
Check Red Hat’s CVE page and advisories for fixed package guidance.
Upgrade affected Red Hat Data Grid/JBoss Data Grid deployments when vendor fixes are available.
Restrict REST API access to required authenticated clients only.
Apply request size and rate controls where already supported by your platform.
Monitor affected services for memory growth and out-of-memory restarts.
Validation and detection
Inventory Red Hat Data Grid 8 and JBoss Data Grid 7 deployments.
Confirm whether the Infinispan REST API is enabled and reachable.
Review authentication paths for users or services allowed to POST to REST APIs.
Check vendor package versions against Red Hat guidance when available.
Review logs and metrics for memory pressure around large REST requests.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-401 · source CWE mapping
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.