|
|
|
|
|
by kentonv
1655 days ago
|
|
FWIW, in Cloudflare Workers, a log4j-type RCE vulnerability would be impossible because Workers does not allow dynamic code loading (eval() and similar are disabled). Of course, a lesser form of the vulnerability -- data leaks rather than RCE -- would still be possible. I agree that being able to restrict outbound traffic would be useful to mitigate that. As a hack that works now, you could monkey-patch `fetch()` to intercept calls and deny them based on URL. (I'm the tech lead of Cloudflare Workers.) |
|
Monkey patching is an option of course, but a native solution would be nice.