Quick answers
- Is CVE-2022-22143 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-22143 being exploited in the wild.
- How severe is CVE-2022-22143?
- Low severity, with a CVSS score of 3.1, published 20 April 2022.
- Which products and versions are affected?
- convict (npm) SEMVER:introduced=0,fixed=6.2.3.
- Is there a fix for CVE-2022-22143?
- Yes. convict (npm): upgrade to 6.2.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2022-22143 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2022-22143?
- Check whether you run convict (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- convict (npm): upgrade to 6.2.3 or later
npm install convict@6.2.3
Technical details
The vulnerability is a prototype pollution flaw (CWE-1321) in how Convict processes configuration input without properly validating or restricting modifications to object prototype attributes. An attacker can craft malicious configuration data that injects attributes into the prototype chain, affecting other components that rely on the configuration object. The attack vector is local and requires no privileges or user interaction, but depends on an attacker being able to inject or modify configuration files. The vulnerability allows arbitrary attribute injection, type confusion leading to crashes, and potential information disclosure. The issue is patched in Convict version 6.2.3; all earlier versions are affected and users should upgrade immediately.
Affected products
- Mozilla Convict < 6.2.3
Identifiers
- CVE-2022-22143
- GHSA-x2w5-725j-gf2g
Timeline
- 2022-04-20: disclosed
- 2022-04-20: patched: Patch available in Convict 6.2.3