I've tried reading through the article, but unfortunately, I'm not the sharpest tool in the shed. I use openSUSE, how does this affect me, and what do I need to do/what can I do about this?
this post was submitted on 19 Mar 2025
89 points (92.4% liked)
Linux
56758 readers
647 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
You don’t need to do anything, these issues have already been fixed.
Perfect. Thank you for taking the time to respond
Do you mean the specific exploit performed by the author has been fixed? Or the general vulnerability that this exploit was intended to demonstrate has been fixed? The article ends with a What's Next section discussing the difficulty of the latter, saying
we don’t think there’s a silver bullet to address the risks caused by the compromise of such central pieces of infrastructure
and going into detail about the challenges for openSUSE OBS. Are you claiming those challenges have all been solved and exploits like this are no longer possible?
The authors found and reported vulnerabilities in Pagure and Open Build Service. These vulnerabilities have since been fixed.
Usually with vulnerabilities like this, they're not gonna say anything about it until after they patch it so that people don't go abuse it
Nice post, ~~but your title is misleading~~: the blog post is actually titled "Supply Chain Attacks on Linux distributions - Overview" - the word "attacks" as used here is a synonym for "vulnerabilities". It is not completely clear from their title if this is going to be a post about vulnerabilities being discovered, or about them actually being exploited maliciously, but the latter is at least not strongly implied.
~~This lemmy post however is titled (currently, hopefully OP will retitle it after this comment) "Supply Chain Attack found in Fedora's Pagure and openSUSE's Open Build Service".~~ edit: @OP thanks for changing the title!
Adding the word "found" (and making "Attack" singular) changes the meaning: this title strongly implies that a malicious party has actually been detected performing a supply chain attack for real - which is not what this post is saying at all. (It does actually discuss some previous real-world attacks first, but it is not about finding those; the new findings in this post are vulnerabilities which were never attacked for real.)
~~I recommend using the original post title (minus its "Overview" suffix) or keeping your more verbose title but changing the word "Attack" to "Vulnerabilities" to make it clearer.~~
TLDR: These security researchers went looking for supply chain vulnerabilities, and found several bugs in two different systems. After responsibly disclosing them, they did these (very nice and accessible, btw - i recommend reading them) writeups about two of the bugs. The two they wrote up are similar in that they both involve going from being able to inject command line arguments, to being able to write to a file, to being able to execute arbitrary code (in a context which would allow attackers to perform supply chain attacks on any software distributed via the targeted infrastructure).
yeah, it turns the thing into clickbait.
Supply chain attacks have been a trendy topic in the past years.
Has the meaning of 'trendy' changed from what I'm used to?
It's 2024, if you're not exploiting CI systems to inject your malware into the dependency chain for large open source projects, what even are you doing with your life?
it's 2025 now but otherwise yeah
Not according to my, completely malware free, waybar-git-real!