Prototype Pollution Vulnerability in node-node-forge Package

node-node-forge Updated 02 Oct 2025

Summary

01/09/2020
N/A
Yes i
Unrated
Not published

DEBIAN-CVE-2020-7720: The package node-forge before 0.10.0 is vulnerable to Prototype Pollution via the util.setPath function. Affects node-node-forge versions < 0.10.0~dfsg-1. Fixed in 0.10.0~dfsg-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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The node-node-forge package is a popular JavaScript library used for implementing various cryptographic functions and protocols. It provides functionalities such as encryption, decryption, and certificate generation, making it a vital tool for developers working on secure applications. However, prior to version 0.10.0, the package was found to be vulnerable to a Prototype Pollution issue, which could lead to security risks in applications utilizing this library.

Vulnerability Detail

The vulnerability in node-node-forge arises from the util.setPath function, which allows an attacker to manipulate the prototype of an object. This can lead to unauthorized access or modification of properties in the application, potentially compromising the integrity and security of the software. The issue is particularly concerning as it can be exploited without proper validation of user input, making it a significant risk for developers relying on this library.

How To Fix

Minimum fixed version

0.10.0~dfsg-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade node-node-forge

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

Workaround

As a temporary measure, developers can avoid using the util.setPath function in their code until the package is updated. Additionally, implementing input validation and sanitization can help mitigate the risk of exploitation.

Conclusion

The Prototype Pollution vulnerability in the node-node-forge package poses a significant risk to applications that utilize this library. It is crucial for developers to update to the patched version 0.10.0 or later to ensure the security of their applications. Additionally, utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for node-node-forge →

Share this vulnerability

FAQ

Prototype Pollution is a type of vulnerability that allows an attacker to manipulate the prototype of an object, potentially leading to unauthorized access or modification of properties.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Exploitation of this vulnerability can lead to severe security risks, including unauthorized access to sensitive data and potential application compromise.

Yes, the vulnerability has been patched in version 0.10.0 of the node-node-forge package. It is recommended to update to this version or later.

If an immediate update is not possible, consider implementing input validation and avoiding the use of the vulnerable functions as a temporary workaround.

Related vulnerabilities

Recent vulnerabilities recorded for node-node-forge.

How To Fix

Minimum fixed version

0.10.0~dfsg-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade node-node-forge

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