GHSA-6729-95v3-pjc2: Infoleak

First published: Fri Jan 24 2025(Updated: )

### 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](https://github.com/HL7/fhir-ig-publisher/releases/tag/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.

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

• agent/severity
• agent/source
• agent/softwarecombine
• agent/description
• agent/first-publish-date
• agent/type
• agent/event
• collector/github-advisory-latest
• source/GitHub
• alias/GHSA-6729-95v3-pjc2
• alias/CVE-2025-24363
• agent/software-canonical-lookup
• agent/references
• agent/weakness
• agent/last-modified-date
• agent/tags
• package-manager/maven