<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Michael Crenshaw on Medium]]></title>
        <description><![CDATA[Stories by Michael Crenshaw on Medium]]></description>
        <link>https://medium.com/@crenshaw.dev_intuit?source=rss-812c77c99da5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*M9qPDCAWqCyUX31L4lxRCQ.png</url>
            <title>Stories by Michael Crenshaw on Medium</title>
            <link>https://medium.com/@crenshaw.dev_intuit?source=rss-812c77c99da5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 19:51:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@crenshaw.dev_intuit/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Argo CD v2.5 release candidate]]></title>
            <link>https://blog.argoproj.io/argo-cd-v2-5-release-candidate-e2121f2002ba?source=rss-812c77c99da5------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2121f2002ba</guid>
            <category><![CDATA[cicd]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[gitops]]></category>
            <category><![CDATA[argoproj]]></category>
            <dc:creator><![CDATA[Michael Crenshaw]]></dc:creator>
            <pubDate>Wed, 05 Oct 2022 18:15:25 GMT</pubDate>
            <atom:updated>2022-10-05T18:20:17.118Z</atom:updated>
            <content:encoded><![CDATA[<p>Four months after the release of Argo CD v2.4, we’re excited to preview version 2.5 with the first release candidate! 128 contributors (85 of them new) made awesome improvements, including 58 new features. Please <a href="https://github.com/argoproj/argo-cd/releases/tag/v2.5.0-rc1">take the release candidate for a spin</a> and <a href="https://github.com/argoproj/argo-cd#community">send us feedback</a> about how you’re using new features or about any bugs you encounter.</p><figure><img alt="Two crochet octupi. The one on the left is green, and the one on the right is blue. They seem to be holding hands." src="https://cdn-images-1.medium.com/max/1024/1*3rmQNCC8IHDX-BoAOSgxsw.jpeg" /><figcaption>Photo credit to <a href="https://flickr.com/photos/morganmorgan/2562626252/in/photolist-4Us8vf-ZddkK-4uiw9K-6bx95G-4AL5kk-6bt1r4-6bx8Vq-6bx8YN-5SR3HV-3jFYHR-4JLuEm-4JGfgK-4axBgh-CEiZm-kq2NV-5YAmbq-6pCt1K-5G2whN-efUmWG-5WX4ot-owvVxc-dFqEUP-6iDyAZ-7AvgYz-6j5MaA-dUtQn9-efNB6P-KZkncJ-9DEGFf-9kdsNG-9kapsX-2dyEfEq-5V2UiQ-mehmD-8eQtv2-4zFWuL-6gRB6q-4vNTtS-5KZHc9-6iDyEp-7RM9aP-5XwfoG-4DxrLj-PzSyCx-NwELxM-PzSz7t-NwELqx-PzSzjx-MdbsN-PzSyTx">iwishmynamewasmarsha</a>. This version is lightly edited.</figcaption></figure><h3>Beta Support for Server-Side Apply</h3><p>The Argo CD Application controller <a href="https://argo-cd.readthedocs.io/en/latest/user-guide/sync-options/#server-side-apply">can now sync resources using server-side apply</a>. This helps avoid errors when applying very large resources. It also resolves edge-case issues with inaccurate manifest diffs. This feature introduces brand new diffing logic based on how Kubernetes calculates diffs server-side. It is a <strong>beta feature</strong> that, once thoroughly validated, will be made the default apply option.</p><figure><img alt="Screenshot of the Argo CD web UI’s “synchronize” panel. There are many checkboxes for various sync options. There is one checked box, labeled “server-side apply.”" src="https://cdn-images-1.medium.com/max/1024/1*pK3Uq1oubczuJqTbiC0JuA.png" /><figcaption>Syncing an application with the “server-side apply” option enabled in the UI.</figcaption></figure><p>Thank you to <a href="https://github.com/leoluz">Leonardo Almeida</a> from Intuit for contributing this enhancement!</p><h3>API and CLI Support for ApplicationSets, and Advanced Templating</h3><p>The Argo CD CLI and API now <a href="https://argo-cd.readthedocs.io/en/latest/user-guide/commands/argocd_appset/">support get/create/update/delete operations on ApplicationSets</a>. You can enable user access to argocd appset commands with <a href="https://argo-cd.readthedocs.io/en/latest/operator-manual/rbac/#the-applicationsets-resource">the </a><a href="https://argo-cd.readthedocs.io/en/latest/operator-manual/rbac/#the-applicationsets-resource">applicationsets RBAC resource</a>.</p><pre>$ argocd appset create guestbook-appset.yaml<br>ApplicationSet &#39;guestbook&#39; created<br>$ argocd appset get guestbook<br>Name:               guestbook<br>Project:            default<br>Server:             {{url}}<br>Namespace:          guestbook<br>Repo:               <a href="https://github.com/argoproj/argo-cd.git">https://github.com/argoproj/argo-cd.git</a><br>Target:             HEAD<br>Path:               applicationset/examples/list-generator/guestbook/{{cluster}}<br>SyncPolicy:         &lt;none&gt;</pre><pre>CONDITION            STATUS  MESSAGE                                                 LAST TRANSITION<br>ErrorOccurred        False   Successfully generated parameters for all Applications  2022-09-17 19:34:35 -0400 EDT<br>ParametersGenerated  True    Successfully generated parameters for all Applications  2022-09-17 19:34:35 -0400 EDT<br>ResourcesUpToDate    True    ApplicationSet up to date                               2022-09-17 19:34:35 -0400 EDT</pre><p>Thanks to <a href="https://github.com/ishitasequeira">Ishita Sequeira</a> from Red Hat for the <em>major</em> effort to add this feature!</p><p><strong>Advanced templating with the go text template engine</strong> <a href="https://argo-cd.readthedocs.io/en/latest/operator-manual/applicationset/GoTemplate/">is now possible in ApplicationSets</a>. This allows things like <a href="https://argo-cd.readthedocs.io/en/latest/operator-manual/applicationset/GoTemplate/#fallbacks-for-unset-parameters">setting default fallback parameter values</a> and sanitizing/truncating values to be used in DNS fields. Users will have access to functions from the Sprig library, so the possibilities are expansive.</p><pre>apiVersion: argoproj.io/v1alpha1<br>kind: ApplicationSet<br>metadata:<br>  name: cluster-addons<br>spec:<br>  goTemplate: true<br>  generators:<br>  - git:<br>      repoURL: https://github.com/argoproj/argo-cd.git<br>      revision: HEAD<br>      directories:<br>      - path: applicationset/examples/git-generator-directory/cluster-addons/*<br>  template:<br>    metadata:<br>      name: &#39;<strong>{{index (splitList &quot;/&quot; .path.path) 0}}</strong>&#39;<br>    spec:<br>      project: default<br>      source:<br>        repoURL: https://github.com/argoproj/argo-cd.git<br>        targetRevision: HEAD<br>        path: &#39;{{.path.path}}&#39;<br>      destination:<br>        server: https://kubernetes.default.svc<br>        namespace: &#39;<strong>{{normalize .path.basename}}</strong>&#39;</pre><p>Thanks to Geoffrey Muselli from Ubisoft for contributing this feature!</p><h3>Security Improvements</h3><h4>New Project-Level Restrictions</h4><p>Project destination patterns <a href="https://argo-cd.readthedocs.io/en/latest/user-guide/projects/#managing-projects">now support <strong>a </strong></a><a href="https://argo-cd.readthedocs.io/en/latest/user-guide/projects/#managing-projects"><strong>! prefix to negate the pattern</strong></a>. This allows blocking deployments to sensitive destinations (for example, the argocd namespace).</p><figure><img alt="A screenshot of the “Projects” page in the Argo CD web UI. The screenshot shows the “Destinations” section of the page with one destination entry. The “cluster” field holds an asterisk, the “name” field holds an asterisk, and the “namespace” field holds the word “argocd” preceded by an exclamation mark. There is an “edit” button at the top-right of the screenshot, showing that the user may modify the destination fields." src="https://cdn-images-1.medium.com/max/1024/1*dxPjmIpDS9dJixAqf_lyyg.png" /><figcaption>Setting a “deny destination” of the argocd namespace. Applications in this project will be unable to deploy to the `argocd` namespace.</figcaption></figure><figure><img alt="A screenshot of the “sync status” panel in the Argo CD web UI. There is an error message reading “namespace argocd is not permitted in project ‘dev’.”" src="https://cdn-images-1.medium.com/max/1024/1*x8bufecenNveoxDRQw0vcg.png" /><figcaption>Attempting to sync resources to `argocd` when the project has the namespace destination `!argocd`.</figcaption></figure><p>There is also a new field to <strong>restrict deployments to only </strong><a href="https://argo-cd.readthedocs.io/en/latest/user-guide/projects/#project-scoped-repositories-and-clusters"><strong>project-scoped clusters</strong></a> (the default is to allow deployment to any cluster matching a destination pattern).</p><p>Thanks to <a href="https://github.com/blakepettersson">Blake Pettersson</a> for both of these improvements!</p><h4>Better Network Security</h4><p>Traffic between the Argo CD server and the bundled Dex instance is <a href="https://argo-cd.readthedocs.io/en/latest/operator-manual/tls/#configuring-inbound-tls-for-argocd-dex-server">now encrypted by default</a>. And the NetworkPolicy ingress and egress rules between several Argo CD components are now further-restricted, decreasing the risk of lateral movement by an attacker. Thanks to <a href="https://github.com/notfromstatefarm">Jake J</a> from Cobalt and to <a href="https://github.com/34fathombelow">34fathombelow</a> for these improvements. These folks have put in a lot of work on Argo CD security for this release.</p><h3>User Interface Improvements</h3><p>Argo CD supports UI extensions to add custom features to your Argo CD UI. <a href="https://github.com/alexmt">Alexander Matyushentsev</a> from Akuity has added support for loading <a href="https://argo-cd.readthedocs.io/en/latest/developer-guide/ui-extensions/#application-tab-extensions"><strong>extensions in the Application details page</strong></a> (instead of just resource pages, like Pods). He has also added support for <strong>loading </strong><a href="https://github.com/argoproj/argo-cd/commit/58d4068f9a0212072818fdc7a08cd8b088475843"><strong>multiple extensions per resource group/kind</strong></a>.</p><p>Another enhancement adds the ability to <a href="https://github.com/argoproj/argo-cd/commit/f93d678daebcf4c1424d6c309d969cf8150eb4de"><strong>edit HTTPS repository credentials</strong></a> in the Argo CD UI’s “Repositories” page. Previously, the credentials could only be edited by directly modifying a Secret resource in Kubernetes.</p><figure><img alt="Screenshot of the Argo CD web UI’s tool to edit repository credentials. The repository type, project, and URL are visible but not mutable. The username and password fields are text fields which may be edited. There is a “save” and a “cancel” button at the top-right of the repository details panel." src="https://cdn-images-1.medium.com/max/1024/1*Q5KHgLngwqFeiakT5abNsA.png" /><figcaption>Editing HTTPS repository credentials from the UI.</figcaption></figure><p>Thanks to <a href="https://github.com/ciiay">Yi Cai</a> from Red Hat for contributing this UI enhancement!</p><h4>Other Notable Changes</h4><ul><li>Add an experimental option to <a href="https://argo-cd--10678.org.readthedocs.build/en/10678/operator-manual/app-any-namespace/">allow applications in any namespace</a> and restrict projects to applications in certain namespaces (by <a href="https://github.com/jannfis">Jann Fischer</a> from Red Hat)</li><li>The ApplicationSet SCM Provider generator <a href="https://argo-cd.readthedocs.io/en/latest/operator-manual/applicationset/Generators-SCM-Provider/#azure-devops">now supports Azure DevOps</a> (by <a href="https://github.com/brinchm">brinchm</a>)</li><li>The UI <a href="https://github.com/argoproj/argo-cd/commit/af40d52ca03f1a345cf8772da5668ea848904c6c">now respects the “default container” annotation</a> when displaying logs (by <a href="https://github.com/edwardgronroos">Edward Grönroos</a>)</li><li>The Argo CD API <a href="https://github.com/argoproj/argo-cd/commit/37ad43375939dcb66734d4bc04c79a3b9b370877">now supports managing notifications</a> (by <a href="https://github.com/aborilov">Aborilov Pavel</a> from Akuity)</li><li>Argo CD <a href="https://github.com/argoproj/argo-cd/commit/9b4f468f728d44ef4e90d5a1f9cc22c45dd0adc1">now supports Gzip-compressing data stored in Redis </a>for lighter network activity (by <a href="https://github.com/alexmt">Alexander Matyushentsev</a> from Akuity)</li></ul><h3>Where Can I Get the New Release?</h3><p>For more details and installation instructions, check the <a href="https://github.com/argoproj/argo-cd/releases/tag/v2.5.0-rc1">release notes</a>, and <a href="https://argo-cd.readthedocs.io/en/latest/operator-manual/upgrading/2.4-2.5/">upgrade instructions</a>. Please try the release candidate and <a href="https://github.com/argoproj/argo-cd#community">share your feedback</a>. A big thanks to all Argo Community contributors and users for their contributions, feedback, and help in testing the release!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2121f2002ba" width="1" height="1" alt=""><hr><p><a href="https://blog.argoproj.io/argo-cd-v2-5-release-candidate-e2121f2002ba">Argo CD v2.5 release candidate</a> was originally published in <a href="https://blog.argoproj.io/">Argo Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2022 Argo external security audit: Lessons learned]]></title>
            <link>https://blog.argoproj.io/2022-argo-external-security-audit-lessons-learned-951f80e0450d?source=rss-812c77c99da5------2</link>
            <guid isPermaLink="false">https://medium.com/p/951f80e0450d</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[audit]]></category>
            <category><![CDATA[argoproj]]></category>
            <category><![CDATA[argo]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Michael Crenshaw]]></dc:creator>
            <pubDate>Mon, 18 Jul 2022 15:13:40 GMT</pubDate>
            <atom:updated>2022-07-18T15:44:19.870Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A magnifying glass held by fingers with black nail polish. The magnifying glass and hand are in sharp focus, but they are in front of a landscape which is blurred and out of focus. The magnifying glass inverts the landscape, so the glass shows the blurry sky beneath a dark treeline." src="https://cdn-images-1.medium.com/max/1024/1*QMWYrzKpMLkya47nWqbEqw.jpeg" /></figure><p>In early 2022, the Argo team and CNCF began work with Ada Logics to perform a security audit on the four Argo projects. Ada Logics discovered a number of issues which were then either triaged or resolved by the Argo team. This post summarizes the findings and notes a few things learned along the way.</p><p>We are very grateful to <a href="https://www.cncf.io/">CNCF</a> for helping drive this effort, to <a href="https://ostif.org/">OSTIF</a> for financing the audit, and to <a href="https://adalogics.com/">Ada Logics</a> for actually conducting the audit.</p><h3>Summary of findings</h3><p>Ada Logics identified twenty-six issues: seven in Argo CD, six in Argo Workflows, and thirteen in Argo Events. Seven CVEs were issued for Argo CD, and two CVEs were issued for Argo Events. The remaining issues are being tracked as non-CVEs.</p><h3>Argo CD</h3><p>Four of the seven issues identified by Ada Logics were new vulnerabilities. One of the seven (#5 below) was an old vulnerability from a previous audit (it had not been considered a vulnerability at the time, but our thinking has since shifted — see notes below about multi-tenancy). Another vulnerability from the previous audit (#2 below) had not been addressed.</p><p>One additional vulnerability (#3) was discovered by the Argo team while reviewing notes from the Ada Logics draft report.</p><p>All seven vulnerabilities have been patched. They are listed below in descending order of severity. Where applicable, the Ada Logics issue number (ADA-ARGO-SA-*) and/or the issue number from the <a href="https://github.com/argoproj/argoproj/blob/4324729c1c9d3ea21d22afbf7378921826fd2529/docs/argo_security_final_report.pdf">previous audit</a>, conducted by Trail of Bits, (TOB-ARGO-*) is included.</p><ol><li><a href="https://github.com/argoproj/argo-cd/security/advisories/GHSA-h4w9-6x78-8vrj">External URLs for Deployments can include javascript</a> (CVSS 9.0, Critical) (ADA-ARGO-SA-02)</li><li><a href="https://github.com/argoproj/argo-cd/security/advisories/GHSA-2m7h-86qq-fp4v">Insecure entropy in PKCE/Oauth2/OIDC params</a> (CVSS 8.3, High) (TOB-ARGO-017)</li><li><a href="https://github.com/argoproj/argo-cd/security/advisories/GHSA-7943-82jg-wmw5">Certificate verification is skipped for connections to OIDC providers</a> (CVSS 8.3, High)</li><li><a href="https://github.com/argoproj/argo-cd/security/advisories/GHSA-jhqp-vf4w-rpwq">Denial of service through large directory app manifest files</a> (CVSS 6.5, Medium) (ADA-ARGO-SA-17)</li><li><a href="https://github.com/argoproj/argo-cd/security/advisories/GHSA-q4w5-4gq2-98vm">Symlink following allows leaking out-of-bounds YAML files from Argo CD repo-server</a> (CVSS 4.3, Medium) (ADA-ARGO-SA-15)</li><li><a href="https://github.com/argoproj/argo-cd/security/advisories/GHSA-6gcg-hp2x-q54h">Symlink following allows leaking out-of-bound manifests and JSON files from Argo CD repo-server</a> (CVSS 4.3, Medium) (TOB-ARGO-018/ADA-ARGO-SA-16)</li><li><a href="https://github.com/argoproj/argo-cd/security/advisories/GHSA-pmjg-52h9-72qv">A leaked API server encryption key can allow XSS for SSO users</a> (CVSS 2.6, Low) (ADA-ARGO-SA-09)</li></ol><p>All issues which were not evaluated to be vulnerabilities are being tracked in a <a href="https://github.com/orgs/argoproj/projects/19">GitHub project</a>.</p><h4>Patterns</h4><p><strong>Path traversal and symlink following in the repo-server</strong></p><p>Preventing path traversal and out-of-bounds symlink following in the Argo CD repo-server is difficult, due to the many places where paths and symlinks are read during manifest generation. There have been three vulnerabilities involving path traversal and three vulnerabilities involving symlinks (all of moderate or high severity).</p><p>Argo CD 2.4 went a long way towards mitigating these attacks. Each repository in the repo-server’s on-disk cache now gets its own randomized directory, and permissions are locked down when manifest generation is not actively in progress. And plugins no longer share the same cache directory as the built-in config management tools (Helm, Kustomize, etc.).</p><p>Even with these improvements, defeating symlink attacks remains a priority. Argo CD 2.5 will completely block out-of-bounds symlinks in all repositories by default, whether or not those symlinks appear to be involved in manifest generation.</p><p>Until stronger unprivileged filesystem protections (user namespaces) gain wider support with cloud providers, path traversal and symlink-following risks will require constant vigilance. In the meantime, the Argo CD team will continue to evaluate other mitigations, such as per-tenant repo-server segmentation.</p><p><strong>Evolving operator security needs</strong></p><p>With more Argo CD operators using single instances for multiple tenants, the project’s way of evaluating security concerns has shifted. For example, we used to consider source files from git as trusted. But due to the possibility of an adversarial tenant exploiting path traversal, we now must treat source files as potentially-malicious.</p><p>The rise of multi-tenancy has also affected how we calculate vulnerability severity scores. For example, when considering the impact of a cross-site scripting attack via CVE-2022–31035, we evaluated the worst case scenario: a malicious tenant hijacking an admin account to attack other tenants. That analysis yielded a 9.0 (critical) score. Scoring this way helps us communicate urgency to the most security-sensitive operators.</p><h4>Processes</h4><p>The Argo CD team is extremely proud of recent work to improve how we handle each reported vulnerability. The issues reported by Ada Logics gave us an opportunity to test and tweak our processes.</p><p>The security team now tracks vulnerability reports as issues in a private GitHub repository. The issue template includes a checklist to make sure reports are handled uniformly and that important steps are not missed.</p><p>Once we’ve established that a vulnerability is valid, we create a GitHub Security Advisory (GHSA) with a private fork to develop a patch. We also write a detailed Security Advisory with a standard set of components such as affected versions and mitigations.</p><p>Standardized issue tracking in GitHub also gives us an easy way to look back and evaluate what we’ve done and identify trends. For example, since we started using the GitHub issues, we have taken a median of 39 days from initial report to release patches (min. 20, max. 70). If this number shifts over time, we can evaluate what we are doing right (or wrong) to move the needle.</p><h3>Community</h3><p>As the core Argo CD team has worked on vulnerabilities reported by Ada Logics, we’ve been delighted by community-led activity to contribute security enhancements such as <a href="https://github.com/argoproj/argo-cd/pull/9652">deny rules in Project destinations</a> and <a href="https://github.com/argoproj/argo-cd/issues/9738">symlink blocking</a>. This work demonstrates the vitality of the Argo community, and will pay huge dividends by mitigating or eliminating future vulnerabilities. Thank you, Argo community, you are awesome!</p><h3>Argo Events</h3><p>Among the audit findings by Ada Logics for Argo Events, there are 2 high severity vulnerabilities that should be particularly mentioned.</p><ul><li><a href="https://github.com/argoproj/argo-events/security/advisories/GHSA-qpgx-64h2-gc3c">Insecure path traversal in Git Trigger Source can lead to arbitrary file read</a> (ADA-ARGO-SA-13)</li><li><a href="https://github.com/argoproj/argo-events/security/advisories/GHSA-5q86-62xr-3r57">Uses of deprecated API can be used to cause DoS in user-facing endpoints</a> (ADA-ARGO-SA-12)</li></ul><p>One of them is about the potential path traversal and symbol link attack attack when using Git as the triggering source artifactory. As mentioned in the Argo CD portion, this is a pattern across multiple Argo projects. We have made an effort to mitigate this issue in version v1.7.1+.</p><p>The other high severity issue revealed was about using a deprecated package <em>ioutil</em> without enforcing read limit on I/O operations, which could potentially cause DoS attack for all the webhook based EventSources such as BitBucket, Gitlab, etc.</p><p>Besides these, another issue revealed by the audit was the use of deprecated or unmaintained libraries, which could potentially mean including undiscovered and not reported vulnerabilities. We have been making efforts to move away from those libraries. We recommend upgrading Argo Event to version v1.7.1+ to make it more secure.</p><h3>Summary</h3><p>The Argo team owes a huge thanks to the CNCF, OSTIF, and Ada Logics for sponsoring, facilitating, and conducting this security audit. If you have questions about the report, drop a comment here or visit us in <a href="https://argoproj.github.io/community/join-slack/">CNCF Slack</a>.</p><h3>Links</h3><ul><li>Full report: <a href="https://github.com/argoproj/argoproj/blob/master/docs/argo_security_audit_2022.pdf">https://github.com/argoproj/argoproj/blob/master/docs/argo_security_audit_2022.pdf</a></li><li>Ada Logics announcement: <a href="https://adalogics.com/blog/argo-security-audit-2022">https://adalogics.com/blog/argo-security-audit-2022</a></li><li>OSTIF announcement: <a href="https://ostif.org/our-audit-of-argo-is-complete-critical-and-high-severity-security-issues-found-and-fixed/">https://ostif.org/our-audit-of-argo-is-complete-critical-and-high-severity-security-issues-found-and-fixed/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=951f80e0450d" width="1" height="1" alt=""><hr><p><a href="https://blog.argoproj.io/2022-argo-external-security-audit-lessons-learned-951f80e0450d">2022 Argo external security audit: Lessons learned</a> was originally published in <a href="https://blog.argoproj.io/">Argo Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Breaking Changes in Argo CD 2.4]]></title>
            <link>https://blog.argoproj.io/breaking-changes-in-argo-cd-2-4-29e3c2ac30c9?source=rss-812c77c99da5------2</link>
            <guid isPermaLink="false">https://medium.com/p/29e3c2ac30c9</guid>
            <dc:creator><![CDATA[Michael Crenshaw]]></dc:creator>
            <pubDate>Mon, 06 Jun 2022 20:42:30 GMT</pubDate>
            <atom:updated>2022-06-06T21:01:20.135Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/259/1*xJtRC36vvNLpRn73HKs05Q.jpeg" /></figure><p>Argo CD 2.4 includes some <a href="https://blog.argoproj.io/argo-cd-v2-4-release-candidate-d1a0eef6b908">awesome improvement</a>s and also gave the Argo CD team an opportunity to clean up some tech debt.</p><p>This clean-up introduced some breaking changes, so make sure to read up on these changes below to ensure a smooth upgrade process.</p><h3>Update your Helm 2 or Ksonnet manifests</h3><p>Argo CD 2.4 removes Helm 2 and Ksonnet support, as these have reached end of life.</p><p>If you use Ksonnet, convert your manifests to a <a href="https://argo-cd.readthedocs.io/en/stable/user-guide/application_sources/">supported config management tool</a>. If you use Helm 2, follow their <a href="https://helm.sh/docs/topics/v2_v3_migration/">migration guide</a> before upgrading to Argo CD 2.4.</p><h3>Update your RBAC to handle Web Terminal</h3><p>Argo CD 2.4 introduces a new Web Terminal feature. This allows users to “exec into” Pods via the Argo CD UI.</p><p>It’s an awesome feature, and it’s also powerful. <strong>If you use RBAC wildcards, you might unintentionally enable this feature for users that shouldnt have access to it when upgrading to 2.4.</strong></p><p>The third column in your <a href="https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/">Argo CD RBAC config</a> is the “resource” column. If you have a wildcard (*) in that column, the new exec resource is automatically included. For example:</p><pre>p, role:org-admin, *, create, my-proj/*, allow</pre><p>To continue allowing all the non-exec resources, enumerate them instead of using *. You would replace the example above with the following:</p><pre>p, role: org-admin, clusters, create, my-proj/*, allow<br>p, role: org-admin, projects, create, my-proj/*, allow<br>p, role: org-admin, applications, create, my-proj/*, allow<br>p, role: org-admin, repositories, create, my-proj/*, allow<br>p, role: org-admin, certificates, create, my-proj/*, allow<br>p, role: org-admin, accounts, create, my-proj/*, allow<br>p, role: org-admin, gpgkeys, create, my-proj/*, allow</pre><h3>Test the repository sever with its new Service Account</h3><p>As a security enhancement, Argo CD 2.4’s install manifests include a dedicated Service Account for the <a href="https://argo-cd.readthedocs.io/en/stable/operator-manual/architecture/#repository-server">repository server</a> Deployment.</p><p>If your setup relies on the repository server using the default Service Account (for example, if a plugin uses the default Service Account for auth), upgrading to Argo CD 2.4 could cause problems. You may need to replicate customizations from the default Service Account to the argocd-repo-server Service Account.</p><p>We recommend testing Argo CD 2.4 on a non-production instance before upgrading.</p><h3>Update your plugins’ configuration</h3><p>The introduction of <a href="https://argo-cd.readthedocs.io/en/stable/user-guide/config-management-plugins/">config management plugins</a> has allowed people to customize Argo CD in many incredible ways! The plugin system is designed for flexibility, and by necessity plugins are granted a certain level of trust in the <a href="https://argo-cd.readthedocs.io/en/stable/operator-manual/architecture/">Argo CD architecture</a>. This also means that Argo CD can’t validate or guarantee that an external plugin is secure! Design your custom plugins carefully and always audit any third-party plugins before installing them.</p><p>The following breaking changes in 2.4 are designed to help plugin authors keep their implementation secure.</p><p><strong>If you use config management plugins, it’s critical to read the following three sections carefully.</strong> If you do not use config management plugins, feel free to skip to the Conclusion!</p><h4>Update your plugins to use newly-prefixed environment variables</h4><p>Config management plugins accept user-defined variables from the Application manifest. For example:</p><pre>apiVersion: argoproj.io/v1alpha1<br>kind: Application<br>spec:<br>  source:<br>    plugin:<br>      env:<br>        - name: FOO<br>          value: bar</pre><p>Before 2.4, those environment variables were injected in the init and generate commands configured in the plugin.</p><p>Since many plugins use third-party tools whose behavior is configurable via environment variables (such as git), we do not want to allow users to set arbitrary environment variables.</p><p><em>Starting with Argo CD 2.4, all user-supplied environment variables will be prefixed with </em><em>ARGOCD_ENV_ before being sent to the plugin’s commands.</em> The plugin author can still choose to remove the prefix (export FOO=$ARGOCD_ENV_FOO), but they must do so explicitly.</p><p>If you have written a custom config management plugin which relies on user-supplied environment variables, <strong>update your plugin logic to handle the new prefix before upgrading to 2.4</strong>.</p><p><strong>If you use a third-party plugin, make sure the plugin is compatible with Argo CD 2.4. </strong>If the project doesn’t explicitly advertise support for 2.4, open an issue to verify whether they have added support.</p><p>(Note: If you don’t need a new 2.4 feature, it’s safe to stay on the 2.3.x series until all your plugins support 2.4. We’ll continue publishing security patches for 2.3.x until 2.6.0 is released.)</p><h4>Confirm that your sidecar plugin environment variables are set on the sidecar container</h4><p>If you use a plugin that’s installed as a sidecar (instead of in the argocd-cm ConfigMap), a <a href="https://github.com/argoproj/argo-cd/pull/9566">bug fix in 2.4</a> could prevent the plugin from receiving all its required environment variables.</p><p>Before 2.4, environment variables on the main repo-server container were sent to the plugin’s commands, taking precedence over environment variables set on the sidecar.</p><p>Starting with 2.4, environment variables (besides the standard <a href="https://argo-cd.readthedocs.io/en/stable/user-guide/build-environment/">build environment</a> and user-supplied variables) must be set directly on the sidecar container in order to be picked up by the configured plugin commands.</p><p><strong>Before upgrading to Argo CD 2.4, check your sidecar plugins’ configurations to see what environment variables they require.</strong> If any of them is set on the main repo-server container instead of the sidecar container, you might need to also set the environment variable on the sidecar container.</p><h4>Replace the shared /tmp volume in plugin sidecars</h4><p>If you use a plugin that’s installed as a sidecar (instead of in the argocd-cm ConfigMap), it mounts a volume at /tmp. Before 2.4, that volume needed to be the same as the temp volume mounted by the main repo-server container.</p><p>Starting with Argo CD 2.4, each sidecar plugin should mount its own temp volume. This helps mitigate the risk of directory traversal attacks. For example:</p><pre>apiVersion: apps/v1<br>kind: Deployment<br>metadata:<br>  name: argocd-repo-server<br>spec:<br>  template:<br>    spec:<br>      containers:<br>      - name: your-plugin-name<br>        volumeMounts:<br>        - mountPath: /tmp<br>          name: your-plugin-name-tmp<br>      volumes:<br>        # Add this volume.<br>        - name: your-plugin-name-tmp<br>          emptyDir: {}</pre><h3>Extra credit: prepare for 2.5 by enabling logs RBAC enforcement</h3><p>Argo CD 2.5 will include finer-grained RBAC control of logs access. You can <a href="https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/upgrading/2.3-2.4.md#enable-logs-rbac-enforcement">opt in to log RBAC control in 2.4</a> to make the 2.4-to-2.5 upgrade process faster and easier.</p><h3>Conclusion</h3><p>The Argo CD team takes breaking changes seriously. We’ll only include a breaking change if we’re certain it’s critical for the health of the project and to the users.</p><p>The items above are also listed in the <a href="https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/upgrading/2.3-2.4.md">2.3 to 2.4 upgrade guide</a>. If you are upgrading from an older version, read the <a href="https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/upgrading/overview.md">other upgrade guides</a> before skipping versions. If you follow all the instructions, the upgrade process should go smoothly.</p><p>If you have questions or encounter issues, reach out on <a href="https://argoproj.github.io/community/join-slack">Slack</a> or <a href="https://github.com/argoproj/argo-cd/issues">GitHub</a>, and we’ll be happy to help!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29e3c2ac30c9" width="1" height="1" alt=""><hr><p><a href="https://blog.argoproj.io/breaking-changes-in-argo-cd-2-4-29e3c2ac30c9">Breaking Changes in Argo CD 2.4</a> was originally published in <a href="https://blog.argoproj.io/">Argo Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>