Live data from Hacker News

The Tapplock IoT padlock has multiple security vulnerabilities

nakedsecurity.sophos.com

1–10 of 102 posts

Re: The Tapplock IoT padlock has multiple security vulnerabilities

#3

Genuinely curious how people still manage to fuck up this kind of super basic secure coding practices

Maybe they took the „f*ck it, ship it“ advice too seriously and shipped it a bit too fast?

Who knows but after learning this I would be highly cautious to buy anything from this company until they‘ve proofen to be more careful in the future.

Re: The Tapplock IoT padlock has multiple security vulnerabilities

#5

Genuinely curious how people still manage to fuck up this kind of super basic secure coding practices

Out of interest what strategies could be implemented to avoid this?

I've worked as a developer for a number of companies who handle sensitive data and I could have fairly easily have pushed malicious code. Even with mandatory code reviews, significantly complicated code with a well placed security hole would likely be missed.

Re: The Tapplock IoT padlock has multiple security vulnerabilities

#7
>What to do?

>Tapplock user? Get and install any and all patches provided. Apparently, the company has now addressed the most obvious web portal holes (guessable account IDs and no HTTPS), but we assume an app update will be needed as well.

Also, stop being a Tapplock user

Re: The Tapplock IoT padlock has multiple security vulnerabilities

#8
> ”Incredibly, Tapplock’s back-end system would not only let him open other people’s locks using the official app, but also tell him where to find the locks he could now open!”

Never heard of this product before but what a hilarious read. They seem to fix some of the issues pretty quick. But what a nightmare IoT are. I’m stressed out by not keeping up to date with computer/phone updates (mostly because I wait a bit to ensure programs I use still work). Can’t imagine owning even more products that I have to maintain software updates on...

Re: The Tapplock IoT padlock has multiple security vulnerabilities

#9
> Web programmer? Don’t make account IDs easy to guess. In an otherwise secure system, account numbers that go 1,2,3… shouldn’t be a problem, but why make it easy?

Is that the best advice to web programmers they can give based on this story? That's the "obscurity" part in the security by obscurity scheme. If you've got your security otherwise nailed down fine, some obscurity on the top doesn't hurt: security-in-depth, people seem to call that. But use only the obscurity, and only one person has to find out how your scheme works, and it's game over.

I'd, you know, recommend to think about authentication. Your authentication state is not "logged in", it's "logged in as user X". So the code that decides whether a client can see a specific page can and should (!) depend on what specifically you're authenticated as.

Oh, and yes, this company has proved that they don't know the least thing about security. But that was clear already.

Re: The Tapplock IoT padlock has multiple security vulnerabilities

#10
Frankly, this all seems like quite a lock of fuss over nothing. Firstly, pad locks are generally very easy to just break open with a set of bolt cutters. Particularly, if you look at more secure traditional pad locks practically all of them share physical design features intended at minimizing the amount of the actual shackle that's accessible. So to be clear- the second you see the shape of that padlock you know that it's not designed to be super secure.

With that in mind - which are you more worried about? Something spoofing your Bluetooth pass code using some advanced tech, physically unscrewing the back and deconstructing the padlock, or the third option: chop open the shackle?

What I find amazing is that they thought they advertise this product as more secure than any other padlock with the same mechanism. This padlock is a finger print padlock, maybe people like that convenience, but don't try and pretend physical security isn't a concern.

Post reply on HN