Re:Auth0 JWT Auth Bypass: Case-Sensitive Blacklisting Is Har...
by thinkshiv on Thursday April 16, 2020 @08:16PM
(#22894973)
Hi all - Shiv from Auth0. I am the CPO and wanted to share some additional context here. On July 31st 2019, at 5:11 am, we received an email from Insomnia reporting a service vulnerability. By 11:00 pm the same day, we had fixed the issue in production. We analyzed the logs and validated that no one exploited the vulnerability. More details from our CSO here: https://auth0.com/blog/insomnia-security-disclosure/?utm_sou.... Thanks to Insomnia for reporting the vulnerability and their partnership in coordinated disclosure. We appreciate the continued feedback from the security community-at-large to ensure we are providing the most secure platform for our global customers.
[ Parent
| on HN ]
Re:Auth0 JWT Auth Bypass: Case-Sensitive Blacklisting Is Har...
by treve on Friday April 17, 2020 @12:07AM
(#22896108)
Why did your implementation have a case-sensitive check for a fixed list of algorithms, and why are you blacklisting vs. whitelisting acceptable algorithms? 'Old, stable' codebase or not... this is production code for a security product and seems like something that would be picked up during an audit.