cache poisoning
An attack that plants malicious content in a cache so later trusted builds restore and use it.
A poisoned entry runs attacker code inside builds that look trusted.
In more detail
A workflow that a fork can trigger with a write token, or that trusts restored files without checking them, can let an attacker fill the cache that the default branch later consumes. It is a software supply chain attack.
Related terms
- dependency cache — Saved copies of downloaded dependencies that GitHub Actions restores into later runs so they need not be fetched again.
- software supply chain — Everything that goes into your software before it runs: base images, packages, build tools, CI systems and registries.
- fork — A copy of someone else's repository made on a hosting service such as GitHub, under your own account, so you can push to it.
Taught in
- Speeding Up Builds: Caching Dependencies — Continuous Integration & Continuous Delivery Pipelines