8 ms·
Researchers: Weak Security Defaults Enabled Squarespace Domains Hijacks
- hahahacorn 2y agoI know we all make mistakes, and that I'm particularly fallible, but... Damn. I think I'm going to switch from fintech to cybersecurity.
- justin_oaks 2y agoIf you do, be sure you're on the side that is intentionally trying to find vulnerabilities, not the side trying to defend against them. The defense side sucks. You have to deal with security vendors that are eager to sell you snake oil. You have to actively fight against management that wants to save money. You have to fight against users who don't care about security. If everything goes smoothly and you have no security problems, the bosses wonder why they even pay you. If you have a security incident, the bosses wonder why they even pay you.
- mxuribe 2y agoFor much of the last decade, my career seems to be more and more partnered with cybersecurity teams...I like the kinds of people, and i like partnering with such teams. I work so closely with such teams, and many of my peers/colleagues - both on the cyber teams and others not on cyber teams - have suggested that i should pursue a career in cybersecurity...they often say that i have the head for it...that i have a natural knack for actually working in cybersecurity...but I've hesitated and i can't always succinctly verbalize why. Well, i think you stated it much better than i could; the defense side sucks for the reasons you stated!!! :-)
- WillPostForFood 2y agoClearly Squarespace is the guilty party here, but man, I am still upset Google shut down Domains, and can't help but direct some ire their abandonment of yet another product.
- deleted 2y ago[deleted]
- iakov 2y agoThey did? I missed that. It hasn’t lasted even ten years, has it? I remember reading the Domains announcement and thought to myself - “you have to be a fool to trust Google to host your domains long-term”. Feels good to be right, but I feel bad for everyone who jumped on the bandwagon. I cant imagine trusting Google products to last those days.
- deleted 2y ago[deleted]
- JohnMakin 2y agoIt was useful because it integrated super nicely into workspace account administration. Unfortunately all the issues have been painfully predictable and the rollout has been bad.
- dvzk 2y agoThe entire consumer registrar industry is untrustworthy. I can't think of a worse category of online services, ranked by security and sleazebaggery, with the possible exception of the VPN market.
- binkHN 2y agoI'm in your same boat. I had a bunch of domains with Google because of the brand recognition, but this acquisition annoys me immensely and clearly it's off to a great start!
- meiraleal 2y agoPeople that registered those domains and got hacked bought them from Google, so trusting google was the security issue.
- jddj 2y agoUgh. Any recommendations for a quality domain registrar? Might as well get started with the migration
- dewey 2y agoI’ve been with Namecheap forever. It’s not super pretty UX wise but it works and boring is what I’m looking for in a domain registrar.
- ioblomov 2y agoEnom sounds similar. Been using it, with short default TTLs, for years.
- deleted 2y ago[deleted]
- x0x0 2y agoThey're not competent. Data point: they sent me an email saying my domain would automatically renew in 30 days, and then renewed it in 2. While sure, I'm not upset that my domain renewed, I ended up moving to porkbun because I expect a registrar to accurately tell me dates and times. If you say something is happening in X days, I expect it to happen in X days.
- dewey 2y agoLabeling a whole company with millions of domains under management "not competent" because they sent one wrong email or there's a misunderstanding on how it works on the customer side? Hard to please everyone I guess.
- x0x0 2y agoThere was no misunderstanding on my side. And exactly, I expect clear and correct communications. If you say "your domains will automatically renew in 1 month" then it needs to be in one month.
- diggan 2y ago> Taylor Monahan, lead product manager at Metamask, said Squarespace never accounted for the possibility that a threat actor might sign up for an account using an email associated with a recently-migrated domain before the legitimate email holder created the account themselves. > “Thus nothing actually stops them from trying to login with an email,” Monahan told KrebsOnSecurity. “And since there’s no password on the account, it just shoots them to the ‘create password for your new account’ flow. And since the account is half-initialized on the backend, they now have access to the domain in question.” This sounds like gross security negligence, and should probably be considered a crime when you're at the size of Squarespace with (assuming) a dedicated security team. Hopefully executives/management can be held responsible for whatever damage was done because of this.
- refulgentis 2y agoSquarespace is directly responsible, my irrational instinct is to blame Google even more, in that their role involved active abdication of responsibility for purely self-interested reasons and involved more employees than just their security engineering team. Domains are critical infrastructure, wasn't any reason to sell them other than Wall Street puffery. Obvious downside was leaving business customers who got them via Cloud exposed. Per my uninformed intuition at the time, there wasn't a secure way to do this sort of switchover without a lot of manual reaching out neither of them were going to do. Additionally, Google went out of their way to sweeten the deal by A) making Squarespace the reseller for any associated Google Workspace records which B) greatly widened the vulnerability surface. [1] This sounded uninformed to me, until it happened, so [2] quotes the retrospective at length to show there was no secure and automated choice. both via Security Alliance's "A Squarespace Retrospective": https://securityalliance.notion.site/A-Squarespace-Retrospective-or-How-to-Coordinate-an-Industry-Wide-Incident-Response-fead693b66c14543a48283d85aec19ad https://securityalliance.notion.site/A-Squarespace-Retrospec... [1] "Furthermore, as Squarespace is an authorized Google Workspace reseller, any teams who had purchased Google Workspace through Google Domains had their license transferred to Squarespace. This allows the threat actor to create new administrators in Google Workspace via the hijacked Squarespace account." [2] "However, what happens for [domain owner] emails which are not already registered to an [Squarespace] account? Well, you could preemptively create a new account for that email and send them a temporary password, but sending passwords in plain text is not a good practice, it would be pretty complicated to create millions of users with temporary passwords, and most people migrating probably want to use their Google account to sign in, not a password. Maybe your systems don’t even support creating temporary users like this."
- IntToDouble 2y agoDirect link to the retrospective: https://securityalliance.notion.site/A-Squarespace-Retrospective-or-How-to-Coordinate-an-Industry-Wide-Incident-Response-fead693b66c14543a48283d85aec19ad https://securityalliance.notion.site/A-Squarespace-Retrospec...
- diggan 2y agoDirect link to an unofficial and 3rd party retrospective, it would seem. > As Squarespace has yet to release an official statement or postmortem, the following is our strongest theory on how the threat actor was able to gain initial access to Squarespace accounts. It is the most likely explanation given the information we collected from numerous affected companies and experiments we ran ourselves.
- kentonv 2y agoSo many products make email verification optional in order to improve their funnel. But it's a huge security risk, because it leads to bugs like this. Very few engineers and PMs will actually stop to think: "Wait, what if the user's email address isn't verified?" I kind of wish we could just pass a law that says you have to validate email addresses before attaching them to accounts at all. Because otherwise, competitive pressure will keep pushing people towards not doing it and aiming this gun at their foot in the name of conversions. In the absence of a law: If your service insists on allowing unverified email addresses, you should store them in a completely different place in your database from verified ones. Maybe even obfuscate them with some encoding. Do whatever you can to make it really hard for anyone to accidentally rely on an unverified address. Ideally make it impossible for anyone except the team in charge of authentication to even see an unverified address. On another note, holy shit. So many people (myself included) chose Google Domains specifically because they thought it would be secure and trustworthy, because it's Google. Won't make that mistake again.
- justin_oaks 2y agoAt a previous job I complained to company leadership that we shouldn't trust email addresses without verification. I think the company eventually required verification, not because their trusted employee told them, but because a security review of the product pointed out the lack of email verification.
- zadokshi 2y agoWhen it’s a security review and something is on paper, there is now documentation of potential liability. When it’s just a random staff member complaining they want to do something that makes it harder to onboard customers, there’s no proof of incompetence, and incompetence can still be blamed on the developers.
- lionkor 2y agoDoes that mean that suggestions like that should maybe be sent by email, with multiple important people CCd?
- meiraleal 2y agoWow that's a terrible way Google managed customers security, selling them to an incompetent buyer. So many red flags pushing me to stop using anything Google.
- wintermutestwin 2y agoWhen I evaluated squarespace for a couple nonprofits I work with, they lost out to Wix because squarespace lacked a backup solution. I was stunned by that, but certainly not that such a cluefree team would cut security corners. How is it possible that this team blew off backup functionality for a product that is targeted at low skill end users? Maybe they ran out of money paying designers for yet another template that utilizes a full screen image on the landing page?
- cynicalsecurity 2y agoSquarespace spends a lot on marketing. They probably ran out of money on engineers.
- SoftTalker 2y agoSquarespace is targeted at technically illiterate small organizations. They make their workflows as simple as possible for that user base. I helped a local small nonprofit with their Squarespace site around 10 years ago, I know that's been long enough that it might not represent how things are today, but doing anything that wasn't implemented by their site builder tool was basically impossible.
- kube-system 2y ago> How is it possible that this team blew off backup functionality for a product that is targeted at low skill end users? That sounds to me like the perfect target market for blowing off backup functionality. That market doesn't demand that functionality. Backups are something that a more technically-literate purchaser might demand.
- tomrod 2y agoSo glad I migrated everything off of Squarespace. Just an awful experience. Slick website. Slow as mud movement for everything else. AND--the owner can't modify MX records, you have to create and grant admin rights as the owner to an entirely separate account. Schnikey.
- 23B1 2y agoThis move of google domains over to squarespace is the dumbest deal I have ever experienced and it makes me hate both companies even more.
- klabb3 2y agoOut of the thousands of product Google provides, domains was the one they were best aligned with their expertise and core business. I can’t for the life of me understand why they would get rid of it.
- x0x0 2y agoAdditionally, if you want to be a paas, you're now a paas that can't register domains. Moronic.
- christophilus 2y agoIs there a reason that there isn’t a Let’s Encrypt-like disruptor for registrars? It seems like it’s such a cesspool.
- Thorrez 2y agoWhen a CA issues a cert, the cost to the CA is essentially nothing. When a registrar registers a domain, that costs the registrar money because the registrar has to pay a fee to the registry. So a registrar generally cannot give out domains for free. Now, a registry could in decide to charge no fee. That's what .tk used to do. So you could get a .tk domain for free. Of course then .tk domains got the reputation of being cheap junk and spam.
- dvzk 2y agoZero cost TLS certificates might be what Let's Encrypt is known for, but it wasn't the first entity to offer them. LE also disrupted the CA market because of IdenTrust's initial cross-signing, and ACME's development and rollout, under the banner of a well-funded reputable 501(c)(3). Nothing is stopping someone from starting an above-cost 501(c) non-profit registrar, similar to the ISRG or the PIR.
- pants2 2y agoWell, CloudFlare registers domains at-cost, so that's about as close as you can get.
- saagarjha 2y agoCloudflare of course does not do so out of the goodness of their heart.
- case 2y agoNot only are there wholesale per-domain fees for registries (which tend to increase every few years), and the small ICANN fee for gTLDs, domains also have high customer support overhead that can’t easily be automated away like the LE cert process. Also keep in mind that domains are a “source of truth” unlike certs, which rely on the domains for verification.
- dboreham 2y agoFor the impatient, what they did was: put a zillion DNS registration accounts into a limbo state where anyone who knew, or could guess the email address associated with an account, could supply that, and a password of their choice, to gain authentication credentials valid for the account because they stored the supplied password without any verification that it came from the owner of the associated email address.
- deleted 2y ago[deleted]
- awinter-py 2y agowelp that was fast
- nikolay 2y agoGoogle sold Google Domains to the worst possible buyer! Right after a bunch of my domains, one by one got transferred to those amateurs, creating a random subdomain for each domain, I started to receive notifications about somebody trying to reset my password!
- TheNewsIsHere 2y agoThe problem with Squarespace remaining silent with this is that there’s a deafening lack of authoritative information about whether this issue has been patched. The researchers and Krebs are stopping short of making definitive statements because obviously only Squarespace can do that, and they aren’t. I have emailed some former clients I knew to use Google Domains just as a heads up, with steps from the article. It would be nice if Squarespace showed a modicum of ownership for their failings here.