CVE-2023-24531 Affecting argo-workflows package, versions <3.6.2-r4


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.05% (18th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-ARGOWORKFLOWS-8603601
  • published8 Jan 2025
  • disclosed2 Jul 2024

Introduced: 2 Jul 2024

CVE-2023-24531  (opens in a new tab)

How to fix?

Upgrade Chainguard argo-workflows to version 3.6.2-r4 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream argo-workflows package and not the argo-workflows package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

Command go env is documented as outputting a shell script containing the Go environment. However, go env doesn't sanitize values, so executing its output as a shell script can cause various bad bahaviors, including executing arbitrary commands or inserting new environment variables. This issue is relatively minor because, in general, if an attacker can set arbitrary environment variables on a system, they have better attack vectors than making "go env" print them out.