level 1
I don't really understand how hooking the verification function and replacing it with one that always reports success is "bypassing the verifier"?
level 2
What it means is that any future class files that are loaded will not be verified. I would call this a bypass.
Of course, this bypass does require native code access, however this is provided by every JVM through JNI. While it can be disabled by the Security Manager I have never seen this happen in any system, especially since many legitimate libraries also rely on native code.
level 1
See #1 for more info about what the verifier is and why it’s so important, as well as a less interesting exploit of the same purpose
level 1
Really interesting stuff!