wolfi-dev wolfictl up to 0.16.9 file access

Summaryinfo

A vulnerability was found in wolfi-dev wolfictl up to 0.16.9. It has been rated as problematic. Affected by this issue is some unknown functionality. The manipulation leads to file access. This vulnerability is documented as CVE-2024-35183. The attack needs to be performed locally. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in wolfi-dev wolfictl up to 0.16.9 and classified as problematic. This issue affects an unknown function. The manipulation with an unknown input leads to a file access vulnerability. Using CWE to declare the problem leads to CWE-552. The product makes files or directories accessible to unauthorized actors, even though they should not be. Impacted is confidentiality. The summary by CVE is:

wolfictl is a command line tool for working with Wolfi. A git authentication issue in versions prior to 0.16.10 allows a local user’s GitHub token to be sent to remote servers other than `github.com`. Most git-dependent functionality in wolfictl relies on its own `git` package, which contains centralized logic for implementing interactions with git repositories. Some of this functionality requires authentication in order to access private repositories. A central function `GetGitAuth` looks for a GitHub token in the environment variable `GITHUB_TOKEN` and returns it as an HTTP basic auth object to be used with the `github.com/go-git/go-git/v5` library. Most callers (direct or indirect) of `GetGitAuth` use the token to authenticate to github.com only; however, in some cases callers were passing this authentication without checking that the remote git repository was hosted on github.com. This behavior has existed in one form or another since commit 0d06e1578300327c212dda26a5ab31d09352b9d0 - committed January 25, 2023. This impacts anyone who ran the `wolfictl check update` commands with a Melange configuration that included a `git-checkout` directive step that referenced a git repository not hosted on github.com. This also impacts anyone who ran `wolfictl update ` with a remote URL outside of github.com. Additionally, these subcommands must have run with the `GITHUB_TOKEN` environment variable set to a valid GitHub token. Users should upgrade to version 0.16.10 to receive a patch.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2024-35183 since 05/10/2024. The exploitation is known to be difficult. Attacking locally is a requirement. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1083 according to MITRE ATT&CK.

Upgrading to version 0.16.10 eliminates this vulnerability. Applying the patch 0d06e1578300327c212dda26a5ab31d09352b9d0 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

• wolfi-dev

Name

• wolfictl

Version

• 0.16.0
• 0.16.1
• 0.16.2
• 0.16.3
• 0.16.4
• 0.16.5
• 0.16.6
• 0.16.7
• 0.16.8
• 0.16.9

License

• open-source

Website

• Product: https://github.com/wolfi-dev/wolfictl/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion