The GitHub Personal Access Token (PAT) used by EasyBuild for the GitHub integration features (like --new-pr
, --from-pr
, etc.) is shown in plain text in EasyBuild debug log files.
Scope:
--upload-test-report
in combination with --from-pr
, nor in the installation logs that are copied to the software installation directories;--debug
, so it will not appear when using the default EasyBuild configuration (only info messages are logged by default);--from-pr
, but also via various other GitHub integration options like --new-pr
, --merge-pr
, --close-pr
, etc., but usually only appears in the temporary log file that is cleaned up automatically as soon as eb completes successfully;/tmp
(or a different location if you’ve set the --tmpdir
EasyBuild configuration option) on the systems where you use EasyBuild, but they are located in a subdirectory that is only accessible to your account (permissions set to 700);The issue is fixed with the changes in https://github.com/easybuilders/easybuild-framework/pull/3248.
This fix is included in EasyBuild v4.1.2 (released on Mon Mar 16th 2020), and in the master
+ develop
branches of the easybuild-framework
repository since Mon Mar 16th 2020 (see https://github.com/easybuilders/easybuild-framework/pull/3248 and https://github.com/easybuilders/easybuild-framework/pull/3249 resp.).
Make sure you revoke the existing GitHub tokens you’re using with EasyBuild (via https://github.com/settings/tokens), and install new ones using “eb --install-github-token --force
” (see also https://easybuild.readthedocs.io/en/latest/Integration_with_GitHub.html#installing-a-github-token-install-github-token).
/tmp
on the system(s) where you`re using EasyBuildeasybuild-framework
repositorygithub.com/easybuilders/easybuild-framework/commit/210743d0e3618a8ac0a56eb9c0f4fa4fd8ae53b9
github.com/easybuilders/easybuild-framework/pull/3248
github.com/easybuilders/easybuild-framework/pull/3249
github.com/easybuilders/easybuild-framework/security/advisories/GHSA-2wx6-wc87-rmjm
nvd.nist.gov/vuln/detail/CVE-2020-5262