Impact
This is mainly for nodejs processes which are using the second argument of the zxcvbn function. It can result in an unbounded resource consumption as the user inputs array is extended with every function call.
Browsers are impacted, too but a single user need to do a lot of input changes so that it affects the browser, while the node process gets the inputs of every user of a platform and can be killed that way.
Patches
The problem is patched in version 3.0.2
Workarounds
Stop using the second argument of the zxcvbn function and use the zxcvbnOptions.setOptions function
Impact
This is mainly for nodejs processes which are using the second argument of the zxcvbn function. It can result in an unbounded resource consumption as the user inputs array is extended with every function call.
Browsers are impacted, too but a single user need to do a lot of input changes so that it affects the browser, while the node process gets the inputs of every user of a platform and can be killed that way.
Patches
The problem is patched in version 3.0.2
Workarounds
Stop using the second argument of the zxcvbn function and use the zxcvbnOptions.setOptions function