Alex Chapman

I created a container image that prints the runc version in use. Why is this useful? I have no idea, but it was pretty fun working it out.

Code at https://github.com/ajxchapman/runc-version-image
#Docker #Kuberntes

GitHub - ajxchapman/runc-version-image: A container image that prints the version of `runc` in use

A container image that prints the version of `runc` in use - GitHub - ajxchapman/runc-version-image: A container image that prints the version of `runc` in use

GitHub
Dec 1, 2022 at 4:25pmWeb
Show threadAnant Shrivastava aka anantshriDec 1, 2022
@ajxchapman I am assuming you have already seen this https://threatpost.com/azurescape-kubernetes-attack-container-cloud-compromise/169319/#:~:text=The%20first%20step%20in%20the%20attack%20proved%20easier%20than%20expected.%20Unit%2042%20researchers%20found%20that%20Azure%20uses%20RunC%2C%20the%20industry%20standard%20container%20runtime%2C%20to%20power%20ACI.%20Unfortunately%2C%20this%20happens%20to%20be%20an%20ancient%20version%20of%20the%20technology%20(RunC%20v1.0.0%2Drc2)%2C%20which%20was%20released%20on%20Oct.%201%2C%202016.
‘Azurescape’ Kubernetes Attack Allows Cross-Container Cloud Compromise

A chain of exploits could allow a malicious Azure user to infiltrate other customers' cloud instances within Microsoft's container-as-a-service offering.

Threatpost
Show threadAlex ChapmanDec 1, 2022
@anant yeah, this sort of auditing was part of the reason I was investigating runc.