OpenC3 stores passwords in clear text (`GHSL-2024-129`)GHSA-4xqv-47rm-37mm
MEDIUMFix: OpenC3/cosmos@b5ab34fGHSA-4xqv-47rm-37mm is a medium-severity (CVSS 5.9) CWE-312 vulnerability in @openc3/tool-common. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for @openc3/tool-common — see the affected versions and patch details below.
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-4xqv-47rm-37mm.
EPSS Exploitation Probability
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
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.
@openc3/tool-commonnpmDescription
OpenC3 COSMOS provides the functionality needed to send commands to and receive data from one or more embedded systems. 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). This vulnerability is fixed in 5.19.0. This only affects Open Source edition, and not OpenC3 COSMOS Enterprise Edition.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @openc3/tool-common | all versions | 5.19.0npm install @openc3/tool-common@5.19.0 |
| 🐍PyPI | openc3 | all versions | 5.19.0pip install --upgrade 'openc3==5.19.0' |
| 💎RubyGems | openc3 | all versions | 5.19.0bundle update openc3 --conservative |
Affected Products
cosmosopenc3Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @openc3/tool-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-4xqv-47rm-37mm in your dependencies?
Find it across npm, PyPI, RubyGems, including transitive dependencies.