# CVE-2020-11003: CSRF and DNS Rebinding in Oasis

> Attackers can exploit CSRF and DNS rebinding to read or modify data in Oasis applications by tricking users into visiting malicious sites.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-j438-45hc-vjhm

## What is CVE-2020-11003?

CVE-2020-11003 is a medium-severity vulnerability in fraction oasis, published on 14 Apr 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Oasis before version 2.15.0 has a potential DNS rebinding or CSRF vulnerability. 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. This has been patched in 2.15.0.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2020-11003?

2 open source packages ship an affected version, including @fraction/oasis. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@fraction/oasis` | npm | All versions | 2.15.0 |
| `@fraction/oasis` | npm | All versions | 2.15.0 |

Products: Fraction Oasis.

## How do I fix CVE-2020-11003?

Upgrade @fraction/oasis to 2.15.0 or later.

## Is CVE-2020-11003 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11003 and fix it if it is affected.

What it is: CVE-2020-11003 is a medium-severity vulnerability in fraction oasis, published on 14 Apr 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-11003 in the wild and no public exploit code.

Affected packages and fixed versions:
- @fraction/oasis (npm): affected all versions; fixed in 2.15.0
- @fraction/oasis (npm): affected all versions; fixed in 2.15.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-2020-11003/ (Markdown: https://insights.sbomify.com/CVE-2020-11003/index.md)
```

## Sources

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

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