Hi folks.
I hope the week's email finds you well! :-) There's some valuable lessons on Github Actions, and an eye-watering $32B acquisition by Google. I hope you enjoy the read!
I'll be pausing the newsletter for about two months. There's a big maintenance window coming up at the powerplant where I work, which requires all hands on deck, and after that we're moving house. When all that is done, I'll be back :-) Cheers!
Github Actions supply chain attack
A re-usable Github action building block, 'tj-actions/changed-files', which is used by 23,000 repositories, was hijacked. The attackers injected code that dumped CI secrets as a readable file in the affected Github repository. The impact is somewhat limited though, with "only" 218 repositories actually ending up exposing secrets.
If you use Github actions yourself it's a very worthwhile read to extract some lessons from. Like for example not pinning your actions to certain versions, because those can still be changed. Instead it is recommended to pin them to specific commit hashes.
Three articles that explain it well, in chronological order:
- Supply chain attack on popular GitHub Action exposes CI/CD secrets: link.
- GitHub Action hack likely led to another in cascading supply chain attack: link.
- GitHub Action supply chain attack exposed secrets in 218 repos: link.
From the article: "MegaRAC BMC (Baseboard Management Controller) provides "lights-out" and "out-of-band" remote system management capabilities that help admins troubleshoot servers as if they were physically in front of the devices. The firmware is used by over a dozen server vendors that provide equipment to many cloud service and data center providers, including HPE, Asus, ASRock, and others."
The vulnerability allows remote attackers to access the management interface and do all kinds of bad stuff with them. Worth checking up on if you use these BMC's.