Skip to content

CI logs expose S3 object listing metadata #606

Closed

Description

@kongqing999

Finding

The traffic-light integration step in .github/workflows/build.yml runs aws s3 ls s3://stackql-trial-bucket-02 and echoes the captured listing into the workflow log. For qualifying runs on this public repository, that makes the bucket's object names and listing metadata publicly visible. Whether those names are sensitive depends on the bucket contents, so this is a potential metadata disclosure, not evidence that credentials were printed.

Requested change

Keep the empty/non-empty access check, but do not print the listing itself. The step already emits a success or failure message afterward.

Scope and evidence

The exact workflow step is Run traffic light robot integration tests in .github/workflows/build.yml. This review found no explicit logging of secret environment values in the workflow. The original report did not identify a location or provide a reproduction, and no linked PR from the reporter was found.

Activity

  1. changed the title [-]Security suggestion: avoid exposing sensitive information in CI logs[/-] [+]CI logs expose S3 object listing metadata[/+] on Nov 13, 2026
  2. self-assigned this
    on Nov 13, 2026
  3. jeffreyaven commented on Nov 13, 2026

    @jeffreyaven
    Member

    The referenced bucket is a test bucket. Its name is not sensitive, and our review found no evidence that the workflow explicitly logs credentials or other sensitive values. The output is the bucket listing used by the integration check.

    Closing as this is not identified a sensitive data exposure or an actionable issue. If a specific sensitive value in a workflow log is found, please open a new issue with the relevant run and log excerpt, with any secrets redacted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions