CVE-2020-11003
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOasis 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOasis before version 2.15.0 contains a combined DNS rebinding and CSRF vulnerability. An attacker who tricks a user into visiting a malicious website can exploit DNS rebinding to bypass same-origin policy protections and perform unauthorized read/write operations against vulnerable applications running locally on the user's computer.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.15.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate Oasis installationSearch common installation directories or check your system's installed applications list for 'Oasis' or 'Fraction Oasis'. Check typical application paths like /opt/, Program Files, or use system package managers (dpkg, rpm, brew) if on Linux/macOS.Affected if Oasis is found installed on the system
-
Determine installed versionRun 'oasis --version' or check the application's about/info panel if it has a GUI. If it runs as a service, check the service version or examine the binary/executable properties.Affected if The version is below 2.15.0 (e.g., 2.14.x, 2.13.x, etc.)
-
Verify web interface is accessibleCheck if the Oasis web interface is running and reachable. Look for listening ports (commonly 8080, 8000, or 3000) using 'netstat' or 'ss' commands, or attempt to access the typical web URL (e.g., http://localhost:port).Affected if The Oasis web interface is running and network-accessible (even locally)
-
Check for exposed network listenersReview any firewall rules or port configurations that allow access to Oasis web endpoints. Verify if it binds to localhost only or is exposed to other network interfaces.Affected if Oasis listens on non-localhost interfaces or has permissive firewall rules
You are affected if Oasis (Fraction Oasis) is installed with a version lower than 2.15.0 and its web interface is accessible, since the DNS rebinding and CSRF attack requires the vulnerable web component to be reachable.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.15.0
Upgrade Oasis to version 2.15.0 or later to incorporate the security patch that addresses this DNS rebinding and CSRF vulnerability.
- Consultation3.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,840.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11003 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-11003 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data