News for hackers. Stuff that matters.
Re:Patch Critical Cryptographic Vulnerability in Microsoft W... by tptacek on Tuesday January 14, 2020 @04:59PM (#22049676)
There's a history of vulnerabilities like these, in some of the most important crypto libraries. For instance: until 2008, NSS, the TLS library used by Firefox, couldn't properly validate RSA signatures from e=3 RSA keys (it wasn't validating the full signature block, but rather parsing it and looking for the embedded hash). For e=3 roots, which were readily available at the time, you could simply build any signature block you wanted and then take its cube root.
Re:Patch Critical Cryptographic Vulnerability in Microsoft W... by Herrera on Tuesday January 14, 2020 @05:21PM (#22049835)
Bleichenbacher'06 never dies.
Re:Patch Critical Cryptographic Vulnerability in Microsoft W... by CiPHPerCoder on Tuesday January 14, 2020 @07:13PM (#22050576)
Neither does BB'98
Re:Patch Critical Cryptographic Vulnerability in Microsoft W... by baby on Tuesday January 14, 2020 @07:27PM (#22050669)
Can’t wait for BB20
Re:Patch Critical Cryptographic Vulnerability in Microsoft W... by gonnabezuul on Tuesday January 14, 2020 @06:20PM (#22050254)
Interesting. Were there any similar vulnerabilities in Windows XP's crypto libraries?
Re:Patch Critical Cryptographic Vulnerability in Microsoft W... by tptacek on Tuesday January 14, 2020 @06:26PM (#22050280)
There have been crypto vulnerabilities in Windows libraries before, but not the e=3 vulnerability; CryptoAPI parsed RSA signatures back-to-front, and so sidestepped the issue.