Hacker News

New stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. What If You Could Do It All Over?(newyorker.com ↗)
    discuss
  2. Permission to Live (In Japan)(buttondown.com/whatever_jamie ↗)
    1comments
  3. SpaceX's next Starship launch is Sept. 22, aims to reach orbit for first time(space.com ↗)
    discuss
  4. The End of Verygoodsoftwarenotvirus.ru(verygoodsoftwarenotvirus.dev ↗)
    discuss
  5. Asking Authors About Their Own Papers(medium.com/tmlrorg ↗)
    discuss
  6. Next-gen gravitational wave detectors could spot the first black holes(phys.org ↗)
    discuss
  7. US interest rates raised for first time in three years(bbc.com ↗)
    discuss
  8. My website charged AI agents a penny per page. I watched Claude pay it(suganthan.com ↗)
    1comments
  9. Show HN: Helping agents break out of their sandboxes in a monitorable way(sparrowsystems.co ↗)
    discuss
  10. Encouraging Deception in Compaction Summaries(alignment.openai.com ↗)
    discuss
  11. vLLM: Jev-like mode for the DiffusionGemma model(github.com/vllm-project ↗)
    discuss
  12. DeepSeek's Parent Company(high-flyer.cn ↗)
    discuss
  13. The Flask Mega-Tutorial, Part I: Hello, World(miguelgrinberg.com ↗)
    discuss
  14. Typesafe.ai Jev Open Source Alternative Qwen-2.5-1B-RLCD(huggingface.co ↗)
    discuss
  15. AI Debt vs. Treasuries(ft.com ↗)
    1comments
  16. "WeWorm": Zero-click worm could have taken over all WeChat accounts(heise.de ↗)
    discuss
  17. Dwarf Star Support for Qwen3.8 Flash Next(github.com/antirez ↗)
    discuss
  18. YuE2 – Frontier music generation with editable scores(github.com/multimodal-art-projection ↗)
    discuss
  19. Pactora – AI contract review built by a lawyer, not engineers(pactora.uk ↗)
    discuss
  20. Automattic says CEO Mullenweg was gone and back inside 33 hours. What happened?(thenewstack.io ↗)
    discuss
  21. OpenSpec – A lightweight and configurable AI spec framework(openspec.dev ↗)
    3comments
  22. Calculator for Australian take-home pay, tax and super(auspaycalculator.org ↗)
    discuss
  23. How much does one hour of bots cost on Cloudflare Workers?(gfuse.dev ↗)
    discuss
  24. Plans for Agents (and Humans)(hive.technology ↗)
    discuss
  25. Australia says it could follow Canada in forging deeper ties with EU(independent.co.uk ↗)
    4comments
  26. Fossil tooth analysis confirms Tyrannosaurus rex was warm-blooded(cnn.com ↗)
    discuss
  27. The mascots, design and visual history of Wikipedia(itsnicethat.com ↗)
    discuss
  28. 60%+ of Japan firms with foreign workers would struggle without overseas hiring(japantimes.co.jp ↗)
    discuss
  29. Show HN: DroidPutter – Run Cardputer Apps on Android via USB OTG(github.com/fcavalcantirj ↗)
    discuss
  30. Why building a Rust LSP is hard(rust-glancer.github.io ↗)
    discuss

Flock cameras are riddled with security vulnerabilities and hardcoded creds

38 pointsby 1h agomicahflee.com
5 comments
1h agoHN ↗

tldr from my skim, the two worst things:

* Probably vulnerable to CVEs that were patched in 2018 and 2021.

* Generates API key to phone home based only on its own MAC address.

53m agoHN ↗

Having hardcoded credentials is a sign of total incompetence. In this case at least it wasn't a password, but an API key which can be used to request credentials (stored in plaintext) which look like they'd get you access Flock's servers. Not quite as bad as a hardcoded admin password, and it's not clear what you'd be able to do if you did authenticate successfully as a camera, but its worrying enough. There have been enough vulnerabilities found in Flock's systems that it's pretty clear they aren't concerned about their security and it's plainly obvious that they don't care at all about our privacy or security.

Even if we decided that this level of mass surveillance on the American public was acceptable to us, Flock Safety/Flock Group as already demonstrated that they can't and shouldn't be trusted to implement it.

48m agoHN ↗

I don't think having credentials stored on the device is all that fatal. The device has to read them back, after all. What they did, however, is much worse: the credentials come from the MAC address. So they're literally broadcasted on every network packet.