News for hackers. Stuff that matters.
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.

There are no comments on this comment yet.