How severe is CVE-2024-43795?

No CVSS score has been assigned to CVE-2024-43795 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-43795?

CVE-2024-43795 affects the following packages: @openc3/tool-common (npm), openc3 (PyPI), openc3 (RubyGems). Ecosystems affected: npm, PyPI, RubyGems.

How do I fix CVE-2024-43795?

Update @openc3/tool-common to 5.19.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-43795 is resolved across your whole dependency graph.

How do I detect CVE-2024-43795 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 CVE-2024-43795 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 CVE-2024-43795?

O3 pinpoints whether CVE-2024-43795 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 CVE-2024-43795 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-43795 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 type of vulnerability is CVE-2024-43795?

CVE-2024-43795 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2024-43795 published, and has it been updated?

CVE-2024-43795 was published on October 2, 2024 and was last updated on July 15, 2026. 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

CVE-2024-43795

Fix: OpenC3/cosmos@762d7e0

CVE-2024-43795 is a Cross-site Scripting (XSS) vulnerability in @openc3/tool-common. O3 Security confirms whether CVE-2024-43795 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenC3 COSMOS vulnerable to cross-site scripting in Login functionality (`GHSL-2024-128`)

Also known asGHSA-vfj8-5pj7-2f9gPYSEC-2024-100

Published

Oct 2, 2024

Updated

Jul 15, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Real-World Exposure

3 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

@openc3/tool-commonnpm

35downloads / week

Description

OpenC3 COSMOS provides the functionality needed to send commands to and receive data from one or more embedded systems. The login functionality contains a reflected cross-site scripting (XSS) vulnerability. This vulnerability is fixed in 5.19.0. Note: This CVE only affects Open Source Edition, and not OpenC3 COSMOS Enterprise Edition.

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

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 CVE-2024-43795 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 CVE-2024-43795 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 CVE-2024-43795. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2024-43795 in your dependencies?

O3 detects CVE-2024-43795 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