Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2024-52007

HIGH

CVE-2024-52007 is a high-severity (CVSS 8.6) XML External Entity (XXE) vulnerability in ca.uhn.hapi.fhir:org.hl7.fhir.dstu3. O3 Security confirms whether CVE-2024-52007 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

XXE vulnerability in XSLT parsing in `org.hl7.fhir.core`

Also known asGHSA-gr3c-q7xf-47vh
Published
Nov 8, 2024
Updated
Jul 15, 2026
Affected
6 pkgs
Patched
6 / 6
Exploits
None indexed

Blast Radius

6 pkgs affected
ca.uhn.hapi.fhir:org.hl7.fhir.dstu3ca.uhn.hapi.fhir:org.hl7.fhir.r4ca.uhn.hapi.fhir:org.hl7.fhir.r4bca.uhn.hapi.fhir:org.hl7.fhir.r5ca.uhn.hapi.fhir:org.hl7.fhir.utilitiesca.uhn.hapi.fhir:org.hl7.fhir.dstu2016may

Real-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

HAPI FHIR is a complete implementation of the HL7 FHIR standard for healthcare interoperability in Java. XSLT parsing performed by various components are vulnerable to XML external entity injections. A processed XML file with a malicious DTD tag ( <!DOCTYPE foo [<!ENTITY example SYSTEM "/etc/passwd"> ]> could produce XML containing data from the host system. This impacts use cases where org.hl7.fhir.core is being used to within a host where external clients can submit XML. This is related to GHSA-6cr6-ph3p-f5rf, in which its fix (#1571 & #1717) was incomplete. This issue has been addressed in release version 6.4.0 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

Affected Packages

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
Mavenca.uhn.hapi.fhir:org.hl7.fhir.dstu3all versions6.4.0
Mavenca.uhn.hapi.fhir:org.hl7.fhir.r4all versions6.4.0
Mavenca.uhn.hapi.fhir:org.hl7.fhir.r4ball versions6.4.0
Mavenca.uhn.hapi.fhir:org.hl7.fhir.r5all versions6.4.0
Mavenca.uhn.hapi.fhir:org.hl7.fhir.utilitiesall versions6.4.0
Mavenca.uhn.hapi.fhir:org.hl7.fhir.dstu2016mayall versions6.4.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ca.uhn.hapi.fhir:org.hl7.fhir.dstu3. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update ca.uhn.hapi.fhir:org.hl7.fhir.dstu3 to 6.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-52007 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2024-52007 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2024-52007. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

HAPI FHIR is a complete implementation of the HL7 FHIR standard for healthcare interoperability in Java. XSLT parsing performed by various components are vulnerable to XML external entity injections. A processed XML file with a malicious DTD tag ( <!DOCTYPE foo [<!ENTITY example SYSTEM "/etc/passwd"> ]> could produce XML containing data from the host system. This impacts use cases where org.hl7.fhir.core is being used to within a host where external clients can submit XML. This is related to GHSA-6cr6-ph3p-f5rf, in which its fix (#1571 & #1717) was incomplete. This issue has been addressed in
O3 Security · Impact-Aware SCA

Is CVE-2024-52007 in your dependencies?

O3 detects CVE-2024-52007 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.