-
Improvement
-
Resolution: Unresolved
-
Minor
-
Jenkins 2.235.5, SLES 11.3, role-strategy-plugin 3.0
Despite running jobs are filtered out by item roles, Build Executor Status is shown for nodes, which the user has no access via node roles.
This blows up the Build Executor Status with Build Processors from this nodes.
Additional an hacker gets information, that these nodes exist and can show some details about it, eg. Labels.
There is no permission in Jenkins that allows to hide the existence of an agent, similar to what we have for jobs (Job/Discover, and Job/Read). Such a thing needs to be implemented in Jenkins core directly so that also matrix auth would be able to work with this.