CVE-2020-7788: Prototype pollution via malicious INI file in ini@1.3.4

node-ini Updated 02 Oct 2025

Summary

11/12/2020
N/A
Yes i
Critical
9.8

CVE-2020-7788: This affects the package ini before 1.3.6. Affects node-ini across 2 version ranges.

< 2.0.0-1 < 56d2805e07ccd94e2ba0984ac9240ff02d44b6f1

Fixed in 2.0.0-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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The 'ini' package is a popular Node.js library used for parsing and manipulating INI files. INI files are simple configuration files that store settings in a key-value format. The 'ini' package provides functions to parse INI files and convert them into JavaScript objects. However, versions of the 'ini' package before 1.3.6 are vulnerable to prototype pollution. If an attacker submits a malicious INI file to an application that parses it with 'ini.parse', they can pollute the prototype on the application, leading to potential exploitation depending on the context.

Vulnerability Detail

The vulnerability, identified as CVE-2020-7788, allows an attacker to pollute the prototype of an application by submitting a malicious INI file. This can result in various security issues depending on how the polluted prototype is used within the application. The impact of this vulnerability can range from unauthorized access to sensitive data to remote code execution. It is crucial to update the 'ini' package to version 1.3.6 or higher to mitigate this vulnerability.

How To Fix

Minimum fixed version

2.0.0-1

This is the first release that contains the fix.

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

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

Conclusion

The 'ini' package before version 1.3.6 is vulnerable to prototype pollution, which can have severe security implications. It is crucial to update the package to the latest version to protect your application from potential exploitation. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for node-ini →

Share this vulnerability

FAQ

The 'ini' package is a Node.js library used for parsing and manipulating INI files, which are simple configuration files.

Prototype pollution is a vulnerability that occurs when an attacker can modify the prototype of an object, leading to unexpected behavior or security issues.

By submitting a malicious INI file to an application that uses the 'ini' package to parse it, an attacker can pollute the prototype of the application and potentially exploit it depending on the context.

The consequences of this vulnerability can vary depending on how the polluted prototype is used within the application. It can lead to unauthorized access to sensitive data, remote code execution, or other security issues.

To mitigate this vulnerability, it is recommended to update the 'ini' package to version 1.3.6 or higher.

Related vulnerabilities

Recent vulnerabilities recorded for node-ini.

How To Fix

Minimum fixed version

2.0.0-1

This is the first release that contains the fix.

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

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