Vulnerability in Oasis (CVE-2020-11003)
Summary
Vulnerability in Oasis (CVE-2020-11003). Confidential information can be exposed externally. Mitigation: upgrade to 2.15.0 or later.
Original description
The description as published by the source.
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
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-11003 has been found in Oasis.
Confidential information can be exposed externally.
What to do: upgrade Oasis to 2.15.0 or later.
If unsure, ask your IT team or search "Oasis CVE-2020-11003" on the vendor's site.
CVE-2020-11003 (Oasis)
Attack vector: remote (network-reachable) / unauthenticated
Patched: 2.15.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in Oasis.
Check the vendor advisory for the affected versions of Oasis.
Severity: ?. Confidential information can be exposed externally.
Update to 2.15.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Oasis' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Oasis' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Oasisを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Oasis to 2.15.0ステージング環境で 2.15.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com