dbcve.org
Hl7 Fhir CoreApplication · Hapifhir

CVE-2023-28465

HIGH · 7.5 CVSS v3.1 Published 2023-12-12
Fix available
A fix is available. Upgrade to 5.6.106 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The package-decompression feature in HL7 (Health Level 7) FHIR Core Libraries before 5.6.106 allows attackers to copy arbitrary files to certain directories via directory traversal, if an allowed directory name is a substring of the directory name chosen by the attacker. NOTE: this issue exists because of an incomplete fix for CVE-2023-24057.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

HL7 FHIR Core Libraries before version 5.6.106 contain a directory traversal vulnerability in the package-decompression feature. Attackers can write arbitrary files to directories outside the intended extraction path by using directory names that contain the allowed directory name as a substring, bypassing existing security checks. This is an incomplete fix for CVE-2023-24057.

MitigationUpgrade HL7 FHIR Core Libraries to version 5.6.106 or later to obtain the complete fix for this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Hl7 Fhir CoreApplication
Affected:< 5.6.106

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed version of Hapifhir HL7 FHIR Core library
    Locate the hapi-fhir-core library in your project dependencies (Maven pom.xml, Gradle build.gradle, or JAR file manifest) and note the exact version number
    Affected if The version is below 5.6.106 (for example, 5.6.0, 5.5.0, etc.)
  2. Locate decompression-related code using HAPI FHIR libraries
    Search your codebase for usage of FHIR resource bundle reading or PackageArchive class methods that handle compression (look for imports like org.hl7.fhir.r4b.utils.zip, PackageArchive, or methods related to extracting resources from packages)
    Affected if Your application processes compressed FHIR bundles or uses the package-decompression feature from HAPI FHIR libraries
  3. Identify decompression input sources
    Review where compressed FHIR packages (such as NPM packages or expansion profiles) are loaded from and trace the extraction flow in your application logs and code
    Affected if Compressed packages from untrusted or external sources are being processed by your application without additional validation
  4. Check for path validation in decompression logic
    Examine your application logs and behavior when processing package archives with directory structures; note whether the extraction path allows traversal outside the intended target directory
    Affected if The application permits extraction paths that could escape the designated directory (for example, paths containing the allowed directory name as a substring)

You are affected if you are using Hapifhir HL7 FHIR Core version below 5.6.106 AND your application processes compressed FHIR packages using the package-decompression feature from this library.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.6.106 or later
Fixed in 5.6.106
Interim mitigation

Upgrade HL7 FHIR Core Libraries to version 5.6.106 or later to obtain the complete fix for this vulnerability.

Recommended fix High confidence

HL7 FHIR Core version 5.6.106

  1. Upgrade HL7 FHIR Core Libraries to version 5.6.106 or later
  2. Verify the installed version matches or exceeds 5.6.106
  3. Rebuild and redeploy any applications or services that depend on the HL7 FHIR Core Libraries
  4. Test package-decompression functionality to confirm the path traversal vulnerability is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hl7 Fhir Core Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28465 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-28465 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data