ADO Pwn Request #169
Merged
ADO Pwn Request #169
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… Changes to Azure Devops(what can be detected from workflow file)
|
Can you please update documentation with Best , Bad examples and also small caveat section that false positive is likely given that static analysis of solely the pipeline file is not enough to confirm exploitability. Maybe take even screenshots of the ADO UI in the best vs bad. To show really how it would be bad |
fproulx-boostsecurity
requested changes
Jul 23, 2024
fproulx-boostsecurity
approved these changes
Jul 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #164 Adds support for finding Arbitrary Code Execution from Untrusted Code Changes to Azure Devops(what can be detected from workflow file)