hard20 pts · first answer countsdevsecopsgithub-actionssupply-chain

Cache poisoning in a release build

A low-privilege workflow on the default branch runs untrusted input and can save to the Actions cache. The release workflow restores the same cache key before building. What is the risk?

A.The release build will only run a little more slowlyB.The cache encrypts the release artifacts by mistakeC.A poisoned cache entry can put bad files in releasesD.Release secrets get copied into the cache key

Discussion 0

Join free to post in the discussion.

Cache poisoning in a release build

Discussion 0

Related questions