How severe is GHSA-4cx6-fj7j-pjx9?

GHSA-4cx6-fj7j-pjx9 has a CVSS score of 7.7/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-4cx6-fj7j-pjx9?

GHSA-4cx6-fj7j-pjx9 affects the following packages: github.com/stripe/stripe-cli (Go). Ecosystems affected: Go.

How do I fix GHSA-4cx6-fj7j-pjx9?

Update github.com/stripe/stripe-cli to 1.7.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4cx6-fj7j-pjx9 is resolved across your whole dependency graph.

How do I detect GHSA-4cx6-fj7j-pjx9 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/stripe/stripe-cli. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-4cx6-fj7j-pjx9 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-4cx6-fj7j-pjx9?

O3 pinpoints whether GHSA-4cx6-fj7j-pjx9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-4cx6-fj7j-pjx9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-4cx6-fj7j-pjx9 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-4cx6-fj7j-pjx9?

GHSA-4cx6-fj7j-pjx9 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 24th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-4cx6-fj7j-pjx9?

GHSA-4cx6-fj7j-pjx9 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-4cx6-fj7j-pjx9 published, and has it been updated?

GHSA-4cx6-fj7j-pjx9 was published on March 10, 2022 and was last updated on August 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-4cx6-fj7j-pjx9

HIGH

Code injection in Stripe CLI on windows

Also known asCVE-2022-24753GO-2022-0350

Published

Mar 10, 2022

Updated

Aug 21, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk24th percentile+0.18%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐹github.com/stripe/stripe-cli

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

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].

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/stripe/stripe-cli`	all versions	1.7.13

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/stripe/stripe-cli. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/stripe/stripe-cli to 1.7.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4cx6-fj7j-pjx9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-4cx6-fj7j-pjx9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-4cx6-fj7j-pjx9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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.

O3 Security · Impact-Aware SCA

Is GHSA-4cx6-fj7j-pjx9 in your dependencies?

O3 detects GHSA-4cx6-fj7j-pjx9 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works