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
Not sure if that's a bug but we found a duplicate similarity_id for 2 resource types in the same file
{
"query_name": "ServiceAccount Allows Access Secrets",
"query_id": "056ac60e-fe07-4acc-9b34-8e1d51716ab9",
"query_url": "https://kubernetes.io/docs/reference/access-authn-authz/rbac/",
"severity": "MEDIUM",
"platform": "Kubernetes",
"category": "Secret Management",
"description": "Roles and ClusterRoles when binded, should not use get, list or watch as verbs",
"description_id": "79619280",
"files": [
{
"file_name": "../ingress_takeover.yaml",
"similarity_id": "97148540dde559c5d4cdf9770ea286105f13c07626bb1f29120eefe69790c54d",
"line": 51,
"resource_type": "ClusterRole",
"resource_name": "ingress-nginx",
"issue_type": "IncorrectValue",
"search_key": "metadata.name={{ingress-nginx}}.rules",
"search_line": 0,
"search_value": "",
"expected_value": "The metadata.name={{ingress-nginx}}.rules.verbs should not contain the following verbs: [["list", "watch"]]",
"actual_value": "The metadata.name={{ingress-nginx}}.rules.verbs contain the following verbs: [["list", "watch"]]"
},
{
"file_name": "../ingress_takeover.yaml",
"similarity_id": "97148540dde559c5d4cdf9770ea286105f13c07626bb1f29120eefe69790c54d",
"line": 51,
"resource_type": "Role",
"resource_name": "ingress-nginx",
"issue_type": "IncorrectValue",
"search_key": "metadata.name={{ingress-nginx}}.rules",
"search_line": 0,
"search_value": "",
"expected_value": "The metadata.name={{ingress-nginx}}.rules.verbs should not contain the following verbs: [["get", "list", "watch"]]",
"actual_value": "The metadata.name={{ingress-nginx}}.rules.verbs contain the following verbs: [["get", "list", "watch"]]"
}
]
}
The text was updated successfully, but these errors were encountered:
Hi @niro-lightspin, hope you are doing great!
I am glad to inform you that this issue is being addressed in #6111.
The similarity id was the same for the results because the similarity id is computed using the path, query id, and search key which were the same for those 2 results.
Thank you so much for finding this bug.
Not sure if that's a bug but we found a duplicate similarity_id for 2 resource types in the same file
The text was updated successfully, but these errors were encountered: