aboutsummaryrefslogtreecommitdiff
path: root/lume/src/shitposts
diff options
context:
space:
mode:
authorXe Iaso <me@xeiaso.net>2024-05-14 20:04:43 -0500
committerXe Iaso <me@xeiaso.net>2024-05-14 20:04:43 -0500
commit755890f983d9e48abcdcc93c91510b4895a8c448 (patch)
treeb9fc751091b68e0cb826ed8a590fa87acbe9db8a /lume/src/shitposts
parent687cb6451b528041e4586d84d8dec4d0e036a1f6 (diff)
downloadxesite-755890f983d9e48abcdcc93c91510b4895a8c448.tar.xz
xesite-755890f983d9e48abcdcc93c91510b4895a8c448.zip
fuck i fucked up
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-32004.md8
1 files changed, 5 insertions, 3 deletions
diff --git a/lume/src/shitposts/no-way-to-prevent-this/CVE-2024-32004.md b/lume/src/shitposts/no-way-to-prevent-this/CVE-2024-32004.md
index 1112e97..80ba227 100644
--- a/lume/src/shitposts/no-way-to-prevent-this/CVE-2024-32004.md
+++ b/lume/src/shitposts/no-way-to-prevent-this/CVE-2024-32004.md
@@ -1,5 +1,5 @@
---
-title: '"No way to prevent this" say users of only language where this regularly happens'
+title: '[RETRACTED] "No way to prevent this" say users of only language where this regularly happens'
date: 2024-05-14
series: "no-way-to-prevent-this"
type: blog
@@ -9,7 +9,9 @@ hero:
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-32004](https://github.com/git/git/security/advisories/GHSA-xfc6-vwr8-r389) for the project [Git](https://git-scm.com/), site reliability workers
+I fucked up, this isn't memory safety. Ignore this.
+
+~~In the hours following the release of [CVE-2024-32004](https://github.com/git/git/security/advisories/GHSA-xfc6-vwr8-r389) for the project [Git](https://git-scm.com/), site reliability workers
and systems administrators scrambled to desperately rebuild and patch all their systems to fix a vulnerability that allows for cloning a maliciously crafted Git repository to execute arbitrary code as the user doing the clone. 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 Mr. Odell Altenwerth, echoing statements
@@ -17,4 +19,4 @@ expressed by hundreds of thousands of programmers who use the only language wher
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."
+regularly happen once or twice per quarter for the last eight years were referring to themselves and their situation as "helpless."~~