{"answers":{"affected":"1 open source package ship an affected version, including RageAgainstThePixel/setup-steamcmd.","exploited":"There is no known exploitation of GHSA-c5qx-p38x-qf5w in the wild and no public exploit code.","fix":"Upgrade RageAgainstThePixel/setup-steamcmd to 1.3.0 or later.","what":"GHSA-c5qx-p38x-qf5w is a vulnerability in RageAgainstThePixel/setup-steamcmd, published on 21 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-c5qx-p38x-qf5w and fix it if it is affected.\n\nWhat it is: GHSA-c5qx-p38x-qf5w is a vulnerability in RageAgainstThePixel/setup-steamcmd, published on 21 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-c5qx-p38x-qf5w in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- RageAgainstThePixel/setup-steamcmd (GitHub Actions): affected all versions; fixed in 1.3.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-c5qx-p38x-qf5w/ (Markdown: https://insights.sbomify.com/GHSA-c5qx-p38x-qf5w/index.md)","id":"GHSA-c5qx-p38x-qf5w","markdown":"https://insights.sbomify.com/GHSA-c5qx-p38x-qf5w/index.md","name":"GHSA-c5qx-p38x-qf5w","record":{"aliases":[],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"GitHub Actions","requires_auth":"none","summary":"The setup-steamcmd action leaks Steam authentication tokens in public logs, allowing attackers to hijack accounts and access sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Summary\nLog output includes authentication token that provides full account access\n\n### Details\nThe post job action prints the contents of `config/config.vdf` which 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.vdf` contains potentially sensitive information which should not be included in public logs.\n\n### PoC\nUse the following workflow step\n```\nsteps:\n      - name: Setup SteamCMD\n        uses: buildalon/setup-steamcmd@v1.0.4\n\n      - name: Sign into steam\n        shell: bash\n        run: |\n          steamcmd +login ${{ secrets.WORKSHOP_USERNAME }} ${{ secrets.WORKSHOP_PASSWORD }} +quit\n```\n\n### Impact\nAnyone 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.","ecosystems":["GitHub Actions"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"RageAgainstThePixel/setup-steamcmd leaked authentication token in job output logs","id":"GHSA-c5qx-p38x-qf5w","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"GitHub Actions","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"GitHub Actions","fixed":["1.3.0"],"introduced":["0"],"last_affected":[],"package":"RageAgainstThePixel/setup-steamcmd","purl":null,"source":"GHSA-c5qx-p38x-qf5w"}],"products":null,"published":"2025-07-21","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"The setup-steamcmd action leaks Steam authentication tokens in public logs, allowing attackers to hijack accounts and access sensitive data.","url":"https://insights.sbomify.com/GHSA-c5qx-p38x-qf5w/"}