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.
Threat-Mapped Scoring
Score: 0.0
Priority: Unclassified
EPSS
Score: 0.00073 Percentile:
0.2275
CVSS Scoring
CVSS v3.1 Score: 4.4
Severity: MEDIUM
Mapped CWE(s)
CWE-200
: Exposure of Sensitive Information to an Unauthorized Actor
CWE-214
: Invocation of Process Using Visible Sensitive Information
All CAPEC(s)
CAPEC-116: Excavation
CAPEC-13: Subverting Environment Variable Values
CAPEC-169: Footprinting
CAPEC-22: Exploiting Trust in Client
CAPEC-224: Fingerprinting
CAPEC-285: ICMP Echo Request Ping
CAPEC-287: TCP SYN Scan
CAPEC-290: Enumerate Mail Exchange (MX) Records
CAPEC-291: DNS Zone Transfers
CAPEC-292: Host Discovery
CAPEC-293: Traceroute Route Enumeration
CAPEC-294: ICMP Address Mask Request
CAPEC-295: Timestamp Request
CAPEC-296: ICMP Information Request
CAPEC-297: TCP ACK Ping
CAPEC-298: UDP Ping
CAPEC-299: TCP SYN Ping
CAPEC-300: Port Scanning
CAPEC-301: TCP Connect Scan
CAPEC-302: TCP FIN Scan
CAPEC-303: TCP Xmas Scan
CAPEC-304: TCP Null Scan
CAPEC-305: TCP ACK Scan
CAPEC-306: TCP Window Scan
CAPEC-307: TCP RPC Scan
CAPEC-308: UDP Scan
CAPEC-309: Network Topology Mapping
CAPEC-310: Scanning for Vulnerable Software
CAPEC-312: Active OS Fingerprinting
CAPEC-313: Passive OS Fingerprinting
CAPEC-317: IP ID Sequencing Probe
CAPEC-318: IP 'ID' Echoed Byte-Order Probe
CAPEC-319: IP (DF) 'Don't Fragment Bit' Echoing Probe
CAPEC-320: TCP Timestamp Probe
CAPEC-321: TCP Sequence Number Probe
CAPEC-322: TCP (ISN) Greatest Common Divisor Probe