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
When enumerating organizations, Gato-X uses a heuristic to only pull run logs for workflows that potentially use self-hosted runners. This is for speed and to prevent hitting secondary rate limits when pulling run logs.
The problem is that the workflow run log is associated with the calling workflow, so the callee containing the job using a self-hosted runner will not have runs associated with it. The fix here is to use the same parsing logic Gato-X uses for detecting Pwn requests/Injection in called workflows to identify the calling workflow.
The text was updated successfully, but these errors were encountered:
Describe the bug
When enumerating organizations, Gato-X uses a heuristic to only pull run logs for workflows that potentially use self-hosted runners. This is for speed and to prevent hitting secondary rate limits when pulling run logs.
The problem is that the workflow run log is associated with the calling workflow, so the callee containing the job using a self-hosted runner will not have runs associated with it. The fix here is to use the same parsing logic Gato-X uses for detecting Pwn requests/Injection in called workflows to identify the calling workflow.
The text was updated successfully, but these errors were encountered: