GHSA-prqf-xr2j-xf65

    Dashboard / Vulnerabilities / GHSA-prqf-xr2j-xf65

    GHSA-prqf-xr2j-xf65

    Published: 23 Aug 2021Last Modified: 21 Aug 2024
    Aliases:
    GO-2022-0405

    Summary: Potential privilege escalation on Kubernetes >= v1.19 when the Argo Sever is run with `--auth-mode=client`

    Details: ### Impact This is pro-active fix. No know exploits exist. Impacted: * You're running Kubernetes >= v1.19 * You're running Argo Server * It is configured to with `--auth-mode=client` * Is not configured with `--auth-mode=server` * You are not running Argo Server in Kubernetes pod. E.g. on bare metal or other VM. * You're using client key to authenticate on the server. * The server has more permissions that the connecting client's account. The client's authentication will be ignored and the server's authentication will be used. This will result in privilege escalation to that of the the server's account. ### Patches https://github.com/argoproj/argo-workflows/pull/6506 ### Workarounds None.

    References: https://github.com/argoproj/argo-workflows/security/advisories/GHSA-prqf-xr2j-xf65

    Affected packages

    Package

    Name: github.com/argoproj/argo-workflows/v3

    Purl: pkg:golang/github.com/argoproj/argo-workflows/v3

    Affected ranges

    Type: SEMVER

    Events:

    Introduced- 3.0.0
    Fixed -3.0.9

    Affected versions

    Common Vulnerability Scoring System

    Attack Vector
    Network
    Adjacent
    Local
    Physical
    Privileges Required
    None
    Low
    High
    User Interaction
    None
    Required
    Scope
    Unchanged
    Changed
    Confidentiality
    None
    Low
    High
    Integrity
    None
    Low
    High
    Availability
    None
    Low
    High
    GHSA-prqf-xr2j-xf65 | CVE-DB