CVE-2020-28274: Prototype pollution vulnerability in deepref

deepref Updated 02 Oct 2025

Summary

12/10/2021
No i
Critical
9.8

CVE-2020-28274: Prototype pollution vulnerability in 'deepref'. Affects deepref versions >= 1.1.1, <= 1.2.1. No fix is published. 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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The 'deepref' package is an npm package that provides deep object reference tracking. It allows developers to track and manage references to objects within their code. The package is commonly used in JavaScript applications to handle complex data structures and object references.

Vulnerability Detail

The 'deepref' package versions 1.1.1 through 1.2.1 are vulnerable to prototype pollution. This vulnerability allows an attacker to manipulate the prototype of objects, leading to a denial of service and potential remote code execution. By injecting malicious data into the application, an attacker can modify the behavior of the affected application, potentially leading to unauthorized access, data leaks, or other security breaches.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to upgrade to a non-vulnerable version of the 'deepref' package as soon as possible.

Conclusion

The 'deepref' package versions 1.1.1 through 1.2.1 are vulnerable to a prototype pollution vulnerability. This vulnerability can lead to a denial of service and potential remote code execution. To mitigate the risk, it is crucial to upgrade to a non-vulnerable version of the 'deepref' package (version 1.2.2 or higher). Thorough testing should be performed after the upgrade to ensure the vulnerability has been successfully addressed. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for deepref →

Share this vulnerability

FAQ

Prototype pollution is a vulnerability that occurs when an attacker is able to modify the prototype of an object. By manipulating the prototype, the attacker can modify the behavior of the affected application, potentially leading to security breaches.

This vulnerability can lead to a denial of service and potential remote code execution. An attacker can exploit this vulnerability to gain unauthorized access, leak sensitive data, or perform other malicious actions.

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide your package-lock.json file, and Vulert will analyze it for any open-source vulnerabilities, including this one.

Yes, a fix is available for this vulnerability. It is recommended to upgrade to a non-vulnerable version of the 'deepref' package (version 1.2.2 or higher) to mitigate the risk.

For further support on vulnerability remediation, you can reach out to info@devnack.com. They can provide guidance and assistance in addressing this vulnerability in your application.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. 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