Tag Archive for: Dumpster

Disney’s social dumpster fire, Anom phones, and TikTok tragedies • Graham Cluley


Smashing Security podcast #283: Disney's social dumpster fire, Anom phones, and TikTok tragedies

A self-proclaimed “super hacker” causes problems in the Magic Kingdom, criminals regret trusting Anom phones, and lawsuits are filed against TikTok.

All this and much more is discussed in the latest edition of the award-winning “Smashing Security” podcast by computer security veterans Graham Cluley and Carole Theriault, joined this week by Anna Brading.

Plus don’t miss our featured interview with Scott McCrady, the CEO of SolCyber Managed Security Services.




Hosts:

Graham Cluley – @gcluley
Carole Theriault – @caroletheriault

Guest:

Anna Brading – @annabrading

Show notes:

Sponsored by:

  • Bitwarden – Password security you can trust. Bitwarden is an open source password manager trusted by millions of individuals, teams, and organizations worldwide for secure password storage and sharing.
  • The Secure Developer – A conversational and insightful podcast, that bridges the gap between dev and sec, from Snyk.
  • SolCyber – SolCyber delivers Fortune 500 level cybersecurity for small and medium-sized enterprises. If the bad guys aren’t being discriminating about who they’re attacking, how can you settle for anything less?

Follow the show:

Follow the show on Twitter at @SmashinSecurity, on the Smashing Security subreddit, or visit our website for more episodes.

Remember: Subscribe on Apple Podcasts, or your favourite podcast app, to catch all of the episodes as they go live. Thanks for listening!

Warning: This podcast may contain nuts, adult themes, and rude language.

Found this article interesting? Follow Graham Cluley on Twitter to read more of the exclusive content we post.



Graham Cluley is a veteran of the anti-virus industry having worked for a number of security companies since the early 1990s when he wrote the first ever version of Dr Solomon’s Anti-Virus Toolkit for Windows. Now an independent security analyst, he regularly makes media appearances and is an international public speaker on the topic of computer security, hackers, and online privacy.

Follow him on Twitter at @gcluley, or drop him an email.

Source…

Log4Shell is a dumpster fire that should have been avoided


On Thursday, December 9, 2021, my young, Minecraft-addicted kids were still completely oblivious of the Log4j vulnerabilities in their favorite game. Then again, so was every cybersecurity professional in the world.

Log4Shell should have been avoided

That all changed when the Apache Log4j project announced CVE-2021-44228 (aka Log4Shell) – a zero-day vulnerability in Log4j’s standardized method of handling log files used by apps all over the world, from Microsoft’s Minecraft to Twitter to Tesla to Apple’s iCloud. This led to a blaze of stories about how the internet is “on fire.”

These screaming headlines make sense for us in the software and digital services industry. This vulnerability, which continues to be followed by others, is bad news. And it’s hard to find a metaphor to describe an easily exploitable zero-days vulnerability in a huge number of high-value targets.

Rationally, nearly every business, organization, and government that does anything related to software went into crisis mode. It is difficult to imagine anyone having been unaffected, and most probably many are still on high alert even after nearly two weeks.

However, for most internet users, life went on as usual.

If they have read about the Log4Shell firestorm, average users have probably concluded this story was all smoke and no fire: Minecraft works, Facebook works, their iPhone is charged. Who cares? Amazon’s services in the US have been a bit on and off lately, but these were unrelated outages.

Fortunately, my kids, like most people, likely have no idea how bad this could get—at least not yet. But if you work in cybersecurity, you know one thing is true: most of us have lucked out, so far.

We could have avoided Log4Shell

The truth is we have no idea how severely attackers have taken advantage of the vulnerabilities in Log4j. Attackers can obfuscate their intrusions relatively easily and it’s unlikely that the hundreds of thousands of companies that have been busy patching their systems have engaged in any sort of incident response to detect whether the vulnerability was exploited before the update.

Without a doubt, this is a dumpster fire. And mostly everyone in our industry is doing their best to make sure…

Source…

Ring Throws A Moist Towelette On Its Dumpster Fire With A Couple Of Minimal Security Tweaks

Things have gotten worse and worse for Amazon’s Ring over the past several months. Once just the pusher of a snitch app that allowed city residents to engage in racial profiling from the comfort of their homes, Ring is now synonymous with poor security practices and questionable “partnerships” with hundreds of law enforcement agencies around the nation.

Ring owners recently discovered how easily their cameras could be hijacked by assholes with no moral compass and too much time on their hands. Using credentials harvested from security breaches, online forum members took control of people’s cameras to entertain a podcast audience who listened along as hijackers verbally abused Ring owners and their children.

Ring is now being sued for selling such an easily-compromised product. Ring’s response to the original reports of hijackings was to blame customers for not taking their own security more seriously. Ring does recommend two-factor authentication but that’s about all it does. It does not inform users when login attempts are made from unrecognized IP addresses or devices, and does not put the system on lockdown after a certain number of failed attempts are made.

Yes, users should use strong passwords (and not reuse passwords), but blaming customers for engaging in behavior most customers will engage in is unproductive. Instead of making two-factor authentication a requirement before deployment, Ring has just repeatedly pointed to its prior statements about its “encouragement” of 2FA — an “encouragement” that is mostly comprised of defensive statements issued in response to another negative news cycle.

Since it can’t keep blaming its millions of customers for its own failings, Ring is taking a very, very small step in the direction of actually taking its customers’ security seriously. [Please hold your tepid applause until the end of the announcement.]

Ring has announced that it is adding a new privacy dashboard to its mobile apps that will let Ring owners manage their connected devices, third-party services, and whether local police partnered with Ring can make requests to access video from the Ring cameras on the account. The company says that other privacy and security settings will be added to the dashboard in the future. This new Control Center will be available in the iOS and Android versions of the Ring app later this month.

It’s barely enough to make any one feel whelmed, much less overly so. There are two small additions that put this ahead of what Ring offered prior to the newsworthy camera hijackings. First, the app will allow users to see who’s logged in at any given time and logout unrecognized IP addresses or locations from within the app.

The second addition finally puts some (baby) teeth into Ring’s 2FA recommendation:

[R]ing is continuing to inform its customers of the importance of two-factor authentication on their accounts and will be making it an “opt-out” thing for new account setups, as opposed to the opt-in setup it currently is.

Swell. So that’s kind of… fixed. I guess. Now Ring just needs to work on all the other problematic things about itself, like the fact that it’s still not going to notify users when new IP addresses, devices, or locations attempt to access their cameras. And it’s not going to stop using cop shops as Ring marketing street teams. And for all of its insistence footage is never handed over to cops without the proper paperwork, it still deals from the bottom of the deck by claiming end users own all their footage even as it’s handing this footage to law enforcement without the end user’s permission or involvement.

Ring has a lot to fix if it’s ever going to make its way out of the PR pit it’s dug for itself. This is something, but it’s just barely something. It’s not enough. And it says Ring still isn’t serious about protecting its customers — not from law enforcement and not from malicious idiots who’ve found a new IoT toy to play with.

Permalink | Comments | Email This Story

Techdirt.

Consumer Reports: Your ‘Smart’ TV Remains A Privacy & Security Dumpster Fire

By now it has been pretty well established that the security and privacy of most “internet of things” devices is decidedly half-assed. Companies are so eager to cash in on the IOT craze, nobody wants to take responsibility for their decision to forget basic security and privacy standards. As a result, we’ve now got millions of new attack vectors being introduced daily, including easily-hacked “smart” kettles, door locks, refrigerators, power outlets, Barbie dolls, and more. Security experts have warned the check for this dysfunction is coming due, and it could be disastrous.

Smart televisions have long been part of this conversation, where security standards and privacy have also taken a back seat to blind gee whizzery. Numerous set vendors have already been caught hoovering up private conversations or transmitting private user data unencrypted to the cloud. One study last year surmised that around 90% of smart televisions can be hacked remotely, something intelligence agencies, private contractors and other hackers are clearly eager to take full advantage of.

Consumer Reports this week released a study suggesting that things aren’t really improving. The outfit, which is working to expand inclusion of privacy and security in product reviews, studied numerous streaming devices and smart TVs from numerous vendors. What they found is more of the same: companies that don’t clearly disclose what consumer data is being collected and sold, aren’t adequately encrypting the data they collect, and still don’t seem to care that their devices are filled with security holes leaving their customers open to attack.

The company was quick to highlight Roku’s many smart TVs and streaming devices, and the company’s failure to address an unsecured API vulnerability that could allow an attacker access to smart televisions operating on your home network. This is one of several problems that has been bouncing around since at least 2015, notes the report:

“The problem we found involved the application programming interface, or API, the program that lets developers make their own products work with the Roku platform. “Roku devices have a totally unsecured remote control API enabled by default,” says Eason Goodale, Disconnect’s lead engineer. “This means that even extremely unsophisticated hackers can take control of Rokus. It’s less of a locked door and more of a see-through curtain next to a neon ‘We’re open!’ sign.”

To become a victim of a real-world attack, a TV user would need to be using a phone or laptop running on the same WiFi network as the television, and then visit a site or download a mobile app with malicious code. That could happen, for instance, if they were tricked into clicking on a link in a phishing email or if they visited a site containing an advertisement with the code embedded.”

Roku was quick to issue a blog post stating that Consumer Reports had engaged in the “mischaracterization of a feature,” and told its customers not to worry about it:

“Consumer Reports issued a report saying that Roku TVs and players are vulnerable to hacking. This is a mischaracterization of a feature. It is unfortunate that the feature was reported in this way. We want to assure our customers that there is no security risk.

Roku enables third-party developers to create remote control applications that consumers can use to control their Roku products. This is achieved through the use of an open interface that Roku designed and published. There is no security risk to our customers’ accounts or the Roku platform with the use of this API. In addition, consumers can turn off this feature on their Roku player or Roku TV by going to Settings>System>Advanced System Settings>External Control>Disabled.”

Roku fails to mention that doing so disables the ability for consumers to control the device with Roku’s own app, taking away valuable functionality from the end user (something Consumer Reports mentions in its write up). And Roku doesn’t even address the other complaints in the report, including concerns that streaming hardware and TV companies aren’t making data collection and third-party sales clear, aren’t clearly showcasing their privacy policies, and often don’t let users opt out of such collection without losing functionality (much like the broadband ISPs and numerous services and apps these devices are connected to).

Roku’s response highlights the SOP approach (somebody else’s problem) inherent in the IOT. As experts like Bruce Schneier have repeatedly noted, the tech industry is caught in a cycle of security dysfunction where nobody in the chain has any real motivation to actually fix the problem:

“The market can’t fix this because neither the buyer nor the seller cares. Think of all the CCTV cameras and DVRs used in the attack against Brian Krebs. The owners of those devices don’t care. Their devices were cheap to buy, they still work, and they don’t even know Brian. The sellers of those devices don’t care: they’re now selling newer and better models, and the original buyers only cared about price and features. There is no market solution because the insecurity is what economists call an externality: it’s an effect of the purchasing decision that affects other people. Think of it kind of like invisible pollution.”

Schneier has repeatedly warned that we need cooperative engagement between governments, companies, experts and the public to craft over-arching standards and policies. The alternative isn’t just a few hacks and embarrassing PR gaffes now and again. The influx of millions of poorly secured internet-connected devices (many of which are being automatically integrated into historically-nasty botnets) is a massive dumpster fire with the potential for genuine human casualties. It’s easy to downplay these kinds of reports as just “a few minor problems with a television set,” but that ignores the massive scope of the problem and the chain of security and privacy apathy that has created it.

Permalink | Comments | Email This Story

Techdirt.