Earlier quoted context omitted.
Based on what? Proc title?
Proc title is very easily forged (without root even). Obviously a real privileged process could modify the kernel and do whatever it wants, but if I were trying to detect this I would start with /proc/$id/exe.
How Cloudflare responded to the “Copy Fail” Linux vulnerability
11–20 of 86 posts
Re: How Cloudflare responded to the “Copy Fail” Linux vulnerability
#12Re: How Cloudflare responded to the “Copy Fail” Linux vulnerability
#13Earlier quoted context omitted.
Would certainly be interesting to learn more about. A simple check: allowlist of known "processes that run as root". Any new process shows up, something happened.
Based on what? Proc title?
Re: How Cloudflare responded to the “Copy Fail” Linux vulnerability
#14Earlier quoted context omitted.
Based on what? Proc title?
Proc title is very easily forged (without root even). Obviously a real privileged process could modify the kernel and do whatever it wants, but if I were trying to detect this I would start with /proc/$id/exe.
I have a fileless, execless copyfail exploit that works by injecting shellcode directly into systemd's pid 1. (I should probably publish it at some point...)
Re: How Cloudflare responded to the “Copy Fail” Linux vulnerability
#15this is a techincal dive into how cloudflare responded, not a confirmation that they responded for whatever reason, unknown to me, hn automatically strips "how" from the start of titles. i cant remember ever seeing a title where this was an improvement.
Re: How Cloudflare responded to the “Copy Fail” Linux vulnerability
#16Re: How Cloudflare responded to the “Copy Fail” Linux vulnerability
#17Re: How Cloudflare responded to the “Copy Fail” Linux vulnerability
#18That could be as low as 50.1%, I wish they'd provide an actual percentage.
Re: How Cloudflare responded to the “Copy Fail” Linux vulnerability
#19Would love to learn more about their internal behavioural detection program. > One of the first things our security team did was confirm that our existing endpoint detection would catch this exploit. Our servers run behavioral detection that continuously monitors process execution patterns. It doesn't rely on knowing about specific vulnerabilities; it watches for anomalous behavior across the fleet.
Re: How Cloudflare responded to the “Copy Fail” Linux vulnerability
#20The "Hunting for Exploitation" section is unclear to me: "The exploit leaves a distinctive trace in kernel logs when it runs." Hmm. Wouldn't a system with a compromised kernel also log exactly what the attacker wanted logged?
Although given the tendency for end point logging agents to run on buffers to reduce their network chattiness I do wonder if a fast acting exploit could dump that buffer before it manages to be transmitted.
I don't think any of the agents are complex enough to immediately transmit permission elevation log messages over the regular background noise.