March 2024 Summaries
2 posts from Codefresh
Filter
Month:
Year:
Post Summaries
Back to Blog
In September 2023, security researchers from KTrust identified and reported three security vulnerabilities in Argo CD, which were addressed in coordination with Argo maintainers and other partners such as Codefresh, RedHat, Intuit, and Akuity. These vulnerabilities, known as CVEs, involved attempts to bypass login protections and could potentially allow unauthorized access to user accounts on unpatched versions of Argo CD. While Codefresh GitOps users were less at risk due to the platform's architecture, updates were still recommended, and security patches were issued for Argo CD versions 2.10, 2.9, and 2.8. Users were advised to update their systems promptly or employ additional security measures like removing default admin accounts and restricting API access. The Argo Project collaborates with HackerOne and the CNCF on bug bounties to incentivize and reward contributions toward improving security, underscoring the importance of community efforts in addressing such vulnerabilities.
Mar 17, 2024
412 words in the original blog post.
The text discusses the challenges and solutions for managing secrets in GitOps deployments, particularly focusing on integrating AWS Secrets Manager with Kubernetes clusters using the External Secrets Operator (ESO). The article outlines the process of using ESO to retrieve secrets from AWS Secrets Manager and making them available as Kubernetes Secrets, which can then be utilized by applications deployed using Argo CD and Codefresh on an Amazon EKS cluster. It highlights the benefits of this approach, including the secure and dynamic fetching of secrets without storing sensitive information in Git, and provides a step-by-step guide to setting up the necessary infrastructure and configurations. The article also hints at an alternative method using the ArgoCD Vault Plugin for those interested in exploring different techniques for secret management in GitOps environments.
Mar 05, 2024
1,048 words in the original blog post.