Skip to content

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

High severity GitHub Reviewed Published Mar 10, 2023 in hapifhir/org.hl7.fhir.core • Updated Dec 15, 2023

Package

maven ca.uhn.hapi.fhir:org.hl7.fhir.convertors (Maven)

Affected versions

< 5.6.106

Patched versions

5.6.106
maven ca.uhn.hapi.fhir:org.hl7.fhir.core (Maven)
< 5.6.106
5.6.106
maven ca.uhn.hapi.fhir:org.hl7.fhir.r4b (Maven)
< 5.6.106
5.6.106
maven ca.uhn.hapi.fhir:org.hl7.fhir.r5 (Maven)
< 5.6.106
5.6.106
maven ca.uhn.hapi.fhir:org.hl7.fhir.utilities (Maven)
< 5.6.106
5.6.106
maven ca.uhn.hapi.fhir:org.hl7.fhir.validation (Maven)
< 5.6.106
5.6.106

Description

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 java.nio.files.Path#startsWith will adequately protect againts this vulnerability.

For example: file.getCanonicalFile().toPath().startsWith(BASE_DIRECTORY) or file.getCanonicalFile().toPath().startsWith(BASE_DIRECTORY_FILE.getCanonicalFile().toPath())

Other Examples

Vulnerability

https://github.com/hapifhir/org.hl7.fhir.core/blob/b0daf666725fa14476d147522155af1e81922aac/org.hl7.fhir.r4b/src/main/java/org/hl7/fhir/r4b/terminologies/TerminologyCacheManager.java#L99-L105

While getAbsolutePath will return a normalized path, because the string path is not slash terminated, the guard can be bypassed to write the contents of the Zip file to a sibling directory of the cache directory.

Patches

All org.hl7.fhir.core libraries should be updated to 5.6.106.

Workarounds

Unknown

References

References

@dotasek dotasek published to hapifhir/org.hl7.fhir.core Mar 10, 2023
Published to the GitHub Advisory Database Mar 10, 2023
Reviewed Mar 10, 2023
Published by the National Vulnerability Database Dec 12, 2023
Last updated Dec 15, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.064%
(29th percentile)

Weaknesses

CVE ID

CVE-2023-28465

GHSA ID

GHSA-9654-pr4f-gh6m

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.