diff options
| author | Xe Iaso <me@xeiaso.net> | 2024-07-01 11:50:31 -0400 |
|---|---|---|
| committer | Xe Iaso <me@xeiaso.net> | 2024-07-01 11:50:31 -0400 |
| commit | 2d956780bbcb09c39f7f57924b2553e7ef13a00d (patch) | |
| tree | bfba8b9501e1a97b288689abcedde91b46a9c0bf /lume/src/shitposts | |
| parent | 24f4c7e765cfee6c0bbbdfa4b188e5d15016b9cc (diff) | |
| download | xesite-2d956780bbcb09c39f7f57924b2553e7ef13a00d.tar.xz xesite-2d956780bbcb09c39f7f57924b2553e7ef13a00d.zip | |
add CVE-2024-6387
Signed-off-by: Xe Iaso <me@xeiaso.net>
Diffstat (limited to 'lume/src/shitposts')
| -rw-r--r-- | lume/src/shitposts/no-way-to-prevent-this/CVE-2024-6387.md | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/lume/src/shitposts/no-way-to-prevent-this/CVE-2024-6387.md b/lume/src/shitposts/no-way-to-prevent-this/CVE-2024-6387.md new file mode 100644 index 0000000..ff8d92c --- /dev/null +++ b/lume/src/shitposts/no-way-to-prevent-this/CVE-2024-6387.md @@ -0,0 +1,20 @@ +--- +title: '"No way to prevent this" say users of only language where this regularly happens' +date: 2024-07-01 +series: "no-way-to-prevent-this" +type: blog +hero: + ai: "Photo by Andrea Piacquadio, source: Pexels" + file: sad-business-man + prompt: A forlorn business man resting his head on a brown wall next to a window. +--- + +In the hours following the release of [CVE-2024-6387](https://www.qualys.com/2024/07/01/cve-2024-6387/regresshion.txt) for the project [OpenSSH](https://www.openssh.com/), site reliability workers +and systems administrators scrambled to desperately rebuild and patch all their systems to fix a combination of memory unsafety and glibc's creative decisions in signal handler implementation logic allowing remote unprivileged users can gain arbitrary code execution after predicting SSH memory addresses in a forged public key while a SIGALRM handler is being executed. 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. Maurine Wilderman, 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 +regularly happen once or twice per quarter for the last eight years were referring to themselves and their situation as "helpless." |