<- Back to list

"No way to prevent this" say users of only language where this regularly happens

xeiaso.net

securityprogrammingperformancenetworkingsecurity/Webperformance/Optimization

AI 摘要

NGINX项目披露了两个高危HTTP/2漏洞(CVE-2026-123633和CVE-2026-123007),可导致未经身份验证的远程代码执行。文章指出这些漏洞源于使用C语言编程,而C语言在过去50年中导致了全球90%的内存安全漏洞。开发者无奈表示对此类漏洞的反复发生感到无助,认为除非程序员愿意采用更健壮的编程方式,否则难以避免。

In the hours following the release of CVE-2026-123633 and CVE-2026-123007 for the project NGINX, site reliability workers and systems administrators scrambled to desperately rebuild and patch all their systems to fix an HTTP/2 connection use-after-free during reverse-proxy processing when connection slots run low, alongside an HTTP/2 flow-control integer underflow that leads to an out-of-bounds memory copy over TLS, both of which can allow unauthenticated remote code execution on affected servers with HTTP/2 enabled. This is due to the affected components being written in C, the only programming language where these vulnerabilities regularly happen. "This was a terrible tragedy, but sometimes these things just happen and there's nothing anyone can do to stop them," said programmer Dr. Deontae Rempel, echoing statements expressed by hundreds of thousands of programmers who use the only language where 90% of the world's memory safety vulnerabilities have occurred in the last 50 years, and whose projects are 20 times more likely to have security vulnerabilities. "It's a shame, but what can we do? There really isn't anything we can do to prevent memory safety vulnerabilities from happening if the programmer doesn't want to write their code in a robust manner." At press time, users of the only programming language in the world where these vulnerabilities happen continuously were referring to themselves and their situation as "helpless."

"No way to prevent this" say users of only language where this regularly happens