CVE-2022-24753

Code injection in Stripe CLI on windows

Acknowledgments

Thanks to trungpabc for reporting the issue.

For more information

Email us at [email protected].

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.

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

CVE-2022-24753 has a CVSS score of 7.7 (High). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.7.13); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Upgrade to Stripe CLI v1.7.13.

1. What is CVE-2022-24753? CVE-2022-24753 is a high-severity OS command injection vulnerability in github.com/stripe/stripe-cli (go), affecting versions < 1.7.13. It is fixed in 1.7.13. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
2. How severe is CVE-2022-24753? CVE-2022-24753 has a CVSS score of 7.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/stripe/stripe-cli are affected by CVE-2022-24753? github.com/stripe/stripe-cli (go) versions < 1.7.13 is affected.
4. Is there a fix for CVE-2022-24753? Yes. CVE-2022-24753 is fixed in 1.7.13. Upgrade to this version or later.
5. Is CVE-2022-24753 exploitable, and should I be worried? Whether CVE-2022-24753 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-24753 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-24753? Upgrade github.com/stripe/stripe-cli to 1.7.13 or later.

Other vulnerabilities in github.com/stripe/stripe-cli