Need this addressed.this is really dangerous since every pipeline as long user have access the could executed a pipeline inside our own branch
https://cloud.google.com/blog/topics/threat-intelligence/bitbucket-pipeline-leaking-secretscould we somehow disable artifacts if there is some command running or like blocked printenv completely
Hey @Prima Adi Pradana - isn't this the case for all cloud CI/CD tools - not just Pipelines? It looks like the exact same thing happens with Github Actions: https://github.com/orgs/community/discussions/24928
If you're concerned about this happening, you could use something like a Dynamic Pipeline to look through any CI workflows before they run and not run any that look to be printing secrets to files.
It looks like you're new here. Sign in or register to get started.
