How severe is GHSA-ghgq-x6wc-6jr5?

GHSA-ghgq-x6wc-6jr5 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-ghgq-x6wc-6jr5?

GHSA-ghgq-x6wc-6jr5 affects the following packages: @zowe/cli (npm). Ecosystems affected: npm.

How do I fix GHSA-ghgq-x6wc-6jr5?

Update @zowe/cli to 7.23.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ghgq-x6wc-6jr5 is resolved across your whole dependency graph.

How do I detect GHSA-ghgq-x6wc-6jr5 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @zowe/cli, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-ghgq-x6wc-6jr5 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.

Is GHSA-ghgq-x6wc-6jr5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-ghgq-x6wc-6jr5 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-ghgq-x6wc-6jr5?

GHSA-ghgq-x6wc-6jr5 has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 3th 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.

When was GHSA-ghgq-x6wc-6jr5 published, and has it been updated?

GHSA-ghgq-x6wc-6jr5 was published on July 17, 2024 and was last updated on July 17, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

MEDIUM severity

Zowe CLI allows storage of previously entered secure credentials in a plaintext fileGHSA-ghgq-x6wc-6jr5

MEDIUMFix: zowe/zowe-cli@6778da5

GHSA-ghgq-x6wc-6jr5 is a medium-severity (CVSS 5.9) vulnerability in @zowe/cli. A fix is available for @zowe/cli — see the affected versions and patch details below.

Also known asCVE-2024-6833

Published

Jul 17, 2024

Updated

Jul 17, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-ghgq-x6wc-6jr5.

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs3th percentile — riskier than 3% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

4other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@zowe/clinpm

8Kdownloads / week

Description

A vulnerability in Zowe CLI allows local, privileged actors to store previously entered secure credentials in a plaintext file as part of an auto-init operation.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@zowe/cli`	≥ 7.18.0&&< 7.23.5	7.23.5`npm install @zowe/cli@7.23.5`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @zowe/cli, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @zowe/cli to 7.23.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ghgq-x6wc-6jr5 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.

Frequently Asked Questions

A vulnerability in Zowe CLI allows local, privileged actors to store previously entered secure credentials in a plaintext file as part of an auto-init operation.

O3 Security · Impact-Aware SCA

Is GHSA-ghgq-x6wc-6jr5 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works