Telecom company Sprint has shared some of its plans when it comes to 5G service in the U.S. The company announced at MWC in Barcelona that mobile customers in Atlanta, Chicago, Dallas and Kansas City can expect 5G service as soon as May 2019.
If you don’t live in one of those cities, maybe you live in Houston, Los Angeles, New York City, Phoenix or Washington, D.C., Sprint also promises 5G coverage in those cities soon after the initial launch, at some point before the end of June 2019.
Overall, Sprint expects to cover 1,000 square miles in nine cities by the end of the first half of 2019. It’s going to take years to roll out 5G coverage across the U.S.
When it comes to devices, Sprint will sell smartphones that are compatible with its 5G network. The first one will be the LG V50 ThinQ 5G. The company will also sell the Samsung Galaxy S10 5G at some point this summer.
Sprint is also partnering with Google so that Google Fi customers can take advantage of Sprint’s 5G network if they have a compatible device.
And that’s about all there is to know. It’s still unclear whether 5G plans are going to cost more.
The Google Assistant’s “Broadcast” feature has long existed as a way to blast a message to every Google smart speaker in the house. Instead of hunting down every individual family member at dinner time, put those smart speakers to work by saying, “Hey Google, broadcast, ‘It’s dinner time!'”
In a new blog post, Google called Broadcast “one of our most popular Assistant features” and announced that the feature is expanding to show messages on phones, too, even when they’re outside the home Wi-Fi network. That means Broadcast is basically turning into a new Google messaging service.
Broadcast will now be able to send and receive messages on the Google Home and Nest smart speakers, the Google Home Hub and Nest Hub smart displays, any Android phone, and iPhones running the Google Assistant app. Phones will get a notification when new messages arrive, and group chat members include both individual people (presumably with personal devices like a phone) and more public home devices. Just like any other messaging service, opening the notification will show a scrolling list of broadcast messages. The one big limitation is that the messaging only happens within a Google Family Group. If you want to include an outsider, you’ll have to awkwardly switch group messaging services.
Broadcast messaging uses audio by default, so speakers and smart displays will play the voice recording of your message. Phones and smart displays will show a transcription of your message and a play button, so you can listen or read if you want, and it looks like phones have the option of typing a response, too. Presumably, this would play back on speakers using text-to-speech.
One of many bespoke Google messaging services
Google has never been able to throw its full weight behind a single messaging service, and the constant launching and shutting down of competing messaging services has left the company without a competitive messaging platform to back. Several Google apps like the Google Assistant have aimed to include some smaller messaging functionality over the years, but without a clear Google service to plug into, they end up spinning up their own bespoke messaging services.
Besides this Google Assistant messaging service, YouTube Messaging existed from 2017-2019, Google Maps Messages (to message businesses) launched in 2018, Google Photos Messaging launched in 2019, Stadia Messaging was added in 2020, and Google Pay Messaging came out of beta with the app revamp in March 2021. And who could forget Google Docs Chat, which has existed seemingly forever, though awkwardly only on desktop clients. We can also give half-credit to Google News, which lets you send a message with a shared news article and will pop up a notification through the Google News app, although the feature doesn’t support replies. It would be nice if any of these services talked to each other through a single Google Messaging service, but instead, you’ll be managing individual contact lists and message histories.
This is one of a few new Google Assistant features that is supposed to arrive “just in time” for Mother’s Day (this Sunday—you all remembered, right?) so it should be rolling out soon.
Makers of high-end Android devices are responding to the discovery of a Qualcomm chip flaw that researchers say could be exploited to partially backdoor about a third of the world’s smartphones.
The vulnerability, discovered by researchers from security firm Check Point Research, resides in Qualcomm’s Mobile Station Modem, a system of chips that provides capabilities for things like voice, SMS, and high-definition recording, mostly on higher-end devices made by Google, Samsung, LG, Xiaomi, and OnePlus. Phone-makers can customize the chips so they do additional things like handle SIM unlock requests. The chips run in 31 percent of the world’s smartphones, according to figures from Counterpoint Research.
The heap overflow the researchers found can be exploited by a malicious app installed on the phone, and from there the app can plant malicious code inside the MSM, Check Point researchers said in a blog post published Thursday. The nearly undetectable code might then be able to tap into some of a phone’s most vital functions.
“This means an attacker could have used this vulnerability to inject malicious code into the modem from Android, giving them access to the device user’s call history and SMS, as well as the ability to listen to the device user’s conversations,” the researchers wrote. “A hacker can also exploit the vulnerability to unlock the device’s SIM, thereby overcoming the limitations imposed by service providers on it.”
Fixes take time
Check Point spokesman Ekram Ahmed told me that Qualcomm has released a patch and disclosed the bug to all customers who use the chip. Because of the intricacies involved, it’s not yet clear which vulnerable Android devices are fixed and which ones aren’t.
“From our experience, the implementation of these fixes takes time, so some of the phones may still be prone to the threat,” he wrote in an email. “Accordingly, we decided not to share all the technical details, as it would give hackers a roadmap on how to orchestrate an exploitation.”
Qualcomm representatives weren’t available on Wednesday evening to answer questions.
The vulnerability is tracked as CVE-2020-11292. Check Point discovered it by using a process known as fuzzing, which exposed the chip system to unusual inputs in an attempt to find bugs in the firmware. Thursday’s research provides a deep dive into the inner workings of the chip system and the general outline they used to exploit the vulnerability.
The research is a reminder that phones and other modern-day computing devices are actually a collection of dozens if not hundreds of interconnected computing devices. While successfully infecting individual chips typically requires nation-state-level hacking resources, the feat would allow an attacker to run malware that couldn’t be detected without time and money.
“We believe this research to be a potential leap in the very popular area of mobile chip research,” Check Point researchers wrote. “Our hope is that our findings will pave the way for a much easier inspection of the modem code by security researchers, a task that is notoriously hard to do today.”
Yesterday, infosec research firm SentinelLabs revealed twelve year old flaws in Dell’s firmware updater, DBUtil 2.3. The vulnerable firmware updater has been installed by default on hundreds of millions of Dell systems since 2009.
The five high severity flaws SentinelLabs discovered and reported to Dell lurk in the dbutil_2_3.sys module, and have been rounded up under a single CVE tracking number, CVE-2021-21551. There are two memory corruption issues and two lack of input validation issues, all of which can lead to local privilege escalation, and a code logic issue which could lead to a denial of service.
A hypothetical attacker abusing these vulnerabilities can escalate the privileges of another process, or bypass security controls to write directly to system storage. This offers multiple routes to the ultimate goal of local kernel-level access—a step even higher than Administrator or “root” access—to the entire system.
This is not a remote code execution vulnerability—an attacker sitting across the world, or even across the coffee shop, cannot use it directly to compromise your system. The major risk is that an attacker who gets an unprivileged shell via some other vulnerability can use a local privilege escalation exploit like this one to bypass security controls.
Since SentinelLabs notified Dell in December 2020, the company has provided documentation of the flaws, and mitigation instructions which for now boil down to “remove the utility.” A replacement driver is also available, and should be automatically installed at the next firmware update check on affected Dell systems.
SentinelLabs’ Kasif Dekel was at least the fourth researcher to discover and report this issue, following CrowdStrike’s Satoshi Tanda and Yarden Shafir, and IOActive’s Enrique Nissim. It’s not clear why it took Dell two years and three separate infosec companies’ reports to patch the issue—but to paraphrase CrowdStrike’s Alex Ionescu above, what matters most is that Dell’s users will finally be protected.