aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorXe Iaso <me@xeiaso.net>2024-10-29 14:43:47 -0400
committerXe Iaso <me@xeiaso.net>2024-10-29 14:43:47 -0400
commit937f9642b8f759916200598bfa9a068adc334bab (patch)
tree815e28b344539f8cb1abb7d7db21611718d91a3e
parenteef4b5295db3d5f2ed56e6ead2b1089a1fd519ff (diff)
downloadxesite-937f9642b8f759916200598bfa9a068adc334bab.tar.xz
xesite-937f9642b8f759916200598bfa9a068adc334bab.zip
CVE-2024-9632
Signed-off-by: Xe Iaso <me@xeiaso.net>
-rw-r--r--lume/src/shitposts/no-way-to-prevent-this/CVE-2024-9632.md20
1 files changed, 20 insertions, 0 deletions
diff --git a/lume/src/shitposts/no-way-to-prevent-this/CVE-2024-9632.md b/lume/src/shitposts/no-way-to-prevent-this/CVE-2024-9632.md
new file mode 100644
index 0000000..c39c6db
--- /dev/null
+++ b/lume/src/shitposts/no-way-to-prevent-this/CVE-2024-9632.md
@@ -0,0 +1,20 @@
+---
+title: '"No way to prevent this" say users of only language where this regularly happens'
+date: 2024-10-29
+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-9632](https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2024-9632) for the project [X.org](https://x.org/wiki/), site reliability workers
+and systems administrators scrambled to desperately rebuild and patch all their systems to fix a buffer overflow that allows an attacker with access to raw X client calls to arbitrarily read and write memory, allowing for privilege escalation attacks. 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 Queen Annamarie Bayer, 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."