Vulnerability Database · npm · ini-parser · Version
ini-parser 0.0.1
0.0.1 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 1 High 0 Medium 0 Low 0 Unrated 0
-
Released 06 Aug 2014
Also known from other sources 1
Newer releases 2
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
ini-parser 0.0.1 vulnerabilities
1 vulnerability cover ini-parser 0.0.1. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2020-7617: Prototype Pollution in ini-parser | 9.8 critical | No fix published | 10 Jun 2020 |
Looking for another version, or everything Vulert holds for ini-parser?
Questions
About ini-parser 0.0.1
Is ini-parser 0.0.1 vulnerable?
Yes. 1 vulnerability in the Vulert database cover ini-parser 0.0.1: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 0.0.1 the latest release of ini-parser?
No. 0.0.1 was published 06 Aug 2014, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor ini-parser for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the ini-parser version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.