GHSA-mj96-mh85-r574
Suggest an improvement- Source
- https://github.com/advisories/GHSA-mj96-mh85-r574
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2025/07/GHSA-mj96-mh85-r574/GHSA-mj96-mh85-r574.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/GHSA-mj96-mh85-r574
- Published
- 2025-07-21T19:12:48Z
- Modified
- 2025-07-21T19:12:48Z
- Severity
-
- 8.7 (High) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N CVSS Calculator
- Summary
- buildalon/setup-steamcmd leaked authentication token in job output logs
- Details
-
Summary
Log output includes authentication token that provides full account access
Details
The post job action prints the contents of
config/config.vdfwhich holds the saved authentication token and can be used to sign in on another machine. This means any public use of this action leaves authentication tokes for the associated steam accounts publicly available. Additionally,userdata/$user_id$/config/localconfig.vdfcontains potentially sensitive information which should not be included in public logs.PoC
Use the following workflow step
steps: - name: Setup SteamCMD uses: buildalon/setup-steamcmd@v1.0.4 - name: Sign into steam shell: bash run: | steamcmd +login ${{ secrets.WORKSHOP_USERNAME }} ${{ secrets.WORKSHOP_PASSWORD }} +quitImpact
Anyone who has used this workflow action with a steam account is affected and has had valid authentication tokens leaked in the job logs. This is particularly bad for public repositories, as anyone with a GitHub account can access the logs and view the token.
- Database specific
{ "severity": "HIGH", "github_reviewed": true, "github_reviewed_at": "2025-07-21T19:12:48Z", "nvd_published_at": null, "cwe_ids": [ "CWE-532" ] }- References