Noise-Java up to 2020-08-27 ChaChaPolyCipherState.encryptWithAd memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Noise-Java up to 2020-08-27. This affects the function ChaChaPolyCipherState.encryptWithAd. This manipulation causes memory corruption.
The identification of this vulnerability is CVE-2020-25021. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability was found in Noise-Java up to 2020-08-27 (Programming Language Software). It has been declared as critical. Affected by this vulnerability is the function ChaChaPolyCipherState.encryptWithAd. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in Noise-Java through 2020-08-27. ChaChaPolyCipherState.encryptWithAd() allows out-of-bounds access.
The weakness was shared 09/04/2020 (GitHub Repository). The advisory is shared at github.com. This vulnerability is known as CVE-2020-25021 since 08/29/2020. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known.
It is possible to download the exploit at packetstormsecurity.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Additional details are provided at seclists.org. The entries VDB-160730 and VDB-160731 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.1
VulDB Base Score: 7.3
VulDB Temp Score: 6.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Memory corruptionCWE: CWE-119
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/29/2020 🔍09/04/2020 🔍
09/04/2020 🔍
06/16/2024 🔍
Sources
Advisory: github.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2020-25021 (🔍)
GCVE (CVE): GCVE-0-2020-25021
GCVE (VulDB): GCVE-100-160729
scip Labs: https://www.scip.ch/en/?labs.20161013
Misc.: 🔍
See also: 🔍
Entry
Created: 09/04/2020 01:44 PMUpdated: 06/16/2024 10:45 AM
Changes: 09/04/2020 01:44 PM (38), 09/08/2020 12:25 PM (18), 11/12/2020 05:43 PM (1), 06/16/2024 10:45 AM (24)
Complete: 🔍
Cache ID: 244:1A6:40
No comments yet. Languages: en.
Please log in to comment.