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 6 articles for you...
210
security advisoryuser protectionlinux securityChrome 131: Emergency Update for High-Risk Vulnerabilities in Linux
Google recently unveiled a critical security update to their popular web browser, Google Chrome, addressing over a dozen significant security vulnerabilities. Chrome version 131 is now available in stable channels for Windows, Mac, Linux, and Android, and users should update promptly so their systems remain secure. . In this article, we explore these recent Chrome vulnerabilities, their impact, and how users can protect themselves. In addition, we offer mitigation advice to Linux admins looking to protect themselves from future Chrome bugs. Understanding These Vulnerabilities & Their Impact Chrome 131 includes several security fixes aimed at improving users' system security. Below is an overview of the vulnerabilities recently found and fixed in Chrome: CVE-2024-11110 : Inappropriate Implementation in Blink Severity: High Reported by: Vsevolod Kokorin (Slonser) of Solidlab Reported on: 2024-10-14 Description: This issue concerns an inappropriate implementation in Blink, Chrome's browser engine. The vulnerability could allow attackers to exploit the system, potentially leading to unauthorized access or manipulation of the user's data. CVE-2024-11111 : Inappropriate Implementation in Autofill Severity: Medium Reported by: Narendra Bhati, Suma Soft Pvt. Ltd - Pune (India) Reported on: 2024-08-18 Description: This vulnerability involves Autofill functionalities, which could result in sensitive information being incorrectly supplied or leaked. CVE-2024-11112 : Use-After-Free in Media Severity: Medium Reported by: Nan Wang and Zhenghang Xiao of 360 Vulnerability Research Institute Reported on: 2024-07-23 Description: This use-after-free vulnerability affects Chrome's media handling, which could allow attackers to execute arbitrary code or cause a denial of service. CVE-2024-11113 : Use-After-Free in Accessibility Severity: Medium Reported by: Weipeng Jiang of VRI Reported on: 2024-08-16 Description: This issue involves the Accessibilitycomponent. Similar to the media vulnerability, it could enable arbitrary code execution or crash the application. CVE-2024-11114 : Inappropriate Implementation in Views Severity: Medium Reported by: Micky Reported on: 2024-10-02 Description: This vulnerability pertains to the Views feature, leading to potential unauthorized interactions or data manipulation. CVE-2024-11115 : Insufficient Policy Enforcement in Navigation Severity: Medium Reported by: mastersplinter Reported on: 2024-10-07 Description: Issues in navigation policy enforcement could result in unauthorized navigation actions that bypass intended security controls. CVE-2024-11116 : Inappropriate Implementation in Paint Severity: Medium Reported by: Thomas Orlita Reported on: 2023-11-14 Description: Vulnerabilities in the Paint feature can lead to improper rendering or manipulation of user content. CVE-2024-11117 : Inappropriate Implementation in FileSystem Severity: Low Reported by: Ameen Basha M K Reported on: 2023-01-06 Description: This issue affects the FileSystem API and could expose file-handling operations to unauthorized actions. CVE-2024-11395 : Type Confusion Issue in V8 Severity: High Reported by: Anonymous Reported on: 2024-11-05 Description: A Type Confusion issue in V8, Chrome’s JavaScript engine, allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. CVE-2024-12053: Type Confusion Issue in V8 Severity: High Reported by: Anonymous Reported on: 2024-12-03 Description: A Type Confusion Bug in V8 in Google Chrome before 131.0.6778.108 allowed a remote attacker to exploit object corruption via a crafted HTML page. Additional issues were identified and resolved through Google’s internal security work, leveraging tools like AddressSanitizer, MemorySanitizer, and other fuzzing initiatives . These preventive measures are essential in identifying and addressing vulnerabilities before exploitation. At-Risk Chrome Versions Google Chrome versions before 131.0.6778.108/.109 for Linux are vulnerable, so users on these platforms must update their browsers immediately to reduce potential threats. Consistently updating Chrome ensures you benefit from the latest security patches and feature enhancements. How Can I Update Google Chrome on Linux? Updating Google Chrome is crucial because it ensures you have the latest security patches, protecting you from potential threats like malware and phishing attacks while also providing access to new features and performance improvements, making your browsing experience safer and more efficient; essentially, keeping your Chrome browser up-to-date is vital for optimal security and functionality. Updating Google Chrome on your Linux system using a package manager is straightforward and necessary for us security-conscious admins! The LinuxSecurity team has put together a comprehensive guide on keeping your distro updated that explains the steps you can follow to update Chrome to the latest version for your distro. You can also verify that you're using the latest version of Chrome by following a few simple steps. After performing the update using a package manager, open Google Chrome and click on the three-dot menu in the upper-right corner. Then, navigate to Help > About Google Chrome . This will display the current version of Chrome installed on your system. Compare this with the latest version. If the versions match, your update was successful. Additionally, you can use commands like google-chrome --version on the command line to check the installed version directly. Ensure the version number reflected here matches the latest release. It is essential to stay informed and proactive about maintaining your system's security and functionality, and LinuxSecurity's Feature articles and newsletters are an excellent way to do so. Practical Mitigation Advice for Linux Administrators Linux admins can implement additional safeguards tofortify their systems against browser-related vulnerabilities. While staying current with Chrome updates is the primary solution, the measures below will further protect your systems: Regular Updates Implement a policy of regular system updates, including browser updates and updates to your Linux distro(s). Also, admins should Use package managers like APT (Debian-based systems) or YUM (RedHat-based systems) to keep software up-to-date automatically. Restrictive Permissions Limit the permissions of browser processes using AppArmor or SELinux policies to limit what Chrome can access on the system and minimize potential impact from compromised browsers. Sandboxing for Isolation Use tools like Firejail to run Chrome in an isolated sandbox environment, which adds another layer of protection and limits an attacker's reach even if Chrome becomes compromised. Restrict Network Activity Apply network-level protections to filter and monitor traffic, restricting connections to known safe locations while looking for suspicious activity. Security Hardening Apply general hardening policies across all systems. Disable unnecessary services, limit user permissions and enforce strong password policies. Regular Security Audits and Penetration Testing Conduct regular security audits and penetration testing to detect vulnerabilities in system configuration and software before hackers can exploit them. Our Final Thoughts on Securing Against These Recent Chrome Bugs Linux administrators can significantly mitigate browser vulnerability risks and maintain robust system security by taking proactive steps and implementing these mitigation measures. By understanding the nature of these vulnerabilities, swiftly updating Chrome, and applying recommended mitigation strategies, users and administrators can better protect their systems from potential threats and enjoy a safer browsing experience. . Investigate the newest Chrome security flaws, their consequences, and the best methods tosafeguard your systems efficiently.. Chrome Update, System Security, Browser Vulnerabilities, User Protection. . Brittany Day
Dec 04, 2024
•
Security Vulnerabilities
210
security advisoryremote code executionthreat mitigationGhostscript 10.03.0 Security Advisory: Critical RCE Threat Overview
Recently, open-source security was rocked by the discovery of an alarming Remote Code Execution (RCE) vulnerability within the Ghostscript document conversion toolkit — CVE-2024729510 . Ghostscript is the engine behind many other Linux applications, making Ghostscript flaws like this one especially severe and impactful. . This particular vulnerability can compromise countless Linux systems worldwide. To help you understand and protect against this threat, I'll walk you through how this flaw works, its impact, and practical strategies for mitigating your risk. What Is CVE-2024-29510? CVE-2024-29510 is an RCE vulnerability that affects all versions of Ghostscript up to 10.03.0. Ghostscript is a crucial part of modern computing - rendering files for LibreOffice, GIMP, Inkscape, and Scribus while powering printing services via CUPS. Ghostscript software contains a flaw that allows an attacker, using specially crafted Postscript files, to bypass safety checks provided by its dSAFER sandbox, a safety measure designed to stop unsafe operations when converting documents. Although enabled by default to prevent security breaches, attackers can alter strings related to uni print device arguments after the sandbox has started, execute commands without permission, and perform file I/O operations without security monitoring. What Is the Impact of This RCE Bug? Exploiting this flaw could allow attackers to execute arbitrary commands, access sensitive files, and potentially gain control of affected systems. As a result, the efficacy of Ghostscript as a security measure is severely undermined, raising severe concerns for web applications or services using Ghostscript in document conversion or preview applications or previews indirectly or directly. Can you imagine converting your Postscript documents into PDFs and getting hacked? Attackers are exploiting this bug in the wild by masking malicious Postscript files as harmless-appearing JPGs and passing them along to be processed by Ghostscript'svulnerable component. This allows attackers to gain shell access and subsequently compromise your entire system. You can check if your systems are vulnerable to this flaw by running this Postscript file with the command: ghostscript -q -dNODISPLAY -dBATCH CVE-2024-29510_testkit.ps Brief History of Ghostscript RCE Vulnerabilities Ghostscript has been vulnerable to Remote Code Execution attacks in the past. CVE-2023-36664 , for instance, was identified and patched, also concerning handling maliciously crafted files. Although efforts were undertaken to eliminate security holes posed by these RCE flaws, CVE-2024-29510 indicates the continuing struggle to ensure robust protection measures remain in place. Practical Mitigation Measures for Linux Admins To combat the imminent risk presented by CVE-2024-29510, system administrators and users alike should immediately take various proactive and reactive steps. Ghostscript released an update, version 10.03.1, that resolves CVE-2024-29510 and must be applied as soon as possible to mitigate risk. Depending on your distribution, additional patched versions may also be made available and must be swiftly applied as quickly as possible. Debian, Fedora, and Ubuntu have released security patch updates to mitigate this flaw. Patch Application: If upgrading is not feasible due to compatibility or other considerations, apply any available patches from your Linux distribution or software vendor to close any existing security gaps. Vulnerability Scanning: Scan your systems to identify whether they are susceptible to the CVE-2024-29510 vulnerability. This step is essential to understanding your exposure. Isolation of Services: Where possible, isolate services reliant upon Ghostscript from external networks and non-essential internal systems to limit its spread in an attack scenario. Usage Audit: Conduct an audit to identify where Ghostscript is utilized within your organization and evaluate if its presence is necessary in eachcontext or if other options should be explored if its associated risk proves too great. Implement Regular Monitoring and Logging: For applications using Ghostscript, regular monitoring and logging practices should be used to detect abnormal behaviors that might indicate exploitation attempts. Incident Response: Craft an incident response plan specific to any possible Ghostscript-related breaches, as quick containment and remediation efforts can help lessen the impact of successful exploit attempts. Security Awareness: Inform end-users about the risks of opening documents from untrustworthy sources and provide them with guidelines on recognizing any possible phishing attempts or malware-infected files. Ghostscript released an update, version 10.03.1, that resolves CVE-2024-29510 and must be applied as soon as possible to mitigate risk. Depending on your distribution, additional patched versions may also be made available and must be swiftly applied as quickly as possible. Our Final Thoughts on Addressing This Ghostscript RCE Flaw The discovery of CVE-2024-29510 in Ghostscript underscores the ongoing challenge of software security and the necessity of heightened vigilance. While immediate responses include patching affected systems, long-term solutions include regular security audits, rapid patch management, and building a culture of safety within all operational practices. Taking these proactive steps will allow administrators to safeguard their infrastructure against future security threats such as this latest Ghostscript vulnerability as well. . A severe RCE vulnerability in Ghostscript endangers numerous Linux platforms; discover ways to safeguard your systems.. Ghostscript RCE Threat, Linux Admin Mitigation, Remote Code Risks. . Anthony Pell
Aug 14, 2024
•
Security Vulnerabilities
210
security advisorysecurity issueRed HatZombieland v2 Intel Bug: Ongoing Security Challenges for Linux Systems
Have you heard about the latest Intel CPU bug, Zombieland v2? Learn more about this security vulnerability and what Red Hat and other Linux vendors are doing about it in an informative ZDNet article: . Here's the bad news: We're going to keep seeing fundamental Intel CPU security holes popping open until every last one of the current generations of these chips is in landfills. Zombieland v2 is only the latest of a line of problems, which go back to Meltdown and Spectre . The "good" news is for now Intel and the operating system companies are staying ahead of hackers. Here's what Linux and Red Hat are doing about the latest nastiness. First, Zombieland v2 isn't just a worry for people using older Intel processors. No, this shambler of a security hole can also be used against all recent Intel processors, including the latest and greatest Cascade Lake . The link for this article located at ZDNet is no longer available. . Intel processors will likely keep revealing vulnerabilities; discover how companies are tackling the Zombieland v2 risk in Linux systems.. Intel CPU Vulnerabilities, Zombieland v2 Security, Red Hat Response, Technical Security Issues. . Brittany Day
Nov 14, 2019
•
Security Vulnerabilities
79
security researchmemory exploitsystem vulnerabilityNew Memory Exploit Elevates Linux User Rights Using DDR3 System Flaw
In one of more impressive hacks in recent memory, researchers have devised an attack that exploits physical weaknesses in certain types of DDR memory chips to elevate the system rights of untrusted users of Intel-compatible PCs running Linux.. The technique, outlined in a blog post published Monday by Google's Project Zero security initiative, works by reversing individual bits of data stored in DDR3 chip modules known as DIMMs. Last year, scientists proved that such "bit flipping" could be accomplished by repeatedly accessing small regions of memory, a feat that. Discover a fresh vulnerability in memory that permits user privilege escalation on Linux systems through exploits in DDR memory architecture.. Linux Memory Exploit, DDR3 Vulnerability, User Rights Elevation. . LinuxSecurity.com Team
Mar 10, 2015
•
Security Projects
83
security advisorycritical severitysystem vulnerabilitySupermicro: Critical Advisory On Admin Password Exposure In BMC
An alarming number of servers containing motherboards manufactured by Supermicro continue to expose administrator passwords despite the release of an update that patches the critical vulnerability, an advisory published Thursday warned.. The threat resides in the baseboard management controller (BMC), a motherboard component that allows administrators to monitor the physical status of large fleets of servers, including their temperatures, disk and memory performance, and fan speeds. Unpatched BMCs in Supermicro motherboards contain a binary file that stores remote login passwords in clear text. Vulnerable systems can be detected by performing an Internet scan on port 49152. A recent query on the Shodan search engine indicated there are 31,964 machines still vulnerable, a number that may not include many virtual machines used in shared hosting environments.. Unsecured Supermicro BMCs reveal admin credentials, jeopardizing numerous servers. Discover the implications of this critical vulnerability.. Supermicro Servers, Admin Passwords, BMC Vulnerability. . LinuxSecurity.com Team
Jun 23, 2014
•
Hacks/Cracks
74
network securitysecurity toolsmalware techniquesExploring HP Active Countermeasures’ Wormlike Techniques for Security
Opinion: No, it's not a worm, but HP's Active Countermeasures uses wormlike techniques to find and secure vulnerable systems. Although we shouldn't be afraid, it needs to be used judiciously. . . .. Opinion: No, it's not a worm, but HP's Active Countermeasures uses wormlike techniques to find and secure vulnerable systems. Although we shouldn't be afraid, it needs to be used judiciously. Worms and other malware employ a variety of techniques to find new systems to attack. Many of them scan the network for systems containing specific, remotely exploitable vulnerabilities. Some of the fastest and most successful worms, such as Slammer and Code Red, worked this way. The link for this article located at eWeek is no longer available. . Opinion: No, it's not a worm, but HP's Active Countermeasures uses wormlike techniques to find and s. opinion, active, countermeasures, wormlike, techniques. . Anthony Pell
Aug 27, 2004
•
Network Security
78
security advisoryencryptionthreatSignificant SSL Threat: Password Flaws Found by Researchers
The most commonly used security system to protect passwords over the internet has been cracked by researchers at one of Switzerland's top technology universities. A team at the Federal Institute for Technology in Lausanne said they had been able to . . . . The most commonly used security system to protect passwords over the internet has been cracked by researchers at one of Switzerland's top technology universities. A team at the Federal Institute for Technology in Lausanne said they had been able to decipher a password in less than an hour. "It is the first time we have noticed a security problem in the SSL protocol itself and not in how we use it or how we implement it," Professor Serge Vaudenay, director of the institute's security and cryptography lab, told the BBC. But the researchers say the loophole does not apply to credit card transactions, as banks and e-commerce sites use a different type of SSL (Secure Sockets Layer) technology. . The most commonly used security system to protect passwords over the internet has been cracked by re. commonly, security, system, protect, passwords, internet, cracked. . LinuxSecurity.com Team
Feb 20, 2003
•
Vendors/Products
67
encryptioninformation securitycryptographyExploring Cryptography Challenges with Paul Kocher on Security Issues
In 1995, Paul Kocher caught the attention of information-security experts when he unveiled a method for cracking a handful of commonly used computer codes by timing how long it took for computers to process requests using those code algorithims. Today, Kocher . . . . In 1995, Paul Kocher caught the attention of information-security experts when he unveiled a method for cracking a handful of commonly used computer codes by timing how long it took for computers to process requests using those code algorithims. Today, Kocher remains a prominent voice in the cryptography field. As head of Cryptography Research, he and his small band of San Francisco-based cryptographers are paid by banks and credit-card companies to "hack" their products in hopes of uncovering system vulnerabilities. Far from being an unqualified believer in cryptography, however, Kocher is deeply concerned. What worries him is that the tried and true methods, which rely on increased computing power to crack codes, will fall behind in their capacity to solve information-security problems. I recently spoke with Kocher about encryption's looming challenges. The link for this article located at BusinessWeek is no longer available. . In 1995, Paul Kocher caught the attention of information-security experts when he unveiled a method . kocher, caught, attention, information-security, experts, unveiled, method. . LinuxSecurity.com Team
Sep 19, 2002
•
Cryptography
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!