{"answers":{"affected":"3 open source packages ship an affected version, including github.com/go-vela/types.","exploited":"There is no known exploitation of GHSA-7v38-w32m-wx4m in the wild and no public exploit code.","fix":"Upgrade github.com/go-vela/types to 0.23.2 or later.","what":"GHSA-7v38-w32m-wx4m is a vulnerability in github.com/go-vela/types, published on 15 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-7v38-w32m-wx4m and fix it if it is affected.\n\nWhat it is: GHSA-7v38-w32m-wx4m is a vulnerability in github.com/go-vela/types, published on 15 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-7v38-w32m-wx4m in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/go-vela/types (Go): affected all versions; fixed in 0.23.2\n- github.com/go-vela/types (Go): affected all versions; fixed in 0.23.2\n- github.com/go-vela/types (Go): affected all versions; fixed in 0.23.2\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-7v38-w32m-wx4m/ (Markdown: https://insights.sbomify.com/GHSA-7v38-w32m-wx4m/index.md)","id":"GHSA-7v38-w32m-wx4m","markdown":"https://insights.sbomify.com/GHSA-7v38-w32m-wx4m/index.md","name":"GHSA-7v38-w32m-wx4m","record":{"aliases":["GO-2024-2649"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Vela CI/CD","requires_auth":"low_privilege","summary":"Attackers can expose secrets in Vela pipelines by injecting them into insensitive fields like parameters or image tags, bypassing log masking and command restrictions.","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":"### 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: \u003csome plugin\u003e\n    secrets: [ example_secret ]\n    parameters:\n      example: $${EXAMPLE_SECRET}\n```\n\nusing `image` tag\n```yaml\nsteps:\n  - name: example\n    image: \u003csome plugin\u003e:latest${EXAMPLE_SECRET}\n    secrets: [ example_secret ]\n```\n\nusing `entrypoint` as a shim for `commands`\n```yaml\nsteps:\n  - name: example\n    image: \u003csome plugin\u003e\n    secrets: [ example_secret ]\n    entrypoint:\n      [\n        \"sh\",\n        \"-c\",\n        \"echo $EXAMPLE_SECRET\",\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`","ecosystems":["Go"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Types for Vela Insecure Variable Substitution","id":"GHSA-7v38-w32m-wx4m","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"Go","fixed":["0.23.2"],"introduced":["0"],"last_affected":[],"package":"github.com/go-vela/types","purl":null,"source":"GHSA-7v38-w32m-wx4m"},{"ecosystem":"Go","fixed":["0.23.2"],"introduced":["0"],"last_affected":[],"package":"github.com/go-vela/types","purl":"pkg:golang/github.com/go-vela/types","source":"GHSA-7v38-w32m-wx4m"},{"ecosystem":"Go","fixed":["0.23.2"],"introduced":["0"],"last_affected":[],"package":"github.com/go-vela/types","purl":"pkg:golang/github.com/go-vela/types","source":"GO-2024-2649"}],"products":null,"published":"2024-03-15","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can expose secrets in Vela pipelines by injecting them into insensitive fields like parameters or image tags, bypassing log masking and command restrictions.","url":"https://insights.sbomify.com/GHSA-7v38-w32m-wx4m/"}