How severe is GHSA-4xqv-47rm-37mm?

GHSA-4xqv-47rm-37mm 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-4xqv-47rm-37mm?

GHSA-4xqv-47rm-37mm affects the following packages: @openc3/tool-common (npm), openc3 (PyPI), openc3 (RubyGems). Ecosystems affected: npm, PyPI, RubyGems.

How do I fix GHSA-4xqv-47rm-37mm?

Update @openc3/tool-common to 5.19.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4xqv-47rm-37mm is resolved across your whole dependency graph.

How do I detect GHSA-4xqv-47rm-37mm in my npm, PyPI, RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @openc3/tool-common. 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-4xqv-47rm-37mm 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-4xqv-47rm-37mm?

O3 pinpoints whether GHSA-4xqv-47rm-37mm 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-4xqv-47rm-37mm actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-4xqv-47rm-37mm, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-4xqv-47rm-37mm?

GHSA-4xqv-47rm-37mm has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 26th 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-4xqv-47rm-37mm?

GHSA-4xqv-47rm-37mm is classified as CWE-312 (CWE-312). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-4xqv-47rm-37mm published, and has it been updated?

GHSA-4xqv-47rm-37mm was published on October 2, 2024 and was last updated on November 13, 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🐍 PyPI💎 RubyGems

GHSA-4xqv-47rm-37mm

MEDIUM

OpenC3 stores passwords in clear text (`GHSL-2024-129`)

Also known asCVE-2024-47529PYSEC-2024-121

Published

Oct 2, 2024

Updated

Nov 13, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk26th percentile-0.58%

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

3 pkgs affected

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

@openc3/tool-commonnpm

59downloads / week

Description

Summary

OpenC3 COSMOS stores the password of a user unencrypted in the LocalStorage of a web browser. This makes the user password susceptible to exfiltration via Cross-site scripting (see GHSL-2024-128).

Note: This CVE only affects Open Source edition, and not OpenC3 COSMOS Enterprise Edition

Impact

This issue may lead to Information Disclosure.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@openc3/tool-common`	all versions	5.19.0
🐍PyPI	`openc3`	all versions	5.19.0
💎RubyGems	`openc3`	all versions	5.19.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

OpenC3 COSMOS provides the functionality needed to send commands to and …

securitylab.github.comNVDNov 2024

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @openc3/tool-common. 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 @openc3/tool-common to 5.19.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4xqv-47rm-37mm 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-4xqv-47rm-37mm 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-4xqv-47rm-37mm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary OpenC3 COSMOS stores the password of a user unencrypted in the LocalStorage of a web browser. This makes the user password susceptible to exfiltration via Cross-site scripting (see GHSL-2024-128). Note: This CVE only affects Open Source edition, and not OpenC3 COSMOS Enterprise Edition ### Impact This issue may lead to Information Disclosure.

O3 Security · Impact-Aware SCA

Is GHSA-4xqv-47rm-37mm in your dependencies?

O3 detects GHSA-4xqv-47rm-37mm across npm, PyPI, RubyGems 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