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.
The product does not properly control the allocation and maintenance of a limited resource.
Link | Tags |
---|---|
https://hapifhir.io | vendor advisory |
https://github.com/hapifhir/hapi-fhir/issues/2641 | third party advisory |
https://github.com/hapifhir/hapi-fhir/pull/2642 | third party advisory patch |