Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Informational severity, published 23 November 2022.
- Which products and versions are affected?
- sweetalert2 (npm) SEMVER:introduced=9.17.4,fixed=11.22.4.
- Is there a fix for This vulnerability?
- Yes. sweetalert2 (npm): upgrade to 11.22.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network.
- Am I affected?
- Check whether you run sweetalert2 (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
- sweetalert2 (npm): upgrade to 11.22.4 or later
npm install sweetalert2@11.22.4
Technical details
The vulnerability involves unauthorized hidden functionality injected into sweetalert2 versions 9.17.4 through 10.0.0 by the package maintainer. The issue manifests as embedded audio and/or video output that serves no purpose for the library's core functionality (displaying alert dialogs). The attack vector is supply-chain delivery—any application using affected versions will automatically include the hidden behavior. This is not a traditional code injection vulnerability but rather a case of intentional unwanted code committed by the maintainer. The issue was remediated in version 11.22.4; users can also downgrade to versions 9.0.0–9.17.3 which do not contain the hidden functionality.
Affected products
- sweetalert2 sweetalert2 9.17.4 to 10.0.0, prior to 11.22.4
Timeline
- 2022-11-23: disclosed
- 2022-11-23: patched: Fixed in version 11.22.4