Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

GitHub Actions package

rageagainstthepixel/setup-steamcmd

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.7GitHub ActionsPublished

    RageAgainstThePixel/setup-steamcmd leaked authentication token in job output logs

    GHSA-c5qx-p38x-qf5w

    Affected
    • GitHub Actions rageagainstthepixel/setup-steamcmd < 1.3.0
    Fixed in
    1.3.0· Vendor fix available
    Issue
    Log output includes authentication token that provides full account access Details The 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/$userid$/config/localconfig.vdf contains potentially sensitive information which should not be included in public logs. PoC Use the following workflow step Impact 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.

    Recommended action: Upgrade to 1.3.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →