CVE-2017-20189
Clojure insecure deserialization
- Published22 Jan 2024
Description
In Clojure before 1.9.0, classes can be used to construct a serialized object that executes arbitrary code upon deserialization. This is relevant if a server deserializes untrusted objects.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://clojure.atlassian.net/browse/CLJ-2204
- https://github.com/clojure/clojure/commit/271674c9b484d798484d134a5ac40a6df15d3ac3
- https://github.com/frohoff/ysoserial/pull/68/files
- https://hackmd.io/%40fe1w0/HyefvRQKp
- https://security.netapp.com/advisory/ntap-20241108-0002/
- https://security.snyk.io/vuln/SNYK-JAVA-ORGCLOJURE-5740378
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2017-20189 being actively exploited?
CVE-2017-20189 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 1.33%.
How severe is CVE-2017-20189?
CVE-2017-20189 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 1.33% probability of exploitation.
Which products are affected by CVE-2017-20189?
Affected products include Clojure.
How do I fix CVE-2017-20189?
Upgrade affected software to a fixed version, for example Clojure 1.9.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2017-20189 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.