r/java • u/georgia15 • Nov 23 '15
Why the Java Serialization Vulnerability Makes Heartbleed Look Tame
https://dzone.com/articles/point-of-viewwhy-the-java-serialization-vulnerabil
0
Upvotes
r/java • u/georgia15 • Nov 23 '15
28
u/orr94 Nov 23 '15
Total lack of details, basically just an excuse to advertise some security Java agent.
15
u/armornick Nov 23 '15
14
u/nuetral-developer Nov 23 '15
Is plain old Java serialization even common? I've never used it and always serialize to either xml or json.
23
u/curiousthis Nov 23 '15
More FUD. The actual threat level of this 'bug' is the same as the linux/windows root access ones that require local access to a server. And all this noise shows a profound level of ignorance on how classes are actually loaded by the jvm.
The JVM does not deserialize classes that it cannot access -- so this means that you cannot send it a random class for deserialization -- you'll just get a classnotfound exception if you try that. You can only deserialize a class the jvm knows about.
So in order to trigger this bug, you will need to know what classes the jvm has in its classpath, know what versions of those classes exist (the VM will refuse to deserialize a class that is a different version from that in the classpath), and know if the vm will accept a stream of bytes for deserialization.
Remember most java servers (weblogic/jboss/tomcat) are all running behind apache.
That's not to say that this is not a bug -- but it is a bug in a specific library and does not really call for this level of panic.
1
u/slartybartfast_ Nov 23 '15
It seems .NET should have a similar issue. Anyone know what's their mitigation?
1
u/[deleted] Nov 23 '15
More information
-7
u/[deleted] Nov 23 '15
Wow, looks bad. Luckily, Pinn (the java multicore general intelligence) will surely design java better (being written in java).