ReadyTalk Avian 1.2.0 classpath-common.h vm::arrayCopy Negative Length memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in ReadyTalk Avian 1.2.0. This affects the function vm::arrayCopy of the file classpath-common.h. Performing a manipulation as part of Negative Length results in memory corruption.
This vulnerability is reported as CVE-2020-17361. The attack requires a local approach. No exploit exists.
It is advised to substitute the affected component with an alternative.
Details
A vulnerability classified as critical has been found in ReadyTalk Avian 1.2.0. This affects the function vm::arrayCopy of the file classpath-common.h. The manipulation as part of a Negative Length leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
** UNSUPPORTED WHEN ASSIGNED ** An issue was discovered in ReadyTalk Avian 1.2.0. The vm::arrayCopy method defined in classpath-common.h returns silently when a negative length is provided (instead of throwing an exception). This could result in data being lost during the copy, with varying consequences depending on the subsequent use of the destination buffer. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
The weakness was disclosed 08/12/2020 as not defined mailinglist post (Full-Disclosure). The advisory is shared at seclists.org. This vulnerability is uniquely identified as CVE-2020-17361 since 08/05/2020. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
The problem might be mitigated by replacing the product with as an alternative.
The entry VDB-159776 is pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
Support
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: AlternativeStatus: 🔍
0-Day Time: 🔍
Timeline
08/05/2020 🔍08/12/2020 🔍
08/13/2020 🔍
05/05/2025 🔍
Sources
Advisory: seclists.orgStatus: Not defined
CVE: CVE-2020-17361 (🔍)
GCVE (CVE): GCVE-0-2020-17361
GCVE (VulDB): GCVE-100-159777
See also: 🔍
Entry
Created: 08/13/2020 13:52Updated: 05/05/2025 06:23
Changes: 08/13/2020 13:52 (42), 08/29/2020 15:54 (17), 08/04/2024 17:17 (16), 05/05/2025 06:23 (3)
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.