gsd-2023-25163
Vulnerability from gsd
Modified
2023-12-13 01:20
Details
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting with v2.6.0-rc1 have an output sanitization bug which leaks repository access credentials in error messages. These error messages are visible to the user, and they are logged. The error message is visible when a user attempts to create or update an Application via the Argo CD API (and therefor the UI or CLI). The user must have `applications, create` or `applications, update` RBAC access to reach the code which may produce the error. The user is not guaranteed to be able to trigger the error message. They may attempt to spam the API with requests to trigger a rate limit error from the upstream repository. If the user has `repositories, update` access, they may edit an existing repository to introduce a URL typo or otherwise force an error message. But if they have that level of access, they are probably intended to have access to the credentials anyway. A patch for this vulnerability has been released in version 2.6.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Aliases
Aliases
CVE-2023-25163


To clipboard 

{
  "GSD": {
    "alias": "CVE-2023-25163",
    "id": "GSD-2023-25163"
  },
  "gsd": {
    "metadata": {
      "exploitCode": "unknown",
      "remediation": "unknown",
      "reportConfidence": "confirmed",
      "type": "vulnerability"
    },
    "osvSchema": {
      "aliases": [
        "CVE-2023-25163"
      ],
      "details": "Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting with v2.6.0-rc1 have an output sanitization bug which leaks repository access credentials in error messages. These error messages are visible to the user, and they are logged. The error message is visible when a user attempts to create or update an Application via the Argo CD API (and therefor the UI or CLI). The user must have `applications, create` or `applications, update` RBAC access to reach the code which may produce the error. The user is not guaranteed to be able to trigger the error message. They may attempt to spam the API with requests to trigger a rate limit error from the upstream repository. If the user has `repositories, update` access, they may edit an existing repository to introduce a URL typo or otherwise force an error message. But if they have that level of access, they are probably intended to have access to the credentials anyway. A patch for this vulnerability has been released in version 2.6.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.",
      "id": "GSD-2023-25163",
      "modified": "2023-12-13T01:20:39.957961Z",
      "schema_version": "1.4.0"
    }
  },
  "namespaces": {
    "cve.org": {
      "CVE_data_meta": {
        "ASSIGNER": "security-advisories@github.com",
        "ID": "CVE-2023-25163",
        "STATE": "PUBLIC"
      },
      "affects": {
        "vendor": {
          "vendor_data": [
            {
              "product": {
                "product_data": [
                  {
                    "product_name": "argo-cd",
                    "version": {
                      "version_data": [
                        {
                          "version_affected": "=",
                          "version_value": "\u003e= 2.6.0-rc1, \u003c 2.6.1"
                        }
                      ]
                    }
                  }
                ]
              },
              "vendor_name": "argoproj"
            }
          ]
        }
      },
      "data_format": "MITRE",
      "data_type": "CVE",
      "data_version": "4.0",
      "description": {
        "description_data": [
          {
            "lang": "eng",
            "value": "Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting with v2.6.0-rc1 have an output sanitization bug which leaks repository access credentials in error messages. These error messages are visible to the user, and they are logged. The error message is visible when a user attempts to create or update an Application via the Argo CD API (and therefor the UI or CLI). The user must have `applications, create` or `applications, update` RBAC access to reach the code which may produce the error. The user is not guaranteed to be able to trigger the error message. They may attempt to spam the API with requests to trigger a rate limit error from the upstream repository. If the user has `repositories, update` access, they may edit an existing repository to introduce a URL typo or otherwise force an error message. But if they have that level of access, they are probably intended to have access to the credentials anyway. A patch for this vulnerability has been released in version 2.6.1. Users are advised to upgrade. There are no known workarounds for this vulnerability."
          }
        ]
      },
      "impact": {
        "cvss": [
          {
            "attackComplexity": "HIGH",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 6.3,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "NONE",
            "privilegesRequired": "LOW",
            "scope": "CHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N",
            "version": "3.1"
          }
        ]
      },
      "problemtype": {
        "problemtype_data": [
          {
            "description": [
              {
                "cweId": "CWE-532",
                "lang": "eng",
                "value": "CWE-532: Insertion of Sensitive Information into Log File"
              }
            ]
          }
        ]
      },
      "references": {
        "reference_data": [
          {
            "name": "https://github.com/argoproj/argo-cd/security/advisories/GHSA-mv6w-j4xc-qpfw",
            "refsource": "MISC",
            "url": "https://github.com/argoproj/argo-cd/security/advisories/GHSA-mv6w-j4xc-qpfw"
          },
          {
            "name": "https://github.com/argoproj/argo-cd/issues/12309",
            "refsource": "MISC",
            "url": "https://github.com/argoproj/argo-cd/issues/12309"
          },
          {
            "name": "https://github.com/argoproj/argo-cd/pull/12320",
            "refsource": "MISC",
            "url": "https://github.com/argoproj/argo-cd/pull/12320"
          },
          {
            "name": "https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/",
            "refsource": "MISC",
            "url": "https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/"
          }
        ]
      },
      "source": {
        "advisory": "GHSA-mv6w-j4xc-qpfw",
        "discovery": "UNKNOWN"
      }
    },
    "gitlab.com": {
      "advisories": [
        {
          "affected_range": "\u003e=v2.6.0-rc1 \u003cv2.6.1",
          "affected_versions": "All versions starting from 2.6.0-rc1 before 2.6.1",
          "cwe_ids": [
            "CWE-1035",
            "CWE-532",
            "CWE-937"
          ],
          "date": "2023-02-08",
          "description": "Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting with v2.6.0-rc1 have an output sanitization bug which leaks repository access credentials in error messages. These error messages are visible to the user, and they are logged. The error message is visible when a user attempts to create or update an Application via the Argo CD API (and therefor the UI or CLI). The user must have `applications, create` or `applications, update` RBAC access to reach the code which may produce the error. The user is not guaranteed to be able to trigger the error message. They may attempt to spam the API with requests to trigger a rate limit error from the upstream repository. If the user has `repositories, update` access, they may edit an existing repository to introduce a URL typo or otherwise force an error message. But if they have that level of access, they are probably intended to have access to the credentials anyway. A patch for this vulnerability has been released in version 2.6.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.",
          "fixed_versions": [
            "v2.6.1"
          ],
          "identifier": "CVE-2023-25163",
          "identifiers": [
            "GHSA-mv6w-j4xc-qpfw",
            "CVE-2023-25163"
          ],
          "not_impacted": "All versions before 2.6.0-rc1, all versions starting from 2.6.1",
          "package_slug": "go/github.com/argoproj/argo-cd",
          "pubdate": "2023-02-08",
          "solution": "Upgrade to version 2.6.1 or above.",
          "title": "Insertion of Sensitive Information into Log File",
          "urls": [
            "https://github.com/argoproj/argo-cd/security/advisories/GHSA-mv6w-j4xc-qpfw",
            "https://nvd.nist.gov/vuln/detail/CVE-2023-25163",
            "https://github.com/argoproj/argo-cd/issues/12309",
            "https://github.com/argoproj/argo-cd/pull/12320",
            "https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/",
            "https://github.com/advisories/GHSA-mv6w-j4xc-qpfw"
          ],
          "uuid": "20ab6d52-1ee0-441e-8cc5-3d80ab7b3dc8",
          "versions": [
            {
              "commit": {
                "sha": "81e40d53fe8eee50b00ab38c4b07b34b3dcd6d25",
                "tags": [
                  "v2.6.0-rc1"
                ],
                "timestamp": "20221219163627"
              },
              "number": "v2.6.0-rc1"
            },
            {
              "commit": {
                "sha": "3f143c9307f99a61bf7049a2b1c7194699a7c21b",
                "tags": [
                  "v2.6.1"
                ],
                "timestamp": "20230208183536"
              },
              "number": "v2.6.1"
            }
          ]
        },
        {
          "affected_range": "\u003e=v2.6.0-rc1 \u003cv2.6.1",
          "affected_versions": "All versions starting from 2.6.0-rc1 before 2.6.1",
          "cwe_ids": [
            "CWE-1035",
            "CWE-532",
            "CWE-937"
          ],
          "date": "2023-02-15",
          "description": "Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting with v2.6.0-rc1 have an output sanitization bug which leaks repository access credentials in error messages. These error messages are visible to the user, and they are logged. The error message is visible when a user attempts to create or update an Application via the Argo CD API (and therefor the UI or CLI). The user must have `applications, create` or `applications, update` RBAC access to reach the code which may produce the error. The user is not guaranteed to be able to trigger the error message. They may attempt to spam the API with requests to trigger a rate limit error from the upstream repository. If the user has `repositories, update` access, they may edit an existing repository to introduce a URL typo or otherwise force an error message. But if they have that level of access, they are probably intended to have access to the credentials anyway. A patch for this vulnerability has been released in version 2.6.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.",
          "fixed_versions": [
            "v2.6.1"
          ],
          "identifier": "CVE-2023-25163",
          "identifiers": [
            "GHSA-mv6w-j4xc-qpfw",
            "CVE-2023-25163"
          ],
          "not_impacted": "All versions before 2.6.0-rc1, all versions starting from 2.6.1",
          "package_slug": "go/github.com/argoproj/argo-cd/v2",
          "pubdate": "2023-02-08",
          "solution": "Upgrade to version 2.6.1 or above.",
          "title": "Insertion of Sensitive Information into Log File",
          "urls": [
            "https://github.com/argoproj/argo-cd/security/advisories/GHSA-mv6w-j4xc-qpfw",
            "https://nvd.nist.gov/vuln/detail/CVE-2023-25163",
            "https://github.com/argoproj/argo-cd/issues/12309",
            "https://github.com/argoproj/argo-cd/pull/12320",
            "https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/",
            "https://pkg.go.dev/vuln/GO-2023-1548",
            "https://github.com/advisories/GHSA-mv6w-j4xc-qpfw"
          ],
          "uuid": "a20205eb-3b62-467d-a9f7-de11bde96144",
          "versions": [
            {
              "commit": {
                "sha": "81e40d53fe8eee50b00ab38c4b07b34b3dcd6d25",
                "tags": [
                  "v2.6.0-rc1"
                ],
                "timestamp": "20221219163627"
              },
              "number": "v2.6.0-rc1"
            },
            {
              "commit": {
                "sha": "3f143c9307f99a61bf7049a2b1c7194699a7c21b",
                "tags": [
                  "v2.6.1"
                ],
                "timestamp": "20230208183536"
              },
              "number": "v2.6.1"
            }
          ]
        }
      ]
    },
    "nvd.nist.gov": {
      "configurations": {
        "CVE_data_version": "4.0",
        "nodes": [
          {
            "children": [],
            "cpe_match": [
              {
                "cpe23Uri": "cpe:2.3:a:linuxfoundation:argo_continuous_delivery:2.6.0:rc1:*:*:*:kubernetes:*:*",
                "cpe_name": [],
                "vulnerable": true
              },
              {
                "cpe23Uri": "cpe:2.3:a:linuxfoundation:argo_continuous_delivery:2.6.0:rc2:*:*:*:kubernetes:*:*",
                "cpe_name": [],
                "vulnerable": true
              },
              {
                "cpe23Uri": "cpe:2.3:a:linuxfoundation:argo_continuous_delivery:2.6.0:rc3:*:*:*:kubernetes:*:*",
                "cpe_name": [],
                "vulnerable": true
              },
              {
                "cpe23Uri": "cpe:2.3:a:linuxfoundation:argo_continuous_delivery:2.6.0:rc4:*:*:*:kubernetes:*:*",
                "cpe_name": [],
                "vulnerable": true
              },
              {
                "cpe23Uri": "cpe:2.3:a:linuxfoundation:argo_continuous_delivery:2.6.0:rc5:*:*:*:kubernetes:*:*",
                "cpe_name": [],
                "vulnerable": true
              },
              {
                "cpe23Uri": "cpe:2.3:a:linuxfoundation:argo_continuous_delivery:2.6.0:rc6:*:*:*:kubernetes:*:*",
                "cpe_name": [],
                "vulnerable": true
              },
              {
                "cpe23Uri": "cpe:2.3:a:linuxfoundation:argo_continuous_delivery:2.6.0:rc7:*:*:*:kubernetes:*:*",
                "cpe_name": [],
                "vulnerable": true
              },
              {
                "cpe23Uri": "cpe:2.3:a:linuxfoundation:argo_continuous_delivery:2.6.0:-:*:*:*:kubernetes:*:*",
                "cpe_name": [],
                "vulnerable": true
              }
            ],
            "operator": "OR"
          }
        ]
      },
      "cve": {
        "CVE_data_meta": {
          "ASSIGNER": "security-advisories@github.com",
          "ID": "CVE-2023-25163"
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "en",
              "value": "Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting with v2.6.0-rc1 have an output sanitization bug which leaks repository access credentials in error messages. These error messages are visible to the user, and they are logged. The error message is visible when a user attempts to create or update an Application via the Argo CD API (and therefor the UI or CLI). The user must have `applications, create` or `applications, update` RBAC access to reach the code which may produce the error. The user is not guaranteed to be able to trigger the error message. They may attempt to spam the API with requests to trigger a rate limit error from the upstream repository. If the user has `repositories, update` access, they may edit an existing repository to introduce a URL typo or otherwise force an error message. But if they have that level of access, they are probably intended to have access to the credentials anyway. A patch for this vulnerability has been released in version 2.6.1. Users are advised to upgrade. There are no known workarounds for this vulnerability."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "en",
                  "value": "CWE-532"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://github.com/argoproj/argo-cd/issues/12309",
              "refsource": "MISC",
              "tags": [
                "Issue Tracking",
                "Third Party Advisory"
              ],
              "url": "https://github.com/argoproj/argo-cd/issues/12309"
            },
            {
              "name": "https://github.com/argoproj/argo-cd/pull/12320",
              "refsource": "MISC",
              "tags": [
                "Patch"
              ],
              "url": "https://github.com/argoproj/argo-cd/pull/12320"
            },
            {
              "name": "https://github.com/argoproj/argo-cd/security/advisories/GHSA-mv6w-j4xc-qpfw",
              "refsource": "MISC",
              "tags": [
                "Vendor Advisory"
              ],
              "url": "https://github.com/argoproj/argo-cd/security/advisories/GHSA-mv6w-j4xc-qpfw"
            },
            {
              "name": "https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/",
              "refsource": "MISC",
              "tags": [
                "Not Applicable"
              ],
              "url": "https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/"
            }
          ]
        }
      },
      "impact": {
        "baseMetricV3": {
          "cvssV3": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 6.5,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "NONE",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
            "version": "3.1"
          },
          "exploitabilityScore": 2.8,
          "impactScore": 3.6
        }
      },
      "lastModifiedDate": "2023-02-18T21:48Z",
      "publishedDate": "2023-02-08T21:15Z"
    }
  }
}


Log in or create an account to share your comment.




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.