PC vendors scramble as Intel announces vulnerability in firmware

Enlarge / All the Cores are affected by a major vulnerability in management firmware—as are Xeon servers and Atom, Celeron and Pentium devices. (credit: Intel ) Intel has issued a security alert that management firmware on a number of recent PC, server, and Internet-of-Things processor platforms is vulnerable to remote attack. Using the vulnerabilities, the most severe of which was uncovered by Mark Ermolov and Maxim Goryachy of Positive Technologies Research, remote attackers could launch commands on a host of Intel-based computers, including laptops and desktops shipped with Intel Core processors since 2015. They could gain access to privileged system information, and millions of computers could essentially be taken over as a result of the bug. The company has posted a detection tool on its support website for Windows and Linux to help identify systems that are vulnerable. In the security alert, members of Intel’s security team stated that “in response to issues identified by external researchers, Intel has performed an in-depth comprehensive security review of its Intel® Management Engine (ME), Intel® Trusted Execution Engine (TXE), and Intel® Server Platform Services (SPS) with the objective of enhancing firmware resilience.” Four vulnerabilities were discovered that affect Intel Management Engine firmware versions 11.0 through 11.20. Two were found in earlier versions of ME, as well as two in Server Platform Services version 4.0 firmware and two in TXE version 3.0. Read 3 remaining paragraphs | Comments

See the original article here:
PC vendors scramble as Intel announces vulnerability in firmware

Intel Planning To End Legacy BIOS Support By 2020, Report Says

Michael Larabel, writing for Phoronix: Intel is planning to end “legacy BIOS” support in their new platforms by 2020 in requiring UEFI Class 3 or higher. Making rounds this weekend is a slide deck from the recent UEFI Plugfest. Brian Richardson of Intel talked about the “last mile” barriers to removing legacy BIOS support from systems. By 2020, they will be supporting no less than UEFI Class 3, which means only UEFI support and no more legacy BIOS or CSM compatibility support mode. But that’s not going to force on UEFI Secure Boot unconditionally: Secure Boot enabled is considered UEFI Class 3+. Intel hasn’t removed legacy BIOS / CSM support yet due to many customers’ software packages still relying upon legacy BIOS, among other reasons. Removing the legacy BIOS support will mitigate some security risks, needs less validation by vendors, allows for supporting more modern technologies, etc. Read more of this story at Slashdot.

View the original here:
Intel Planning To End Legacy BIOS Support By 2020, Report Says

Samsung To Let Proper Linux Distros Run on Galaxy Smartphones

An anonymous reader shares a report: Samsung has announced it will soon become possible to run actual proper Linux on its Note8, Galaxy S8 and S8+ smartphones — and even Linux desktops. Yeah, yeah, we know Android is built on Linux, but you know what we mean. Samsung said it’s working on an app called “Linux on Galaxy” that will let users “run their preferred Linux distribution on their smartphones utilizing the same Linux kernel that powers the Android OS.” “Whenever they need to use a function that is not available on the smartphone OS, users can simply switch to the app and run any program they need to in a Linux OS environment, ” Samsung says. The app also allows multiple OSes to run on a device. Linux desktops will become available if users plug their phones into the DeX Station, the device that lets a Galaxy 8 run a Samsung-created desktop-like environment when connected to the DeX and an external monitor. Read more of this story at Slashdot.

See the original article here:
Samsung To Let Proper Linux Distros Run on Galaxy Smartphones

Microsoft Has Already Fixed the Wi-Fi Attack Vulnerability; Android Will Be Patched Within Weeks

Microsoft says it has already fixed the problem for customers running supported versions of Windows. From a report: “We have released a security update to address this issue, ” says a Microsoft spokesperson in a statement to The Verge. “Customers who apply the update, or have automatic updates enabled, will be protected. We continue to encourage customers to turn on automatic updates to help ensure they are protected.” Microsoft is planning to publish details of the update later today. While it looks like Android and Linux devices are affected by the worst part of the vulnerabilities, allowing attackers to manipulate websites, Google has promised a fix for affected devices “in the coming weeks.” Google’s own Pixel devices will be the first to receive fixes with security patch level of November 6, 2017, but most other handsets are still well behind even the latest updates. Security researchers claim 41 percent of Android devices are vulnerable to an “exceptionally devastating” variant of the Wi-Fi attack that involves manipulating traffic, and it will take time to patch older devices. Read more of this story at Slashdot.

Read the article:
Microsoft Has Already Fixed the Wi-Fi Attack Vulnerability; Android Will Be Patched Within Weeks

Equifax Blames Open-Source Software For Its Record-Breaking Security Breach

The blame for the record-breaking cybersecurity breach that affects at least 143 million people falls on the open-source server framework, Apache Struts, according to an unsubstantiated report by equity research firm Baird. The firm’s source, per one report, is believed to be Equifax. ZDNet reports: Apache Struts is a popular open-source software programming Model-View-Controller (MVC) framework for Java. It is not, as some headlines have had it, a vendor software program. It’s also not proven that Struts was the source of the hole the hackers drove through. In fact, several headlines — some of which have since been retracted — all source a single quote by a non-technical analyst from an Equifax source. Not only is that troubling journalistically, it’s problematic from a technical point of view. In case you haven’t noticed, Equifax appears to be utterly and completely clueless about their own technology. Equifax’s own data breach detector isn’t just useless: it’s untrustworthy. Adding insult to injury, the credit agency’s advice and support site looks, at first glance, to be a bogus, phishing-type site: “equifaxsecurity2017.com.” That domain name screams fake. And what does it ask for if you go there? The last six figures of your social security number and last name. In other words, exactly the kind of information a hacker might ask for. Equifax’s technical expertise, it has been shown, is less than acceptable. Could the root cause of the hack be a Struts security hole? Two days before the Equifax breach was reported, ZDNet reported a new and significant Struts security problem. While many jumped on this as the security hole, Equifax admitted hackers had broken in between mid-May through July, long before the most recent Struts flaw was revealed. “It’s possible that the hackers found the hole on their own, but zero-day exploits aren’t that common, ” reports ZDNet. “It’s far more likely that — if the problem was indeed with Struts — it was with a separate but equally serious security problem in Struts, first patched in March.” The question then becomes: is it the fault of Struts developers or Equifax’s developers, system admins, and their management? “The people who ran the code with a known ‘total compromise of system integrity’ should get the blame, ” reports ZDNet. Read more of this story at Slashdot.

View post:
Equifax Blames Open-Source Software For Its Record-Breaking Security Breach

California Has So Much Solar Power That Other States Are Paid To Take It

“On 14 days during March, Arizona utilities got a gift from California: free solar power, ” reported the Los Angeles Times. Mic reports: California is generating so much solar energy that it is resorting to paying other states to take the excess electricity in order to prevent overloading power lines. According to the Los Angeles Times, Arizona residents have already saved millions in 2017 thanks to California’s contribution. The state, which produced little to no solar energy just 15 years ago, has made strides — it single-handedly has nearly half of the country’s solar electricity generating capacity… When there’s too much solar energy, there is a risk of the electricity grid overloading. This can result in blackouts. In times like this, California offers other states a financial incentive to take their power. But it’s not as environmentally friendly as one would think. Take Arizona, for example. The state opts to put a pin in its own solar energy sources instead of fossil fuel power, which means greenhouse gas emissions aren’t getting any better due to California’s overproduction. The Los Angeles Times suggests over-construction of natural gas plants created part of the problem — Californians now pay roughly 50% more than the rest of the country for power — but they report that power supplies could become more predictable when battery storage technologies improve. Read more of this story at Slashdot.

Read More:
California Has So Much Solar Power That Other States Are Paid To Take It

Malware Uses Obscure Intel CPU Feature To Steal Data and Avoid Firewalls

An anonymous reader writes: Microsoft’s security team has come across a malware family that uses Intel’s Active Management Technology (AMT) Serial-over-LAN (SOL) interface as a file transfer tool. The problem with Intel AMT SOL is that it’s part of Intel’s ME, a separate chip inside Intel CPUs that runs its own OS and stays on even when the main CPU is off. Inside Intel’s ME, AMT SOL opens a virtual network interface which works even when the PC is turned off. Furthermore, because this virtual network interface runs inside ME, firewalls and security products installed on the main OS won’t detected malware using AMT SOL to exfiltrate data. The malware was created and used by a nation-state cyber-espionage unit codenamed PLATINUM, active since 2009, and which has targeted countries around the South China Sea. PLATINUM is by far one of the most sophisticated hacking groups ever discovered. Last year [PDF], the OS maker said the group was installing malware by abusing hotpatching — a mechanism that allows Microsoft to issue updates that tap into active processes and upgrade applications or the operating system without having to reboot the computer. Details about PLATINUM’s recent targets and attacks are available in a report [PDF] Microsoft released yesterday. Read more of this story at Slashdot.

View the original here:
Malware Uses Obscure Intel CPU Feature To Steal Data and Avoid Firewalls

NIST’s Draft To Remove Periodic Password Change Requirements Gets Vendors’ Approval

An anonymous reader writes: A recently released draft of the National Institute of Standards and Technology’s digital identity guidelines has met with approval by vendors. The draft guidelines revise password security recommendations and altering many of the standards and best practices security professionals use when forming policies for their companies. The new framework recommends, among other things: “Remove periodic password change requirements.” There have been multiple studies that have shown requiring frequent password changes to actually be counterproductive to good password security, said Mike Wilson, founder of PasswordPing. NIST said this guideline was suggested because passwords should be changed when a user wants to change it or if there is indication of breach. Read more of this story at Slashdot.

Link:
NIST’s Draft To Remove Periodic Password Change Requirements Gets Vendors’ Approval

NIST’s Draft To Remove Periodic Password Change Requirements Gets Vendors’ Approval

An anonymous reader writes: A recently released draft of the National Institute of Standards and Technology’s digital identity guidelines has met with approval by vendors. The draft guidelines revise password security recommendations and altering many of the standards and best practices security professionals use when forming policies for their companies. The new framework recommends, among other things: “Remove periodic password change requirements.” There have been multiple studies that have shown requiring frequent password changes to actually be counterproductive to good password security, said Mike Wilson, founder of PasswordPing. NIST said this guideline was suggested because passwords should be changed when a user wants to change it or if there is indication of breach. Read more of this story at Slashdot.

See the article here:
NIST’s Draft To Remove Periodic Password Change Requirements Gets Vendors’ Approval

NIST’s Draft To Remove Periodic Password Change Requirements Gets Vendors’ Approval

An anonymous reader writes: A recently released draft of the National Institute of Standards and Technology’s digital identity guidelines has met with approval by vendors. The draft guidelines revise password security recommendations and altering many of the standards and best practices security professionals use when forming policies for their companies. The new framework recommends, among other things: “Remove periodic password change requirements.” There have been multiple studies that have shown requiring frequent password changes to actually be counterproductive to good password security, said Mike Wilson, founder of PasswordPing. NIST said this guideline was suggested because passwords should be changed when a user wants to change it or if there is indication of breach. Read more of this story at Slashdot.

Read this article:
NIST’s Draft To Remove Periodic Password Change Requirements Gets Vendors’ Approval