GHSA-4CX6-FJ7J-PJX9

Vulnerability from github – Published: 2022-03-10 18:17 – Updated: 2022-03-18 21:10
VLAI
Summary
Code injection in Stripe CLI on windows
Details

Impact

A vulnerability in Stripe CLI exists on Windows when certain commands are run in a directory where an attacker has planted files. The commands are stripe login, stripe config -e, stripe community, and stripe open. MacOS and Linux are unaffected.

An attacker who successfully exploits the vulnerability can run arbitrary code in the context of the current user. The update addresses the vulnerability by throwing an error in these situations before the code can run.

There has been no evidence of exploitation of this vulnerability.

Recommendation

Upgrade to Stripe CLI v1.7.13.

Acknowledgments

Thanks to trungpabc for reporting the issue.

For more information

Email us at security@stripe.com.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/stripe/stripe-cli"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.7.13"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2022-24753"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-78"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2022-03-10T18:17:50Z",
    "nvd_published_at": "2022-03-09T23:15:00Z",
    "severity": "HIGH"
  },
  "details": "### Impact\nA vulnerability in Stripe CLI exists on Windows when certain commands are run in a directory where an attacker has planted files. The commands are `stripe login`, `stripe config -e`, `stripe community`, and `stripe open`. MacOS and Linux are unaffected.\n\nAn attacker who successfully exploits the vulnerability can run arbitrary code in the context of the current user. The update addresses the vulnerability by throwing an error in these situations before the code can run.\n\nThere has been no evidence of exploitation of this vulnerability.\n\n### Recommendation\nUpgrade to Stripe CLI v1.7.13.\n\n### Acknowledgments\nThanks to [trungpabc](https://hackerone.com/trungpabc) for reporting the issue.\n\n### For more information\nEmail us at [security@stripe.com](mailto:security@stripe.com).\n",
  "id": "GHSA-4cx6-fj7j-pjx9",
  "modified": "2022-03-18T21:10:48Z",
  "published": "2022-03-10T18:17:50Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/stripe/stripe-cli/security/advisories/GHSA-4cx6-fj7j-pjx9"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-24753"
    },
    {
      "type": "WEB",
      "url": "https://github.com/stripe/stripe-cli/commit/be38da5c0191adb77f661f769ffff2fbc7ddf6cd"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/stripe/stripe-cli"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Code injection in Stripe CLI on windows"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

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…