CVE-2020-8125: Improper Input Validation in klona

klona Updated 02 Oct 2025

Summary

13/04/2021
Yes i
High
9.8

CVE-2020-8125: Improper Input Validation in klona. Affects klona versions < 1.1.1. Fixed in 1.1.1. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

klona is an npm package that provides a cloning utility for JavaScript objects. It allows developers to create deep copies of objects, which can be useful in various scenarios. However, versions 1.1.0 and earlier of klona are vulnerable to an improper input validation issue. This vulnerability can be exploited through a prototype pollution attack, potentially leading to remote code execution or denial of service in applications that use klona.

Vulnerability Detail

The vulnerability in klona arises from a flaw in input validation. By manipulating the input to klona, an attacker can pollute the prototype of objects, which can have severe consequences. This can result in the execution of arbitrary code or the disruption of normal application functionality. The impact of this vulnerability depends on how klona is used within an application and the privileges it has.

How To Fix

Latest published version: 2.0.6 as of 22 Oct 2026

npm install klona@2.0.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.1.1

This is the first release that contains the fix.

npm install klona@1.1.1

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

Workaround

If updating the klona package is not immediately feasible, developers can consider implementing input validation and sanitization mechanisms in their own code. By carefully validating and sanitizing user input before passing it to klona, the risk of exploitation can be mitigated. Here's an example of how input validation can be performed in JavaScript:

function validateInput(input) {
  if (typeof input !== 'object' || input === null) {
    throw new Error('Invalid input');
  }
}

Conclusion

The vulnerability in klona version 1.1.0 and earlier can be exploited through prototype pollution attacks, potentially leading to remote code execution or denial of service. It is crucial for developers to update their klona package to version 1.1.1 or later to mitigate this vulnerability. If immediate updating is not possible, implementing input validation and sanitization mechanisms can provide temporary protection. For further assistance in vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for klona →

Share this vulnerability

FAQ

klona is an npm package that provides a cloning utility for JavaScript objects. It allows developers to create deep copies of objects.

The vulnerability in klona is an improper input validation issue that can lead to prototype pollution attacks.

This vulnerability can result in remote code execution or denial of service in applications that use klona.

To fix this vulnerability, update the klona package to version 1.1.1 or later.

If updating the klona package is not immediately feasible, implement input validation and sanitization mechanisms in your own code.

Related vulnerabilities

Recent vulnerabilities recorded for klona.

How To Fix

Latest published version: 2.0.6 as of 22 Oct 2026

npm install klona@2.0.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.1.1

This is the first release that contains the fix.

npm install klona@1.1.1

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