argo-cd: Missing Authorization
CVE-2022-24768 is a high-severity missing authorization vulnerability in argo-cd from Argoproj, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected argo-cd versions: >= 0.5.0, < 2.1.14; >= 2.2.0, < 2.2.8; >= 2.3.0, < 2.3.2. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.25% chance of exploitation within 30 days, higher than 70% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of argo-cd you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on github.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Argoproj | argo-cd | >= 0.5.0, < 2.1.14; >= 2.2.0, < 2.2.8; >= 2.3.0, < 2.3.2 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.9 | Critical | CNA (github.com) |
| CVSS 3.1 | 8.8 | High | NVD |
| CVSS 2.0 | 6.5 | Medium | NVD |
Official description
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All unpatched versions of Argo CD starting with 1.0.0 are vulnerable to an improper access control bug, allowing a malicious user to potentially escalate their privileges to admin-level. Versions starting with 0.8.0 and 0.5.0 contain limited versions of this issue. To perform 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. A patch for this vulnerability has been released in Argo CD versions 2.3.2, 2.2.8, and 2.1.14. Some mitigation measures are available but do not serve as a substitute for upgrading. To avoid privilege escalation, limit who has push access to Application source repositories or `sync` + `override` access to Applications; and 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Authorization
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
How developers prevent this class of flaw
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- github.com/argoproj/argo-cd/security/advisories/GHSA-2f5v-8r3f-8pwwMitigation, Third Party Advisory
Patches and release notes
- github.com/argoproj/argo-cd/commit/af03b291d4b7e9d3ce9a6580ae9c8141af0e05cfThird Party Advisory
- github.com/argoproj/argo-cd/releases/tag/v2.1.14Release Notes, Third Party Advisory
- github.com/argoproj/argo-cd/releases/tag/v2.2.8Release Notes, Third Party Advisory
- github.com/argoproj/argo-cd/releases/tag/v2.3.2Release Notes, Third Party Advisory
Other vulnerabilities in argo-cd
- 9.9 Critical severity
- 9.9 Critical severity
- 9.9 Critical severity
- 9.9 Critical severity
- 8.8 High severity
- 8.7 High severity
Recent Missing Authorization vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Linux Kernel Improper Authentication Exploited
- 8.8 High severity
- 10.0 Critical severity
- 8.8 High severity
Spotted an error? Tell us.