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
sanitizeParams function does not filter out fields inside query params. This presents a challenge in "hiding" fields in from public access, since an attacker can still query using those fields and gain privileged information.
I am not exactly sure what intention of "fields" setting is, but I sure do hope no one is using them with the assumption that access is restricted to those fields
Problem / motivation
sanitizeParams
function does not filter out fields insidequery
params. This presents a challenge in "hiding" fields in from public access, since an attacker can still query using those fields and gain privileged information.I am not exactly sure what intention of "fields" setting is, but I sure do hope no one is using them with the assumption that access is restricted to those fields
Example
Suppose I have the following:
I can still use hiddenField in actions with
query
param. For example:call example.list --query '{"hiddenField": false}'
will list out all the fields where
hiddenField
is false. Ideally, querying in this manner shouldnot work.
Suggested Solution
Inside
sanitizeParams
function after parsing, one could filter by:The text was updated successfully, but these errors were encountered: