Explore top 10 tips to secure your open-source projects now. Read More

×
Alerts This Week
Warning Icon 1 526
Alerts This Week
Warning Icon 1 526

Stay Ahead With Linux Security News

Filter%20icon Refine news
X Clear Filters
X Clear Filters
View More

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Community Poll

Is continuous patching actually viable?

No answer selected. Please try again.
Please select either existing option or enter your own, however not both.
Please select minimum {0} answer(s).
Please select maximum {0} answer(s).
/main-polls/156-is-continuous-patching-actually-viable?task=poll.vote&format=json
156
radio
0
[{"id":503,"title":"Delayed updates invite catastrophic breaches.","votes":1,"type":"x","order":1,"pct":50,"resources":[]},{"id":504,"title":"Automated fixes break production environments.","votes":1,"type":"x","order":2,"pct":50,"resources":[]},{"id":505,"title":"Manual approvals cannot keep pace.","votes":0,"type":"x","order":3,"pct":0,"resources":[]}] ["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"] ["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"] 350
bottom 200
Loading...

Explore Latest Linux Security news

We found 14 articles for you...
77

Windows XP Important UPnP Remote Access Security Risk 2001-0011

The latest Microsoft bug is a doozy. Why do these things keep cropping up? The federal government and technology industry want you to believe the threats to our networks are external, not internal, where someone must be held accountable when things go wrong. Thus, we hear the rhetoric about cyberterrorists, hackers, and the so-called 'Digital Pearl Harbor' - things you can't easily point fingers at and hold someone accountable for when bad things happen.. . . . The latest Microsoft bug is a doozy. Why do these things keep cropping up? The federal government and technology industry want you to believe the threats to our networks are external, not internal, where someone must be held accountable when things go wrong. Thus, we hear the rhetoric about cyberterrorists, hackers, and the so-called 'Digital Pearl Harbor' - things you can't easily point fingers at and hold someone accountable for when bad things happen. Richard Forno 20 December 2001: Essay #2001-15 This email address is being protected from spambots. You need JavaScript enabled to view it. (c) 2001 by Author. Permission is granted to quote, reprint or redistribute provided the text is not altered, and appropriate credit is given. Summary: The latest Microsoft bug is a doozy. Why do these things keep cropping up? Reader feedback is here. This gives "Plug and Pray" a whole new meaning... Plug your XP box to the Internet and pray the hackers don't find it. (Slashdot) "The only secure Microsoft software is what's still shrink-wrapped in their warehouse..." (Forno) By now, people know that I'm not the world's greatest Microsoft fan. Truth be told, I'm not completely biased against the company, and will even acknowledge that it has - at various points - produced some decent products. I also don't 'bash' Microsoft because it's the 'in' thing to do these days, but because there are serious problems with the software company's products and services that they continue to ignore. In fact, some would argue, they just don't get it. Such observations, therefore, must be voiced. The federalgovernment and technology industry want you to believe the threats to our networks are external, not internal, where someone must be held accountable when things go wrong. Thus, we hear the rhetoric about cyberterrorists, hackers, and the so-called 'Digital Pearl Harbor' - things you can't easily point fingers at and hold someone accountable for when bad things happen. The White House would be wise to look at our nation's own self-induced vulnerabilities before rushing to spin up a sinister external threat; absent the rich target of opportunity presented by nearly all Microsoft products, hackers, crackers, and electronic evildoers would have a much harder time causing mainstream mischief every other week. Windows XP was promoted by Microsoft as perhaps the ultimate and most secured Windows operating system the firm had ever created, and one of its key features was increased security from electronic evildoers like hackers, crackers, and so-called cyberterrorists. In fact, in a recent interviewwith E-Week, Microsoft Vice President Jim Allchin said that Windows XP is "...dramatically more secure than Windows 2000 or any of the prior systems." Released on October 25, it was to be the default operating system on all new personal computers sold, and its release was timed to coincide with new PC sales for the 2001 holiday season. Unfortunately, Windows XP doesn't protect you from Microsoft , an entity some argue is more dangerous than any cyberterrorist or hacker gang. It turns out that the Windows XP ships with a new feature called Universal Plug and Play (UPnP) enabled (turned on) by default - thus allowing UPnP devices to locate each other on a local network, so that your home computer can talk to your refrigerator can talk to your toaster can talk to your stereo can send messages to your PDA, and so forth. However, as a result of this oversight, someone could remotely use this feature to exploit, control, or disrupt a system from remote locations around the world. As if computer exploits aren't badenough, you'll soon have to worry about someone turning off your freezer and spoiling your holiday leftovers.... Note this is not to be confused with the Windows Remote Assistance feature - promoted as one of the major benefits of using Windows XP, yet functioning in essentially the same way as the UPnP exploit. (One wonders how quickly the Remote Assistance feature will be exploited in the future as well.) Marc Maiffret, the talented, blue-haired 'Chief Hacking Officer' of Eeye Security, demonstrated the UPnP exploit to a shocked group of reporters yesterday. As a result, media and security experts are calling this "The Mother of All Exploits" for Windows XP, scrambling to inform the public about the importance of downloading and installing the fix for this problem - a security problem not caused by a hacker or cracker, but developed and implemented exclusively by Microsoft for your computing convenience and to enhance your user experience as a 'feature' of the product. According to an AP story by Ted Bridis, Microsoft Security Manager Scott Culp, called this latest vulnerability the "the first network-based, remote compromise that I'm aware of for Windows desktop systems" and a "very serious vulnerability." I guess it's all in how you define "compromise." How very Clintonian. Although repeatedly interviewed by the media reporting on Microsoft-based security events over the years, Culp apparently doesn't consider any of the following Microsoft-centric security exploits as "network-based, remote compromises" for "Windows desktop systems" either - the series of Back Orifice programs from the always-amusing Cult of the Dead Cow (CDC) to e-mail worms, trojans, and viruses (think BadTrans) that can transmit sensitive information from systems they infect. Did Culp miss a few days of class here and there and forget to read up on SECHOLE.EXE (July 1998), the assorted Internet Explorer cross-frame scripting exploits (September 1998) or the mid-2000 ability to remotely exploit a Windows desktop through abuffer overflow found in the Clip Art feature of Microsoft Office? And what about Windows File and Print Sharing vulnerabilities from back in 1995? How about the seemingly-endless number of buffer overflow exploits (think CodeRed, Lion, and Nimda) that plague Microsoft Internet Information Server (IIS) - granted, IIS isn't made for "Windows desktops" but it deserves mention given the nearly-identical software code in Microsoft's desktop and server products. So how exactly does Microsoft classify these other types of network-centric exploits? As nuisances but the price of doing business in the wired world? When will it end? And what to do about this latest security problem originating in Redmond? Microsoft, as the world's largest purveyor of PC software, with an established monopoly status, needs to do the responsible thing. Rather than continue to preach security as a marketing tool for its .NET venture, an avenue for business development with new proprietary 'standards' and fee-based, censored security 'partnerships' or review its reactive measures , it should get back to the basics and look within for the solution to its internal problems that usually evolve into the world's problems . Simply put, Microsoft needs to review its software code line-by-line and clean it up. Years of service packing, patching, re-patching, updating, critical updating, and hotfixing Windows products have made them dirty and prone to breaking, as we see every few months. Better yet, Microsoft needs to revisit the basic design of Windows - namely, removing the shared code between applications and the underlying Windows operating system (like the pervasiveness of the Web-enabled Internet Explorer across each Windows application and system.) Like a car, it's time to bring the Windows code into the shop for a major tune-up. Actually, a worldwide recall might in order. In addition, Microsoft must not ensure its products work well together, but also conduct much more aggressive 'abuse testing' of its software (e.g., XP)before it gets released to the Real World. Such testing should be done by independent third parties and conducted in a transparent, public manner to preclude any claims of bias in the results of such testing. In general, Microsoft should conduct what the rest of the computing community considers a real "beta test" - namely, making sure that a supposedly finished application works as intended, using experienced users to test the functionality, durability, and security of the product in a real-world, real-use, take-no-prisoners environment.....not use its much bally-hooed 'beta test' periods as the opportunity to market advance copies of their products, many of which never seem to get out of the beta stage even when they're officially released for sale! In none of the interviews regarding the UPnP situation has Culp admitted that Eeye did the responsible thing by informing Microsoft and waiting for the fix to be available from Microsoft before releasing information on this critical exploit to the internet community, something many folks in the security community (all outside of Microsoft) consider 'responsible disclosure.' According to reports, it took Microsoft nearly two months to release a patch after learning of the exploit. While Eeye's actions were praiseworthy, I wouldn't wait so long before mentioning such a critical security problem to the community. Realisticly, a vendor should be able to examine and verify a reported exploit - particularly one as critical as this one - and release a patch or publish corrective guidance to the public in about two weeks. In this case, Microsoft - had it decided it was in its interest to do so - could have easily assigned fourteen thousand programmer man-days (1000 programmers x 14 days) to address the problem within two weeks. Eeye was very generous in giving Microsoft so long to fix the problem, although why it took nearly two months for Microsoft to address the problem raises some disturbing questions. Perhaps acknowledging this would be contrary to the toneand contents of Culp's October 2001 missive calling for a Microsoft-based Vatican of Vulnerability to quell the public disclosure of security vulnerabilities and implement software security through obscurity and public ignorance. More interestingly, Eeye reported the UPnP exploit to Microsoft back in October (according to sources at EEye, the day after Windows XP was released.) Was Microsoft's two-month silence on this critical exploit a business decision to avoid public embarassment on a new product so close to the holiday (e.g., "new PC purchasing") season? We can only wonder. Microsoft is by far the most notorious in their vulnerability announcements, legaleese, and cover-their-tail security alerts, something CDC member Tweety Fish noted in a 1999 interview discussing the growing number of Microsoft-generated security problems back then. He noted that Microsoft "will not consider any given security risk a problem until it becomes a problem in the press." Or, to put it another way, it's not really a problem until Microsoft says so. Actions speak louder than words. Microsoft pays security plenty of lip service for marketing and public relations spin control, but the firm's history of addressing security problems falls quite short of what security professionals would consider a robust, long-term committment to effectively dealing with the matter. Thus, it's up to third parties like Eeye and other research firms to continue serving as a "check and balance" against a future of vendor-induced security-through-obscurity and public ignorance. Thanks to Eeye's responsible disclosure of this catastrophic vulnerability in Windows XP, not only is the Internet a bit safer, but their actions prove once again that voluntary disclosure of vulnerability information is possible without a fee-based vendor-sponsored club. Resources EEye Security Advisory and Technical Discussion - Easy to Understand (20 Dec 01) Microsoft's Fix to the UPnP Exploit Article: "Microsoft," No. "Mickeysoft", Yes. (28Nov 01) Article: The Freedom to Innovate Includes The Freedom to Obfuscate: Why Microsoft's New "Security Framework" is Just Another .NET Vulnerability (10 Nov 2001) Article: The Microsoft-English Dictionary 1.5 (What Microsoft Really Means To Say) (28 Nov 01) . Microsoft has warned about a critical vulnerability in the UPnP protocol in Windows XP, risking unauthorized access and user safety for outdated systems.. Windows XP Security, UPnP Security Risks, Eeye Security Exploit. . LinuxSecurity.com Team

Calendar%202 Apr 06, 2024 User Avatar LinuxSecurity.com Team Server Security
78

WSL 0.50.2.0: Microsoft Updates Kernel And Introduces New Icon

Microsoft has released the latest preview version of Windows Subsystem for Linux, bringing with it a lengthy changelog, an updated kernel and a new icon. . With the launch of Windows Subsystem for Linux Pre-release 0.50.2.0, Microsoft has introduced a new icon (featuring, of course, a penguin), but there's far more to this release than just this visual update. The latest version fixes various WSL issues, updates the Linux kernel, and includes numerous other changes and additions. Continuing its embrace of Linux, Microsoft has used the latest version of WSL to make numerous changes to this increasingly invaluable tool. Key changes with this release include updating the tar used for importing and exporting WSL2 distributions, as well as adding new strings and parameters, while updating existing ones. . The newest version of WSL Pre-release 0.50.2.0 from Microsoft showcases a revamped logo along with significant kernel enhancements, boosting efficiency and user experience.. Windows Subsystem For Linux, WSL Update, Microsoft Linux Tool. . LinuxSecurity.com Team

Calendar%202 Nov 17, 2021 User Avatar LinuxSecurity.com Team Vendors/Products
78

Linux Mint 20 Versus Ubuntu And Windows: An Admin's Insights

Wondering how Linux Mint compares to Ubuntu and Windows? Get an experienced admin's perspective in this article. . As a long term user of Microsoft Windows, Fedora, Ubuntu and Linux Mint, I have seen some of the more intricate tantrums a Windows or Linux operating system can throw. My first Mint 20 installation was in early April 2020, even before Mint 20 was released. I have had the unique opportunity to compare it with Microsoft Windows and Ubuntu 20 for day-to-day work and use, and have made some interesting discoveries. Read on to find out. . Explore Linux Mint 20, Ubuntu, and Windows through the insights of a seasoned administrator, highlighting their unique features, usability, and user needs. Linux Mint, Ubuntu Comparison, Admin Perspectives, Windows Insights. . LinuxSecurity.com Team

Calendar%202 Mar 16, 2021 User Avatar LinuxSecurity.com Team Vendors/Products
210

Three Malicious Npm Packages Open Shells On Linux And Windows Systems

Three malicious npm JavaScript packages have been found opening shells on Linux and Windows systems. According to npm staff: "Any computer that has this package installed or running should be considered fully compromised." . Three JavaScript packages have been removed from the npm portal on Thursday for containing malicious code. According to advisories from the npm security team, the three JavaScript libraries opened shells on the computers of developers who imported the packages into their projects. The shells, a technical term used by cyber-security researchers, allowed threat actors to connect remotely to the infected computer and execute malicious operations. The npm security team said the shells could work on both Windows and *nix operating systems, such as Linux, FreeBSD, OpenBSD, and others. . On Thursday, a trio of JavaScript packages was taken down from the npm repository due to the discovery of harmful shell access vulnerabilities.. Malicious Npm Packages, JavaScript Security Risks, Shell Exploits, Remote Access Threats. . Brittany Day

Calendar%202 Oct 19, 2020 User Avatar Brittany Day Security Vulnerabilities
78

Morphisec Enhances Windows Security with Unhackable Initiative

Due to its vulnerability to hacks and exploits, many of the Windows and Linux users describe Windows as a very unsafe operating system. However, one Israeli security organization is claiming to work towards to change the impression of Microsoft. The Isreali security organization, Morphisec is presently working on making a Windows version that The link for this article located at TechWorm is no longer available. . Cybersecurity company Morphisec from Israel is working on a flawless Windows system to bolster defenses against vulnerabilities and cyberattacks.. Windows Security, Cyber Defense, Morphisec Solution, Exploit Protection. . LinuxSecurity.com Team

Calendar%202 Sep 07, 2015 User Avatar LinuxSecurity.com Team Vendors/Products
74

Windows Critical Patch: Immediate Action Required For Exploit Risk

Listen up, this one is serious. There is a critical vulnerability in many versions of Windows, which could be exploited to spread a worm automatically between vulnerable computers.. Microsoft has issued a patch, urging owners of vulnerable PCs to fix their computers as a matter of urgency. The link for this article located at Sophos is no longer available. . An urgent security flaw in macOS has surfaced across multiple iterations, leading Apple to release immediate updates. Take action now!. Windows Exploit Patch, Microsoft Security Risk, Critical Patch Urgency. . Anthony Pell

Calendar%202 Mar 14, 2012 User Avatar Anthony Pell Network Security
83

TDL-4 Botnet: Persistent Cyber Threat to Millions of Windows PCs

A new and improved botnet that has infected 4.5 million Windows PCs is "practically indestructible," security researchers say.. TDL-4, the name for both the bot Trojan that infects machines and the ensuing collection of compromised computers, is "the most sophisticated threat today," reported Kaspersky Labs researcher Sergey Golovanov late last month. "[TDL-4] is practically indestructible," Golovanov said. The link for this article located at Network World is no longer available. . TDL-4, an advanced botnet, significantly threatens millions of Windows PCs with its remarkable resilience and persistence.. TDL-4 Botnet, Windows Malware, Botnet Security, Cyber Threats, Malware Analysis. . LinuxSecurity.com Team

Calendar%202 Jul 18, 2011 User Avatar LinuxSecurity.com Team Hacks/Cracks
82

NSA Advisory: Upgrade to Windows 7 or Vista for Enhanced Protection

Top US spooks are advising businesses to upgrade to Vista or Windows 7, claiming that other operating systems do not cut the mustard when it comes to security.. According to a best practices sheet which the National Security Agency sends out, both Windows 7 and Vista provide substantial security enhancements over earlier Windows workstation operating systems such as XP. Many of these security features are enabled by default and help prevent common attack vectors, it says. In addition, implementing the 64-bit mode of the OS on a 64-bit hardware platform substantially increases the effort of an adversary to attain a system or root compromise. For any Windows-based OS, verify that Windows Update is configured to provide updates automatically, the leaflet claims. The link for this article located at TechEye is no longer available. . The NSA recommends transitioning to Windows 7 or Vista to boost security, featuring robust defenses, timely updates, enhanced encryption, and better access controls. NSA Advisory, Windows Security, Business Best Practices. . Dave Wreski

Calendar%202 May 02, 2011 User Avatar Dave Wreski Government
News Add Esm H340

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Community Poll

Is continuous patching actually viable?

No answer selected. Please try again.
Please select either existing option or enter your own, however not both.
Please select minimum {0} answer(s).
Please select maximum {0} answer(s).
/main-polls/156-is-continuous-patching-actually-viable?task=poll.vote&format=json
156
radio
0
[{"id":503,"title":"Delayed updates invite catastrophic breaches.","votes":1,"type":"x","order":1,"pct":50,"resources":[]},{"id":504,"title":"Automated fixes break production environments.","votes":1,"type":"x","order":2,"pct":50,"resources":[]},{"id":505,"title":"Manual approvals cannot keep pace.","votes":0,"type":"x","order":3,"pct":0,"resources":[]}] ["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"] ["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"] 350
bottom 200