GHSA-786Q-9HCG-V9FF

Vulnerability from github – Published: 2025-09-04 19:49 – Updated: 2025-09-05 16:09
VLAI?
Summary
Argo CD's Project API Token Exposes Repository Credentials
Details

Summary

Argo CD API tokens with project-level permissions are able to retrieve sensitive repository credentials (usernames, passwords) through the project details API endpoint, even when the token only has standard application management permissions and no explicit access to secrets.

Component: Project API (/api/v1/projects/{project}/detailed)

Vulnerability Details

Expected Behavior

API tokens should require explicit permission to access sensitive credential information. Standard project permissions should not grant access to repository secrets.

Actual Behavior

API tokens with basic project permissions can retrieve all repository credentials associated with a project through the detailed project API endpoint.

Note: This vulnerability does not only affect project-level permissions. Any token with project get permissions is also vulnerable, including global permissions such as: p, role/user, projects, get, *, allow

Steps to Reproduce

  1. Create an API token with the following project-level permissions: p, proj:myProject:project-automation-role, applications, sync, myProject/*, allow p, proj:myProject:project-automation-role, applications, action/argoproj.io/Rollout/*, myProject/*, allow p, proj:myProject:project-automation-role, applications, get, myProject/*, allow

  2. Call the project details API: ``` bashcurl -sH "Authorization: Bearer $ARGOCD_API_TOKEN" \ "https://argocd.example.com/api/v1/projects/myProject/detailed"

3. Observe that the response includes sensitive repository credentials: { "repositories": [ { "username": "", "password": "", "type": "helm", "name": "test-helm-repo", "project": "myProject" } ] } ```

Patches

  • v3.1.2
  • v3.0.14
  • v2.14.16
  • v2.13.9

Credits to @ashishgoyal111 for helping identify this issue.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/argoproj/argo-cd/v2"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.13.0"
            },
            {
              "fixed": "2.13.9"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/argoproj/argo-cd/v2"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.14.0"
            },
            {
              "fixed": "2.14.16"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/argoproj/argo-cd/v3"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.0.14"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/argoproj/argo-cd/v3"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "3.1.0-rc1"
            },
            {
              "fixed": "3.1.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-55190"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-200"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-09-04T19:49:56Z",
    "nvd_published_at": "2025-09-04T23:15:32Z",
    "severity": "CRITICAL"
  },
  "details": "### Summary\nArgo CD API tokens with project-level permissions are able to retrieve sensitive repository credentials (usernames, passwords) through the project details API endpoint, even when the token only has standard application management permissions and no explicit access to secrets.\n\nComponent: `Project API (/api/v1/projects/{project}/detailed)`\n\n\n## Vulnerability Details\n### Expected Behavior\nAPI tokens should require explicit permission to access sensitive credential information. Standard project permissions should not grant access to repository secrets.\n### Actual Behavior\nAPI tokens with basic project permissions can retrieve all repository credentials associated with a project through the detailed project API endpoint.\n\n**Note**: This vulnerability does not only affect project-level permissions. Any token with project get permissions is also vulnerable, including global permissions such as: `p, role/user, projects, get, *, allow`\n\n### Steps to Reproduce\n\n1. Create an API token with the following project-level permissions:\n  ```\n  p, proj:myProject:project-automation-role, applications, sync, myProject/*, allow\n  p, proj:myProject:project-automation-role, applications, action/argoproj.io/Rollout/*, myProject/*, allow\n  p, proj:myProject:project-automation-role, applications, get, myProject/*, allow\n  ```\n\n2. Call the project details API:\n  ```\n  bashcurl -sH \"Authorization: Bearer $ARGOCD_API_TOKEN\" \\\n    \"https://argocd.example.com/api/v1/projects/myProject/detailed\"\n  \n  ```\n3. Observe that the response includes sensitive repository credentials:\n  ```\n  {\n    \"repositories\": [\n      {\n        \"username\": \"\u003cREDACTED\u003e\",\n        \"password\": \"\u003cREDACTED\u003e\",\n        \"type\": \"helm\",\n        \"name\": \"test-helm-repo\",\n        \"project\": \"myProject\"\n      }\n    ]\n  }\n  ```\n\n## Patches\n\n* v3.1.2\n* v3.0.14\n* v2.14.16\n* v2.13.9\n\n\nCredits to @ashishgoyal111 for helping identify this issue.",
  "id": "GHSA-786q-9hcg-v9ff",
  "modified": "2025-09-05T16:09:59Z",
  "published": "2025-09-04T19:49:56Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/argoproj/argo-cd/security/advisories/GHSA-786q-9hcg-v9ff"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-55190"
    },
    {
      "type": "WEB",
      "url": "https://github.com/argoproj/argo-cd/commit/e8f86101f5378662ae6151ce5c3a76e9141900e8"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/argoproj/argo-cd"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Argo CD\u0027s Project API Token Exposes Repository Credentials"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…