@LiveOverflow@0daySecured Portswigger has a lab on this #bypassing-samesite-lax-restrictions-with-newly-issued-cookies" target="_blank" rel="nofollow noopener">portswigger.net/web-security/c…
Trick question! Simply don't use session cookies, and instead use "Authorization" header :P
But SameSite=Lax/Strict is also fine. fight me.
twitter.com/LiveOverflow/s…
Extremely important #AppSec topic for tech companies and dev teams that is not talked about much. How to focus on the right things to fix and not drown in busywork that doesn't affect the security bottom line? Curious to hear how others approach this. linkedin.com/posts/danloren…
🔖 Terraform as part of the software supply chain
Post examining the supply chain aspects of Terraform, starting with a closer look at malicious Terraform modules and providers and how you can better secure them.
about.gitlab.com/blog/2022/06/0…
A lot of good knowledge here on the security of Terraform. For offensive security teams, I highly recommend you take a look at how your organizations are using it. There is a ton of attack surface there given the right circumstances.
wtf do you do here? Like, you can keep getting back onto the box, but there's no straightforward way to actually communicate out. You can attempt privescs, but you have no idea why things fail since you have no logs.
Attackers - you have a supply chain "rce" into a project. The svc deploys with no external internet access, runs in a docker container, can only communicate to a few internal services, and all comms are mTLS. The instance is rotated daily.
You can exploit reliably, repeatedly.