4 ms·

Same subnet = as another VM in your project? or random GCP VM that happens to share your subnet? Seems like pretty different risk levels... https://github.com/

by asah 5y ago

Same subnet = as another VM in your project? or random GCP VM that happens to share your subnet? Seems like pretty different risk levels... https://github.com/irsl/gcp-dhcp-takeover-code-exec#attack-scenarios https://github.com/irsl/gcp-dhcp-takeover-code-exec#attack-s...

Rockslide 5y ago
it literally says "same project" right there
- asah 5y ago
  Thanks. Sorry, just wanted to be completely sure.
kl4m 5y ago
The usual configuration is 1 or many subnets per VPC, and one or many VPC per project. a Shared VPC setup between projects is also possible but requires prior agreement from both projects.
kobalsky 5y ago
The problem is that it means that any compromised app, container or chroot can now be escalated to a full fleet takeover unless you have the mentioned mitigations in place.