CSRF and DNS Rebinding in Oasis

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.8 · CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N

EPSS

• CVE-2020-11003: 0.52% estimated exploitation activity in the next 30 days; percentile 43.90 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 christianbundy@fraction.io

Published by the source

16 Apr 2020, 03:14 UTC

Last modified by the source

10 Sep 2026, 03:48 UTC

Source last checked

26 Oct 2026, 12:07 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-j438-45hc-vjhm

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-j438-45hc-vjhm

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-11003

Advisory: CSRF and DNS Rebinding in Oasis
IDs: CVE-2020-11003, GHSA-j438-45hc-vjhm
Record: https://patchnext.com/advisories/cve-2020-11003 (revision 2, source checked 26 Oct 2026, 12:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @fraction/oasis 2.15.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @fraction/oasis: affected < 2.15.0; fixed in 2.15.0

## Suggested inspection (read-only)
- `npm ls @fraction/oasis --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @fraction/oasis.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-j438-45hc-vjhm (OSV record GHSA-j438-45hc-vjhm lists affected ranges: npm @fraction/oasis >=0 <2.15.0 (fixed))
- Verified: https://github.com/advisories/GHSA-j438-45hc-vjhm (GitHub-reviewed advisory GHSA-j438-45hc-vjhm lists affected ranges: npm @fraction/oasis >=0 <2.15.0)

Commands are suggestions: review each one before running it.