Add a fix for the vulnerability in zod literal validation message #3846
+6
−20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
zod literal validation was giving the actual literal value in the error message as "Invalid literal, expected ". This could be proven to be a potential vulnerability that exposes sensitive information.
For example, when literals are used for API token validation in backend, the error message will simply expose the api token in http error response or in the logs.
This could potentially add a vulnerability in users code and may cause breach.
This PR will remove literal value in error message.