CVE-2021-32053 is a medium-severity (CVSS 5.3) Uncontrolled Resource Consumption vulnerability in ca.uhn.hapi.fhir:hapi-fhir-jpaserver-base. A fix is available for ca.uhn.hapi.fhir:hapi-fhir-jpaserver-base — see the affected versions and patch details below.
Uncontrolled Resource Consumption in JPA Server in HAPI FHIR
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2021-32053 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
ca.uhn.hapi.fhir:hapi-fhir-jpaserver-baseReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | ca.uhn.hapi.fhir:hapi-fhir-jpaserver-base | all versions | 5.4.0ca.uhn.hapi.fhir:hapi-fhir-jpaserver-base:5.4.0 |
Affected Products
hapi fhirfhirDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ca.uhn.hapi.fhir:hapi-fhir-jpaserver-base, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ca.uhn.hapi.fhir:hapi-fhir-jpaserver-base to 5.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-32053 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2021-32053 in your dependencies?
Find it across Maven, including transitive dependencies.