GHSA-4jhj-3gv3-c3gr: Github.com/go vela/cli CLI For Vela Insecure Variable Vulnerability

HIGH
CVSS 7.7
Published
Advisory Summary

GHSA-4jhj-3gv3-c3gr is a HIGH (CVSS 7.7) cli for vela insecure variable vulnerability (General Security Weakness) affecting Github.com/go vela/cli libraries in the Go ecosystem. The issue involves cli for vela insecure variable substitution. Remediation is available by upgrading affected packages to version 0.23.2.

GHSA-4jhj-3gv3-c3gr at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-4jhj-3gv3-c3gr
Severity HIGH
CVSS v3.1 Base Score 7.7
CWE Classification General Security Weakness
Affected Product Github.com/go vela/cli
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 7.7

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix GHSA-4jhj-3gv3-c3gr

To remediate this vulnerability, upgrade all affected Github.com/go vela/cli dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/go-vela/cli fixed: 0.23.2
Upgrade github.com/go-vela/cli to 0.23.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/go-vela/cli

How to Check if You Are Affected

To determine whether your application is affected by GHSA-4jhj-3gv3-c3gr, inspect your project dependencies for Github.com/go vela/cli:

inspect dependencies for github.com/go-vela/cli

Analyze the terminal output to locate any version of Github.com/go vela/cli in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.23.2), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Github.com/go vela/cli, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact Vela pipelines can use variable substitution combined with insensitive fields like `parameters`, `image` and `entrypoint` to inject secrets into a plugin/image and — by using common substitution string manipulation — can bypass log masking and expose secrets without the use of the commands block. This unexpected behavior primarily impacts secrets restricted by the "no commands" option. This can lead to unintended use of the secret value, and increased risk of exposing the secret during image execution bypassing log masking. Given by the following substitution examples: using `parameters` ```yaml steps: - name: example image: <some plugin> secrets: [ example_secret ] parameters: example: $${EXAMPLE_SECRET} ``` using `image` tag ```yaml steps: - name: example image: <some plugin>:latest${EXAMPLE_SECRET} secrets: [ example_secret ] ``` using `entrypoint` as a shim for `commands` ```yaml steps: - name: example image: <some plugin> secrets: [ example_secret ] entrypoint: [ "sh", "-c", "echo $EXAMPLE_SECRET", ] ``` **To exploit this** the pipeline author must be supplying the secrets to a plugin that is designed in such a way that will print those parameters in logs. Plugin parameters are not designed for sensitive values and are often intentionally printed throughout execution for informational/debugging purposes. Parameters should therefore be treated as insensitive. While Vela provides secrets masking, secrets exposure is not entirely solved by the masking process. A docker image (plugin) can easily expose secrets if they are not handled properly, or altered in some way. There is a responsibility on the end-user to understand how values injected into a plugin are used. This is a risk that exists for many CICD systems (like GitHub Actions) that handle sensitive runtime variables. Rather, the greater risk is that users who restrict a secret to the "no commands" option and use image restriction can still have their secret value exposed via substitution tinkering, which turns the image and command restrictions into a false sense of security. ### Patches N/A ### Workarounds - Do not provide sensitive values to plugins that can potentially expose them, especially in `parameters` that are not intended to be used for sensitive values. - Ensure plugins (especially those that utilize shared secrets) follow best practices to avoid logging parameters that are expected to be sensitive. - Minimize secrets with `pull_request` events enabled, as this allows users to change pipeline configurations and pull in secrets to steps not typically part of the CI process. - Make use of the build approval setting, restricting builds from untrusted users - Limit use of shared secrets, as they are less restrictive to access by nature. ### References - https://github.com/go-vela/worker ### For more information If you have any questions or comments about this advisory: - Email us at [vela@target.com](mailto:vela@target.com) Affected products: `go-vela/worker`

GHSA-4jhj-3gv3-c3gr Affected Github.com/go vela/cli Versions

1 component(s)
Fixed Versions:
0.23.2
Product / Package Ecosystem Affected Versions Fixed Version
github.com/go-vela/cli
Go
< 0.23.2
0.23.2

References

Frequently Asked Questions

What is GHSA-4jhj-3gv3-c3gr?
GHSA-4jhj-3gv3-c3gr is a security vulnerability in Github.com/go vela/cli involving CLI for Vela Insecure Variable Substitution under General Security Weakness.
Which Github.com/go vela/cli versions are affected?
Affected versions include releases prior to 0.23.2 across affected packages: github.com/go-vela/cli.
What version fixes GHSA-4jhj-3gv3-c3gr?
Upgrading to 0.23.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/go-vela/cli affected?
Yes, github.com/go-vela/cli is affected in releases prior to 0.23.2. Upgrade your dependency to 0.23.2 or later.
What is the CVSS score of GHSA-4jhj-3gv3-c3gr?
GHSA-4jhj-3gv3-c3gr has a CVSS v3.1 base score of 7.7 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N.
What CWE is associated with GHSA-4jhj-3gv3-c3gr?
GHSA-4jhj-3gv3-c3gr is classified under General Security Weakness.
How can I check Go dependencies for GHSA-4jhj-3gv3-c3gr?
Run the dependency tree command: 'inspect dependencies for github.com/go-vela/cli'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-4jhj-3gv3-c3gr",
  "modified" : "2024-03-15T20:12:15Z",
  "published" : "2024-03-15T20:12:15Z",
  "aliases" : [ ],
  "summary" : "CLI for Vela Insecure Variable Substitution",
  "details" : "### Impact\nVela pipelines can use variable substitution combined with insensitive fields like `parameters`, `image` and `entrypoint` to inject secrets into a plugin/image and — by using common substitution string manipulation — can bypass log masking and expose secrets without the use of the commands block. This unexpected behavior primarily impacts secrets restricted by the \"no commands\" option. This can lead to unintended use of the secret value, and increased risk of exposing the secret during image execution bypassing log masking.\n\nGiven by the following substitution examples:\nusing `parameters`\n```yaml\nsteps:\n  - name: example\n    image: <some plugin>\n    secrets: [ example_secret ]\n    parameters:\n      example: $${EXAMPLE_SECRET}\n```\n\nusing `image` tag\n```yaml\nsteps:\n  - name: example\n    image: <some plugin>:latest${EXAMPLE_SECRET}\n    secrets: [ example_secret ]\n```\n\nusing `entrypoint` as a shim for `commands`\n```yaml\nsteps:\n  - name: example\n    image: <some plugin>\n    secrets: [ example_secret ]\n    entrypoint:\n      [\n        \"sh\",\n        \"-c\",\n        \"echo $EXAMPLE_SECRET\",\n      ]\n```\n\n\n\n**To exploit this** the pipeline author must be supplying the secrets to a plugin that is designed in such a way that will print those parameters in logs. Plugin parameters are not designed for sensitive values and are often intentionally printed throughout execution for informational/debugging purposes. Parameters should therefore be treated as insensitive.\n\nWhile Vela provides secrets masking, secrets exposure is not entirely solved by the masking process. A docker image (plugin) can easily expose secrets if they are not handled properly, or altered in some way. There is a responsibility on the end-user to understand how values injected into a plugin are used. This is a risk that exists for many CICD systems (like GitHub Actions) that handle sensitive runtime variables. Rather, the greater risk is that users who restrict a secret to the \"no commands\" option and use image restriction can still have their secret value exposed via substitution tinkering, which turns the image and command restrictions into a false sense of security.\n\n### Patches\nN/A\n\n### Workarounds\n- Do not provide sensitive values to plugins that can potentially expose them, especially in `parameters` that are not intended to be used for sensitive values.\n- Ensure plugins (especially those that utilize shared secrets) follow best practices to avoid logging parameters that are expected to be sensitive.\n- Minimize secrets with `pull_request` events enabled, as this allows users to change pipeline configurations and pull in secrets to steps not typically part of the CI process.\n- Make use of the build approval setting, restricting builds from untrusted users\n- Limit use of shared secrets, as they are less restrictive to access by nature.\n\n### References\n- https://github.com/go-vela/worker\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- Email us at [vela@target.com](mailto:vela@target.com)\n\nAffected products: `go-vela/worker`\n",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/go-vela/cli"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.23.2"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.23.1"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/go-vela/cli/security/advisories/GHSA-4jhj-3gv3-c3gr"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/go-vela/cli/commit/0349a2060c35722e341bf65a4215592c6c4bc5b4"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/go-vela/cli"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-03-15T20:12:15Z",
    "nvd_published_at" : null
  }
}