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

How does O3 Security protect against GHSA-ghgq-x6wc-6jr5?

O3 pinpoints whether GHSA-ghgq-x6wc-6jr5 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-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.

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

GHSA-ghgq-x6wc-6jr5

MEDIUM

GHSA-ghgq-x6wc-6jr5 is a medium-severity (CVSS 5.9) vulnerability in @zowe/cli. O3 Security confirms whether GHSA-ghgq-x6wc-6jr5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Zowe CLI allows storage of previously entered secure credentials in a plaintext file

Also known asCVE-2024-6833

Published

Jul 17, 2024

Updated

Jul 17, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

@zowe/clinpm

3Kdownloads / 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

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. 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 @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.
How O3 protects you
O3 pinpoints whether GHSA-ghgq-x6wc-6jr5 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-ghgq-x6wc-6jr5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-ghgq-x6wc-6jr5 across npm 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