Skip to content

CSRF and DNS Rebinding in Oasis

Moderate severity GitHub Reviewed Published Apr 13, 2020 in fraction/oasis • Updated Jan 9, 2023

Package

npm @fraction/oasis (npm)

Affected versions

< 2.15.0

Patched versions

2.15.0

Description

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:

References

@christianbundy christianbundy published to fraction/oasis Apr 13, 2020
Reviewed Apr 15, 2020
Published to the GitHub Advisory Database Apr 16, 2020
Last updated Jan 9, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N

EPSS score

0.073%
(34th percentile)

Weaknesses

CVE ID

CVE-2020-11003

GHSA ID

GHSA-j438-45hc-vjhm

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.