aboutsummaryrefslogtreecommitdiff
path: root/lume/src/shitposts
diff options
context:
space:
mode:
authorXe Iaso <me@xeiaso.net>2024-04-21 14:56:53 -0400
committerXe Iaso <me@xeiaso.net>2024-04-21 14:56:53 -0400
commitccd20508c9c750304c7d454020b72257804eb37c (patch)
tree99f472a9410ce86789c5bc4382d220ffaf03f17d /lume/src/shitposts
parentb6478e009e6630647c19c2b2df081bb6358cac33 (diff)
downloadxesite-ccd20508c9c750304c7d454020b72257804eb37c.tar.xz
xesite-ccd20508c9c750304c7d454020b72257804eb37c.zip
CVE-2024-2961
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-2961.md20
1 files changed, 20 insertions, 0 deletions
diff --git a/lume/src/shitposts/no-way-to-prevent-this/CVE-2024-2961.md b/lume/src/shitposts/no-way-to-prevent-this/CVE-2024-2961.md
new file mode 100644
index 0000000..90f6a2c
--- /dev/null
+++ b/lume/src/shitposts/no-way-to-prevent-this/CVE-2024-2961.md
@@ -0,0 +1,20 @@
+---
+title: '"No way to prevent this" say users of only language where this regularly happens'
+date: 2024-04-21
+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-2961](https://www.openwall.com/lists/oss-security/2024/04/18/4) for the project [GNU glibc](https://sourceware.org/glibc/), site reliability workers
+and systems administrators scrambled to desperately rebuild and patch all their systems to fix a vulnerability when converting strings to the ISO-2022-CN-EXT character set, which may be used to gain arbitrary code execution or arbitrary memory corruption. 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 Miss Esmeralda Skiles, 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."