5 ms·
> create a payload with any of those classes, and send it to the server. But on a deeper level, if a programmer doesn't know anything about security, then this
by chii 8y ago
> create a payload with any of those classes, and send it to the server.
But on a deeper level, if a programmer doesn't know anything about security, then this sort of hole will continue to happen even if java serialization is disabled (just a bit harder to screw up). I m not that big of a fan of making security decisions without programmer's input, since you'd assume a professional programmer should know better anyway.
- MBCook 8y agoFrom the article it sounds like you’ll only be able to use the replacement on Java data classes, sort of like JSON structures or C structs. Since there won’t be any code that gets executed, that particular vector is closed. Of course if the code reading that object does something stupid…
- dwaite 8y agoThe security hole is in the design of java serialization. Any class marked serializable (in your code, your included libraries, or the JVM itself) is a potential security vulnerability as soon as you use this feature. Mark estimated that over half of JRE/JDK vulnerabilities have been due to Serialization. Recent releases added an opt-in feature to filter which classes are allowed to be deserialized, but there's still a horrible amount of open, unauthenticated network ports that take in serialized java. The programmer trying to get the same failures in a post-serialization world would presumably have to find or build a new system with the same design issues.
- usrusr 8y ago> Any class marked serializable (in [...] included libraries [...]) This is the big one: as soon as you deserialize incoming data, any library on the classpath becomes a potential source of remote-callable snippets. And when a vulnerability resides in a library, exploits will tend to be compatible across applications, which makes them far more likely to actually hit you than any custom weaknesses.
- simias 8y agoProgrammers should be more careful but then again footguns exist (or in this case legcannons). You shouldn't trust any 3rd party data before validation but how do you validate it if you can't even deserialize it to see what it contains? It's silly.