CVE-2020-24164: Gadget chain attack in Nippy

com.taoensso:nippy Updated 02 Oct 2025

Summary

10/02/2022
Yes i
High
7.8

CVE-2020-24164: Gadget chain attack in Nippy. Affects com.taoensso:nippy versions < 2.14.2. Fixed in 2.14.2. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Taoensso Nippy is a library for fast serialization and deserialization of Clojure data structures. It is commonly used in Clojure applications to efficiently store and transmit data. However, versions before 2.14.2 are vulnerable to a deserialization flaw that can be exploited by an attacker. This flaw arises from the automatic use of the Java Serializable interface, allowing an attacker to create a malicious payload that, when deserialized, can execute arbitrary code.

Vulnerability Detail

The vulnerability in Taoensso Nippy allows an attacker to craft a malicious payload that, upon deserialization, can execute arbitrary code. This can lead to various security risks, including remote code execution, privilege escalation, and data exfiltration. The flaw arises due to the automatic use of the Java Serializable interface, which can be abused by an attacker to achieve code execution. The impact of this vulnerability is high, with a CVSS score of 7.8.

How To Fix

Minimum fixed version

2.14.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to update to the fixed version of Taoensso Nippy to address the issue.

Conclusion

The deserialization flaw in Taoensso Nippy poses a significant security risk, allowing an attacker to execute arbitrary code. To mitigate this risk, it is crucial to update to version 2.14.2 or later of the library. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for com.taoensso:nippy →

Share this vulnerability

FAQ

Taoensso Nippy is a library for fast serialization and deserialization of Clojure data structures. It is commonly used in Clojure applications to efficiently store and transmit data.

The vulnerability allows an attacker to execute arbitrary code, leading to risks such as remote code execution, privilege escalation, and data exfiltration.

To fix this vulnerability, it is recommended to upgrade to version 2.14.2 or later of Taoensso Nippy.

No, there is no known workaround for this vulnerability. Updating to the fixed version is necessary.

The CVSS score of this vulnerability is 7.8, indicating a high severity.

How To Fix

Minimum fixed version

2.14.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback