Ecosyste.ms: Advisories

Security Advisories: MDE2OlNlY3VyaXR5QWR2aXNvcnlHSFNBLTZjNzMtMnY4eC1xcHZt

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

Permalink: https://github.com/advisories/GHSA-6c73-2v8x-qpvm
JSON: https://advisories.ecosyste.ms/api/v1/advisories/MDE2OlNlY3VyaXR5QWR2aXNvcnlHSFNBLTZjNzMtMnY4eC1xcHZt
Source: GitHub Advisory Database
Origin: Unspecified
Severity: Moderate
Classification: General
Published: over 2 years ago
Updated: over 1 year ago

Identifiers: GHSA-6c73-2v8x-qpvm
References:

• https://github.com/argoproj/argo-workflows/security/advisories/GHSA-6c73-2v8x-qpvm
• https://github.com/advisories/GHSA-6c73-2v8x-qpvm

Repository: https://github.com/argoproj/argo-workflows
Blast Radius: 0.0

Affected Packages