CWE
200 214
Advisory Published
Updated

CVE-2021-32638: CodeQL runner: Command-line options that make GitHub access tokens visible to other processes are now deprecated

First published: Tue May 25 2021(Updated: )

Github's CodeQL action is provided to run CodeQL-based code scanning on non-GitHub CI/CD systems and requires a GitHub access token to connect to a GitHub repository. The runner and its documentation previously suggested passing the GitHub token as a command-line parameter to the process instead of reading it from a file, standard input, or an environment variable. This approach made the token visible to other processes on the same machine, for example in the output of the `ps` command. If the CI system publicly exposes the output of `ps`, for example by logging the output, then the GitHub access token can be exposed beyond the scope intended. Users of the CodeQL runner on 3rd-party systems, who are passing a GitHub token via the `--github-auth` flag, are affected. This applies to both GitHub.com and GitHub Enterprise users. Users of the CodeQL Action on GitHub Actions are not affected. The `--github-auth` flag is now considered insecure and deprecated. The undocumented `--external-repository-token` flag has been removed. To securely provide a GitHub access token to the CodeQL runner, users should **do one of the following instead**: Use the `--github-auth-stdin` flag and pass the token on the command line via standard input OR set the `GITHUB_TOKEN` environment variable to contain the token, then call the command without passing in the token. The old flag remains present for backwards compatibility with existing workflows. If the user tries to specify an access token using the `--github-auth` flag, there is a deprecation warning printed to the terminal that directs the user to one of the above options. All CodeQL runner releases codeql-bundle-20210304 onwards contain the patches. We recommend updating to a recent version of the CodeQL runner, storing a token in your CI system's secret storage mechanism, and passing the token to the CodeQL runner using `--github-auth-stdin` or the `GITHUB_TOKEN` environment variable. If still using the old flag, ensure that process output, such as from `ps`, is not persisted in CI logs.

Credit: security-advisories@github.com

Affected SoftwareAffected VersionHow to fix
Github Codeql Action<20210304

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.

Frequently Asked Questions

  • What is CVE-2021-32638?

    CVE-2021-32638 is a vulnerability in Github's CodeQL action that allows the GitHub token to be passed as a command-line parameter, potentially exposing it to unauthorized access.

  • What is the severity of CVE-2021-32638?

    CVE-2021-32638 has a severity level of medium with a CVSS score of 4.4.

  • How does CVE-2021-32638 affect software?

    CVE-2021-32638 affects the Github CodeQL action version up to exclusive 20210304.

  • How can I fix CVE-2021-32638?

    To fix CVE-2021-32638, update to a version of the Github CodeQL action that includes the fixes introduced in the codeql-bundle-20210304 release.

  • What are the CWEs associated with CVE-2021-32638?

    CVE-2021-32638 is associated with CWE-200 (Information Exposure) and CWE-214 (Sensitive Information Prone to Unauthorized Access).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203