5 ms·
If the vulnerability exists in Java 5, 6 and 7, it seems likely that the underlying problem is pretty old and not a recent development. Version 1.5.0_22 seems t
by brown9-2 14y ago
If the vulnerability exists in Java 5, 6 and 7, it seems likely that the underlying problem is pretty old and not a recent development. Version 1.5.0_22 seems to have been released some time around 2009, and that was the end-of-life release for "Java 5" - it's earlier versions were years before this.
- blinkingled 14y agoGood point - but still, isn't it taking Oracle longer to patch the vulnerabilities? (Last one they knew for what - 4 months?)
- eckyptang 14y agoThis is normal for Oracle and has been for at least 20 years. They are too busy milking people for new contracts rather than looking after their existing customers.