JPA Server in HAPI FHIR before 5.4.0 allows a user to deny service (e.g., disable access to the database after the attack stops) via history requests. This occurs because of a SELECT COUNT statement that requires a full index scan, with an accompanying large amount of server resources if there are many simultaneous history requests.
                
            Metrics
Affected Vendors & Products
Advisories
    | Source | ID | Title | 
|---|---|---|
  EUVD | 
                EUVD-2021-1274 | JPA Server in HAPI FHIR before 5.4.0 allows a user to deny service (e.g., disable access to the database after the attack stops) via history requests. This occurs because of a SELECT COUNT statement that requires a full index scan, with an accompanying large amount of server resources if there are many simultaneous history requests. | 
  Github GHSA | 
                GHSA-67f6-c8mx-4q2m | Uncontrolled Resource Consumption in JPA Server in HAPI FHIR | 
Fixes
    Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
        History
                    No history.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-03T23:17:28.817Z
Reserved: 2021-05-05T00:00:00
Link: CVE-2021-32053
No data.
Status : Modified
Published: 2021-05-10T21:15:07.883
Modified: 2024-11-21T06:06:46.340
Link: CVE-2021-32053
No data.
                        OpenCVE Enrichment
                    No data.
 EUVD
 Github GHSA