It was discovered that DatagramSocket implementation in OpenJDK did not perform any packet source address checks for packets received on connected socket. This could cause an application using DatagramSocket to read a packet from the socket that originates from a different source to the one to which the socket was connected. This problem is caused by BSD socket API oddity, which returns packets form different source if they were queued before socket was connected. This issue can make it easier to perform IP spoofing attacks, as it may allow packets to be processed by an application without packets actually having spoofed source address. It can also lead to limited security manager restrictions bypass. http://docs.oracle.com/javase/7/docs/api/java/net/DatagramSocket.html Acknowledgement: This issue was discovered by Florian Weimer of Red Hat Product Security.
Created attachment 868938 [details] DatagramSocket-connect-9-untested.patch Untested patch against OpenJDK 9. For DatagramSocket, it adds filtering in the socket class itself. For DatagramChannel, the filter is directly in the native code.
Public now via Oracle Critical Patch Update - October 2014. Fixed in Oracle Java SE 5.0u75, 6u85, 7u71, and 8u25. External References: http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA
This issue has been addressed in the following products: Red Hat Enterprise Linux 5 Via RHSA-2014:1633 https://rhn.redhat.com/errata/RHSA-2014-1633.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Red Hat Enterprise Linux 7 Via RHSA-2014:1620 https://rhn.redhat.com/errata/RHSA-2014-1620.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Red Hat Enterprise Linux 7 Red Hat Enterprise Linux 5 Via RHSA-2014:1634 https://rhn.redhat.com/errata/RHSA-2014-1634.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Via RHSA-2014:1636 https://rhn.redhat.com/errata/RHSA-2014-1636.html
IssueDescription: It was discovered that the DatagramSocket implementation in OpenJDK failed to perform source address checks for packets received on a connected socket. A remote attacker could use this flaw to have their packets processed as if they were received from the expected source.
This issue was fixed in IcedTea6 1.13.5 and IcedTea7 2.5.3: http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2014-October/029884.html http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2014-October/029889.html Upstream OpenJDK commit: http://hg.openjdk.java.net/jdk8u/jdk8u/jdk/rev/0798607dd425
This issue has been addressed in the following products: Oracle Java for Red Hat Enterprise Linux 7 Oracle Java for Red Hat Enterprise Linux 6 Oracle Java for Red Hat Enterprise Linux 5 Via RHSA-2014:1658 https://rhn.redhat.com/errata/RHSA-2014-1658.html
This issue has been addressed in the following products: Oracle Java for Red Hat Enterprise Linux 7 Oracle Java for Red Hat Enterprise Linux 6 Oracle Java for Red Hat Enterprise Linux 5 Via RHSA-2014:1657 https://rhn.redhat.com/errata/RHSA-2014-1657.html
This issue has been addressed in the following products: Supplementary for Red Hat Enterprise Linux 5 Supplementary for Red Hat Enterprise Linux 6 Via RHSA-2014:1877 https://rhn.redhat.com/errata/RHSA-2014-1877.html
This issue has been addressed in the following products: Supplementary for Red Hat Enterprise Linux 5 Via RHSA-2014:1876 https://rhn.redhat.com/errata/RHSA-2014-1876.html
This issue has been addressed in the following products: Supplementary for Red Hat Enterprise Linux 6 Via RHSA-2014:1882 https://rhn.redhat.com/errata/RHSA-2014-1882.html
This issue has been addressed in the following products: Supplementary for Red Hat Enterprise Linux 6 Supplementary for Red Hat Enterprise Linux 7 Via RHSA-2014:1880 https://rhn.redhat.com/errata/RHSA-2014-1880.html
This issue has been addressed in the following products: Supplementary for Red Hat Enterprise Linux 5 Supplementary for Red Hat Enterprise Linux 6 Via RHSA-2014:1881 https://rhn.redhat.com/errata/RHSA-2014-1881.html
This issue has been addressed in the following products: Red Hat Satellite Server v 5.6 Via RHSA-2015:0264 https://rhn.redhat.com/errata/RHSA-2015-0264.html