Skip to content

HL7 FHIR IG Publisher potentially exposes GitHub repo user and credential information

Moderate severity GitHub Reviewed Published Jan 24, 2025 in HL7/fhir-ig-publisher • Updated Jan 24, 2025

Package

maven org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli (Maven)

Affected versions

< 1.8.9

Patched versions

1.8.9
maven org.hl7.fhir.publisher:org.hl7.fhir.publisher.core (Maven)
< 1.8.9
1.8.9

Description

Impact

In CI contexts, the IG Publisher CLI uses git commands to determine the URL of the originating repo. If the repo was cloned, or otherwise set to use a repo that uses a username and credential based URL, the entire URL will be included in the built Implementation Guide, exposing username and credential. This does not impact users that clone public repos without credentials, such as those using the auto-ig-build continuous integration infrastructure.

Patches

This problem has been patched in release 1.8.9

Workarounds

Users should update to 1.8.9 or the latest release

OR

Users should ensure the IG repo they are publishing does not have username or credentials included in the origin URL. Running the command git remote origin url should return a URL that contains no username, password, or token.

OR

Users should run the IG Publisher CLI with the -repo parameter and specify a URL that contains no username, password, or token.

References

@dotasek dotasek published to HL7/fhir-ig-publisher Jan 24, 2025
Published by the National Vulnerability Database Jan 24, 2025
Published to the GitHub Advisory Database Jan 24, 2025
Reviewed Jan 24, 2025
Last updated Jan 24, 2025

Severity

Moderate

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
Local
Attack complexity
Low
Privileges required
High
User interaction
Required
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:L/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(18th percentile)

Weaknesses

CVE ID

CVE-2025-24363

GHSA ID

GHSA-6729-95v3-pjc2

Source code

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