How severe is GHSA-vfj8-5pj7-2f9g?

GHSA-vfj8-5pj7-2f9g has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-vfj8-5pj7-2f9g?

GHSA-vfj8-5pj7-2f9g affects the following packages: @openc3/tool-common (npm), openc3 (PyPI), openc3 (RubyGems). Ecosystems affected: npm, PyPI, RubyGems.

How do I fix GHSA-vfj8-5pj7-2f9g?

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-vfj8-5pj7-2f9g is resolved across your whole dependency graph.

How do I detect GHSA-vfj8-5pj7-2f9g 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-vfj8-5pj7-2f9g 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-vfj8-5pj7-2f9g?

O3 pinpoints whether GHSA-vfj8-5pj7-2f9g 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-vfj8-5pj7-2f9g actively exploited in the wild?

No public exploit code has been indexed for GHSA-vfj8-5pj7-2f9g 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 is the EPSS score for GHSA-vfj8-5pj7-2f9g?

GHSA-vfj8-5pj7-2f9g has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 35th 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-vfj8-5pj7-2f9g?

GHSA-vfj8-5pj7-2f9g 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 GHSA-vfj8-5pj7-2f9g published, and has it been updated?

GHSA-vfj8-5pj7-2f9g was published on October 2, 2024 and was last updated on October 31, 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-vfj8-5pj7-2f9g

MEDIUM

OpenC3 Cross-site Scripting in Login functionality (`GHSL-2024-128`)

Also known asCVE-2024-43795PYSEC-2024-100

Published

Oct 2, 2024

Updated

Oct 31, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk35th percentile-1.08%

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

📦@openc3/tool-common🐍openc3💎openc3

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm, PyPI, RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

Summary

The login functionality contains a reflected cross-site scripting (XSS) vulnerability.

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

Impact

This issue may lead up to Remote Code Execution (RCE).

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 GHSA-vfj8-5pj7-2f9g 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-vfj8-5pj7-2f9g 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-vfj8-5pj7-2f9g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary The login functionality contains a reflected cross-site scripting (XSS) vulnerability. Note: This CVE only affects Open Source Edition, and not OpenC3 COSMOS Enterprise Edition ### Impact This issue may lead up to Remote Code Execution (RCE).

O3 Security · Impact-Aware SCA

Is GHSA-vfj8-5pj7-2f9g in your dependencies?

O3 detects GHSA-vfj8-5pj7-2f9g 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