• diffusive@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    11 months ago

    Not the commenter but it seems like the parameters of the HTTP Get/Post weren’t protected/checked. The API was likely something like: Email to reset: string(email account to reset) But it accepted something like: [string(email account to reset), string (email to which the reset mail is sent to)]

      • diffusive@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        11 months ago

        Bobby table, this, buffer overflow… Are all similar in spirit.

        Bobby table is a way for hiding the malicious SQL query after a normal query (in that case after the select with “Bobby” you inject the malicious drop table)

        In this case after the normal email (that normally would serve for both identifying the user and for the mail to send the recovering mail), the attacker sends two mails, the first is fo identifying the user the second to send the recovering mail

        In the case of buffer overflow you inject malicious code after normal(-ish) data

        It’s not an XHR attack since for the mail recovery workflow you don’t need an authenticated session.

        To be a bit more compassionate to the developers, this is probably some dynamic typing problem. Probably ruby is “smart” into understand that an array can contain strings after all… So an array of strings is as good as a string… But here we go into static vs dynamic typing… And it’s a bit of religious war (fun fact in 2011 i was advocating with Guido Van Rossum in having at least an optional static typing check in Python - at the time the discussion was how to make python faster/compiled - and he was borderline mocking me 😅 and few years after pytypes but still no compilation at horizon 😂)