{"id":27649,"date":"2023-01-08T14:26:23","date_gmt":"2023-01-08T22:26:23","guid":{"rendered":"https:\/\/www.podfeet.com\/blog\/?p=27649"},"modified":"2023-01-15T20:36:07","modified_gmt":"2023-01-16T04:36:07","slug":"sb-2023-01-08","status":"publish","type":"post","link":"https:\/\/www.podfeet.com\/blog\/2023\/01\/sb-2023-01-08\/","title":{"rendered":"Security Bits \u2014 8 January 2023"},"content":{"rendered":"<h2>Deep Dive 1 \u2014 Rethinking the Last Pass Breach (It&#8217;s Worse &#x1f641;)<\/h2>\n<p>Two weeks ago the latest details on the Last Pass breach were much fresher, and since then two things have happened:<\/p>\n<ol>\n<li>More facts have come to my attention<\/li>\n<li>More well-reasoned opinions have been expressed<\/li>\n<\/ol>\n<p>In terms of new information we have the following:<\/p>\n<ol>\n<li>Even LastPass&#8217;s current default of 100,100 rounds of PBKDF2 is not best practice, <a href=\"https:\/\/cheatsheetseries.owasp.org\/cheatsheets\/Password_Storage_Cheat_Sheet.html\">OWASP now advise 310,000<\/a>, but worse, when they increased from 50,000 to 100,100 in 2018, they didn&#8217;t update existing vaults, so even today, many vaults are way more vulnerable than LastPass implied\n<ul>\n<li>OWASP is the <a href=\"https:\/\/owasp.org\/\">Open Web Application Security Project<\/a>, and a non-profit foundation dedicated to supporting web security by empowering web developers with guidance, education, and tools<\/li>\n<\/ul>\n<\/li>\n<li>Password Vaults don&#8217;t need to be as vulnerable as LastPass&#8217;s design makes them\n<ul>\n<li>1Password vaults use randomly generated account keys stored locally on users&#8217; devices (and encoded in the recovery kit they ask users to print out and keep safe) combined with the master password to protect vaults. That means that the password is in effect only relevant on your device (it has the key), the copy in the cloud is protected by the key, even if there was no password, and the key is strong enough to outlast the universe. <\/li>\n<li>1Password vaults are fully encrypted in the cloud, metadata and all, so website names would not leak<\/li>\n<\/ul>\n<\/li>\n<li>Humans are terrible at picking passwords, so any password that&#8217;s not computer generated is much weaker than its raw entropy implies, and real-world attackers are very skilled at focusing their cracking attempts at human-type passwords.<\/li>\n<\/ol>\n<p>In terms of opinion, there&#8217;s the obvious fact that lots of smart people are choosing to leave LastPass, and advising others to do the same. What&#8217;s influenced me much more is an observation by Leo Laporte that the breach notifications are actually missing a lot of critical detail, yes, they were timely, and yes they included nerdy technical detail, but they failed to address two critical questions:<\/p>\n<ol>\n<li><strong>Who&#8217;s backups<\/strong> were taken? Everyone&#8217;s? In the absence of detail, I guess we need to assume that.<\/li>\n<li><strong>From when<\/strong>? At what point in time were the backups created? Is it just one backup from a specific date, or is it a time series stretching back from the present to some specific time in the past? Do the backups go back to further than the change to defaulting to 100,100 iterations of PBKDF2 in 2018? If a user moved from a weak to a strong password a year ago, are they safe?<\/li>\n<\/ol>\n<p><strong>Unless you started using LastPass after 2018 and know you have never had a weak password, you must assume baddies have a poorly protected copy of your vault.<\/strong> If you joined before 2018, or if you ever had a poor password, then <strong>you need to change every password you ever stored in LastPass<\/strong> before the baddies have time to break a weakly encrypted vault.<\/p>\n<h3>Links<\/h3>\n<ul>\n<li>&#x1f3a7; <a href=\"https:\/\/www.grc.com\/sn\/sn-904.htm\">Security Now: Episode #904 \u2013 Leaving LastPass \u2014 www.grc.com\/\u2026<\/a><\/li>\n<li><a href=\"https:\/\/blog.1password.com\/not-in-a-million-years\/\">Not in a million years: It can take far less to crack a LastPass password \u2014 blog.1password.com\/\u2026<\/a><\/li>\n<\/ul>\n<h2>Deep Dive 2 \u2014 The Twitter Breach<\/h2>\n<p>With all the hubub around LastPass, the news that up to 400,000 Twitter accounts have have been leaked has gotten rather lost in the mix!<\/p>\n<p>What we now know is that early last year there was a flaw in a Twitter API that allowed an attacker to test if a given phone number or email address matched a Twitter username, and if it did, which one. This allowed attackers to mine Twitter for usernames that match email addresses from other breaches, and, the ranges of telephone numbers used by major providers. This let them build up a searchable database of Twitter usernames with supposedly private email addresses and phone numbers.<\/p>\n<p>For most people the biggest danger here is automated but convincing <strong>targeted phishing<\/strong>, but for high-value users who rely on SMS 2FA being targeted for a SIM swapping attack is the biggest danger. In this case, high-value is from the point of view of baddies, so some categories that leap to my mind include:<\/p>\n<ol>\n<li>Celebrities, political leaders, and government officials<\/li>\n<li>Industry leaders and engineers working on important projects<\/li>\n<li>Any user with a cool username, hacking and selling cool usernames is big business for cybercriminals &#x1f641;<\/li>\n<\/ol>\n<p>While I think it&#8217;s important for all high-value users to change away from SMS 2FA, I think this is probably <strong>a good time for <em>everyone<\/em> still using SMS 2FA on Twitter to switch over to TOTP<\/strong> (Google Authenticator-like codes from an app like Authy or 1Password).<\/p>\n<h3>Links<\/h3>\n<ul>\n<li><a href=\"https:\/\/nakedsecurity.sophos.com\/2022\/12\/28\/twitter-data-of-400-million-unique-users-up-for-sale-what-to-do\/\">Twitter data of \u201c+400 million unique users\u201d up for sale \u2013 what to do? \u2014 nakedsecurity.sophos.com\/\u2026<\/a><\/li>\n<\/ul>\n<h2>Deep Dive 3 \u2014 Meta&#8217;s \u20ac390M ($411M) Fine, and its Implications<\/h2>\n<p>The Irish Data Protection Commissioners (Irish DPC) have found that Meta is not in compliance with the GDPR because it doesn&#8217;t get user consent for targeted advertising. The judgement requires that it pay the fine, and update its processes to gather the needed consent on Facebook &amp; Instagram.<\/p>\n<p>Obviously Meta are appealing the decision, but so are the Irish Data Protection Commissioners (sort of)!<\/p>\n<p>If you want a detailed understanding of the GDPR, I suggest <a href=\"https:\/\/www.podfeet.com\/blog\/2018\/04\/ccatp-534\/\">CCATP episode 534<\/a> where myself and Allison go through the entire regulation in detail, but for this discussion, we just need to understand one concept \u2014 the legal basis on which data is collected. Under the GDPR, each piece of personally identifiable data you collect must be covered by one of six possible legal basises:<\/p>\n<ol>\n<li>Consent<\/li>\n<li>Legitimate Interest<\/li>\n<li>Contractual Obligations<\/li>\n<li>Legal Obligations<\/li>\n<li>Vital Interests<\/li>\n<li>Public Interests<\/li>\n<\/ol>\n<p>Just two of those are in play here \u2014 Consent and Contractual Obligations.<\/p>\n<p>Meta say that by using Facebook you are entering into a contract with them, and that that contract requires tracking for targeted ads, so there is no need for consent.<\/p>\n<p>In their initial ruling on a case brought by Austrian privacy campaigner Max Schrems the Irish DPC agreed with Meta, but that initial ruling had to be sent to all other EU DPCs, and many did not agree. That kicked of a process whereby the ruling went to a board of DPCs, and that board agreed with Schrems that ad targeting is not covered by contractual obligation because tracking is not essential for the delivery of the service, so consent is needed. The board overruled the Irish DPC, and forced them to issue the ruling against Meta that made the news.<\/p>\n<p>The Irish DPC is quite cranky about being overruled like this, so they&#8217;ve filed suit in the European court, alleging that the board of DPCs over-stepped their authority with this ruling.<\/p>\n<p><strong>If the ruling stands<\/strong> it&#8217;s a really big deal, it would mean actual informed consent would be needed for targeted ads.<\/p>\n<h3>Links<\/h3>\n<ul>\n<li><a href=\"https:\/\/www.politico.eu\/article\/meta-fina-ad-business-model\/\">\u20ac390M fine strikes blow to Meta\u2019s ad-fueled business model \u2014 www.politico.eu\/\u2026<\/a><\/li>\n<\/ul>\n<h2>Notable News<\/h2>\n<ul>\n<li>&#x1f1fa;&#x1f1f8; <a href=\"https:\/\/appleinsider.com\/articles\/22\/12\/23\/cambridge-analytica-suit-settled-for-historic-725-million\">Cambridge Analytica suit settled for historic $725 million [u] \u2014 appleinsider.com\/\u2026<\/a><\/li>\n<li>&#x1f9ef; No, Chinese researchers have not just killed cryptography \u2014 <a href=\"https:\/\/nakedsecurity.sophos.com\/2023\/01\/06\/rsa-crypto-cracked-or-perhaps-not\/\">nakedsecurity.sophos.com\/\u2026<\/a> (The article starts with an excellent human-friendly explanation of public key cryptography)\n<ul>\n<li><strong>Related:<\/strong> the US has passed a (largely symbolic) bill to encourage government and industry to cooperate to prepare for a post-quantum world \u2014 <a href=\"https:\/\/nakedsecurity.sophos.com\/2022\/12\/29\/us-passes-the-quantum-computing-cybersecurity-preparedness-act-and-why-not\/\">nakedsecurity.sophos.com\/\u2026<\/a> (The article starts with an excellent explanation of the two types of cryptography quantum computers are threatening to obsolete)<\/li>\n<\/ul>\n<\/li>\n<li>&#x1f9ef; A critical vulnerability in the Linux Kernel implementation of the SMB protocol was responsibly disclosed on the 22nd of December, the bug was patched last summer, and is in the cutting edge kernel implementation of SMB which is very new only used in the most actively maintained distros and devices, it does not affect the SAMBA license used in most distros and NAS devices \u2014 <a href=\"https:\/\/nakedsecurity.sophos.com\/2022\/12\/27\/critical-10-out-of-10-linux-kernel-smb-hole-should-you-worry\/\">nakedsecurity.sophos.com\/\u2026<\/a><\/li>\n<li>&#x1f1fa;&#x1f1e6; <a href=\"https:\/\/nakedsecurity.sophos.com\/2023\/01\/03\/inside-a-scammers-lair-ukraine-busts-40-in-fake-bank-call-centre-raid\/\">Inside a scammers\u2019 lair: Ukraine busts 40 in fake bank call-centre raid \u2014 nakedsecurity.sophos.com\/\u2026<\/a> (The article starts with an excellent overview of the kinds of tactics banking scammers are using today)<\/li>\n<\/ul>\n<h2>Top Tips<\/h2>\n<aside class=\"small-aside\">Tip, tricks, or advice that is likely to be useful to the NosillaCast audience or the family members and friends whose IT they support.<\/aside>\n<ul>\n<li><a href=\"https:\/\/www.intego.com\/mac-security-blog\/10-things-you-can-do-to-improve-your-security-and-privacy-on-your-mac-iphone-or-ipad\/\">10 Things You Can Do to Improve Your Security and Privacy on Your Mac, iPhone, or iPad \u2014 www.intego.com\/\u2026<\/a><\/li>\n<\/ul>\n<h2>Interesting Insights<\/h2>\n<aside class=\"small-aside\">High-quality opinion and editorial content recommended by Bart.<\/aside>\n<ul>\n<li>An excellent descriptions of the implications for users of the changes Apple is expected to have to make to iOS between now and late 2024 when the EU Digital Markets Act goes into force: <a href=\"https:\/\/appleinsider.com\/articles\/22\/12\/13\/you-might-be-ready-for-side-loading-on-iphone-but-your-parents-arent\">You might be ready for side loading on iPhone, but your parents aren&#8217;t \u2014 appleinsider.com\/\u2026<\/a><\/li>\n<\/ul>\n<h2>Palate Cleansers<\/h2>\n<aside class=\"small-aside\">Anything upbeat and nerdy Bart and\/or Allison think you might enjoy.<\/aside>\n<ul>\n<li><strong>From Bart:<\/strong>\n<ul>\n<li>&#x1f3a7; The best, most nuanced, and probably most realistic discussions of what this whole recent boom in generative AI really means, and why a lot of the hype is not justified that I&#8217;ve encountered to date \u2014 <a href=\"https:\/\/overcast.fm\/+oiPWgxJVM\">The Ezra Klein Show: A Skeptical Take on the A.I. Revolution \u2014 overcast.fm\/\u2026<\/a><\/li>\n<li>For those of you missing DarkSkies as much as I am: <a href=\"https:\/\/blog.blankbaby.com\/2023\/01\/replacement-for-dark-sky.html\">Replacement for Dark Sky \u2014 blog.blankbaby.com\/\u2026<\/a> (FWIW, I&#8217;m currently using Carrot Weather &amp; Hello Weather, and like both a lot)\n<ul>\n<li><a href=\"https:\/\/slate.com\/technology\/2022\/12\/dark-sky-weather-app-apple-meteorologists-rip.html\">The World\u2019s Best Terrible Weather App \u2013 slate.com\/&#8230;<\/a><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2>Legend<\/h2>\n<p>When the textual description of a link is part of the link it is the title of the page being linked to, when the text describing a link is not part of the link it is a description written by <a href=\"https:\/\/bartb.ie\/\">Bart<\/a>.<\/p>\n<table>\n<thead>\n<tr>\n<th align=\"center\">Emoji<\/th>\n<th align=\"left\">Meaning<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td align=\"center\">&#x1f3a7;<\/td>\n<td align=\"left\">A link to <strong>audio content<\/strong>, probably a podcast.<\/td>\n<\/tr>\n<tr>\n<td align=\"center\">&#x2757;<\/td>\n<td align=\"left\">A <strong>call to action<\/strong>.<\/td>\n<\/tr>\n<tr>\n<td align=\"center\"><em>flag<\/em><\/td>\n<td align=\"left\">The story is particularly relevant to people living in a <strong>specific country<\/strong>, or, the organisation the story is about is affiliated with the government of a specific country.<\/td>\n<\/tr>\n<tr>\n<td align=\"center\">&#x1f4ca;<\/td>\n<td align=\"left\">A link to <strong>graphical content<\/strong>, probably a chart, graph, or diagram.<\/td>\n<\/tr>\n<tr>\n<td align=\"center\">&#x1f9ef;<\/td>\n<td align=\"left\">A story that has been <strong>over-hyped<\/strong> in the media, or, <em>&#8220;no need to light your hair on fire&#8221;<\/em> &#x1f642;<\/td>\n<\/tr>\n<tr>\n<td align=\"center\">&#x1f4b5;<\/td>\n<td align=\"left\">A link to an article behind a <strong>paywall<\/strong>.<\/td>\n<\/tr>\n<tr>\n<td align=\"center\">&#x1f4cc;<\/td>\n<td align=\"left\">A <strong>pinned<\/strong> story, i.e. one to keep an eye on that&#8217;s likely to develop into something significant in the future.<\/td>\n<\/tr>\n<tr>\n<td align=\"center\">&#x1f3a9;<\/td>\n<td align=\"left\">A <strong><em>tip of the hat<\/em><\/strong> to thank a member of the community for bringing the story to our attention.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"<p>Deep Dive 1 \u2014 Rethinking the Last Pass Breach (It&#8217;s Worse &#x1f641;) Two weeks ago the latest details on the Last Pass breach were much fresher, and since then two things have happened: More facts have come to my attention More well-reasoned opinions have been expressed In terms of new information we have the following: [&hellip;]<\/p>\n","protected":false},"author":4,"featured_media":19030,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[147,214],"tags":[305,2650,170,345,1416,135,73],"class_list":["post-27649","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog-posts","category-security-bits","tag-1password","tag-breach","tag-hack","tag-lastpass","tag-password-manager","tag-passwords","tag-twitter"],"jetpack_featured_media_url":"https:\/\/www.podfeet.com\/blog\/wp-content\/uploads\/2019\/08\/security_bits_logo_400px_no_alpha.jpg","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/27649","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/comments?post=27649"}],"version-history":[{"count":2,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/27649\/revisions"}],"predecessor-version":[{"id":27739,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/27649\/revisions\/27739"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/media\/19030"}],"wp:attachment":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/media?parent=27649"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/categories?post=27649"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/tags?post=27649"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}