Quick answers
- Is CVE-2022-37266 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-37266 being exploited in the wild.
- How severe is CVE-2022-37266?
- Low severity, with a CVSS score of 3.1, published 16 September 2022.
- Which products and versions are affected?
- steal (npm) SEMVER:introduced=0,last_affected=2.3.0.
- Is there a fix for CVE-2022-37266?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2022-37266 attacked?
- It is attacked over the network.
- Am I affected by CVE-2022-37266?
- Check whether you run steal (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.
Technical details
A prototype pollution vulnerability exists in the extend function within babel.js in StealJS, exploitable via the key variable. The vulnerability is classified as CWE-1321 (Improper Restriction of Rendered UI Layers or Frames) and affects the core object extension logic. The attack is network-accessible, requires no authentication or user interaction, and allows attackers to pollute Object.prototype by injecting arbitrary properties. An attacker can achieve arbitrary code execution or significant modifications to application behavior. All versions through 2.3.0 are affected; patch information is available from the StealJS repository.
Affected products
- StealJS steal through 2.3.0
Identifiers
- CVE-2022-37266
- GHSA-vwhq-pm3r-fjm9
Timeline
- 2022-09-16: disclosed: GHSA-vwhq-pm3r-fjm9 published
- 2022-09-15: other: CVE-2022-37266 published on NVD
- 2022-09-14: other: Issue opened in StealJS repository