CVE-2022-22912: Prototype pollution in Plist before 3.0.5 can cause denial of service
Summary
CVE-2022-22912: Prototype pollution in Plist before 3.0.5 can cause denial of service. Affects plist versions < 3.0.5. Fixed in 3.0.5. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
Plist is an npm package that provides functionality for parsing and manipulating property list (plist) files. Plist files are commonly used in macOS and iOS applications to store configuration data. The package allows developers to read and write plist files programmatically. However, a vulnerability in versions prior to 3.0.5 can be exploited to cause a denial of service (DoS) and potentially lead to remote code execution.
Vulnerability Detail
The vulnerability in Plist is due to prototype pollution in the .parse() function. Prototype pollution is a type of vulnerability that occurs when an attacker can modify the prototype of an object and introduce malicious properties or methods. In this case, an attacker can craft a malicious plist file that, when parsed by the vulnerable version of Plist, can modify the prototype of the resulting object. This can lead to unexpected behavior and potentially allow the attacker to execute arbitrary code or cause a DoS by manipulating the object's properties or methods.
How To Fix
Latest published version: 5.0.0 as of 22 Oct 2026
npm install plist@5.0.0Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
3.0.5
This is the first release that contains the fix.
npm install plist@3.0.5Tip — 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 recommended to update to the fixed version of the package as soon as possible.
Conclusion
The vulnerability in Plist before version 3.0.5 can lead to a denial of service and potential remote code execution. Developers should update to version 3.0.5 or later of the package to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for plist →
FAQ
Prototype pollution is a vulnerability that occurs when an attacker can modify the prototype of an object and introduce malicious properties or methods. This can lead to unexpected behavior and potential security issues.
A plist file is a property list file used in macOS and iOS applications to store configuration data. It is an XML or binary file format that represents structured data.
An attacker can craft a malicious plist file that, when parsed by the vulnerable version of Plist, can modify the prototype of the resulting object. This can lead to arbitrary code execution or a denial of service.
Yes, developers can fix this vulnerability by updating to version 3.0.5 or later of the Plist package.
No, there are no known workarounds for this vulnerability. It is recommended to update to the fixed version of the package.
