CVE-2022-1025: Github.com/argoproj/argo cd Argo CD Improper Access Control Vulnerability

HIGH
Advisory Identifier: GHSA-96jv-vj39-x4j6
CVSS 8.8
CWE-284 CWE-1220 CWE-863
Published
Advisory Summary

CVE-2022-1025 is a HIGH (CVSS 8.8) argo cd improper access control vulnerability (CWE-284: Improper Access Control) affecting Github.com/argoproj/argo cd libraries in the Go ecosystem. The issue involves argo cd improper access control bug can allow malicious user to escalate privileges to admin level. Remediation is available by upgrading affected packages to version 2.1.14, 2.2.8, 2.3.2.

CVE-2022-1025 at a Glance

CVE Identifier CVE-2022-1025
GHSA Identifier GHSA-96jv-vj39-x4j6
Severity HIGH
CVSS v3.1 Base Score 8.8
CWE Classification CWE-284: Improper Access Control
Affected Product Github.com/argoproj/argo cd
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 8.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2022-1025

To remediate this vulnerability, upgrade all affected Github.com/argoproj/argo cd dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/argoproj/argo-cd fixed: Latest secure release
Upgrade github.com/argoproj/argo-cd to Latest secure release
github.com/argoproj/argo-cd/v2 fixed: 2.1.14
Upgrade github.com/argoproj/argo-cd/v2 to 2.1.14
github.com/argoproj/argo-cd/v2 fixed: 2.2.8
Upgrade github.com/argoproj/argo-cd/v2 to 2.2.8
github.com/argoproj/argo-cd/v2 fixed: 2.3.2
Upgrade github.com/argoproj/argo-cd/v2 to 2.3.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/argoproj/argo-cd

How to Check if You Are Affected

To determine whether your application is affected by CVE-2022-1025, inspect your project dependencies for Github.com/argoproj/argo cd:

inspect dependencies for github.com/argoproj/argo-cd

Analyze the terminal output to locate any version of Github.com/argoproj/argo cd in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.1.14), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-284: Improper Access Control, where the product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. In Github.com/argoproj/argo cd, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

# Impact ## Impacts for versions starting with v1.0.0 All unpatched versions of Argo CD starting with v1.0.0 are vulnerable to an improper access control bug, allowing a malicious user to potentially escalate their privileges to admin-level. To perform the following exploits, an authorized Argo CD user must have push access to an Application's source git or Helm repository or `sync` and `override` access to an Application. Once a user has that access, different exploitation levels are possible depending on their other RBAC privileges: 1. If that user has `update` access to the Application, they can modify any resource on the Application's destination cluster. If the destination cluster is or can be made to be the same as the cluster hosting Argo CD, the user can escalate their Argo CD permissions to admin-level. 2. If the user has `delete` access to the Application, they can delete any resource on the Application's destination cluster. (This exploit is possible starting with v0.8.0.) 3. If the user has `get` access to the Application, they can view any resource on the Application's destination cluster (except for the contents of Secrets) and list [actions](https://argo-cd.readthedocs.io/en/stable/operator-manual/resource_actions/) available for that resource. 4. If the user has `get` access to the Application, they can view the logs of any Pods on the Application's destination cluster. 5. If the user has `action/{some action or *}` access on the Application, they can run an action for any resource (which supports the allowed action(s)) on the Application's destination cluster. (Some actions are available in Argo CD by default, and others may be configured by an Argo CD admin.) See the [Argo CD RBAC documentation](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#rbac-resources-and-actions) for an explanation of the privileges available in Argo CD. ## Events exploit A related exploit is possible for a user with `get` access to an Application **even if they do not have access to the Application's source git or Helm repository or `sync` and `override` access to the Application**. The user can access any Event in the Application's destination cluster if they know the involved object's name, UID, and namespace. ## Impacts for versions starting with v0.8.0 The same bug exists starting with v0.8.0, but only the following exploits were possible before v1.0.0: - The `delete exploit` (#⁠2 above). - The logs exploit (#⁠4 above). - The Events exploit described above. ## Impacts for versions starting with v0.5.0 The same bug exists starting with v0.5.0 (when RBAC was implemented), but only the Events exploit described above was possible before v0.8.0. Patches A patch for this vulnerability has been released in the following Argo CD versions: - v2.3.2 - v2.2.8 - v2.1.14 **Versions 2.0.x and earlier users**: See the changelog for links to upgrade instructions for your version. It is imperative to upgrade quickly, but some limited mitigations are described in the next section. **argo-helm chart users**: Argo CD users deploying v2.3.x with argo-helm can upgrade the chart to version 4.2.2. Argo CD 2.2 and 2.1 users can set the global.image.tag value to the latest in your current release series (v2.2.8, or v2.1.14). Since charts for the 2.2 and 2.1 series are no longer maintained, you will need to either leave the value override in place or upgrade to the 4.x chart series (and therefore to Argo CD 2.3). ## Workarounds The only certain way to avoid the vulnerability is to upgrade. ## Mitigations - To avoid privilege escalation: - Limit who has push access to Application source repositories or sync + override access to Applications. - Limit which repositories are available in projects where users have update access to Applications. - To avoid unauthorized resource inspection/tampering: - Limit who has delete, get, or action access to Applications. These mitigations can help limit potential damage, but they are not a substitute for upgrading. It is necessary to upgrade immediately.

CVE-2022-1025 Affected Github.com/argoproj/argo cd Versions

4 component(s)
Fixed Versions:
2.1.142.2.82.3.2
Product / Package Ecosystem Affected Versions Fixed Version
github.com/argoproj/argo-cd
Go
≥ 0.5.0
≤ 1.8.7
github.com/argoproj/argo-cd/v2
Go
< 2.1.14
2.1.14
github.com/argoproj/argo-cd/v2
Go
≥ 2.2.0
< 2.2.8
2.2.8
github.com/argoproj/argo-cd/v2
Go
≥ 2.3.0
< 2.3.2
2.3.2

References

Frequently Asked Questions

What is CVE-2022-1025?
CVE-2022-1025 is a security vulnerability in Github.com/argoproj/argo cd involving Argo CD improper access control bug can allow malicious user to escalate privileges to admin level under CWE-284: Improper Access Control.
Which Github.com/argoproj/argo cd versions are affected?
Affected versions include releases prior to 2.1.14, 2.2.8, 2.3.2 across affected packages: github.com/argoproj/argo-cd, github.com/argoproj/argo-cd/v2.
What version fixes CVE-2022-1025?
Upgrading to 2.1.14, 2.2.8, 2.3.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/argoproj/argo-cd affected?
Yes, github.com/argoproj/argo-cd is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
Is github.com/argoproj/argo-cd/v2 affected?
Yes, github.com/argoproj/argo-cd/v2 is affected in releases prior to 2.1.14, 2.2.8, 2.3.2. Upgrade your dependency to 2.1.14, 2.2.8, 2.3.2 or later.
What is the CVSS score of CVE-2022-1025?
CVE-2022-1025 has a CVSS v3.1 base score of 8.8 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2022-1025?
CVE-2022-1025 is classified under CWE-284: Improper Access Control (The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.).
How can I check Go dependencies for CVE-2022-1025?
Run the dependency tree command: 'inspect dependencies for github.com/argoproj/argo-cd'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-96jv-vj39-x4j6",
  "modified" : "2023-06-27T20:58:57Z",
  "published" : "2022-07-13T00:00:41Z",
  "aliases" : [ "CVE-2022-1025" ],
  "summary" : "Argo CD improper access control bug can allow malicious user to escalate privileges to admin level",
  "details" : "# Impact\n\n## Impacts for versions starting with v1.0.0\nAll unpatched versions of Argo CD starting with v1.0.0 are vulnerable to an improper access control bug, allowing a malicious user to potentially escalate their privileges to admin-level.\n\nTo perform the following exploits, an authorized Argo CD user must have push access to an Application's source git or Helm repository or `sync` and `override` access to an Application. Once a user has that access, different exploitation levels are possible depending on their other RBAC privileges:\n\n1. If that user has `update` access to the Application, they can modify any resource on the Application's destination cluster. If the destination cluster is or can be made to be the same as the cluster hosting Argo CD, the user can escalate their Argo CD permissions to admin-level.\n2. If the user has `delete` access to the Application, they can delete any resource on the Application's destination cluster. (This exploit is possible starting with v0.8.0.)\n3. If the user has `get` access to the Application, they can view any resource on the Application's destination cluster (except for the contents of Secrets) and list [actions](https://argo-cd.readthedocs.io/en/stable/operator-manual/resource_actions/) available for that resource.\n4. If the user has `get` access to the Application, they can view the logs of any Pods on the Application's destination cluster.\n5. If the user has `action/{some action or *}` access on the Application, they can run an action for any resource (which supports the allowed action(s)) on the Application's destination cluster. (Some actions are available in Argo CD by default, and others may be configured by an Argo CD admin.)\n\nSee the [Argo CD RBAC documentation](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#rbac-resources-and-actions) for an explanation of the privileges available in Argo CD.\n\n## Events exploit\nA related exploit is possible for a user with `get` access to an Application **even if they do not have access to the Application's source git or Helm repository or `sync` and `override` access to the Application**. The user can access any Event in the Application's destination cluster if they know the involved object's name, UID, and namespace.\n\n## Impacts for versions starting with v0.8.0\nThe same bug exists starting with v0.8.0, but only the following exploits were possible before v1.0.0:\n\n- The `delete exploit` (#⁠2 above).\n- The logs exploit (#⁠4 above).\n- The Events exploit described above.\n\n## Impacts for versions starting with v0.5.0\nThe same bug exists starting with v0.5.0 (when RBAC was implemented), but only the Events exploit described above was possible before v0.8.0.\n\nPatches\nA patch for this vulnerability has been released in the following Argo CD versions:\n\n- v2.3.2\n- v2.2.8\n- v2.1.14\n\n**Versions 2.0.x and earlier users**: See the changelog for links to upgrade instructions for your version. It is imperative to upgrade quickly, but some limited mitigations are described in the next section.\n\n**argo-helm chart users**: Argo CD users deploying v2.3.x with argo-helm can upgrade the chart to version 4.2.2. Argo CD 2.2 and 2.1 users can set the global.image.tag value to the latest in your current release series (v2.2.8, or v2.1.14). Since charts for the 2.2 and 2.1 series are no longer maintained, you will need to either leave the value override in place or upgrade to the 4.x chart series (and therefore to Argo CD 2.3).\n\n## Workarounds\nThe only certain way to avoid the vulnerability is to upgrade.\n\n## Mitigations\n\n- To avoid privilege escalation:\n    - Limit who has push access to Application source repositories or sync + override access to Applications.\n- Limit which repositories are available in projects where users have update access to Applications.\n    - To avoid unauthorized resource inspection/tampering:\n    - Limit who has delete, get, or action access to Applications.\n\nThese mitigations can help limit potential damage, but they are not a substitute for upgrading. It is necessary to upgrade immediately.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/argoproj/argo-cd"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.5.0"
      }, {
        "last_affected" : "1.8.7"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/argoproj/argo-cd/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.1.14"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/argoproj/argo-cd/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.2.0"
      }, {
        "fixed" : "2.2.8"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/argoproj/argo-cd/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.3.0"
      }, {
        "fixed" : "2.3.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/argoproj/argo-cd/security/advisories/GHSA-2f5v-8r3f-8pww"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-1025"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/argoproj/argo-cd/commit/af03b291d4b7e9d3ce9a6580ae9c8141af0e05cf"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2022:1039"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2022:1040"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2022:1041"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2022:1042"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/security/cve/CVE-2022-1025"
  }, {
    "type" : "WEB",
    "url" : "https://bugzilla.redhat.com/show_bug.cgi?id=2064682"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/argoproj/argo-cd"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1220", "CWE-284", "CWE-863" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-07-21T22:29:13Z",
    "nvd_published_at" : "2022-07-12T21:15:00Z"
  }
}