How Spoutible’s Leaky API Spurted out a Deluge of Personal Data - eviltoast

Ever hear one of those stories where as it unravels, you lean in ever closer and mutter “No way! No way! NO WAY!” This one, as far as infosec stories go, had me leaning and muttering like never before. Here goes: Last week, someone reached out to me with what

  • elvith@feddit.de
    link
    fedilink
    English
    arrow-up
    5
    ·
    9 months ago

    They basically did. I bet they just used an ORM in the backed and then pointed the API endpoint to the user entity without filtering the fields. This results in a dump of the user table (although row by row indexed by users instead of a full dump)

    • snooggums@kbin.social
      link
      fedilink
      arrow-up
      2
      ·
      9 months ago

      Ahhhh, I was.wondering why they would take the time to set up an API with that data and forgot that almost everything has a way to just dump things into it without needing to be set. I forget because where I work we actively avoid that approach because of risks like this.