Advisory

GHSA-6c73-2v8x-qpvm

Also known as: GO-2022-0388

Summary

Argo Server TLS requests could be forged by attacker with network access

Details

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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2021-08-23 19:41 UTC
Modified
2024-08-21 14:57 UTC

Affected packages and fixes

github.com/argoproj/argo-workflows/v3

Go · All systems

Affected

  • introduced 3.0.0, fixed 3.0.9 (semver)

Fixed versions

3.0.9

Fix

github.com/argoproj/argo-workflows/v3

Go · All systems

Affected

  • introduced 3.1.0, fixed 3.1.6 (semver)

Fixed versions

3.1.6

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences