GHSA-j438-45hc-vjhm
MEDIUMGHSA-j438-45hc-vjhm is a medium-severity (CVSS 4.8) Cross-Site Request Forgery (CSRF) vulnerability in @fraction/oasis. O3 Security confirms whether GHSA-j438-45hc-vjhm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
CSRF and DNS Rebinding in Oasis
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.
@fraction/oasisnpmDescription
Impact
What kind of vulnerability is it? Who is impacted?
If you're running a vulnerable application on your computer and an attacker can trick you into visiting a malicious website, they could use DNS rebinding and CSRF attacks to read/write to vulnerable applications.
There is no evidence that suggests that this has been used in the wild.
Patches
Has the problem been patched? What versions should users upgrade to?
Yes, 2.15.0.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
No.
References
Are there any links users can visit to find out more?
No.
For more information
If you have any questions or comments about this advisory:
- Open an issue in fraction/oasis
- Email me at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @fraction/oasis | all versions | 2.15.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @fraction/oasis. 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 @fraction/oasis to 2.15.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j438-45hc-vjhm 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-j438-45hc-vjhm 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-j438-45hc-vjhm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-j438-45hc-vjhm in your dependencies?
O3 detects GHSA-j438-45hc-vjhm across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.