Network Security
system security Linux network
system security Linux network The romanticized image of the digital nomad – a laptop on a sun-drenched balcony – rarely accounts for the actual friction of maintaining a professional development environment on the move. . The friction is amplified with Linux. We are looking for a setup that respects our kernel configurations, handles volatile network handovers, and maintains a strict security posture without the hand-holding of a consumer-grade OS – so, put simply, more than just a laptop and a sunny deck. The hardware is...
May 26, 2026
Server Securityopen-source Linux administration
open-source Linux administration Cron has existed in Unix and Linux environments for decades, handling backups, cleanup scripts, patching jobs, log rotation, monitoring tasks, and other maintenance work that administrators do not want to run manually. Most Linux servers rely on it constantly, which is exactly why attackers continue abusing it for persistence after a system has already been compromised. . Persistence through cron is not complicated. Attackers do not need a rootkit or advanced malware framework to maintain...
May 25, 2026
Vendors/Productssecurity breach linux
security breach linux A major internal repository breach at GitHub has exposed a critical and overlooked blind spot in Linux supply chain security. Kernel exploits, exposed SSH services, weak firewall rules, and vulnerable daemons dominated the Linux threat model for years, and in many environments, they still matter. But recent supply-chain incidents involving GitHub ecosystems, npm packages, and malicious developer tooling point somewhere else entirely: the developer workstation. . The breach matters because...
May 21, 2026
Security Trends access control multi-tenant
access control multi-tenant Linux administrators often face an ugly choice in the cloud: prioritize convenience and cost-efficiency by sharing infrastructure, or sacrifice those benefits for the sake of total isolation. Most modern Linux workloads don't live on their own private servers anymore. They live in shared environments like Kubernetes clusters, where multiple teams and services run side-by-side. It sounds efficient, and it usually is. . But cloud isolation isn't as ironclad as it looks on the diagram. If you...
May 21, 2026
Vendors/Productsincident response cloud security
incident response cloud security Managed Extended Detection and Response (MXDR) has become one of the most sought-after security services in the enterprise market — and with good reason. It promises the holy grail: broad visibility across endpoints, network, cloud, email, and identity, combined with the 24/7 human expertise most organizations simply cannot build in-house. . However, the rapid growth of the market has produced a wide range of providers whose capabilities vary considerably beneath the surface. Choosing the...
May 19, 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
What got you started with Linux?
Loading...
Explore Latest Linux Security news
We found 12 articles for you...
210
security advisorycriticalremote code executionGoogle Chrome: CVE-2025-6558 Critical Remote Code Execution Advisory
Let’s talk about CVE-2025-6558 —the latest zero-day vulnerability in Google Chrome. If you’re managing Linux systems or handling infosec at any level, you should care about this one. It’s actively being exploited, which means attackers aren’t waiting for you to patch—they’re already leveraging it to break into systems. . This particular flaw lives in the ANGLE (Almost Native Graphics Layer Engine) and GPU rendering components of Chrome. These systems are responsible for handling graphics processing. Now, when you’re dealing with something that sits this close to the metal in the browser, anything going wrong can open up big avenues for exploitation. With CVE-2025-6558, the issue boils down to incorrect validation of untrusted input in these components. Think of it as Chrome not double-checking its homework before rendering complex graphics or running scripts. Let's take a closer look at this bug, who it impacts, and measures you can take today to lock down your systems against exploits. Why Is CVE-2025-6558 Such A Big Deal? Here’s the thing about ANGLE and the GPU: they’re powerful tools, but vulnerabilities here can become a direct line for sandbox escapes, code execution, and privilege escalation. This isn’t hypothetical either—Google confirmed attackers are already exploiting this flaw in the wild. Imagine this: a malicious actor creates a crafted HTML page exploiting this validation weakness. Once someone visits the page in Chrome, their system could become open to the attacker. That’s not just script-kiddie-level stuff; it’s real-world exploitation that could compromise entire systems. What makes this even trickier is how sandboxing—one of Chrome’s biggest defenses—might be bypassed. If attackers are targeting rendering processes through graphics-heavy content, even something seemingly benign, such as an over-the-top web animation, could pack a payload. How Has Google Addressed This Zero-Day Flaw? Thankfully, Google rolled out an emergencypatch in the latest Stable Channel Update for Desktop (versions 138.0.7204.157 and .158). This patch directly tackles the input validation issue in the ANGLE and GPU components, closing off the weakest points. Google didn’t stop at bandaging the flaw. They’ve hardened Chrome using tools like AddressSanitizer and libFuzzer , both of which simulate exploit scenarios. These tools dig into edge-case bugs that attackers love to exploit. Whenever you see “fuzzing,” think of it as crashing the software in every imaginable way to find where it breaks, then fixing those breakpoints. That’s likely how Google zeroed in on this vulnerability. Practical Protection Measures for Security Pros If you’re running Chrome on Linux systems, now’s the time to act. Apply patches immediately. There’s no excuse to wait, especially since adversaries are already sliding through this flaw like it’s a revolving door. Look, it’s not just about clicking “update” once and forgetting about it. You need to verify that your systems are actually running the patched version. Quick tip: open Chrome and visit chrome://version . If the version isn’t 138.0.7204.157 (or higher), you’ve got work to do. Admins might want to think about temporarily disabling GPU acceleration for critical systems until everything is fully stabilized. While Chrome has done its job with the patch, history shows that vulnerabilities like these can sometimes spawn related issues. Reducing attack surfaces is never a bad move. Beyond Patching Patch management is the obvious answer, but don’t stop there: Automatic Updates Configure Linux systems to handle browser updates automatically. Yes, I get it—some admins dread the idea of anything auto-updating. But in cases like this, it could save your systems when the next zero-day shows up unannounced. Endpoint Monitoring Keep an eye on endpoints. Use tools like EDR to watch for sketchy Chrome behaviors. If suddenly Chrome is leveraging more resources than normalor reaching external IPs under weird circumstances, dig into it. Web Traffic Filtering Block risky or suspicious URLs at the DNS level to reduce the chances of accidental exploits. While it doesn’t fix the vulnerability, it can prevent users from stumbling into the wrong traps. Training and Awareness Let users know about the risks. No need for scary emails, but remind them to avoid downloading random scripts or visiting shady websites until browsers are confirmed safe. Our Final Thoughts on Proactively Addressing CVE-2025-6558 CVE-2025-6558 highlights a critical security challenge: browsers get hit hard because attackers know they’re ubiquitous. If you’re not patching systems now, you’re rolling the dice on this actively exploited vulnerability. The good news? It only takes a few steps to lock down your Linux environments and reduce exposure to attacks. So apply those patches, monitor endpoints, and keep your systems tight and clean. Security isn’t just about reacting—it’s about staying ahead of the curve. And as always, keep your eyes on LinuxSecurity advisories because this fight doesn’t end with one zero-day! . A critical flaw in Google Chrome's ANGLE impacts Linux systems; updates are essential to secure against attacks.. Google Chrome,Critical Flaw,CVE-2025-6558,Security Update. . Brittany Day
Jul 17, 2025
•
Security Vulnerabilities
79
input validationsecure codingsoftware integrityEssential 10 Secure Coding Practices Every Developer Should Follow
With the increasing number of breaches in security with respect to credit card, mobile etc it is becoming imperative that we do all that we can to safeguard our property. So is the case with software developers. . As cited on cio.com, here are 10 things they can do to keep their codes secure -1. Testing inputs rigorously - Attackers require a path into your machines, and the easiest path is via the doors your code opens. In the event that your software derives input from the Internet, you are likely to have something come past you. You must ensure to test the size and structure of the incoming data and never rely on the person on the other end of the Internet. The link for this article located at EFY Times is no longer available. . As cited on cio.com, here are 10 things they can do to keep their codes secure -1. Testing inputs ri. increasing, number, breaches, security, respect, credit, mobile. . LinuxSecurity.com Team
Nov 15, 2013
•
Security Projects
74
application securityinput validationcyber defenseExploring Whitelisting as an Underrated Security Technology
Last week we looked at security technology some readers consider overvalued. This week we're back to study the other side of the coin. Here are four techniques and related technologies several cited as underrated in today's security fight. Since one security pro's miracle tool is another's waste of budget, it's no surprise that a couple of the technologies panned last week are praised here.. Whitelisting Application security is something companies increasingly worry about, as the number of business and personal apps proliferate. Hackers are targeting everything from online banking apps to the gaming apps popular on such social networks as Facebook. Web Application Firewalls (WAFs) are among the technologies designed to reduce the risk. One of the more overlooked features of the technology is whitelisting -- the art of allowing only traffic known to be valid to pass through the gate; thus providing an external input validation shield over the application. Andy Willingham, senior security engineer at E-chx Inc. and founder of AndyITGuy Consulting, believes whitelisting and URL filtering are too quickly dismissed as too difficult. "Most people think that it's too hard to limit what people can run and where they can go," he said. "We've reached the point where we can't just let people do what they want. Too many preach that if we want to attract and retain good employees that we have to allow them to install programs and surf freely but until we get virtual environments to the point where everything is its own virtual session and can be 'cleared' at will or regularly, then we have to start locking down." Chris Young, a VP at ISM Inc., said the biggest setback for this technology has been inconsistency on the management side, but that this piece is improving. "We are at the point where this is no longer a problem and new programs can be added with minimal/no admin assistance in a secure and controlled manner," he said. "On the endpoint it should not be seen as a locking down of the system in that userswon't be able to have any freedom, but it provides admin/user education in the sense that it forces admins/users to check what they are downloading first to make sure it is a legit program and conforms to company policy." The link for this article located at CSO Online is no longer available. . Utilizing often-overlooked techniques like application whitelisting can significantly enhance cybersecurity measures by allowing only trusted apps to run, reducing risks and potential damage.. Underrated Security Technologies, Whitelisting, Application Security. . Alex
Mar 19, 2010
•
Network Security
77
security risksinput validationweb application securityAddressing Security Risks in PHP Command Execution Environments
As the Web continues its march towards becoming the de facto interface for the world's software applications, developers must find effective ways to not only communicate with server processes such as MySQL, but also other operating system tools such as a shell or Ruby script. In this tutorial, I'll show you how to securely execute a variety of system-based commands via a PHP script, demonstrating how to build web applications that can tightly integrate with both the operating system and third-party software.. Minding the Security Risks Hopefully, you understand how important it is to thoroughly validate all user input accepted through a web form; after all, if you neglect this task, your data could be stolen or damaged via a SQL injection attack, or your users could be spoofed via a cross-site scripting attack. The risks of not properly vetting operating system commands initiated through a PHP script are no less severe! With this in mind, before jumping into a few examples it's worth taking a moment to understand how this particular feature can pose a significant security risk to not only your web site, but also to the stability of the entire web server. The link for this article located at PHP Builder is no longer available. . Master the art of safely running system commands within PHP while addressing possible security vulnerabilities in web applications and ensuring server reliability.. PHP Security, System Command, Input Validation, Web App Security. . LinuxSecurity.com Team
Jan 29, 2010
•
Server Security
83
XSSweb applicationsecurity flawPentagon Website XSS Attack: Input Validation Issues Unresolved
A Romanian hacker has posted a proof-of-concept attack exploiting vulnerabilities on the Pentagon's public Website that were first exposed several months ago and remain unfixed. The hacker, who goes by Ne0h, demonstrated input validation errors in the site's Web application that allow an attacker to wage a cross-site scripting (XSS) attack.. The XSS vulnerability had been previously disclosed by at least two other researchers several months ago -- and Ne0h's findings show the bug is still on the site. The site, which is run by the Office of the Assistant Secretary of Defense for Public Affairs, is basically a tourist site for the Pentagon and doesn't appear to house any sensitive data. But a security researcher who studied the Ne0h's work says the Pentagon Website could be used to redirect users to a malicious site posing as the Pentagon site. Daniel Kennedy, partner with Praetorian Security Group, says the session ID appears to be a tracking cookie, and JavaScript can be injected into the page itself to redirect a user to another site, for instance. "Since I can pass that page a reference to an external JavaScript, I can do most anything I can do in JavaScript," says Kennedy, who blogged about the find yesterday. "That includes basic stuff, like crafting a URL to send to users that appears to be from the Pentagon, but actually redirects to 'evil.org,'" for example, he says. The link for this article located at Dark Reading is no longer available. . A Russian cybercriminal reveals unpatched SQL vulnerabilities on a governmental agency's portal, endangering sensitive user data and potential identity theft.. XSS Exploit, Pentagon Security, Input Validation Flaw, Web Application Security. . LinuxSecurity.com Team
Dec 09, 2009
•
Hacks/Cracks
83
security advisoryXSSweb applicationTwitter Security Advisory: XSS Risk For Account Takeover
A newly exposed cross-site scripting (XSS) vulnerability in Twitter lets an attacker wrest control of a victim's account merely by sending him or her a tweet. U.K. researcher James Slater reported the serious flaw earlier this week, and now says Twitter's fix in response to his disclosure doesn't actually fix the problem. . "It seems they've made a pretty amateurish attempt to fix the issue, completely missing the massive problem staring them in the face," Slater said in his blog. The attack basically exploits an input validation weakness in a field of the form used for adding third-party Twitter clients, such as TweetDeck and Twitterific. The form doesn't fully vet what can go in that box, Slater said, so an attacker can put JavaScript tags there as well as raw HTML code, for instance. "Whatever I type in that box will appear at the end of my tweets," he blogged in a follow-up post. "Anyone who sees that tweet will then be viewing that code." The link for this article located at Dark Reading is no longer available. . A critical XSS vulnerability on Twitter permits cybercriminals to hijack user accounts through malicious tweets. Learn further about this security issue.. Twitter Exploit,XSS Attack,Account Security Risk. . LinuxSecurity.com Team
Aug 28, 2009
•
Hacks/Cracks
74
security practicesweb applicationinput validationKey Security Measures for Web Application Input Validation
In this installment, I will cite an example of automated email code designed for another purpose. Nonetheless, I see it is a critical step to confirm the validity of the form's input. Moreover, unless and until I have received the expected human confirmation, that input is left in limbo [1.]. This is another means to prevent spurious, but uncaught data inputs. Thus, this limited human energy expenditure is a high return investment. This article looks at the important security practice of web application input validation. Every time you take input from your web application check needs to be executed before your software does anything to that data. Do you have any tips for checking your user's input data for malicious data? . The link for this article located at lxer.com is no longer available. . Implementing essential validation practices for user input is crucial for web application security, shielding against malicious data effectively. Web App Input Validation, Security Measures, Protecting User Data. . Bill Locke
Jul 01, 2008
•
Network Security
74
data securityweb applicationsecurity strategiesEffective Data Protection Through Input Validation Techniques
My implicit presumption in this series is that break ins are unplanned, opportunistic occurrences. Break in attempts are triggered by encountering an input form. As I mentioned previously, do not give information away needlessly. Moreover, I strongly suggest you consider becoming passively aggressive by making your presentation of the form and its expected input somewhat unpredictable. Moreover, I advise turning your data input into a simple waste of time and effort for those not trained to use the entry way. The intent is to encourage those seeking easy break in opportunities to turn their sights on other targets. This article looks at the problem of how Web Application should validate the data they receive from the end-user. Do you validate your data from the Internet?. . Implementing strong input validation and a defensive design is vital for web data security. Here are key strategies to bolster these practices effectively. Data Security, Web Application Security, Input Validation Strategies. . Bill Locke
Jun 05, 2008
•
Network Security
Get the latest News and Insights
Get the latest Linux and open source security news straight to your inbox.
Community Poll
What got you started with Linux?
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!
Explore top 10 tips to secure your open-source projects now. Read More