As far as I can tell, none of the object operations in this library are subject to the prototype pollution exploits, as all of the object keys are defined by the programmer, not the user. However, we should be safe than sorry and test to make sure we handle those cases.
As far as I can tell, none of the object operations in this library are subject to the prototype pollution exploits, as all of the object keys are defined by the programmer, not the user. However, we should be safe than sorry and test to make sure we handle those cases.
See: https://github.com/JaneJeon/objection-authorize/issues/195