Faye up to 1.0.3/1.1.2/1.2.4 on npm improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.8 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Faye up to 1.0.3/1.1.2/1.2.4 on npm. This affects an unknown part. This manipulation causes improper authentication. This vulnerability is registered as CVE-2020-11020. Remote exploitation of the attack is possible. No exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability classified as critical was found in Faye up to 1.0.3/1.1.2/1.2.4 on npm. Affected by this vulnerability is an unknown code. The manipulation with an unknown input leads to a improper authentication vulnerability. The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Faye (NPM, RubyGem) versions greater than 0.5.0 and before 1.0.4, 1.1.3 and 1.2.5, has the potential for authentication bypass in the extension system. The vulnerability allows any client to bypass checks put in place by server-side extensions, by appending extra segments to the message channel. It is patched in versions 1.0.4, 1.1.3 and 1.2.5.
The weakness was published 04/29/2020 (GitHub Repository). The advisory is shared at github.com. This vulnerability is known as CVE-2020-11020 since 03/30/2020. The attack can be launched remotely. A single authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
Upgrading to version 1.0.4, 1.1.3 or 1.2.5 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
Website
- Product: https://github.com/faye/faye/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.1VulDB Meta Temp Score: 7.8
VulDB Base Score: 7.4
VulDB Temp Score: 6.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.5
NVD Vector: 🔍
CNA Base Score: 8.5
CNA Vector (GitHub, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Faye 1.0.4/1.1.3/1.2.5
Patch: github.com
Timeline
03/30/2020 🔍04/29/2020 🔍
04/30/2020 🔍
06/04/2024 🔍
Sources
Product: github.comAdvisory: 65d297d341b607f3cb0b5fa6021a625a991cc30e
Status: Not defined
Confirmation: 🔍
CVE: CVE-2020-11020 (🔍)
GCVE (CVE): GCVE-0-2020-11020
GCVE (VulDB): GCVE-100-154585
Entry
Created: 04/30/2020 09:22Updated: 06/04/2024 12:27
Changes: 04/30/2020 09:22 (38), 04/30/2020 09:27 (11), 10/14/2020 12:47 (1), 10/14/2020 12:55 (1), 06/04/2024 12:21 (19), 06/04/2024 12:27 (18)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.