# CVE-2024-47529: OpenC3 COSMOS uses clear text storage of password/token (`GHSL-2024-129`)

> OpenC3 COSMOS stores user passwords in clear text in browser LocalStorage, allowing attackers to steal credentials via XSS or other means.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Oct 2024
- **Updated:** 31 Oct 2024
- **Also known as:** GHSA-4xqv-47rm-37mm, PYSEC-2024-121

## What is CVE-2024-47529?

CVE-2024-47529 is a medium-severity vulnerability in OpenC3 cosmos, published on 2 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2024-47529?

7 open source packages ship an affected version, including openc3 and @openc3/tool-common. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openc3` | PyPI | All versions | 5.19.0 |
| `openc3` | PyPI | All versions | 5.19.0 |
| `openc3` | PyPI | All versions | 5.19.0 |
| `openc3` | RubyGems | All versions | 5.19.0 |
| `openc3` | RubyGems | All versions | 5.19.0 |
| `@openc3/tool-common` | npm | All versions | 5.19.0 |
| `@openc3/tool-common` | npm | All versions | 5.19.0 |

Products: Openc3 Cosmos.

## How do I fix CVE-2024-47529?

Upgrade openc3 to 5.19.0 or later.

## Is CVE-2024-47529 being exploited?

There is no known exploitation of CVE-2024-47529 in the wild and no public exploit code.

## Other vulnerabilities in OpenC3 cosmos

- [CVE-2025-28386](https://insights.sbomify.com/CVE-2025-28386/): Code injection in n/a (critical 9.8)
- [CVE-2025-28388](https://insights.sbomify.com/CVE-2025-28388/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2025-28389](https://insights.sbomify.com/CVE-2025-28389/): Weak cryptography in n/a (critical 9.8)
- [CVE-2026-42087](https://insights.sbomify.com/CVE-2026-42087/): OpenC3 COSMOS: SQL Injection in QuestDB Time-Series Data Base (critical 9.6)
- [CVE-2026-42088](https://insights.sbomify.com/CVE-2026-42088/): OpenC3 COSMOS: Administrative Actions via the Script Runner Tool (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-47529 and fix it if it is affected.

What it is: CVE-2024-47529 is a medium-severity vulnerability in OpenC3 cosmos, published on 2 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-47529 in the wild and no public exploit code.

Affected packages and fixed versions:
- openc3 (PyPI): affected all versions; fixed in 5.19.0
- openc3 (PyPI): affected all versions; fixed in 5.19.0
- openc3 (PyPI): affected all versions; fixed in 5.19.0
- openc3 (RubyGems): affected all versions; fixed in 5.19.0
- openc3 (RubyGems): affected all versions; fixed in 5.19.0
- @openc3/tool-common (npm): affected all versions; fixed in 5.19.0
- @openc3/tool-common (npm): affected all versions; fixed in 5.19.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-47529/ (Markdown: https://insights.sbomify.com/CVE-2024-47529/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-47529
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-47529
- OSV: https://osv.dev/vulnerability/CVE-2024-47529

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-47529/
Summaries are generated and may contain mistakes; the official description above is the record.