CVE-2020-17361 json
An issue was discovered in ReadyTalk Avian 1.2.0.
published 6y ago modified 4mo ago also EUVD-2020-9315
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 67%
- public exploits
- 0
- none known
Summary
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
Is CVE-2020-17361 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.18% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- seclists.org http://seclists.org/fulldisclosure/2020/Aug/10 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-755 Improper Handling of Exceptional Conditions
References
-
seclists.org
/fulldisclosure/2020/Aug/10
exploit, mailing-list, third-party-advisory
-
github.com
/ReadyTalk/avian/issues
third-party-advisory
-
seclists.org
/fulldisclosure/2020/Sep/11
mailing-list, third-party-advisory
-
seclists.org
/fulldisclosure/2020/Sep/14
mailing-list, third-party-advisory
-
seclists.org
/fulldisclosure/2020/Sep/13
mailing-list, third-party-advisory
Sources
- CVE List CVE-2020-17361
- NVD CVE-2020-17361
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.