GitHub PAT written to debug artifacts
HighCVE-2025-24362 · Published Jan 24, 2025 · updated Mar 5, 2025
### Impact summary In some circumstances, debug artifacts uploaded by the CodeQL Action after a failed code scanning workflow run may contain the environment variables from the workflow run, including any secrets that were exposed as environment variables to the workflow. Users with read access to the repository would be able to access this artifact, containing any secrets from the environment. For some affected workflow runs, the exposed environment variables in the debug artifacts included a valid `GITHUB_TOKEN` for the workflow run, which has access to the repository in which the workflow ran, and all the permissions specified in the workflow or job. The `GITHUB_TOKEN` is valid until the job completes or 24 hours has elapsed, whichever comes first. Environment variables are exposed only from workflow runs that satisfy all of the following conditions: - Code scanning workflow configured to scan the Java/Kotlin languages. - Running in a repository containing Kotlin source code. - Running with [debug artifacts enabled](https://docs.github.com/en/code-security/code-scanning/troubleshooting-code-scanning/logs-not-detailed-enough). - Using CodeQL Action versions <= 3.28.2, and Code...
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| CodeQL CLI Product | >= 2.9.2, < 2.20.3 | 2.20.3 |
| github/codeql-action Product | >= 3.26.11, < 3.28.3 | 3.28.3 |
Details and references
### Impact summary In some circumstances, debug artifacts uploaded by the CodeQL Action after a failed code scanning workflow run may contain the environment variables from the workflow run, including any secrets that were exposed as environment variables to the workflow. Users with read access to the repository would be able to access this artifact, containing any secrets from the environment. For some affected workflow runs, the exposed environment variables in the debug artifacts included a valid `GITHUB_TOKEN` for the workflow run, which has access to the repository in which the workflow ran, and all the permissions specified in the workflow or job. The `GITHUB_TOKEN` is valid until the job completes or 24 hours has elapsed, whichever comes first. Environment variables are exposed only from workflow runs that satisfy all of the following conditions: - Code scanning workflow configured to scan the Java/Kotlin languages. - Running in a repository containing Kotlin source code. - Running with [debug artifacts enabled](https://docs.github.com/en/code-security/code-scanning/troubleshooting-code-scanning/logs-not-detailed-enough). - Using CodeQL Action versions <= 3.28.2, and CodeQL CLI versions >= 2.9.2 (May 2022) and <= 2.20.2. - The workflow run fails before the CodeQL database is finalized within the `github/codeql-action/analyze` step. - Running in any GitHub environment: GitHub.com, GitHub Enterprise Cloud, and GitHub Enterprise Server. (Note: artifacts are only accessible to users within the same GitHub environment with access to the scanned repo.) The `GITHUB_TOKEN` exposed in this way would only have been valid for workflow runs that satisfy all of the following conditions, in addition to the conditions above: - Using CodeQL Action versions >= 3.26.11 (October 2024) and <= 3.28.2, or >= 2.26.11 and < 3. - Running in GitHub.com or GitHub Enterprise Cloud only (not valid on GitHub Enterprise Server). In rare cases during advanced setup, logging of environment variables may also occur during database creation of Java, Swift, and C/C++. Please read the corresponding CodeQL CLI advisory [GHSA-gqh3-9prg-j95m](https://github.com/github/codeql-cli-binaries/security/advisories/GHSA-gqh3-9prg-j95m) for more details. #### Impact on GitHub This vulnerability also affected an integration test workflow on the `github/codeql-action` repository that tested this debug functionality, exposing `GITHUB_TOKEN`s with write access to the repository for a brief window during each run of the workflow. This created a potential supply chain vulnerability, where modifications to the `github/codeql-action` repository (in particular its tagged release versions) would have been used in customer code scanning workflows. GitHub has found no evidence of compromise to its platform or systems through this method, except for the benign proof-of-concept used initially to demonstrate and report this vulnerability, which would not have affected the tagged release versions used by customer workflows. ### Impact details In CodeQL CLI versions >= 2.9.2 and <= 2.20.2, the CodeQL Kotlin extractor logs all environment variables by default into an intermediate file during the process of creating a CodeQL database for Kotlin code. This is a part of the CodeQL CLI and is invoked by the CodeQL Action for analyzing Kotlin repositories. On Actions, the environment variables logged include GITHUB_TOKEN, which grants permissions to the repository being scanned. The intermediate file containing environment variables is deleted when finalizing the database, so it is not included in a successfully created database. It is, however, included in the debug artifact that is uploaded on a failed analysis run if the CodeQL Action was invoked in debug mode. Therefore, under these specific circumstances (incomplete database creation using the CodeQL Action in debug mode) an attacker with access to the debug artifact would gain unauthorized
- Severity from
- GitHub (reviewed advisory)
More GitHub advisories
All GitHub| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Jul 17 | GitHub Enterprise Server: path traversal | High8.6 | No fix yet |
| Jul 17 | GitHub Enterprise Server: denial of service | Medium5.7 | No fix yet |
| Jul 1 | GitHub Enterprise Server: improper authorization | Medium5.3 | No fix yet |
| Jun 3 | CSP directive injection via sandbox, plugin_types, and report_to when given untrusted input | Medium4.7 | 7.3.0 |
| Jul 252024 | Arbitrary File Overwrite in CodeQL versions less than 2.18.1 | High | 2.18.1 |
| Feb 222024 | Limited data exfiltration in CodeQL CLI | Low2.7 | 2.16.3 |