x-crypto prior 0.0.0-20200220183623-bac4c82f6975 on Go Signature Verification signature verification
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in x-crypto on Go and classified as critical. This affects an unknown part of the component Signature Verification Handler. Performing a manipulation results in signature verification. This vulnerability is known as CVE-2020-9283. Remote exploitation of the attack is possible. Furthermore, an exploit is available. The affected component should be upgraded.
Details
A vulnerability was found in x-crypto on Go. It has been classified as critical. This affects an unknown part of the component Signature Verification Handler. The manipulation with an unknown input leads to a signature verification vulnerability. CWE is classifying the issue as CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
golang.org/x/crypto before v0.0.0-20200220183623-bac4c82f6975 for Go allows a panic during signature verification in the golang.org/x/crypto/ssh package. A client can attack an SSH server that accepts public keys. Also, a server can attack any SSH client.
The weakness was published 02/20/2020 (Website). The advisory is shared at groups.google.com. This vulnerability is uniquely identified as CVE-2020-9283 since 02/19/2020. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are unknown but a public exploit is available.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept.
Upgrading to version 0.0.0-20200220183623-bac4c82f6975 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Exploit-DB (48121). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
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: Signature verificationCWE: CWE-347 / CWE-345
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: x-crypto 0.0.0-20200220183623-bac4c82f6975
Timeline
02/19/2020 🔍02/20/2020 🔍
02/21/2020 🔍
08/18/2024 🔍
Sources
Advisory: 156480Status: Not defined
CVE: CVE-2020-9283 (🔍)
GCVE (CVE): GCVE-0-2020-9283
GCVE (VulDB): GCVE-100-150405
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 02/21/2020 08:34Updated: 08/18/2024 21:14
Changes: 02/21/2020 08:34 (39), 02/21/2020 08:39 (17), 04/02/2024 09:00 (18), 04/02/2024 09:03 (1), 08/18/2024 21:14 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.