<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 13:02:20 +0000</lastBuildDate>
    <item>
      <title>bdu:2022-03977</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2022-03977</link>
      <description>bdu:2022-03977</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2022-03977</guid>
    </item>
    <item>
      <title>EUVD-2026-233967</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-233967</link>
      <description>EUVD-2026-233967</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-233967</guid>
    </item>
    <item>
      <title>fkie_cve-2022-31034</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-31034</link>
      <description>&lt;p&gt;Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting with v0.11.0 are vulnerable to a variety of attacks when an SSO login is initiated from the Argo CD CLI or UI. The vulnerabilities are due to the use of insufficiently random values in parameters in Oauth2/OIDC login flows. In each case, using a relatively-predictable (time-based) seed in a non-cryptographically-secure pseudo-random number generator made the parameter less random than required by the relevant spec or by general best practices. In some cases, using too short a value made the entropy even less sufficient. The attacks on login flows which are meant to be mitigated by these parameters are difficult to accomplish but can have a high impact potentially granting an attacker admin access to Argo CD. Patches for this vulnerability has been released in the following Argo CD versions: v2.4.1, v2.3.5, v2.2.10 and v2.1.16. There are no known workarounds for this vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting with v0.11.0 are vulnerable to a variety of attacks when an SSO login is initiated from the Argo CD CLI or UI. The vulnerabilities are due to the use of insufficiently random values in parameters in Oauth2/OIDC login flows. In each case, using a relatively-predictable (time-based) seed in a non-cryptographically-secure pseudo-random number generator made the parameter less random than required by the relevant spec or by general best practices. In some cases, using too short a value made the entropy even less sufficient. The attacks on login flows which are meant to be mitigated by these parameters are difficult to accomplish but can have a high impact potentially granting an attacker admin access to Argo CD. Patches for this vulnerability has been released in the following Argo CD versions: v2.4.1, v2.3.5, v2.2.10 and v2.1.16. There are no known workarounds for this vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-31034</guid>
    </item>
    <item>
      <title>GHSA-2m7h-86qq-fp4v — Insecure entropy in Argo CD's PKCE/Oauth2/OIDC params</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2m7h-86qq-fp4v</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/argoproj/argo-cd, Go: github.com/argoproj/argo-cd/v2&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;All versions of Argo CD starting with v0.11.0 are vulnerable to a variety of attacks when an SSO login is initiated from the Argo CD CLI or UI. The vulnerabilities are due to the use of insufficiently random values in parameters in Oauth2/OIDC login flows. In each case, using a relatively-predictable (time-based) seed in a non-cryptographically-secure pseudo-random number generator made the parameter less random than required by the relevant spec or by general best practices. In some cases, using too short a value made the entropy even less sufficient. (The specific weak parameters are listed in the References section.)&lt;/p&gt;
&lt;p&gt;The attacks on login flows which are meant to be mitigated by these parameters are difficult to accomplish but can have a high impact (potentially granting an attacker admin access to Argo CD). The CVSS for this Security Advisory assumes the worst-case scenario.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;A patch for this vulnerability has been released in the following Argo CD versions:&lt;/p&gt;
&lt;p&gt;* v2.4.1
* v2.3.5
* v2.2.10
* v2.1.16&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;There are no workarounds. You must upgrade to a patched version to resolve the vulnerability.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;These are the insufficiently-random parameters:&lt;/p&gt;
&lt;p&gt;1. (since 0.11.0) The [`state` parameter](https://datatracker.ietf.org/doc/html/rfc6749#section-4.1.1) generated by the `argocd login` command for Oauth2 login used a non-cryptographically secure source of entropy and generated a parameter that was too short to provide the entrop…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/argoproj/argo-cd, Go: github.com/argoproj/argo-cd/v2&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;All versions of Argo CD starting with v0.11.0 are vulnerable to a variety of attacks when an SSO login is initiated from the Argo CD CLI or UI. The vulnerabilities are due to the use of insufficiently random values in parameters in Oauth2/OIDC login flows. In each case, using a relatively-predictable (time-based) seed in a non-cryptographically-secure pseudo-random number generator made the parameter less random than required by the relevant spec or by general best practices. In some cases, using too short a value made the entropy even less sufficient. (The specific weak parameters are listed in the References section.)&lt;/p&gt;
&lt;p&gt;The attacks on login flows which are meant to be mitigated by these parameters are difficult to accomplish but can have a high impact (potentially granting an attacker admin access to Argo CD). The CVSS for this Security Advisory assumes the worst-case scenario.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;A patch for this vulnerability has been released in the following Argo CD versions:&lt;/p&gt;
&lt;p&gt;* v2.4.1
* v2.3.5
* v2.2.10
* v2.1.16&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;There are no workarounds. You must upgrade to a patched version to resolve the vulnerability.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;These are the insufficiently-random parameters:&lt;/p&gt;
&lt;p&gt;1. (since 0.11.0) The [`state` parameter](https://datatracker.ietf.org/doc/html/rfc6749#section-4.1.1) generated by the `argocd login` command for Oauth2 login used a non-cryptographically secure source of entropy and generated a parameter that was too short to provide the entrop…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2m7h-86qq-fp4v</guid>
    </item>
    <item>
      <title>gsd-2022-31034</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-31034</link>
      <description>gsd-2022-31034</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-31034</guid>
    </item>
    <item>
      <title>RHSA-2022:5152 — Red Hat Security Advisory: Red Hat OpenShift GitOps security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2022:5152</link>
      <description>&lt;p&gt;argocd: vulnerable to an uncontrolled memory consumption bug argocd: vulnerable to a variety of attacks when an SSO login is initiated from the Argo CD CLI or the UI. argocd: cross-site scripting (XSS) allow a malicious user to inject a javascript link in the UI argocd: vulnerable to a symlink following bug allowing a malicious user with repository write access&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;argocd: vulnerable to an uncontrolled memory consumption bug argocd: vulnerable to a variety of attacks when an SSO login is initiated from the Argo CD CLI or the UI. argocd: cross-site scripting (XSS) allow a malicious user to inject a javascript link in the UI argocd: vulnerable to a symlink following bug allowing a malicious user with repository write access&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2022:5152</guid>
    </item>
  </channel>
</rss>
