Kerberos Bug Introduced in d777e2918a77?
rob.mckenna at oracle.com
Wed Apr 22 16:21:22 UTC 2015
Thanks for the report, I'm cc'ing the security-dev alias.
On 22/04/15 13:10, Daniel Jones wrote:
> Hi all,
> Apologies if this is the wrong mailing list - please direct me to the
> correct one if so.
> I believe I've found a bug in OpenJDK 1.8.0_40, introduced in commit
> The change introduced on line 548 means that an authentication mechanism is
> only accepted if the OID of the mechanism desired is the *first* in the
> list of mechanisms specified as acceptable in the incoming ticket.
> In the case of my current client their service tickets are specifying 4
> acceptable mechanism OIDs, but the only available mechanism's OID appears
> second on that list. So whilst the server *can *satisfy the ticket, the
> code change on line 548 prevents this from happening.
> Using the same server code, the same Kerberos KDC, and OpenJDK 1.8.0_31,
> everything works. Changing only the JDK results in the mechContext not
> being properly populated, which in turn causes a NullPointerException from
> some Spring Security Kerberos code.
> Has anyone else experienced this?
More information about the security-dev