Conversation

So this week has had RCEs in NGINX, PHP, and BIND9, all of which are present and on the edge for most F5 shops. Fucking yikes.

3
1
1
@cR0w Nginx too? Fuck. That's the only thing running on my server… (If I wasn't so dysfunctional it would already have a website with actual content and an Akkoma instance)
1
0
0

@cR0w okay not vulnerable

0
0
1

@cR0w OK, BIND I can understand, perhaps also PHP. But NGINX? This is the first I've heard about it. Nothing Internet facing here, but I use it internally for hosting cgit.

1
0
0

@cR0w @bms oh, that cve is months old, isn't it?

1
0
0

@ryanc @cR0w That could be why it didn't click with me. Issues with regexp are de rigeur-mortis frankly; it's one prime source of UB and memory safety problems because of all the indirection and recursion involved. I generally try to stick to using PCRE as a known quantity. Probably worth checking if it's been CHERIfied for future use, some of the code bases I'm dealing with are not amenable to CHERIfication because of pointer use assumptions. Why intptr_t exists...

0
0
1

@LunaDragofelis Don't worry, the NginX vuln is so specific that it's unlikely you're affected if you don't actually run anything on it. You really only have to worry if you have some form of file upload form involved.

0
0
1