USN-7098-1: OpenJDK 17 vulnerabilities
11 November 2024
Several security issues were fixed in OpenJDK 17.
Releases
Packages
- openjdk-17 - Open Source Java implementation
Details
Andy Boothe discovered that the Networking component of OpenJDK 17 did not
properly handle access under certain circumstances. An unauthenticated
attacker could possibly use this issue to cause a denial of service.
(CVE-2024-21208)
It was discovered that the Hotspot component of OpenJDK 17 did not properly
handle vectorization under certain circumstances. An unauthenticated
attacker could possibly use this issue to access unauthorized resources
and expose sensitive information. (CVE-2024-21210, CVE-2024-21235)
It was discovered that the Serialization component of OpenJDK 17 did not
properly handle deserialization under certain circumstances. An
unauthenticated attacker could possibly use this issue to cause a denial
of service. (CVE-2024-21217)
It was discovered that the Hotspot component of OpenJDK 17 was not properly
bounding certain UTF-8 strings, which could lead to a buffer overflow. An
attacker could possibly use this issue to cause a denial of service or
execute arbitrary code. This issue was only addressed in Ubuntu 18.04 LTS.
(CVE-2024-21131)
It was discovered that the Hotspot component of OpenJDK 17 could be made to
run into an infinite loop. If an automated system were tricked into
processing excessively large symbols, an attacker could possibly use this
issue to cause a denial of service. This issue was only addressed in Ubuntu
18.04 LTS. (CVE-2024-21138)
It was discovered that the Hotspot component of OpenJDK 17 did not properly
perform range check elimination. An attacker could possibly use this issue
to cause a denial of service, execute arbitrary code or bypass Java
sandbox restrictions. This issue was only addressed in Ubuntu 18.04 LTS.
(CVE-2024-21140)
Sergey Bylokhov discovered that OpenJDK 17 did not properly manage memory
when handling 2D images. An attacker could possibly use this issue to
obtain sensitive information. This issue was only addressed in Ubuntu
18.04 LTS. (CVE-2024-21145)
It was discovered that the Hotspot component of OpenJDK 17 incorrectly
handled memory when performing range check elimination under certain
circumstances. An attacker could possibly use this issue to cause a
denial of service, execute arbitrary code or bypass Java sandbox
restrictions. This issue was only addressed in Ubuntu 18.04 LTS.
(CVE-2024-21147)
Update instructions
The problem can be corrected by updating your system to the following package versions:
Ubuntu 24.10
-
openjdk-17-jdk
-
17.0.13+11-2ubuntu1~24.10
-
openjdk-17-jdk-headless
-
17.0.13+11-2ubuntu1~24.10
-
openjdk-17-jre
-
17.0.13+11-2ubuntu1~24.10
-
openjdk-17-jre-headless
-
17.0.13+11-2ubuntu1~24.10
-
openjdk-17-jre-zero
-
17.0.13+11-2ubuntu1~24.10
Ubuntu 24.04
-
openjdk-17-jdk
-
17.0.13+11-2ubuntu1~24.04
-
openjdk-17-jdk-headless
-
17.0.13+11-2ubuntu1~24.04
-
openjdk-17-jre
-
17.0.13+11-2ubuntu1~24.04
-
openjdk-17-jre-headless
-
17.0.13+11-2ubuntu1~24.04
-
openjdk-17-jre-zero
-
17.0.13+11-2ubuntu1~24.04
Ubuntu 22.04
-
openjdk-17-jdk
-
17.0.13+11-2ubuntu1~22.04
-
openjdk-17-jdk-headless
-
17.0.13+11-2ubuntu1~22.04
-
openjdk-17-jre
-
17.0.13+11-2ubuntu1~22.04
-
openjdk-17-jre-headless
-
17.0.13+11-2ubuntu1~22.04
-
openjdk-17-jre-zero
-
17.0.13+11-2ubuntu1~22.04
Ubuntu 20.04
-
openjdk-17-jdk
-
17.0.13+11-2ubuntu1~20.04
-
openjdk-17-jdk-headless
-
17.0.13+11-2ubuntu1~20.04
-
openjdk-17-jre
-
17.0.13+11-2ubuntu1~20.04
-
openjdk-17-jre-headless
-
17.0.13+11-2ubuntu1~20.04
-
openjdk-17-jre-zero
-
17.0.13+11-2ubuntu1~20.04
Ubuntu 18.04
-
openjdk-17-jdk
-
17.0.13+11-2ubuntu1~18.04.2
Available with Ubuntu Pro
-
openjdk-17-jdk-headless
-
17.0.13+11-2ubuntu1~18.04.2
Available with Ubuntu Pro
-
openjdk-17-jre
-
17.0.13+11-2ubuntu1~18.04.2
Available with Ubuntu Pro
-
openjdk-17-jre-headless
-
17.0.13+11-2ubuntu1~18.04.2
Available with Ubuntu Pro
-
openjdk-17-jre-zero
-
17.0.13+11-2ubuntu1~18.04.2
Available with Ubuntu Pro
This update uses a new upstream release, which includes additional bug
fixes. After a standard system update you need to restart Java
applications to make all the necessary changes.