Deserialization in Taoensso Nippy
CVE-2020-24164
- CVSS v3
- 7.8 High
- Public exploits
- None known
- EPSS
- 0.011 · 66.8th percentile
- Published
- 2020-09-11
A deserialization flaw is present in Taoensso Nippy before 2.14.2. In some circumstances, it is possible for an attacker to create a malicious payload that, when deserialized, will allow arbitrary code to be executed. This occurs because there is automatic use of the Java Serializable interface.
Vulnerability class: Insecure Deserialization
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.8 (High). Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
- Attack Vector
- Local
AV:L - Attack Complexity
- Low
AC:L - Privileges Required
- None
PR:N - User Interaction
- Required
UI:R - Scope
- Unchanged
S:U - Confidentiality
- High
C:H - Integrity
- High
I:H - Availability
- High
A:H
EPSS exploit prediction
EPSS 0.011, 66.8th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 5 other repositories (404notf0und/CVE-Flow, AdeliaNitzsche/Java-Deserialization-Cheat-Sheet, BrittanyKuhn/javascript-tutorial, …). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- github.com/ptaoussanis/nippy/issues/130 (Third Party Advisory)