CVE-2020-28448: Prototype Pollution in multi-ini

multi-ini Updated 02 Oct 2025

Summary

13/04/2021
Yes i
Critical
9.8

CVE-2020-28448: Prototype Pollution in multi-ini. Affects multi-ini versions < 2.1.1. Fixed in 2.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 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 multi-ini package is an npm package used for parsing and manipulating INI files. It provides functionality to read, write, and modify INI files in JavaScript applications. The package is widely used in various projects and allows developers to work with INI configuration files in a convenient manner. However, a vulnerability has been discovered in versions before 2.1.1 that allows for prototype pollution.

Vulnerability Detail

The vulnerability, identified as CVE-2020-28448, is a prototype pollution vulnerability in the multi-ini package. By specifying the proto object as part of an array, it is possible to pollute an object's prototype. This can lead to various security issues, including remote code execution, data tampering, and privilege escalation. The impact of this vulnerability is critical, with a CVSS score of 9.8.

How To Fix

Minimum fixed version

2.1.1

This is the first release that contains the fix.

npm install multi-ini@2.1.1

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 the multi-ini package to the fixed version to mitigate the risk of exploitation.

Conclusion

The multi-ini package before version 2.1.1 is vulnerable to prototype pollution, which can have severe security implications. It is crucial to update the package to the fixed version to mitigate the risk of exploitation. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for multi-ini →

Share this vulnerability

FAQ

multi-ini is an npm package used for parsing and manipulating INI files in JavaScript applications.

Prototype pollution is a vulnerability that allows an attacker to modify the prototype of an object, leading to potential security issues.

The vulnerability can result in remote code execution, data tampering, and privilege escalation.

To fix this vulnerability, update the multi-ini package to version 2.1.1 or later.

No, there is no known workaround for this vulnerability. Updating the package is the recommended solution.

Related vulnerabilities

Recent vulnerabilities recorded for multi-ini.

How To Fix

Minimum fixed version

2.1.1

This is the first release that contains the fix.

npm install multi-ini@2.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