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

中GHSA-6c73-2v8x-qpvm · GO-2022-0388 · 23/08/2021 公開 · 21/08/2024 更新

要点

パッケージ	影響を受けるバージョン	修正済みバージョン
github.com/argoproj/argo-workflows/v3 Go	`≥ 3.0.0, < 3.0.9≥ 3.1.0, < 3.1.6`	`3.0.93.1.6`

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.

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

これらの製品をお使いですか？サイトをスキャンして、脆弱なバージョンが公開されていないか確認しましょう。

パッケージ

影響を受けるバージョン

修正済みバージョン

≥ 3.0.0, < 3.0.9≥ 3.1.0, < 3.1.6

3.0.93.1.6

概要

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.

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

github.com/argoproj/argo-workflows/v3 のその他の脆弱性

すべて見る →