HL7 FHIR Partial Path Zip Slip due to bypass of CVE-2023-24057

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2023-28465: 1.30% estimated exploitation activity in the next 30 days; percentile 70.48 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Zip Slip protections implemented in CVE-2023-24057 (GHSA-jqh6-9574-5x22) can be bypassed due a partial path traversal vulnerability. This issue allows a malicious actor to potentially break out of the TerminologyCacheManager cache directory. The impact is limited to sibling directories. To demonstrate the vulnerability, consider userControlled.getCanonicalPath().startsWith("/usr/out") will allow an attacker to access a directory with a name like /usr/outnot. Why? To demonstrate this vulnerability, consider "/usr/outnot".startsWith("/usr/out"). The check is bypassed although /outnot is not under the /out directory. It's important to understand that the terminating slash may be removed when using various String representations of the File object. For example, on Linux, println(new File("/var")) will print /var, but println(new File("/var", "/") will print /var/; however, println(new File("/var", "/").getCanonicalPath()) will print /var. The Fix Comparing paths with the…

Published by the source

10 Mar 2023, 22:15 UTC

Last modified by the source

15 Dec 2023, 22:19 UTC

Source last checked

26 Oct 2026, 16:21 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9654-pr4f-gh6m

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-28465

Advisory: HL7 FHIR Partial Path Zip Slip due to bypass of CVE-2023-24057
IDs: CVE-2023-28465, GHSA-9654-pr4f-gh6m
Record: https://patchnext.com/advisories/cve-2023-28465 (revision 1, source checked 26 Oct 2026, 16:21 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: ca.uhn.hapi.fhir:org.hl7.fhir.convertors 5.6.106; ca.uhn.hapi.fhir:org.hl7.fhir.validation 5.6.106; ca.uhn.hapi.fhir:org.hl7.fhir.r4b 5.6.106; ca.uhn.hapi.fhir:org.hl7.fhir.utilities 5.6.106; ca.uhn.hapi.fhir:org.hl7.fhir.core 5.6.106; ca.uhn.hapi.fhir:org.hl7.fhir.r5 5.6.106. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven ca.uhn.hapi.fhir:org.hl7.fhir.convertors: affected < 5.6.106; fixed in 5.6.106
- Maven ca.uhn.hapi.fhir:org.hl7.fhir.validation: affected < 5.6.106; fixed in 5.6.106
- Maven ca.uhn.hapi.fhir:org.hl7.fhir.r4b: affected < 5.6.106; fixed in 5.6.106
- Maven ca.uhn.hapi.fhir:org.hl7.fhir.utilities: affected < 5.6.106; fixed in 5.6.106
- Maven ca.uhn.hapi.fhir:org.hl7.fhir.core: affected < 5.6.106; fixed in 5.6.106
- Maven ca.uhn.hapi.fhir:org.hl7.fhir.r5: affected < 5.6.106; fixed in 5.6.106

## Suggested inspection (read-only)
- Maven ca.uhn.hapi.fhir:org.hl7.fhir.convertors: check the installed version with your package manager.
- Maven ca.uhn.hapi.fhir:org.hl7.fhir.validation: check the installed version with your package manager.
- Maven ca.uhn.hapi.fhir:org.hl7.fhir.r4b: check the installed version with your package manager.
- Maven ca.uhn.hapi.fhir:org.hl7.fhir.utilities: check the installed version with your package manager.
- Maven ca.uhn.hapi.fhir:org.hl7.fhir.core: check the installed version with your package manager.
- Maven ca.uhn.hapi.fhir:org.hl7.fhir.r5: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ca.uhn.hapi.fhir:org.hl7.fhir.convertors, ca.uhn.hapi.fhir:org.hl7.fhir.validation, ca.uhn.hapi.fhir:org.hl7.fhir.r4b, ca.uhn.hapi.fhir:org.hl7.fhir.utilities, ca.uhn.hapi.fhir:org.hl7.fhir.core, ca.uhn.hapi.fhir:org.hl7.fhir.r5.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9654-pr4f-gh6m (GitHub-reviewed advisory GHSA-9654-pr4f-gh6m lists affected ranges: Maven ca.uhn.hapi.fhir:org.hl7.fhir.core >=0 =0 =0 =0 =0 =0 <5.6.106)

Commands are suggestions: review each one before running it.