GHSA-6c73-2v8x-qpvm – github.com/argoproj/argo-workflows/v3

Package

Manager: go
Name: github.com/argoproj/argo-workflows/v3
Vulnerable Version: >=3.0.0 <3.0.9 || >=3.1.0 <3.1.6

Severity

Level: Medium

CVSS v3.1: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N/E:P/RL:O/RC:C

CVSS v4.0: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

EPSS: N/A pctlN/A

Details

Argo Server TLS requests could be forged by attacker with network access ### Impact We are not aware of any exploits. This is a pro-active fix. Impacted: * You are running Argo Server < v3.0 with `--secure=true` or >= v3.0 with `--secure` unspecified (note - running in secure mode is recommended regardless). * The attacker is within your network. If you expose Argo Server to the Internet then "your network" is "the Internet". The Argo Server's keys are packaged within the image. They could be extracted and used to decrypt traffic, or forge requests. ### Patches https://github.com/argoproj/argo-workflows/pull/6540 ### Workarounds * Make sure that your Argo Server service or pod are not directly accessible outside of your cluster. Put TLS load balancer in front of it. This was identified by engineers at Jetstack.io

Metadata

Created: 2021-08-23T19:41:30Z
Modified: 2021-08-23T17:02:24Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2021/08/GHSA-6c73-2v8x-qpvm/GHSA-6c73-2v8x-qpvm.json
CWE IDs: []
Alternative ID: N/A
Finding: F163
Auto approve: 1