diff options
| author | Xe Iaso <me@xeiaso.net> | 2024-02-01 15:28:57 -0500 |
|---|---|---|
| committer | Xe Iaso <me@xeiaso.net> | 2024-02-01 15:28:57 -0500 |
| commit | ad884fafc419f5e36aca907fd8e88cb7458e4f58 (patch) | |
| tree | d0c9100347a8ce15cff77a35d716533fd3e2062a /lume/src/shitposts | |
| parent | ee0aa5a05515d16be51229dd42c8c0c4cec19819 (diff) | |
| download | xesite-ad884fafc419f5e36aca907fd8e88cb7458e4f58.tar.xz xesite-ad884fafc419f5e36aca907fd8e88cb7458e4f58.zip | |
'No way to prevent this' says users of the only programming language where this regularly happens
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-2023-6246.md | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/lume/src/shitposts/no-way-to-prevent-this/CVE-2023-6246.md b/lume/src/shitposts/no-way-to-prevent-this/CVE-2023-6246.md new file mode 100644 index 0000000..d0a1411 --- /dev/null +++ b/lume/src/shitposts/no-way-to-prevent-this/CVE-2023-6246.md @@ -0,0 +1,20 @@ +--- +title: '"No way to prevent this" says users of the only programming language where this regularly happens' +date: 2024-01-30 +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-2023-6246](https://www.qualys.com/2024/01/30/cve-2023-6246/syslog.txt) 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 heap-based buffer overflow in the syslog() function resulting in memory corruption or even arbitrary code execution when run in SUID binaries. 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 Willodean Santorella, 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." |