Harden GitHub Actions Workflow - install-tests.yml

[stepsecurity-app]

Summary

This issue is created by StepSecurity related to security issues in install-tests.yml . The platform has identified 1 vulnerability (1 critical, 0 high, 0 medium, 0 low).

Remediation Overview

The platform can generate remediations for a few vulnerabilities. For such vulnerabilities, you can find the fixed workflow file in the Suggested Fix For Auto-Remediable Issues section. You can manually deploy these changes or create a pull request by commenting @stepsecurity-app pull-request create on this issue.

If you’d like an automated pull request with the fixed workflow file, comment:

@stepsecurity-app pull-request create

Other issues require manual investigation and changes.

Once a vulnerability has been remediated, ✅ will appear in the title. Note that it may take up to 24 hours for these issues to be updated.

Please review the individual vulnerability section below and follow the recommended resolution steps.

Security Checks Details

❌ Actions should be pinned to a full-length commit SHA

• Severity: Critical

• Description: GitHub Action tags and Docker tags are mutable. This poses a security risk. GitHub's Security Hardening guide recommends pinning actions to full length commit.

• Resolution: Pin Actions to a full-length commit SHA..

• Automated Remediation Available ?: true

• References:

  • GitHub Security Guide

  • The Open Source Security Foundation (OpenSSF) Security Guide

Suggested Fix For Auto-Remediable Issues

Below is the updated workflow, which fixes the following security vulnerabilities:

• Actions should be pinned to a full-length commit SHA

  name: Installation tests
  on: [push]
  jobs:
    build:
      strategy:
        fail-fast: false
        max-parallel: 1
        matrix:
          platform: [ubuntu-latest, macos-latest, windows-latest]
          node-version: [16.x, 18.x, 20.x]
      runs-on: ${{ matrix.platform }}
      steps:
      - uses: actions/checkout@
+ a37ce9120846195fa4ece8f58b268e6043cb2f26 # 
  v3
+ .7.0
      - name: Use Node.js ${{ matrix.node-version }} on ${{ matrix.platform }}
        uses: actions/setup-node@
+ 3235b876344d2a9aa001b8d1453c930bba69e610 # 
  v3
+ .9.1
        with:
          node-version: ${{ matrix.node-version }}
      - run: npm link sol2uml --only=production
      - name: KoiosECDSA class
        run: sol2uml class 0x2762e676a9f17c7de34fe4b124424837c7e18e1c -v
        env:
          NODE_URL: ${{ secrets.NODE_URL }}
      - name: KoiosECDSA storage
        run: sol2uml storage 0x2762e676a9f17c7de34fe4b124424837c7e18e1c -v
        env:
          NODE_URL: ${{ secrets.NODE_URL }}
      - name: Resonate Fantom flatten
        run: sol2uml flatten --network fantom 0x1a5c2ee3fb7fe4a2c2e42474a3657c71f6c775cf -v
        env:
          NODE_URL: ${{ secrets.NODE_URL }}
      - name: Diff OUSD VaultCore upgrade
        run: sol2uml diff 0x48Cf14DeA2f5dD31c57218877195913412D3278A 0x997c35A0bf8E21404aE4379841E0603C957138c3 -v
        env:
          NODE_URL: ${{ secrets.NODE_URL }}

Additional Information

For more information, refer to the documentation page here.
Please don't make any changes in the description as the platform makes automated updates in description. Please use the comment section below to provide input.

Automated remediation commands and options

• Create a pull request with automated security fixes

@stepsecurity-app pull-request create

• Close this issue and prevent it from being reopened

@stepsecurity-app issue close <REASON>

• Update issue description with latest security check status

@stepsecurity-app issue force-update

• View all available commands and their usage

@stepsecurity-app help

Which GitHub Actions security best practices were evaluated?

The workflow was evaluated for the following GitHub Actions security best practices:

• Network & runtime security monitoring
• Token permissions
• Third‐party GitHub Actions usage & pinning