News for hackers. Stuff that matters.
Re:Pre-auth RCE in Nginx HTTP/2 handling by dyauspitr on Wednesday November 18, 2026 @02:41PM (#50551082)
As someone that was a developer for a long time what is the problem with C? How does going to rust mitigate this? Why is having the stuff in C a security challenge?
Re:Pre-auth RCE in Nginx HTTP/2 handling by unrented7977 on Wednesday November 18, 2026 @02:44PM (#50551116)
Some people think it's fundamentally impossible for C to be correct or memory safe
Re:Pre-auth RCE in Nginx HTTP/2 handling by dralley on Wednesday November 18, 2026 @03:36PM (#50551781)
Fundamentally impossible? No.

Practically impossible? Yes.

SQLite is probably the most thoroughly tested and carefully developed C library in history and they still found a handful of memory safety bugs every year.

Re:Pre-auth RCE in Nginx HTTP/2 handling by djha-skin on Wednesday November 18, 2026 @02:48PM (#50551166)
Rust is memory safe at the cost of being harder to write, but with AI, it's actually really easy to write it because AI's loove strict compilers. So now that AIs can just find 0-days before things are even released (so I'm told), it makes a lot of sense to do bun[1]-style rewrites to Rust with AI.

1: https://bun.com/blog/bun-in-rust

Re:Pre-auth RCE in Nginx HTTP/2 handling by shakna on Wednesday November 18, 2026 @03:11PM (#50551497)
[delayed]
Re:Pre-auth RCE in Nginx HTTP/2 handling by djha-skin on Wednesday November 18, 2026 @04:20PM (#50552270)
I read 0 days like "Exploitable 0 days since _discovery_". Also, it's only a bug in the normal lifecycle if the discoverer tells the developer making it. If they discover it and then have hours and days to perfect a program that exploits it, then starts running immediately when it is deployed or released, that's a new kind of "zero day". Makes you want to start differentiating what "0 days" mean, though.
Re:Pre-auth RCE in Nginx HTTP/2 handling by shakna on Wednesday November 18, 2026 @05:01PM (#50552823)
[delayed]
Re:Pre-auth RCE in Nginx HTTP/2 handling by djha-skin on Wednesday November 18, 2026 @08:04PM (#50554688)
The ai told the hacker. The hacker discovered it with his AI before the developer released by examining his git branch.

I think that's the fundamental disconnect in the conversation here. You think I'm talking about the dev because it's not released yet but just because it isn't tagged and released doesn't mean it's not done in the open where hackers can see it and their AI can scan it.

Re:Pre-auth RCE in Nginx HTTP/2 handling by Delk on Wednesday November 18, 2026 @03:47PM (#50551921)
It's very easy to accidentally write buffer overflows, use-after-frees or other memory-safety bugs in C. Modern tooling can probably catch some of these better than in the days of yore but the fundamentals of the language are still safe.

If e.g. the standard array type in a language has built-in bounds checks that error out when you try to write to an index that's outside of the array, you can't trivially create buffer overflows simply by writing to the wrong index or by trying to write n + 10 bytes into an n-byte array.

But C in itself has no guardrails against something like

  char buffer[100];
  strcpy(buffer, some_user_supplied_string_with_200_chars);
Of course most memory safety bugs aren't trivial like that since C programmers have hopefully learned to avoid the simple mistakes. But there can be more complicated and difficult to spot cases, and C has no guardrails against those either.