Skip to content

Code injection in Stripe CLI on windows

High severity GitHub Reviewed Published Mar 9, 2022 in stripe/stripe-cli • Updated Feb 3, 2023

Package

gomod github.com/stripe/stripe-cli (Go)

Affected versions

< 1.7.13

Patched versions

1.7.13

Description

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 [email protected].

References

@vcheung-stripe vcheung-stripe published to stripe/stripe-cli Mar 9, 2022
Published by the National Vulnerability Database Mar 9, 2022
Published to the GitHub Advisory Database Mar 10, 2022
Reviewed Mar 10, 2022
Last updated Feb 3, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

EPSS score

0.044%
(14th percentile)

Weaknesses

CVE ID

CVE-2022-24753

GHSA ID

GHSA-4cx6-fj7j-pjx9

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.