Google’s Project Zero team has posted a blog post that paints a pretty scary picture for Pixel and Samsung owners:
In late 2022 and early 2023, Project Zero reported eighteen 0-day vulnerabilities in Exynos Modems produced by Samsung Semiconductor. The four most severe of these eighteen vulnerabilities (CVE-2023-24033 and three other vulnerabilities that have yet to be assigned CVE-IDs) allowed for Internet-to-baseband remote code execution. Tests conducted by Project Zero confirm that those four vulnerabilities allow an attacker to remotely compromise a phone at the baseband level with no user interaction, and require only that the attacker know the victim’s phone number. With limited additional research and development, we believe that skilled attackers would be able to quickly create an operational exploit to compromise affected devices silently and remotely.
The fourteen other related vulnerabilities (CVE-2023-26072, CVE-2023-26073, CVE-2023-26074, CVE-2023-26075, CVE-2023-26076 and nine other vulnerabilities that are yet to be assigned CVE-IDs) were not as severe, as they require either a malicious mobile network operator or an attacker with local access to the device.
The following devices are known to be affected by these exploits:
- Samsung phones including the Galaxy S22 series, the Galaxy M33, M13, M12, A71, A53, A33, A21, A13, A12 and A04
- Vivo phones including the S16, S15, S6, X70, X60 and X30
- Google Pixel 6 and 7 series
- Wearables using the Exynos W920 chipset
- Vehicles that use the Exynos Auto T5123 chipset
That’s a very big list. And I have to wonder what cars use Exynos based modems. I guess we will find out shortly. In any case, the mitigation until updates come out is to turn off Wi-Fi calling and Voice-over-LTE (VoLTE). You should be able to find both of these in the Settings menu under Network & internet > SIMs, though the exact location may vary from device to device. If you have a vehicle that uses this chipset, I have no mitigation for you. And I have no way for you to check your vehicle to see if you have this Exynos chipset.
Expect patches for phones and wearables to come out soon, if they haven’t already. As for vehicles, your guess is as good as mine.
UPDATE:
David Maynor, Senior Director of Threat Intelligence at Cybrary had this to say:
“The flaw in the baseband component is important for enterprise customers to be aware of but not for the reasons it seems. The baseband component is the radio that communicates with cellular infrastructure. The software is a binary blob that’s encrypted, and there are not good ways to inspect the baseband state. So, you have a place you can’t monitor with software you can’t inspect that creates a perfect place for bad guys to do nefarious things.”
Ted Miracco, CEO of Approov followed up with this:
“The discovery of 18 vulnerabilities in Samsung’s Exynos chipsets is deeply unsettling, especially given that four of them enable remote code execution without any user interaction or indication. Overall, the discovery of these vulnerabilities highlights the importance of ongoing security research and the need for vendors to prioritize mobile security in their products. While, It also serves as a reminder for users to remain vigilant and take steps to protect themselves from potential attacks, the fact that an attacker only needs the victim’s phone number to carry out these attacks further highlights the severity of these vulnerabilities.”
Rogers Email Issues Continue To Drag On…. With Not Even A Peep From The Telco
Posted in Commentary on March 17, 2023 by itnerdI’ve been covering issues with Rogers Internet offering. It started as a general outage, but what has dragged on for weeks is an issue with email.
Let me the recap the issue that Rogers has been unable to fix. Anyone who uses Rogers email service (in other words they have a @Rogers.com address) cannot get their email. This is in part due to the fact that Rogers requires users to create App Specific Passwords via Rogers Member Center on each program or device that an email address is used on. The creation of new app specific passwords doesn’t work and existing app specific passwords appear to have been deleted in many cases. That pretty much breaks your applications that rely on them.
#Fail
There is a workaround though:
The workaround for this is to open a web browser and go to https://mail.yahoo.com and enter your Rogers email account details there. The password that you should use is the one for Rogers Member Center. This will at least allow you to view and reply to email on the web. And while this is a sub optimal workaround for many, it’s the only workaround that exists right now.
A secondary issue is that you might have tried to reset your email password under the belief that you were using the wrong password. If that’s you, I have some bad news for you. The only way to truly reset your email password is to dial into Rogers to do that. The good news is that once you hit a human, it doesn’t take long to do that. The bad news is that I am hearing wait times of three hours or more to actually get to a human. And I am also hearing that people are getting disconnected while waiting for a human to come onto the line. Which punts you to the back of the line.
The fact that this workaround is available is great. But viewing mail through a web browser is suboptimal. Especially on a smart phone. And having to get a human to reset your password is likely the reason why nobody can get through to Rogers in a timely manner. For a company who has spent a lot of time and effort to improve the customer experience, that’s really bad.
But what’s worse is that the silence from Rogers is stunning. But don’t take my word on that. I’ve been monitoring this situation as I have clients who are affected by this, and there are several threads on Community Forums that I have been watching. And Rogers customers are not happy. Here’s a few examples:
I want to stop here for a second. Assuming that this comment is true, it’s pretty bad when Rogers basically lies to a customer about an issue. That erodes any trust that the customer might have left.
And I want to talk about these last two comments. The first is relates to the fact that Rogers has not said a single word about this. Zip, zero, nada. When you don’t communicate to your customers about an ongoing issue, it creates room for people to say and think anything. Which means that you (or in this case Rogers) loses control of the message. That’s where the first comment comes from. In terms of the second comment, the person who wrote this is 1000% correct. Rogers needs to communicate way better than it has to date. But Rogers hasn’t and as this person has said, they’re left in the dark as a result. That’s not a good customer experience and that will come back to haunt Rogers.
So, what are your options if you’re affected by this and the workaround is sub optimal? Well, some of my customers are having me assist them in creating domains and email addresses associated with them so that they and not their ISP are in control of their email. Basically doing what I suggest here in terms of never using an ISP’s email service. One challenge that they have is exporting emails that they have since doing what I suggest here isn’t an option at the moment. But as long as they can get email on the device or program of their choosing, that’s good enough for them and they will take care of the export part of this whenever Rogers fixes their issues.
Other clients are taking a step further. On top of doing the above, they are also transitioning over to Bell if they have that option. Which in the areas where my clients are located in, they do. The feedback that I get from these clients is that they forgave Rogers for the outage in July of last year. And they even bought into Rogers marketing (Which is dead from what I can tell. Likely because of the backlash to it) that they are “committed to Canadians“. But those days are over and it’s time to dump Rogers as far as they are concerned. The fact is that Rogers really has dropped the ball here and bungled this situation badly. However this turns out, Rogers as a telco would have really deleted whatever goodwill that it had left with its customers. Which to be frank, I didn’t think was possible.
Shame on you Rogers.
Leave a comment »