Prototype Pollution in dset

Description

All versions of dset prior to 3.1.2 are vulnerable to Prototype Pollution via dset/merge mode, as the dset function checks for prototype pollution by validating if the top-level path contains __proto__, constructor or prototype. By crafting a malicious object, it is possible to bypass this check and achieve prototype pollution.

Recommendation

Update the dset package to the latest compatible version. Followings are version details:

• Affected version(s): < 3.1.2
• Patched version(s): 3.1.2

References

• GHSA-23wx-cgxq-vpwx
• snyk.io
• CVE-2022-25645
• CWE-1321
• CAPEC-310
• OWASP 2021-A6

Related Issues

• steal vulnerable to Prototype Pollution via requestedVersion variable - CVE-2022-37257
• deep-object-diff vulnerable to Prototype Pollution - CVE-2022-41713
• steal vulnerable to Prototype Pollution - CVE-2022-37258
• ts-deepmerge before 2.0.2 vulnerable to Prototype Pollution - CVE-2022-25907

You might also like:

How to Secure your NodeJs Express Javascript Application - part 1

How to Secure your NodeJs Express Javascript Application - part 2

10 Secure Coding Best Practices to Follow in Every Project

Tags:

npm

dset