CVE-2020-12835 in the critical feed json
An issue was discovered in SmartBear ReadyAPI SoapUI Pro 3.2.5.
published 2020-05-20 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-5117
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 13.3%
- EPSS 13.3% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known
Summary
An issue was discovered in SmartBear ReadyAPI SoapUI Pro 3.2.5. Due to unsafe use of an Java RMI based protocol in an unsafe configuration, an attacker can inject malicious serialized objects into the communication, resulting in remote code execution in the context of a client-side Network Licensing Protocol component.
Exploit prediction
13.29% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- seclists.org http://seclists.org/fulldisclosure/2020/May/38 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/157772/Protection-Licensing-Toolkit-ReadyAPI-3.2.5-Code-Execution-Deserialization.html referenced PoC, tagged "exploit" by a source, unverified
- syss.de https://www.syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2019-039.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
seclists.org
/fulldisclosure/2020/May/38
mailing-list, exploit, third-party-advisory
-
packetstormsecurity.com
/files/157772/Protection-Licensing-Toolkit-ReadyAPI-3.2.5-Code-Execution-Deserialization.html
exploit, third-party-advisory, vdb-entry
-
syss.de
/fileadmin/dokumente/Publikationen/Advisories/SYSS-2019-039.txt
exploit, third-party-advisory
-
syss.de
/pentest-blog/
third-party-advisory
Sources
- CVE List CVE-2020-12835
- NVD CVE-2020-12835
Fencer Vulns 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.