You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, there's no upperbound when setting a metadata attribute of a GenericEntity (LInk, Switch, Interface), this can lead to massive objects stored and even vulnerability for unauthenticated endpoints. Since this data will also be written on Mongo it's desirable to validate both how large this object is and how many keys.
Maybe we can limit up to 200 metadata keys for now, and also measure on average the expected size of that object, let me know if that sounds reasonable for the number of metadata keys we'll have in prod, what do you think?
The text was updated successfully, but these errors were encountered:
Currently, there's no upperbound when setting a
metadata
attribute of aGenericEntity
(LInk, Switch, Interface), this can lead to massive objects stored and even vulnerability for unauthenticated endpoints. Since this data will also be written on Mongo it's desirable to validate both how large this object is and how many keys.Maybe we can limit up to 200 metadata keys for now, and also measure on average the expected size of that object, let me know if that sounds reasonable for the number of metadata keys we'll have in prod, what do you think?
The text was updated successfully, but these errors were encountered: