Email or username:

Password:

Forgot your password?
Top-level
Foone🏳️‍⚧️

HEY FUN FACT: this was used as part of an Alexa/google home type thing! this is the "cloud" half, as in the part sitting in a warehouse somewhere.
It turns out every time the customer asked for something from the smart assistant, the WAV file was sent to the cloud box

where it is still stored. and I now have eleven thousand wave files

89 comments
Graham Spookyland🎃/Polynomial

@foone the people behind this need to be barred from operating a business ever again. I know this shit happens all the time with liquidated assets but it's fucking unacceptable.

Rob

@foone JFC this is doubleplusungood

Advanced Persistent Teapot

@foone exhibit #1473 in Why I Will Not Have Smart Home Shit, Ever

Glyph

@foone this has _got_ to be some kind of crime, right? like, not you having the wav files, but the fact that someone gave them to you. a HIPAA violation at the very least

Foone🏳️‍⚧️

@glyph oh, most likely.
but I probably have all this shit because they are gone and bankrupt

Graham Spookyland🎃/Polynomial

@glyph @foone sadly, no. at most it's *maybe* a GDPR violation depending on the content of the WAV files, but likely not, and I'm guessing that's going to be impossible to prosecute anyway because the assets are almost certainly a result of an insolvency liquidation. I see this shit all the damn time and right now there's very little recourse for those affected.

Momo

@gsuberland
If this is from an EU customer, it is a GDPR violation. But as you stated, there is probably no legal entity anymore that could pay the fine. Which means we need an appendix that ensures that the insolvency administrator enforces GDPR in liquidation cases (or would be personally liable if shit like this happens).

And again, this would probably not apply to the US so good look out there...
@glyph @foone

@gsuberland
If this is from an EU customer, it is a GDPR violation. But as you stated, there is probably no legal entity anymore that could pay the fine. Which means we need an appendix that ensures that the insolvency administrator enforces GDPR in liquidation cases (or would be personally liable if shit like this happens).

PhreakByte

@gsuberland @glyph @foone The entity that was the data controller at the time of the breach is responsible for reporting it. If the company has been liquidated, the liquidator or administrator may need to handle this obligation (GDPR wise)

Foone🏳️‍⚧️

god the logs are full of errors about assorted video streams failing.
so this thing was connecting to something which had cameras. like, I can tell which room of the house failed.

now I don't think there's any video stored on this device, but keep in mind: the fools that made this thing fill up with WAV files? they also designed the video streaming part. Where are those videos stored, and how safe are they?

Foone🏳️‍⚧️

or maybe the fools who dumped all the NUCs from their entire "AI remote healthcare" in the recycling without yanking any drives are just somehow REALLY GOOD at knowing how to secure their s3 buckets.

Foone🏳️‍⚧️

assuming their S3 keys aren't just saved in this harddrive somewhere

Foone🏳️‍⚧️

jesus christ this isn't the only time THIS MONTH I've found an IoT device and checked the filesystem contents and it's got their private git repos on it

Foone🏳️‍⚧️

and now I can email the lead developer.

or just commit to their git repo, I guess.

Foone🏳️‍⚧️ replied to Foone🏳️‍⚧️

okay so the good news is that they don't just have S3 keys laying around in plain text.
the other good news is that they have a secrets manager
the bad news is that they rolled their own secrets manager
the extra bad news is that I have the source for said secrets manager
and the extra extra bad news is that it has to decrypt those keys without external input, meaning I have all the parts here to pull out their s3 keys

Foone🏳️‍⚧️ replied to Foone🏳️‍⚧️

oh hey!

this thing authenticates to some of their servers (which are still up, even if the company might not be (this is unknown at the moment)) over SSH! using keys kept in the same home-rolled vault thing!

so I can SSH into their servers now!

Foone🏳️‍⚧️ replied to Foone🏳️‍⚧️

oh god this thing sends email from gmail

please tell me they didn't embed the google login into this device

Foone🏳️‍⚧️ replied to Foone🏳️‍⚧️

tempted to drive past their HQ with a megaphone "I'VE GOT YOUR MODELS, YOU AI HACKS!"

Foone🏳️‍⚧️ replied to Foone🏳️‍⚧️

wait. did they seriously stuff videos into their redis database?

Foone🏳️‍⚧️ replied to Foone🏳️‍⚧️

they sure did! I have a video of someone picking something up from outside a door.

Viss replied to Foone🏳️‍⚧️

@foone ffffffffffucking what? they stuffed entire videos INTO REDIS?

Graham Spookyland🎃/Polynomial replied to Viss

@Viss @foone this is more of a thing than you might expect. I've seen a few high-volume realtime media distribution backends that use Redis as a rolling video stream cache.

I'm particularly unsurprised to see it here because there are published tools for realtime ML media analytics using redis:

github.com/RedisGears/EdgeReal

Graham Spookyland🎃/Polynomial replied to Viss

@Viss @foone there is some method in the madness. if you've got a lot of transient video data, and you need access to a rolling window of it (either for buffering/stability purposes or for realtime analytics), storing it to disk ends up costing a fortune because you'll end up running headlong into DWPD limits on drives and having to swap them out constantly. but with RAM there's no such wear. for a few hundred concurrent clients you can do it on a single consumer desktop PC worth of RAM.

Graham Spookyland🎃/Polynomial replied to Graham

@Viss @foone Redis isn't required to flush to disk (the whole dataset is in-memory) and it supports blob storage, so it's not the worst option. my guess is someone ran the `save` command at some point (or they were doing periodic saves because they didn't separate out nonvolatile data into a separate redis instance) and foone's seeing that last snapshot.

Foone🏳️‍⚧️ replied to Foone🏳️‍⚧️

okay found their S3 creds. they hardcoded them in a Jenkinsfile.

Foone🏳️‍⚧️ replied to Foone🏳️‍⚧️

not a good sign to see a bash case statement for environment, and prod sets the server to FOOBAR.EGG
and test sets the server to... FOOBAR.EGG

Foone🏳️‍⚧️ replied to Foone🏳️‍⚧️

anyway I'm gonna be near their HQ on thursday. Maybe I'll stop by and ask if they're still in business, and if they are, do they know where their NUCs are?

Foone🏳️‍⚧️ replied to Foone🏳️‍⚧️

and in case anyone is getting deja-vu:

This is a completely different company than the other one I found like 3 weeks ago:

digipres.club/@foone/112817523

Foone🏳️‍⚧️ replied to Foone🏳️‍⚧️

I'm really not the right person to work in computer security research, but it'd be nice to have a sort of consulting job with a local one where I can just point them at some really broken shit and they investigate it and maybe give me a commission

Gabriel Pettier replied to Foone🏳️‍⚧️

@foone hm, are you *sure* they are bankrupt (i mean, not just technically 😆), if this was in production as of 2 months ago, maybe they just scaled away from this infra and sent everything to ewaste after migrating.

Foone🏳️‍⚧️ replied to Gabriel

@tshirtman yeah. they may have just moved everything to cloud-hosted and didn't need their wall of NUCs

Benjamin Reed replied to Foone🏳️‍⚧️

@foone Did they think the “P" in "PII" stood for “Public”?

Elfi, :verifiedtransbian: cute moth replied to Foone🏳️‍⚧️

@foone Better act fast, 'tis the season for Spirit Halloween to start inhabiting old husks

Σ(i³) = (Σi)² replied to Foone🏳️‍⚧️

@foone
I heard somewhere you were low on cash? I wonder how much what you have there might fetch on some shady website...

:flan_reaper: - On Hiatus replied to Foone🏳️‍⚧️

@foone

Wonder if someone over at like, 404Media, would enjoy writing up a hilariously embarrassing article about these bros.

4censord :neocat_flag_pan: replied to Foone🏳️‍⚧️

@foone@digipres.club didnt you have bascially that same thing happen just a few weeks/months ago? last time with a raspi like thing?

chort ↙️↙️↙️ replied to Foone🏳️‍⚧️

@foone this is exactly as bad as I believe most cloud startups are.

:blobpopcorn:

Wilfried Klaebe replied to Foone🏳️‍⚧️

@foone Can you push to their git server though?

Elfi, :verifiedtransbian: cute moth

@foone If there was a bounty for this kind of shit, you'd never have to work again. my god.

Foone🏳️‍⚧️ replied to Elfi, :verifiedtransbian: cute moth

@elfi yeah. the problem is I'd have to become a security researcher and I'm reasonably sure I'd rather die

Amber replied to Foone🏳️‍⚧️

@foone@digipres.club @elfi@social.pixie.town preliminary write up, post write up, how much writing lol? like you write a couple lines of code max in Python and about 2+ separate college essays

💞 eva 💞 replied to Adam

@voltagex @foone ??? Corporate failures with deficient security policies during hardware decommissioning processes... that has nothing to do with OSS or FOSS.

Most of the incidents like that which I've encountered (obtaining e-wasted/grey market used hardware on ebay or freebies) have been with orgs that definitely use MS, the data is right there to prove it when it's happening. It happens to all manner of orgs, but it's not an open source failure.

Adam ♿ replied to 💞 eva 💞

@winterschon it was a joke, playing off that this code had suddenly become open source.

Juliet Merida (she/they) 🚝🏳️‍⚧️🏹🎯

@foone@digipres.club Based on what you've described so far I'd be surprised if you *don't* find their keys.

The Turtle

@foone some models of those NUCs run Mac OSX pretty well.

Zen_Fox.tar.gz

@foone this is like a horror story ohno 😭

Lars Marowsky-Brée 😷

@foone Uhm. This sounds like you can finance the rest of your life with a class action law suit.
Or, if that has data from EU/California citizens, have a noticeable impact to their shareholder value.
I think you're set.

Tod Beardsley 🤘

@larsmb @foone while Foone probably doesn’t have standing to be in the class, they can certainly try to charge a consulting fee to a law firm.

Wilfried Klaebe

@foone Someone needs to be sued to hell and back. And then to hell again.

Niko :neofox_flag_nb_256: :neofox_flag_trans_256:

@foone oh great
flashbacks to the time i discovered home assistant kept my precise location history for two weeks
at least that was on my own hardware
this is somewhat more terrifying

The Turtle

@foone "HEY ALEXA!!! BUY MORE SHIT FROM THAT PLACE!!"

"Buying more shit from that place."

Dominic

@foone oh good grief I feel like I'd fuck up that drive immediately to be rid of it, might as well be toxic waste for how much I don't want that

Andrew

@foone why the hell were they using NUCs as servers?

DEDGirl

@foone and people are giving all access for convenience. I have Alexa, & a security camera. My camera constantly wants access to Alexa. Why? Um, no. 🙄 My camera constantly wants me to join some cloud service where all the videos live forever. The SD card’s plenty, thanks. Stop trying to make me go cloud service. I know there are tons of people using the cloud service just to make the prompts go away. 20 years ago we wouldn’t even talk about pot in front of our TVs!

Go Up