Need help?
<- Back

Comments (42)

  • RobMurray
    It's really sad that getting a shell on a device you own is now considered a vulnerability.
  • mzajc
    This is a very neat and approachable write-up, but is the final result really a hack? If I understand correctly, you're getting an unprivileged shell on a device you own and have paired with your smartphone; more or less equivalent to installing a terminal emulator on your smartphone, except it's smart glasses in this case.Should the ability to own one's devices really be treated as a vulnerability and reported to security teams?
  • voidUpdate
    > "I used android.media.ToneGenerator in my DAT APK to signal which part of the code was executing:"I've heard that morse code allows for easier debugging than beep counting, if you have to use audio. Not had a chance to put it into practice myself, but since digits especially are simple in morse code, it might be useful to someone
  • malicka
    Maybe I’ve still got the old PS3/PSP-exploit mentality, but reporting an arbitrary code execution vuln to the OEM is kind of sad… that deliberately closes a door for people to use their devices as they see fit.Of course, the “don’t update after this firmware version” bit would always be the case (since any widely-distributed such vuln will be patched eventually), but deliberately moving the timeline to the left is sad.
  • frenchsalmon
    Nice. How robust is this with software upgrades though? Also looks like arbitrary code execution in the app sandbox, so no persistance?
  • Ouman
    Imagine shipping a firmware update to enforce APK signatures, only for the enforcement itself to be controlled by an unauthenticated config value
  • iAMkenough
    Regardless of the exploit, I wonder if there's a market for similar looking smartglasses that let you do whatever you want. Some competition in the space would be good for inviting regulation.
  • croes
  • s907408
    [flagged]