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.
References
Link | Resource |
---|---|
https://github.com/hapifhir/hapi-fhir/issues/2641 | Third Party Advisory |
https://github.com/hapifhir/hapi-fhir/pull/2642 | Patch Third Party Advisory |
https://hapifhir.io | Vendor Advisory |
https://github.com/hapifhir/hapi-fhir/issues/2641 | Third Party Advisory |
https://github.com/hapifhir/hapi-fhir/pull/2642 | Patch Third Party Advisory |
https://hapifhir.io | Vendor Advisory |
Configurations
History
21 Nov 2024, 06:06
Type | Values Removed | Values Added |
---|---|---|
References | () https://github.com/hapifhir/hapi-fhir/issues/2641 - Third Party Advisory | |
References | () https://github.com/hapifhir/hapi-fhir/pull/2642 - Patch, Third Party Advisory | |
References | () https://hapifhir.io - Vendor Advisory |
Information
Published : 2021-05-10 21:15
Updated : 2024-11-21 06:06
NVD link : CVE-2021-32053
Mitre link : CVE-2021-32053
CVE.ORG link : CVE-2021-32053
JSON object : View
Products Affected
fhir
- hapi_fhir
CWE
CWE-400
Uncontrolled Resource Consumption