Flock cameras are riddled with security vulnerabilities and hard-coded credentials. Here's my analysis of today's @ddosecrets Flock leak https://micahflee.com/flock-cameras-are-riddled-with-security-vulnerabilities-and-hard-coded-credentials/
RE: https://infosec.exchange/@micahflee/117282688510612709
*Jabba the Hut laugh* ho ho ho ho
Flock API key = ĐаJ3FgupAm8RrDJW3ĐĐgT9X7Ft27eVaD
This discussion in the â binutilsâ mailing list is interesting. I had no idea the target binary could easily detect and interact with Valgrind directly. Valgrind provides a header (â valgrind.hâ ) to help the client do exactly that.
A change in the â gasâ assembler that optimized â xchg reg, regâ to â mov reg, regâ in specific conditions broke Valgrind. That optimization yielded more efficient code because the â movâ instruction is cheaper.
Valgrind implements a trapdoorâa "hypercall"-like mechanism between the target and Valgrind, officially called the Client Request Mechanism. This trapdoor relies on a magic sequence of preamble instructions followed immediately by an â xchgâ instruction.
Because the â gasâ optimization replaced that â xchgâ with a â movâ , Valgrind was seeing a â movâ and failing to recognize the request.
The problem occurred both when Valgrind itself was built with the optimization, and when target binaries were built with the client-request mechanism through the â valgrind.hâ file. â systemdâ was one of the affected projects. Because there are many projects out there built with the Valgrind header that hardcode the expectation of an â xchgâ instruction, the optimization had to be reverted.
That problem resulted in the following error in Valgrind:
vex amd64->IR: unhandled instruction bytes: 0x48 0xC1 0xC7 0x3 0x48 0xC1 0xC7 0xD 0x48 0xC1
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==568970== valgrind: Unrecognised instruction at address 0x484f1e9.
[PATCH 1/2] x86: optimize XCHG to MOV for same-register forms
https://sourceware.org/pipermail/binutils/2026-July/149944.html
x86: Disable XCHG to MOV optimization
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=49652cd8ecbb4c305a9a0e9099016edb138e6953
Using and understanding the Valgrind core: Advanced Topics
https://valgrind.org/docs/manual/manual-core-adv.html
The entity drifted dreamlessly through space, as it had for aeons. It woke when it neared a star. Scanned for planets, life, signs of technology.
Having found all, it analyzed and decoded radio emissions, then composed a message to send.
"My hovercraft is full of feels."
It resumed dormancy.
James Forshaw at @44CON found an old email about the Morris worm.
Sorry my picture actually shows it in rainbow đ. colors !!
In 1983, Gavilan Computer Corporation introduced what it dubbed "the first mobile computer." The Gavilan was a briefcase-sized machine with a 3-inch disk drive, an 8-line display, and promised 7 hours of battery life. But Gavilan was a bust. It burned $31 million in venture capital and only managed to ship about 1,000 machines before filing for bankruptcy.
I detailed Gavilan's history in a 2024 podcast. You can read the entire transcript here:
https://www.computerchronicles.blog/transcript-gavilans-31-million-ride-to-bankruptcy/
Patch your Cisco ISE. CVE-2026-76460 a perfect 10 and is EITW. đ„ł
The Cisco PSIRT is aware of active exploitation of this vulnerability. Cisco strongly recommends that customers upgrade to a fixed software release to remediate this vulnerability.
New: hackers tore down a Flock camera and managed to extract the software running on it. We then analyzed the data to find how a Flock camera really track cars and people. The amount of data this single camera gathered in a short period was huge, 50,000+ vehicles https://www.404media.co/hackers-stole-flocks-camera-software-revealing-how-the-company-tracks-cars-and-people-2/