News for hackers. Stuff that matters.
Re:Zero-day in Sign in with Apple by fouc on Saturday May 30, 2020 @11:29PM (#23366936)
Oh man, that is classic sloppy web development.

It's often so easy to reach for the values in the params/payload first because you're already working with them, instead of remembering to use the session values instead.

This would be a great audit to do for entire codebases.. Just check all places that are using params/payload values and see if there's actually already a session value that should be used instead.

Re:Zero-day in Sign in with Apple by rags2riches on Sunday May 31, 2020 @01:57AM (#23367542)
Don't just audit. Strengthen the critical APIs with types. A user provided string is not the same type as an authentic identity. Make the developer be explicit about the critical mistake about to be made. Perl had this down decades ago with the tainted checks.
Re:Zero-day in Sign in with Apple by amenod on Sunday May 31, 2020 @05:46AM (#23368394)
This, thousand times. Don't just fix the bug, fix the process that led to the bug. Developers are (usually) not malicious, but we are often working with tooling which makes mistakes easy to do, difficult to detect and grave in consequences. Fix the tooling, not just the bug.
Re:Zero-day in Sign in with Apple by mehrdadn on Sunday May 31, 2020 @12:04AM (#23367091)
I wonder if encoding the query params with some dumb encoding (maybe a custom variant of base64?) and forcing decoding at every usage site would make it inconvenient enough to cause programmers to use the session values instead?