CVE-2020-28441 json
Prototype Pollution
published 2022-07-25 4 y ago modified 2026-06-17 4 mo ago also GHSA-m6mg-jvjf-w44x , EUVD-2022-6373
- cvss
- 7.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 0
- none known
Summary
This affects the package conf-cfg-ini before 1.2.2. If an attacker submits a malicious INI file to an application that parses it with decode, they will pollute the prototype on the application. This can be exploited further depending on the context.
Patch / fix
- npm conf-cfg-ini 1.2.2
- n/a conf-cfg-ini 1.2.2
Exploit prediction
1.22% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- security.snyk.io https://security.snyk.io/vuln/SNYK-JS-CONFCFGINI-1048973 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P |
| CNA | 3.1 | 7.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | conf-cfg-ini | <1.2.2 |
1.2.2 |
Affected products
- n/a conf-cfg-ini
Classification
- Weakness
-
- CWE-1321 Improperly Controlled Modification of Object Prototype Attributes
References
-
github.com
/loge5/conf-cfg-ini/commit/3a88a6c52c31eb6c0f033369eed40aa168a636ea
web, patch, third-party-advisory
-
github.com
/loge5/conf-cfg-ini/commit/ecd878f8f7398e765739e989c7fe7cc052308947
web
-
security.snyk.io
/vuln/SNYK-JS-CONFCFGINI-1048973
web, exploit, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-28441
advisory
-
github.com
/loge5/conf-cfg-ini
package
Sources
- CVE List CVE-2020-28441
- GitHub Advisory GHSA-m6mg-jvjf-w44x
- NVD CVE-2020-28441
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.