fkie_cve-2022-31016
Vulnerability from fkie_nvd
Published
2022-06-25 08:15
Modified
2024-11-21 07:03
Severity ?
6.5 (Medium) - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
6.5 (Medium) - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Summary
Argo CD is a declarative continuous deployment for Kubernetes. Argo CD versions v0.7.0 and later are vulnerable to an uncontrolled memory consumption bug, allowing an authorized malicious user to crash the repo-server service, resulting in a Denial of Service. The attacker must be an authenticated Argo CD user authorized to deploy Applications from a repository which contains (or can be made to contain) a large file. The fix for this vulnerability is available in versions 2.3.5, 2.2.10, 2.1.16, and later. There are no known workarounds. Users are recommended to upgrade.
References
security-advisories@github.comhttps://github.com/argoproj/argo-cd/security/advisories/GHSA-jhqp-vf4w-rpwqPatch, Third Party Advisory
af854a3a-2127-422b-91ae-364da2661108https://github.com/argoproj/argo-cd/security/advisories/GHSA-jhqp-vf4w-rpwqPatch, Third Party Advisory
Impacted products
Vendor Product Version
argoproj argo_cd *
argoproj argo_cd *
argoproj argo_cd *
argoproj argo_cd *


To clipboard 

{
   configurations: [
      {
         nodes: [
            {
               cpeMatch: [
                  {
                     criteria: "cpe:2.3:a:argoproj:argo_cd:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "0468CA77-C2E6-43B2-9018-B5880AF0C9D9",
                     versionEndExcluding: "2.1.16",
                     versionStartIncluding: "0.7.0",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:argoproj:argo_cd:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "CC600EA6-AA95-478D-8D05-B0DD333784ED",
                     versionEndExcluding: "2.2.10",
                     versionStartIncluding: "2.2.0",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:argoproj:argo_cd:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "1C173520-6BD2-493F-97AD-04D38691C6CA",
                     versionEndExcluding: "2.3.5",
                     versionStartIncluding: "2.3.0",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:argoproj:argo_cd:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "82702C21-3D33-4436-8739-1FAE9408DD83",
                     versionEndExcluding: "2.4.1",
                     versionStartIncluding: "2.4.0",
                     vulnerable: true,
                  },
               ],
               negate: false,
               operator: "OR",
            },
         ],
      },
   ],
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "Argo CD is a declarative continuous deployment for Kubernetes. Argo CD versions v0.7.0 and later are vulnerable to an uncontrolled memory consumption bug, allowing an authorized malicious user to crash the repo-server service, resulting in a Denial of Service. The attacker must be an authenticated Argo CD user authorized to deploy Applications from a repository which contains (or can be made to contain) a large file. The fix for this vulnerability is available in versions 2.3.5, 2.2.10, 2.1.16, and later. There are no known workarounds. Users are recommended to upgrade.",
      },
      {
         lang: "es",
         value: "Argo CD es un despliegue continuo declarativo para Kubernetes. Argo CD versiones v0.7.0 y posteriores, son vulnerables a un error de consumo de memoria no controlado, lo que permite a un usuario malicioso autorizado bloquear el servicio de repo-servidor, resultando en una denegación de servicio. El atacante debe ser un usuario autenticado de Argo CD autorizado a desplegar Aplicaciones desde un repositorio que contenga (o pueda hacerse que contenga) un archivo grande. La corrección de esta vulnerabilidad está disponible en versiones 2.3.5, 2.2.10, 2.1.16 y posteriores. No se presentan mitigaciones conocidas. Es recomendado a usuarios actualizar",
      },
   ],
   id: "CVE-2022-31016",
   lastModified: "2024-11-21T07:03:43.183",
   metrics: {
      cvssMetricV2: [
         {
            acInsufInfo: false,
            baseSeverity: "MEDIUM",
            cvssData: {
               accessComplexity: "LOW",
               accessVector: "NETWORK",
               authentication: "SINGLE",
               availabilityImpact: "PARTIAL",
               baseScore: 4,
               confidentialityImpact: "NONE",
               integrityImpact: "NONE",
               vectorString: "AV:N/AC:L/Au:S/C:N/I:N/A:P",
               version: "2.0",
            },
            exploitabilityScore: 8,
            impactScore: 2.9,
            obtainAllPrivilege: false,
            obtainOtherPrivilege: false,
            obtainUserPrivilege: false,
            source: "nvd@nist.gov",
            type: "Primary",
            userInteractionRequired: false,
         },
      ],
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "HIGH",
               baseScore: 6.5,
               baseSeverity: "MEDIUM",
               confidentialityImpact: "NONE",
               integrityImpact: "NONE",
               privilegesRequired: "LOW",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
               version: "3.1",
            },
            exploitabilityScore: 2.8,
            impactScore: 3.6,
            source: "security-advisories@github.com",
            type: "Secondary",
         },
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "HIGH",
               baseScore: 6.5,
               baseSeverity: "MEDIUM",
               confidentialityImpact: "NONE",
               integrityImpact: "NONE",
               privilegesRequired: "LOW",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
               version: "3.1",
            },
            exploitabilityScore: 2.8,
            impactScore: 3.6,
            source: "nvd@nist.gov",
            type: "Primary",
         },
      ],
   },
   published: "2022-06-25T08:15:09.307",
   references: [
      {
         source: "security-advisories@github.com",
         tags: [
            "Patch",
            "Third Party Advisory",
         ],
         url: "https://github.com/argoproj/argo-cd/security/advisories/GHSA-jhqp-vf4w-rpwq",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         tags: [
            "Patch",
            "Third Party Advisory",
         ],
         url: "https://github.com/argoproj/argo-cd/security/advisories/GHSA-jhqp-vf4w-rpwq",
      },
   ],
   sourceIdentifier: "security-advisories@github.com",
   vulnStatus: "Modified",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-400",
            },
         ],
         source: "security-advisories@github.com",
         type: "Secondary",
      },
      {
         description: [
            {
               lang: "en",
               value: "CWE-770",
            },
         ],
         source: "nvd@nist.gov",
         type: "Primary",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.