Microsoft: Windows 10 Devices Open To 'Full Compromise' From Huawei PC Driver (zdnet.com) 112
The kernel sensors are meant to address the difficulty of detecting malicious code running in the kernel and are designed to detect user-space asynchronous procedure call (APC) code injection from the kernel. Microsoft Defender ATP anti-malware uses these sensors to detect actions caused by kernel code that may inject code into user-mode. Huawei's PCManager triggered Defender ATP alerts on multiple Windows 10 devices, prompting Microsoft to launch an investigation. [...] The investigation led the researcher to the executable MateBookService.exe. Due to a flaw in Huawei's 'watchdog' mechanism for HwOs2Ec10x64.sys, an attacker is able to create a malicious instance of MateBookService.exe to gain elevated privileges. The flaw can be used to make code running with low privileges read and write to other processes or to kernel space, leading to a "full machine compromise." Long-time Slashdot reader shanen writes: Though the story features Huawei, there doesn't seem to be anything specific to that company there. Just innuendo that you can't trust Chinese companies, eh? "Don't throw your computer into that Chinese briar patch!" Anyway, the sordid reality is that Microsoft is the root of all evils in the Windows platform. If increasing security had been half as important as maximizing profits, then we'd be in a much better world today. All complicated software is buggy, but adding complexity for no good reason is just begging for more problems. Here's a crazy solution approach: Any OS feature that isn't used by a LARGE majority of the users should be REMOVED from the OS. Maybe that isn't strong enough. Maybe the OS should be strictly limited to what absolutely needs to be there. Guard those eggs carefully!
ASUS Releases Fix For ShadowHammer Malware Attack (engadget.com) 63
The company simultaneously reiterated the narrow scope of ShadowHammer, noting that the malware targeted a "very small and specific user group." It's believed to be an Advanced Persistent Threat -- that is, a state-backed assault against organizations rather than everyday users. Other ASUS devices weren't affected, according to a notice. While the fix is reassuring, it also raises questions as to why the systems weren't locked down earlier. Update tools are prime targets for hackers precisely because they're both trusted and have deep access to the operating system -- tight security is necessary to prevent an intruder from hijacking the process.
Multiple US Airlines Hit By Flight Check-in and Booking Systems Outage (nbcbayarea.com) 41
Firefox Lockbox Comes To Android To Ease Password Pain (cnet.com) 38
Gmail App Changes Will Cause Most IFTTT Features To Stop Working (extremetech.com) 47
As of March 31, Google is placing new restrictions on Gmail apps. Apps can no longer read, create, or modify message bodies. None of IFTTT's seven Gmail triggers will work anymore after the new API rules go into effect. In conversations with Google, IFTTT was able to keep two of the Gmail actions: sending yourself an email and sending an email to someone else. However, the trigger needs to be from another service. You can log into your IFTTT account to see which of your Applets are affected by the change. The new API rules only affect Gmail. Other G Suite services like Google Drive and Assistant will remain operating normally.
Android Users' Security and Privacy At Risk From Shadowy Ecosystem of Pre-Installed Software, Study Warns (techcrunch.com) 27
In all 1,200 developers were identified behind the pre-installed software they found in the data-set they examined, as well as more than 11,000 third party libraries (SDKs). Many of the preloaded apps were found to display what the researchers dub potentially dangerous or undesired behavior. The data-set underpinning their analysis was collected via crowd-sourcing methods -- using a purpose-built app (called Firmware Scanner), and pulling data from the Lumen Privacy Monitor app. The latter provided the researchers with visibility on mobile traffic flow -- via anonymized network flow metadata obtained from its users. They also crawled the Google Play Store to compare their findings on pre-installed apps with publicly available apps -- and found that just 9% of the package names in their dataset were publicly indexed on Play. Another concerning finding relates to permissions. In addition to standard permissions defined in Android (i.e. which can be controlled by the user) the researchers say they identified more than 4,845 owner or "personalized" permissions by different actors in the manufacture and distribution of devices. So that means they found systematic user permissions workarounds being enabled by scores of commercial deals cut in a non-transparency data-driven background Android software ecosystem. The researchers address the lack of transparency and accountability in the Android ecosystem by suggesting the introduction and use of certificates signed by globally-trusted certificate authorities, or a certificate transparency repository "dedicated to providing details and attribution for certificates used to sign various Android apps, including pre-installed apps, even if self-signed." They also suggest Android devices should be required to document all pre-installed apps, plus their purpose, and name the entity responsible for each piece of software -- and do so in a manner that is "accessible and understandable to users."
Google Fixes Chrome 'Evil Cursor' Bug Abused by Tech Support Scam Sites (zdnet.com) 56
Hacking Lawyers or Journalists Is Totally Fine, Says Notorious Cyberweapons Firm (gizmodo.com) 113
Hackers Hijacked ASUS Software Updates To Install Backdoors on Thousands of Computers (vice.com) 114
The researchers estimate half a million Windows machines received the malicious backdoor through the ASUS update server, although the attackers appear to have been targeting only about 600 of those systems. The malware searched for targeted systems through their unique MAC addresses. Once on a system, if it found one of these targeted addresses, the malware reached out to a command-and-control server the attackers operated, which then installed additional malware on those machines. Kaspersky Lab said it uncovered the attack in January after adding a new supply-chain detection technology to its scanning tool to catch anomalous code fragments hidden in legitimate code or catch code that is hijacking normal operations on a machine. The company plans to release a full technical paper and presentation about the ASUS attack, which it has dubbed ShadowHammer, next month at its Security Analyst Summit in Singapore.
Which Programming Language Has The Most Security Vulnerabilities? (techrepublic.com) 330
An anonymous reader quotes TechRepublic: To answer this question, the report compiled information from WhiteSource's database, which aggregates information on open source vulnerabilities from sources including the National Vulnerability Database, security advisories, GitHub issue trackers, and popular open source projects issue trackers. Researchers focused in on open source security vulnerabilities in the seven most widely-used languages of the past 10 years to learn which are most secure, and which vulnerability types are most common in each...
The most common vulnerabilities across most of these languages are Cross-SiteScripting (XSS); Input Validation; Permissions, Privileges, and Access Control; and Information Leak / Disclosure, according to the report.
Across the seven most widely-used programming languages, here's how the vulnerabilities were distributed:
- C (47%)
- PHP (17%)
- Java (11%)
- JavaScript (10%)
- Python (5%)
- C++ (5%)
- Ruby (4%)
But the results are full of disclaimers -- for example, that C tops the list because it's the oldest language with "the highest volume of written code" and "is also one of the languages behind major infrastructure like Open SSL and the Linux kernel."
The report also notes a "substantial rise" across all languages for known open source security vulnerabilities over the last two years, attributing this to more awareness about vulnerable components -- thanks to more research, automated security tools, and "the growing investment in bug bounty programs" -- as well as the increasing popularity of open source software. And it also reports a drop in the percentage of critical vulnerabilities for most languages -- except JavaScript and PHP.
The report then concludes that "the Winner Of Most Secure Programming Language is...no one and everyone...! It is not about the language itself that makes it any more or less secure, but how you use it. If you are mitigating your vulnerabilities throughout the software development lifecycle with the proper management approach, then you are far more likely to stay secure."
Coincidentally, WhiteSource sells software which monitors open source components throughout the software development lifecycle to provide alerts about security (and licensing) issues.
Airline Passenger Walked Past Security With a Loaded Gun Magazine (apnews.com) 171
Security lines were closed and flights were temporarily grounded at a San Francisco International Airport terminal...for nearly an hour, and United Airline flights out of Terminal 3 were grounded Saturday morning as TSA officers looked for the passenger.
"Rotiski said the lines reopened after officers located the passenger and brought him back for re-screening."
Pwn2Own Competitors Crack Tesla, Firefox, Safari, Microsoft Edge, and Windows 10 (zdnet.com) 41
Not coincidentally, Team Fluoroacetate also won the three-day contest after earning 36 "Master of Pwn" points for successful exploits in Apple Safari, Firefox, Microsoft Edge, VMware Workstation, and Windows 10... [R]esearchers also exploited vulnerabilities in Apple Safari, Microsoft Edge, VMware Workstation, Oracle Virtualbox, and Windows 10.
Oracle's Surprise Unannounced Layoffs 'Clear-Cut Teams of Engineers' (ieee.org) 180
Oracle's layoff day started at 5 a.m. Pacific Time, when an email from Oracle executive vice president Don Johnson with the subject line "Organizational Restructuring" arrived in employee inboxes. The email informed staff members that, going forward, everything in the company would revolve around the Oracle Cloud Infrastructure (OCI) operation... Then the email continued with a perky sentence that made some employees furious: "OCI's business is stronger than ever, and this team's future is bright." At approximately 10 a.m., I'm told, just five hours after that email, the layoffs began -- and according to anecdotal reports included significant cuts within at least part of that stronger-than-ever, bright-future cloud business.
Those affected were given 30 minutes to turn in company assets and leave the building, and were told that Friday (today) would their last official day. "The morning felt like a slaughter," one Oracle employee told me. "One person after another...." And, that employee said, the layoff process was handled very badly, with entire teams being ushered into conference rooms as groups and told that they no longer had jobs. This employee indicated that technical teams, particularly those involved in product development and focused on software development, data science, and engineering, seemed to take the biggest hit.
Business Insider reports that Oracle hasn't formally announced the number of people laid off, but adds that "One source we spoke to was told by his manager that 1,500 people worldwide were cut."
Insider Threats Pose the Biggest Security Risk (betanews.com) 46
Among other findings are that 46 percent of IT leaders (heads of IT and above) believe that the rise of SaaS applications makes them the most vulnerable. In addition 40 percent of respondents believe they are most vulnerable to exposure of confidential business information such as financial information and customer lists. Only 26 percent of C-level executives say they've invested enough to mitigate the risk of insider threats, compared to 44 percent of IT managers.
FEMA Data Breach Hits 2.5 Million Disaster Survivors (cnn.com) 16
"To date, FEMA has found no indicators to suggest survivor data has been compromised. FEMA has also worked with the contractor to remove the unnecessary data from the system and updated its contract to ensure compliance with Department of Homeland Security (DHS) cybersecurity and information-sharing standards. As an added measure, FEMA instructed contracted staff to complete additional DHS privacy training."
Over 100,000 GitHub Repos Have Leaked API or Cryptographic Keys (zdnet.com) 52
Facebook Knew of Cambridge Analytica Data Misuse Earlier Than Reported (theguardian.com) 70
In a statement, a company spokesperson said: "Facebook absolutely did not mislead anyone about this timeline." After publication of this article, the spokesperson acknowledged that Facebook employees heard rumors of data scraping by Cambridge Analytica in September 2015. The spokesperson said that this was a "different incident" from Cambridge Analytica's acquisition of a trove of data about as many as 87 million users that has been widely reported on for the past year. "In September 2015 employees heard speculation that Cambridge Analytica was scraping data, something that is unfortunately common for any internet service," the spokesperson said. "In December 2015, we first learned through media reports that Kogan sold data to Cambridge Analytica, and we took action. Those were two different things." The filing raised questions about when Facebook first learned about the misuse of personal data by Cambridge Analytica, the now defunct political consultancy.
750,000 Medtronic Defibrillators Vulnerable To Hacking (startribune.com) 54
The more serious of the two is a vulnerability that could allow improper access to data sent between a defibrillator and an external device like an at-home monitor. The system doesn't use formal authentication or authorization protections, which means an attacker with short-range access to the device could inject or modify data and change device settings, the advisory says. A second vulnerability allows an attacker to read sensitive data streaming out of the device, which could include the patient's name and past health data stored on their device. The system does not use data encryption, the advisory says. (Deploying encryption in medical devices is tricky because is increases computational complexity and therefore uses the battery faster.) The FDA isn't expected to issue a recall as the vulnerabilities are expected to be patched via a future software update.
PewCrypt Ransomware Locks Users' Files and Won't Offer a Decryption Key Until - and Unless - PewDiePie's YouTube Channel Beats T-Series To Hit 100M Subscribers (zdnet.com) 237
While the ransomware was put together as a joke, sadly, it did infect a few users, ZDNet has learned. Its author eventually realized the world of trouble he'd get into if any of those victims filed complaints with authorities, and released the ransomware's source code on GitHub, along with a command-line-based decryption tool.