Overly broad permissions can turn one compromised account into a much larger security problem. Learn how to reduce unnecessary access, review privileges, and apply least privilege across modern Linux systems. Review Linux Privileges×
Desktop Security
security advisory vulnerability
security advisory vulnerability GNOME is officially shortening its standard vulnerability disclosure window from 90 days to 30 days, a change that impacts upstream maintainers, downstream Linux distributions, and system administrators in how they handle software vulnerabilities. The policy shift, announced by long-time security coordinator Michael Catanzaro , addresses modern software patching realities and a growing influx of automated submissions. . Because GNOME is the default desktop environment on several major Linux...
Jul 21, 2026
Security Vulnerabilities security advisory moderate
security advisory moderate For organizations that run a self-hosted Git platform, it’s no longer just about hosting static code repositories. Today, Git servers are responsible for deployment pipelines, API tokens, SSH keys, package repositories, and the automation scripts that push code directly. Confirm that the upgrade addresses known vulnerabilities but also provides production environments. . That makes them trusted systems within the development environment and attractive targets for attackers looking to move...
Jul 20, 2026
Server Securitydata privacy automation
data privacy automation Every system admin has lived through the same Monday morning ritual. A queue of forty tickets, half of them password resets, permission errors, or disk space warnings that any experienced technician could resolve in under two minutes. The other half require actual judgment. For years, automation promised that software would eventually sort the two apart on its own. That promise is now being tested in production Linux environments. . Early results are reshaping how IT teams think about tier-1...
Jul 17, 2026
Privacydata collection automation
data collection automation You're running a web scraping project to collect pricing data from e-commerce sites. You set up a pool of datacenter proxies, launch your scripts, and within minutes — banned . CAPTCHAs everywhere. Your data pipeline stops before it really begins. . It's a frustrating scenario that plays out daily in ad verification, market research, and multi-account management. The website doesn't know you're doing legitimate research or monitoring. It just sees traffic coming from IP ranges it recognizes as...
Jul 17, 2026
Security Trends security advisory social engineering
security advisory social engineering Business Email Compromise used to be a numbers game — mass-blasted emails, broken English, an obvious "URGENT WIRE TRANSFER" subject line. That era is over. Generative AI has turned BEC into a tailored, low-noise operation that mimics writing style, voice, and even video presence. This piece looks at what's actually changed under the hood, what defenders are testing in response, and why so many organizations are still structurally unprepared for it. . The Infrastructure Problem Nobody Wants to...
Jul 17, 2026
Refine news
X Clear Filters
Get the latest News and Insights
Get the latest Linux and open source security news straight to your inbox.
Community Poll
Should Linux servers automatically install security updates?
Trending News
Loading...
Explore Latest Linux Security news
We found 20 articles for you...
78
security advisoryUbuntusudoUbuntu 25.10 introduces Rust-based sudo for improved security features
Ubuntu 25.10 is switching up something we admins use practically every day—sudo. Yep, that trusty command-line companion we run for everything from installing packages to tweaking system settings is getting a replacement. Well, it's not exactly a replacement; it's more like a rewrite. Canonical’s moving from the decades-old C-based version to a Rust-based implementation , and honestly, it’s not just some background tweak you’ll never notice. There’s more going on here than you’d expect, and it’s a shift you’ll probably want to keep on your radar. . Now, Rust might seem like just another buzzword if you’ve been ignoring all the noise about how safe and modern it is, but the switch from C to Rust with sudo isn’t just about trendy programming languages or security posturing. It’s about rethinking a tool that’s basically glued into every admin's workflow, and there are real-world implications for stability and safety here. Maybe you’re already thinking, “Okay, do I need to worry about compatibility or some weird quirks popping up?” It's a legitimate question, and we’ll dive into that. But for now, let’s just say this move is worth your attention, even if you’re skeptical of change—or just already tired of typing "sudo" for the thousandth time today. Why Switch to Rust? First things first: you’re probably wondering why Canonical suddenly decided to rewrite a tool that has been rock-solid (for the most part) for decades. The short answer: security. Rust, unlike C, is built with memory safety baked into its DNA . If you’ve ever stayed up late patching a vulnerability caused by things like buffer overflows or use-after-free bugs, you’ll appreciate what this means. Rust doesn’t let those mistakes happen in the first place—it’s like having a safety net you don’t even notice is there until something tries to go horribly wrong. This change isn’t about jumping on the “modern programming language” bandwagon. It’s a deliberate move to reducesecurity headaches across the board. Rust is smart. It scans for nasties at compile time—so by the time code is running on your system, the odds of low-level bugs being exploitable drop dramatically. And frankly, tools like sudo—which basically hold the keys to the kingdom for elevating permissions—can’t afford to be anything less than airtight. Will Anything Actually Change for You? Here’s the good news: if you already know how to use sudo, there’s nothing new to learn. The syntax? Exactly the same. Whether you’re enabling admin rights with a quick sudo apt update or doing something gnarly like a one-liner shell escape, the core functionality doesn’t change. This isn’t some massive shakeup that’ll force you to rewrite all your scripts or rethink your workflows. But, and this is important— sudo-rs isn’t aimed at being a 1:1 replacement. It’s taking a “less is more” approach. Some obscure features from the original sudo have been culled. Don’t panic just yet; Canonical’s keeping the legacy C-based sudo available in the archives for anyone who’s dependent on some niche functionality. If you’ve got custom systems using funky sudo configurations, you’ll want to test things out before you jump in headfirst. Security Features Admins Will Appreciate Let’s talk about the stuff sudo-rs brings to the table that might make life a little easier—or at least harder for attackers. First off, there’s the reduced attack surface. Rust’s memory safety features mean vectors like memory misuse, overflows, and dangling pointers are essentially squashed. For a tool that deals directly with privilege escalation, that’s huge. You don’t want something that lets attackers slip through cracks—it should slam the door in their faces. Then there’s improved NOEXEC support. This will help lock down shell escapes to prevent privilege escalation shenanigans. If you’ve dealt with attackers trying to spawn shells from tools they weren’t supposed to, this feature isyour friend. For anyone deploying AppArmor profiles, sudo-rs integrates like a champ. It’s better aligned with modern application confinement frameworks, which makes it ideal for locking down environments while keeping a closer lid on privileges. And here’s a nice touch for organizations that are slow to upgrade kernels—sudo-rs supports pre-Linux 5.9 kernels. That’s welcome news for those of us still clinging to older LTS versions like Ubuntu 20.04 for stability reasons. Things to Watch for I’ve got to be upfront: no transition is perfect. While sudo-rs looks solid on paper, there are still a few things that might trip folks up: Missing Features: Some less obvious functionality from the old sudo didn’t make the cut in sudo-rs. Stuff like sudoreplay (great for auditing command logs) or SELinux support isn’t here yet—and those could be deal-breakers for certain enterprise setups. If you rely on those, hold tight for updates. Testing Phase: Canonical’s made it clear they want feedback. This is where you come in. Testing sudo-rs in staging environments could help surface problems before the tool becomes mandatory in Ubuntu 26.04 LTS. Throw it on some non-critical systems and see how it behaves with your workflows. Frankly, this is one of those situations where the transition might seem invisible—but under the right circumstances, small incompatibilities could jump out when you least expect them (looking at you, 3 a.m. outages). The time to find those snags is before sudo-rs becomes the default. The Bigger Picture: Rust in Linux System Utilities As much as this is a technical shift, there’s something symbolic about Canonical putting its weight behind Rust. It’s not just sudo—it’s the beginning of broader Rust adoption in Linux systems programming. Admins, if you haven’t brushed up on Rust, this might be your nudge to at least learn the basics. You don’t need to become an expert overnight, but knowing your way around tools written in Rust(or debugging them when things go sideways) is going to be increasingly relevant. I wouldn’t be surprised if we started seeing other distros follow suit. Debian, Fedora, and the like could easily pick up on the trend for critical components. This isn’t limited to sudo—it’s possible that utilities across the stack will shift toward Rust where it makes sense. What Canonical’s Got Right Switching to sudo-rs might sound like a big scary deal, but Canonical’s doing a couple of things that make it less daunting for admins: Legacy Support: They’re not forcing anyone into the new version cold turkey. If sudo-rs isn’t a perfect fit for your environment yet, the old C-based sudo isn’t disappearing. Feedback Window: By targeting Ubuntu 26.04 LTS for sudo-rs adoption, Canonical is giving us plenty of time to test and tweak. LTS versions are long-term commitments; they’re not rushing this transition. Here’s the kicker, though: most admins probably won’t notice anything dramatically different during their day-to-day operations. This redesign is happening quietly—you won’t see blinking neon signs shouting, “Now in Rust!” It’s designed to be unobtrusive, which, when it comes to a tool like sudo, is exactly what you want. Stability over flashiness. Our Final Thoughts on This Exciting Transition The move to Rust-based sudo isn’t some headline-grabbing gimmick. It’s about hardening one of the most critical pieces of our systems against modern threats while keeping things as seamless as possible for humans like you and me. Take this chance to test sudo-rs—I’d suggest tossing it onto a few staging boxes running varied workloads. The sooner you uncover quirks or compatibility surprises, the smoother your eventual transition will be. And hey, maybe this signals the start of something bigger. Rust creeping deeper into the Linux ecosystem isn’t just a technical curiosity—it’s a shift that could reshape system programming standards for years tocome. As always, the best approach is to get your hands dirty and see where things land. . The shift to a Rust-based sudo in Ubuntu 25.10 marks a move towards modern coding practices, enhancing security and reliability while executing superuser commands. Rust sudo administration security Ubuntu. . Brittany Day
Jun 04, 2025
•
Vendors/Products
78
security advisoryUbuntucoreutilsUbuntu 25.10: Transition to Rust-based Coreutils for Enhanced Security
Canonical has shaken up the Ubuntu ecosystem, announcing a major step forward —or sideways, depending on your view—by replacing the venerable GNU Coreutils with Rust-based uutils , starting with Ubuntu 25.10. This isn't just a tweak to the operating system’s innards. It's a foundational shift with implications that stretch across compatibility, security, and administration. If you’re neck-deep in managing Ubuntu systems, you need to pay attention. Changes like these can ripple through your workflows, and the worst thing you can do is be caught off guard. So, let’s dig in. . Rust is the foundation for this new approach. If you’ve been following the growing enthusiasm around Rust over the last few years, you’ve surely heard about its promises: its type system and how it prevents entire categories of bugs, its built-in security features that address memory safety, and its practical approach to modernizing codebases. Canonical is betting big on these attributes, pushing the Ubuntu project closer to a future where its core utilities are safer, faster, and potentially more maintainable. But this isn’t just about overhauling the inner workings of Ubuntu for the sake of technical symmetry. It’s about how something as basic as ls , cp , or find can fundamentally shift the operating system’s security and stability—or, depending on how this plays out, create headaches for admins who rely on GNU Coreutils behaving exactly as they have for decades. System administrators and developers don’t deal with these foundational tools in abstract terms. They’re baked into your scripts, they’re predictable, they’re trusted. When one of them fails to perform as expected, your day gets a lot worse, fast. Let's take a closer look at the mechanics of this transition, the growing appeal of Rust, the controversy surrounding this transition, and how you can successfully navigate this change. The Mechanics of the Transition Here’s how Canonical is handling this: starting with Ubuntu25.10, the replacement Coreutils will be rolled out as Rust-based versions via a system utility called oxidizr . Think of oxidizr as a kind of bridge, or maybe a valve—it lets you test the waters without diving straight into them. With oxidizr installed, you’ll have the ability to replace GNU Coreutils on your system with the Rust-based versions while keeping the originals safely backed up . If it works, great. If it doesn’t, no harm done; you roll back. The process sounds slick enough—and it needs to be. Canonical has openly stated that they’re pushing the boundaries with this experiment. Administrators will be warned repeatedly to tread cautiously. Oxidizr, at least initially, is labeled as experimental software. “Experimental” isn’t a word that inspires confidence when managing production infrastructure, but that’s exactly why oxidizr allows you to flip the switch back. Canonical has built escape hatches into this rollout because they know there will be edge cases, unexpected behaviors, and outright bugs. Why Rust, and Why Now? The timing of this move is no accident. Over the last few years, Rust has gained traction in both developer and security circles for its ability to write safer, more predictable code. It’s not just trendy—it solves legitimate problems. Many security exploits stem from issues like buffer overflows and use-after-free vulnerabilities, things that Rust’s design actively prevents. By integrating Rust into one of the most popular Linux distributions, Canonical is leaning heavily into this security philosophy. There’s also the question of maintainability. GNU Coreutils works, and it has worked for decades, but its complexities sometimes discourage new contributors from jumping in. Rust offers something that feels more modern, approachable, and inherently safer to newcomers. Canonical hopes this will result in a steady flow of contributors who might not otherwise get involved with legacy C code. And an influx of new minds can only help, especiallywhen security vulnerabilities need patching quickly. For administrators, this shift has a few parallels with adopting Rust-based utilities like sudo-rs , which Canonical is also set to introduce. These tools aren’t completely rewriting the rules of command-line behavior. Instead, they aim for the same functionality—with better safeguards. Over time, you’ll likely see fewer reports of vulnerabilities linked to the utilities embedded into Ubuntu. That’s a big win for everyone, assuming it pans out as expected. What Security Looks Like in Practice Security isn’t just something that gets better in theory. It has to work in the weeds. One of Rust’s standout features is its resistance to memory-related vulnerabilities, which account for a huge chunk of reported security issues in software. These are the kinds of bugs you don’t see coming until something breaks open, whether it’s a buffer overflow or an invalid memory write. With Rust-based utilities, the goal is to make such vulnerabilities disappear outright. But replacing Coreutils means handling functionality in some key edge cases—places where these utilities aren’t just running in isolation but interacting with other layers of the operating system. Compatibility is one concern Canonical isn’t glossing over. Early testing has pointed to missing or incomplete support for features like SELinux labels. These aren’t exotic use cases. If you’re relying on SELinux to enforce critical security policies, you can’t tolerate gaps in support. Canonical’s response, so far, has been to acknowledge these shortcomings and push fixes upstream. For admins, the takeaway is simple: test everything. Early adopters are bound to find workflows where the Rust-based utilities fall short, fall over, or behave differently from their GNU counterparts. That’s your opportunity to report the issue, but it’s also your opportunity to know when you should stick with GNU for the time being. The oxidizr utility provides that fallback mechanism,but relying on it too heavily might mean you’re sailing into waters that aren’t ready yet. Controversy and Conversations A shift of this magnitude doesn’t come quietly. Among admins and developers, the move has sparked debate—some practical, some philosophical. On one side are those with plenty of enthusiasm for Rust. It’s not hard to find praise for Canonical’s willingness to modernize and take risks. Rust-based utilities might not match GNU’s maturity yet, but the long-term security benefits aren’t easy to ignore. For those who spend their days patching bugs and locking down vulnerabilities, this looks like a step in the right direction. On the other side, concerns abound. Some are skeptical about replacing utilities with decades of real-world testing behind them. Stability doesn’t come easy in tools like these, and introducing new code always carries risk. Compatibility concerns are being raised left and right. Scripts, monitoring tools, and automated deployments often assume the behavior of GNU Coreutils. Any deviation—however slight—can gum up the works. There’s also the broader philosophical concern of replacing GNU components, which are tied deeply to the history of Linux itself. Some critics argue that this shift represents a break with traditional Unix philosophies, trading reliability and compatibility for the promise of security. Others worry that Rust-based utilities, while safer from certain classes of bugs, might introduce new issues administrators haven’t yet learned to anticipate. Our Final Thoughts: Navigating the Future as an Ubuntu User Canonical hasn’t left users high and dry with this transition. Their experimental approach signals that they’re aware of the stakes. Oxidizr, for all its warnings and disclaimers, gives admins the tools to experiment without committing. What’s clear is that this isn’t just a technical change—it’s a cultural one. Canonical is asking Ubuntu users, contributors, and administrators to rethink theirexpectations of core utilities. They’re asking the community to trust that the benefits of a safer code will outweigh the pains of adaptation. And they’re betting that Rust’s best features—its memory safety, its performance, its ability to attract contributors—will carry this transition forward. For system administrators, the lesson is straightforward: don’t get caught flat-footed. You need to test these utilities, even if you’re planning to stick with GNU for now. Understand where the differences lie, what edge cases might trip up your workflows, and what scripts or tools might need to be tweaked. Stay close to the community discussion. Canonical has been transparent so far, and the feedback they receive will shape how quickly uutils and oxidizr mature. This change isn’t coming as a surprise—we’ve got time to prepare for it. But make no mistake: Ubuntu 25.10 will mark a turning point, and all signs point to this being just the beginning. Rust is carving out its place in the Linux world. Whether you’re excited or apprehensive, it’s happening. Stay ready. . Examine how Ubuntu's transition to Rust-driven Coreutils is transforming security, improving features, and shaping future administration.. Rust utilities, Ubuntu Coreutils, Canonical shift, system administration. . Brittany Day
May 08, 2025
•
Vendors/Products
78
fedoradebianubuntuIn-depth Security Comparisons: Debian, Fedora, and Ubuntu Distributions
As a Linux security admin, choosing the right distribution is a crucial decision that will immensely impact your administration workflow. Debian, Fedora, and Ubuntu are three popular Linux distros that offer unique security features and characteristics. Fedora is like a cutting-edge scientist, constantly innovating with built-in tools like SELinux and delivering rapid security updates. . On the other hand, Debian is the reliable guardian, known for its stability and extensive testing, albeit with slightly slower adoption of new technologies. Then there’s Ubuntu, the user-friendly diplomat, offering a balance between usability and security with features like AppArmor and timely, albeit less frequent, updates compared to Fedora. In this article, I'll dive into the nitty-gritty of these distributions' security landscapes. I'll explore how each handles default configurations, manages updates, and what kind of community support you can expect. I’ll also highlight some pain points — because no distribution is without flaws — and provide practical insights to help you decide which distro best fits your security needs. Whether you're an SELinux wizard, a Debian stability fan, or an AppArmor enthusiast, understanding these differences can make a notable difference in your day-to-day operations. An In-Depth Security Analysis of Debian Debian is a rock-solid choice for many Linux admins, primarily due to its stability and well-maintained security features. One thing that makes Debian stand out is its predictable and stable release cycle. Each stable release gets around five years of security updates, so you can count on your systems staying secure over time without any surprises. The Debian Security Team is on the ball, too. They issue security advisories and updates promptly, and their dedicated security repository ( security.debian.org ) ensures you can get these patches easily and quickly. Also, Debian's default installation is pretty lean and secure right off the bat. It avoids runningunnecessary services, which helps keep the attack surface small. And if you're looking to beef up security further, Debian supports AppArmor , which lets you confine applications to tight security policies. Debian’s participation in the Reproducible Builds project is a big plus, assuring that the binaries you're running are genuine and haven't been tampered with. Another thing I appreciate about Debian is its strong security community. These folks are passionate and extremely collaborative, consistently working on identifying and fixing vulnerabilities. And let's not forget the Debian Security Tracker, which keeps everything transparent—you can check the status of vulnerabilities and the rollout of patches anytime. However, no system is perfect. One gripe some admins have with Debian is its SELinux support. While it supports AppArmor, SELinux , which offers more granular control, isn’t as polished or user-friendly. This might be a sticking point if you come from a Fedora or CentOS background. Also, while Debian does a good job with security patches, it’s conservative. This means you might not get some updates as fast as you would on a rolling-release distro like Arch Linux. Kernel hardening is another area that could use a bit more love. Debian’s default kernel is secure but not as aggressively hardened as in some security-focused distributions like Qubes OS or Kali Linux . If you want those features, you’ll likely dive into manual configurations. Lastly, the commitment to stability sometimes means you're dealing with older versions of packages. This can be a double-edged sword; while you get well-tested software, you might miss out on newer security features found in the latest versions. Debian’s security framework offers an outstanding balance of stability and security, making it a dependable choice for many scenarios, especially on servers. But as with any distribution, knowing its strengths and weaknesses will help you maximize it for your specific use case. Fedora'sProactive Security Approach: Strengths & Challenges Fedora Linux stands out in the Linux ecosystem due to its solid focus on security. As a Linux admin, you'll appreciate that Fedora integrates cutting-edge technologies with a strong emphasis on keeping systems secure. One of its hallmark features is SELinux, which is baked right into the system to enforce strict access controls—imagine sleeping at night knowing that even if a service gets compromised, it's locked down tighter than Fort Knox! Plus, the Fedora team is on the ball with security patches and updates, pushing them out with a sense of urgency that keeps you ahead of potential threats. It’s also handy that Fedora comes with essential security tools, like firewalld , making it easy to hit the ground running. And let’s not underestimate the power of community; Fedora’s security community is teeming with experts whose contributions often improve not only Fedora but the entire Linux landscape. When setting up a new system, you’ll notice that Fedora promotes security best practices from the start, with default settings prioritizing the highest level of safety. On the flip side, some users find SELinux a bit of a beast to tame. Its complexity can be intimidating, especially for those just dipping their toes into Fedora's waters, sometimes leading them to disable it, precisely what you don't want. Also, given how up-to-the-minute everything is, all these frequent updates can be a bit resource-hungry, which might make you think twice if you're managing systems that aren't exactly brimming with hardware prowess. In essence, Fedora’s proactive security stance and robust community support make it a solid choice for any security-savvy admin. Still, it’s wise to brush up on your SELinux skills to make the most of Fedora's offerings. Ubuntu's Comprehensive Security Features: Benefits & Areas for Improvement Ubuntu is well-regarded for its strong security measures, making it a go-to Linux distribution for many users seekingrobust cybersecurity features. One of the main characteristics that stands out is its design philosophy, which prioritizes ease of use and accessibility, helping even those with a minimal technical background configure secure systems. Ubuntu provides regular security updates and patches faster than many other distributions. This proactive approach enables administrators to address vulnerabilities rapidly, reducing exposure to potential threats. Another unique aspect of Ubuntu is its default installation, which is configured with security in mind. By default, it includes a firewall called UFW (Uncomplicated Firewall) , making it easier to implement basic firewall settings without delving into complex configurations. Moreover, Ubuntu integrates with AppArmor, a security module that restricts the capabilities of programs to fortify your system against potential threats. The security community supporting Ubuntu is active and dedicated, frequently sharing best practices and guidelines for improving system security. Resources like Ubuntu Security Notices and Launchpad are vital for staying informed on recent threats and security patches. Ubuntu’s Security Team ensures that security vulnerabilities are closely monitored and promptly addressed. Despite these strong points, there are areas where Ubuntu could enhance its security offerings. For example, while AppArmor provides good protection, some users feel that the SELinux support isn’t as comprehensive as it could be, limiting users accustomed to the more granular policy controls found in SELinux. Although UFW simplifies firewall management, it does not offer the same depth of features as more advanced firewall solutions. Ubuntu's user-friendly security features, reliable update mechanisms, and supportive community make it a solid choice for many. However, there is always room for improvement, especially in broadening the capabilities of built-in security tools to match those in more specialized security distributions. Our FinalThoughts: Choosing the Right Linux Distribution for Optimal Security Choosing the right Linux distribution can significantly impact your security posture. Debian's focus on stability and extensive testing procedures makes it an excellent choice for those prioritizing a time-tested, reliable environment. Fedora's rapid update cycle and cutting-edge security features, such as SELinux, cater to those who need the latest advancements and are willing to manage a more dynamic system. With its balanced approach, Ubuntu provides an accessible yet secure platform, leveraging features like AppArmor to offer protection with ease of use. Your choice should reflect your specific security needs and operational priorities. Whether you prefer Debian's stability, Fedora's innovation, or Ubuntu's balanced approach, understanding what each distribution offers can help you make the right decision. With this knowledge, you can tailor your security strategy to match the unique characteristics of your chosen distro, ensuring robust protection for your systems. . Evaluate Linux distributions like Debian, Fedora, and Ubuntu by considering their unique security strengths and weaknesses to find the best fit for your needs. Debian Security, Fedora Features, Ubuntu Administration. . Brittany Day
Mar 26, 2025
•
Vendors/Products
83
malwarecyber attackssecurity implicationsUnderstanding DinodasRAT Linux Malware Threats and Defense Measures
A Linux version of the multi-platform backdoor malware called DinodasRAT has been spotted in cyberattacks across several countries. The malware, also known as XDealer, is a C++-based threat that can harvest sensitive data from compromised systems. . The prevalent and evasive malware can be attributed to China-nexus threat actors. This discovery raises significant security implications and emphasizes the importance of proactive measures for Linux administrators and infosec professionals. What Are the Security Implications of DinodasRAT Linux Malware? The emergence of a Linux variant of DinodasRAT is a development concern for security practitioners in the Linux community. Its targeted attacks on Red Hat-based distributions and Ubuntu Linux indicate the need for heightened vigilance in these environments. As Linux admins and system administrators, we must stay up-to-date with the latest threat intelligence and security advisories to protect our infrastructure from this evolving threat landscape. One intriguing aspect of this malware is DinodasRAT's persistence mechanism through SystemV or SystemD startup scripts. This technique enables the malware to establish a foothold on the compromised system, making it challenging to detect and mitigate. Linux admins and sysadmins must thoroughly review the startup scripts on their machines to ensure that this backdoor is not leveraging them. DinodasRAT also can perform various malicious activities, such as file operations, process enumeration, and shell command execution. This comprehensive feature set indicates that the malware operators have significant control over the compromised systems, posing a severe threat to data exfiltration and espionage. Infosec professionals should consider conducting thorough security assessments and penetration tests to identify potential vulnerabilities this malware may exploit. Moreover, DinodasRAT's utilization of the Tiny Encryption Algorithm (TEA) for encrypting command and control (C2) communicationshighlights the sophistication of this threat. This raises questions about how organizations can effectively monitor and detect such encrypted communications, especially in environments with many Linux servers. Investing in robust threat intelligence solutions and maintaining secure network monitoring practices becomes critical to identifying any malicious activity associated with DinodasRAT. The implications of DinodasRAT's presence in cyberattacks across multiple countries cannot be ignored. It prompts us to reevaluate our security strategies and consider potential long-term consequences. As security practitioners, we must question whether our current defenses are adequately equipped to withstand such targeted threats. This article reminds Linux admins, sysadmins, and infosec professionals to continuously enhance their knowledge and skills to safeguard their systems against evolving malware variants. Our Final Thoughts on DinodasRAT Linux Malware The discovery of the Linux version of DinodasRAT highlights the evolving nature of cyber threats and the importance of maintaining robust security measures. Linux admins, infosec professionals, and sysadmins must remain vigilant, update their defenses, and adopt proactive security practices to protect their infrastructure from this and similar malware variants. By leveraging threat intelligence, conducting regular security assessments, and implementing encryption monitoring techniques, we can counter the impact of DinodasRAT and mitigate its potential damage. . DynoesRAT represents significant threats for Unix environments, especially regarding information theft and ongoing presence methods.. DinodasRAT Linux, Backdoor Threats, Malware Security, Linux Admins, Cybersecurity Risk. . Dave Wreski
Mar 31, 2024
•
Hacks/Cracks
78
security advisorysystem upgradeadministrationUbuntu 14.04 LTS Extended Support Until April 2024 for Admins
There's good news for admins looking nervously at their aging Ubuntu boxes - a few more years of support is now on offer as Canonical brings 14.04 and 16.04 LTS into the 10-year fold. . Users still running on 14.04 LTS (Trusty Tahr), released back in April 2014 , now have until April 2024 (up from 2022) to make the move to something more recent. 16.04 LTS ( Xenial Xerus ), which dropped into Extended Security Maintenance (ESM) in April this year , has had this extended from April 2024 to April 2026. Ubuntu has been quietly updating its support and blog posts to reflect the change. The extension is a welcome one for enterprises, who might be reluctant to fiddle with that one server that has been plugging along happily for years without intervention, and should give administrators a little more breathing space. That is, assuming that somebody has coughed up for ESM, which requires an Ubuntu Advantage subscription (free for personal users or Ubuntu Community members, but otherwise requiring the spending of cold hard cash.) . Individuals utilizing the 16.04 LTS (Xenial Xerus), which debuted in April 2016, will have up until April 2026 to perform their upgrade.. Ubuntu Administration,System Support Extension,Upgrading Linux,LTS Management,Extended Support. . LinuxSecurity.com Team
Sep 22, 2021
•
Vendors/Products
77
security tooladministrationLinux serverDiscover UChecker: A Tool For Scanning Outdated Libraries In Linux
Security teams running Linux servers now have access to UChecker , a new tool offered as part of CloudLinux’s TuxCare security services that runs scans on Linux servers to detect outdated shared libraries on both disk and in memory. . UChecker works with all modern Linux distributions and has been licensed under the GNU General Public License, Version 2. According to ZDNet, UChecker tells security pros which application uses which vulnerable library and offers up the relevant process ID and process name. With this new information administrators can see which libraries they need to update. . LibAudit swiftly inspects Unix systems for obsolete packages, providing administrators essential patch details.. UChecker, library scanner, Linux security tool, outdated libraries, TuxCare. . LinuxSecurity.com Team
Jun 16, 2021
•
Server Security
210
security practicesuser managementadministrationWhy User Management Is Critical for Linux Security and Attacks
The rise in attacks on Linux in recent years is not due to problems with the Linux OS, but rather issues with individual accounts and poor administration. LinuxSecurity Founder Dave Wreski states: "Although it may be easy to blame the rise in attacks targeting Linux in recent years on security vulnerabilities in the operating system as a whole, this is simply not the truth. The majority of exploits on Linux systems can be attributed to misconfigured servers and poor administration." . Joe McManus, Director of Security at Canonical, said: "Linux and, particularly Ubuntu, are incredibly secure systems but, that being said, it is their popularity that makes them a target." Ian Thornton-Trump, a threat intelligence expert and the CISO at Cyjax, added: "From an economic and mission perspective, it makes sense for a threat actor to invest in open-source skills for flexibility and the ability to target the systems where the good stuff is happening." The link for this article located at Fudzilla is no longer available. . Grasping the impact of user behaviors on Linux security through the lens of professional analysis and practical experience.. Linux Security Insights, User Management Best Practices, Open Source Defense Techniques. . Brittany Day
Apr 21, 2020
•
Security Vulnerabilities
78
security advisoryvulnerabilitycritical patchMicrosoft: Critical Zero-Day Flaws Require Urgent Attention
Microsoft maintained the pressure on system administrators this month by releasing fixes for over 70 vulnerabilities in its products, two of which are classed as zero-day flaws. . The 15 updates released by Redmond cover 74 unique CVEs in Windows, Internet Explorer, Edge, Office, SharePoint and Exchange. Just like last month, two of them are being actively exploited in the wild and should be prioritized. The link for this article located at InfoSecurity is no longer available. . Apple has rolled out its latest updates tackling 52 security vulnerabilities, with three of them categorized as urgent zero-day threats that demand prompt action from IT professionals.. Windows Updates,ZERO-Day Flaws,Security Patches. . LinuxSecurity.com Team
Apr 10, 2019
•
Vendors/Products
Get the latest News and Insights
Get the latest Linux and open source security news straight to your inbox.
Community Poll
Should Linux servers automatically install security updates?
Trending News
Search Topics
Powered By
Linux Security - Your source for Top Linux News, Advisories, HOWTOs and Feature Releases
QUICK LINKS
subscribe to newsletters!
Like staying secure? So do we.
Sign up for updates, tips, and alerts!