Comment 11 for bug 1365350

I talked with Same yesterday about this. Since the metadata blob is serialized in memory, this could cause memory exhaustion on that particular server. At best, this is a very low impact security issue.

The fix would be to do something like this:

1) accept the meta from the user and merge it with the existing metadata. If it's larger than something like eg 5x the total allowed size, reject the response with a 4xx series code.

2) with the new combined list of metadata entries, filter out all the old deleted ones, and if the resulting set is greater than the allowed max, reject the response with a 4xx series code.

This will keep the metadata bounded, but still allow for users to delete existing rows and keep updating metadata.