Argo Cd: Improper Limitation of a Pathname to a Restricted Directory
CVE-2022-24348 is a high-severity improper limitation of a pathname to a restricted directory vulnerability in Argo Cd from Argoproj, with a CVSS 3.1 base score of 7.7 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. The record lists versions 2.1.9, 2.2.4 as the first without the flaw, so updating Argo Cd to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 2.77% chance of exploitation within 30 days, higher than 87% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Argo Cd to 2.1.9 or 2.2.4, whichever matches your release line, or a later version.
- 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 | before 2.1.9; 2.2.0 up to, but not including, 2.2.4 | 2.1.9, 2.2.4 |
Version data comes from NVD's product matching. 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
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.7 | High | NVD |
| CVSS 2.0 | 4.0 | Medium | NVD |
Official description
Argo CD before 2.1.9 and 2.2.x before 2.2.4 allows directory traversal related to Helm charts because of an error in helmTemplate in repository.go. For example, an attacker may be able to discover credentials stored in a YAML file.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Advisories
- github.com/argoproj/argo-cd/security/advisories/GHSA-63qx-x74g-jcr7Exploit, Third Party Advisory
Technical write-ups (may include proof of concept)
- apiiro.com/blog/malicious-kubernetes-helm-charts-can-be-used-to-steal-sensitive-information-from-argo-cd-depl…Exploit, 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 Improper Limitation of a Pathname to a Restricted Directory vulnerabilities
- 9.1 Critical severity
- 9.8 Critical severity
- 8.1 High severity
- 7.5 High severity
- 7.5 High severity
- 8.1 High severity
Spotted an error? Tell us.