Bug 2318526 (CVE-2024-21208)

Summary: CVE-2024-21208 JDK: HTTP client improper handling of maxHeaderSize (8328286)
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: ahughes, caswilli, chazlett, cmoore, gmccullo, jsamir, kaycoth, kholdawa, khosford, lphiri, mbalao, neugens, pjindal, security-response-team, sraghupu, sthirugn, vkrizan
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Deadline: 2024-10-15   

Description OSIDB Bzimport 2024-10-14 13:25:55 UTC
Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator).

Oracle Critical Patch Update Advisory - October 2024:
https://www.oracle.com/security-alerts/cpuoct2024.html#AppendixJAVA

Comment 1 errata-xmlrpc 2024-10-16 11:09:48 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7 Extended Lifecycle Support

Via RHSA-2024:8120 https://access.redhat.com/errata/RHSA-2024:8120

Comment 2 errata-xmlrpc 2024-10-16 12:04:44 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8
  Red Hat Enterprise Linux 8.8 Extended Update Support
  Red Hat Enterprise Linux 8.2 Advanced Update Support
  Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.4 Update Services for SAP Solutions
  Red Hat Enterprise Linux 8.4 Telecommunications Update Service
  Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions
  Red Hat Enterprise Linux 8.6 Telecommunications Update Service
  Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions
  Red Hat Enterprise Linux 9.2 Extended Update Support
  Red Hat Enterprise Linux 9

Via RHSA-2024:8121 https://access.redhat.com/errata/RHSA-2024:8121

Comment 3 errata-xmlrpc 2024-10-16 14:22:03 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8
  Red Hat Enterprise Linux 9

Via RHSA-2024:8127 https://access.redhat.com/errata/RHSA-2024:8127

Comment 4 errata-xmlrpc 2024-10-16 15:01:50 UTC
This issue has been addressed in the following products:

  Red Hat Build of OpenJDK 8u432

Via RHSA-2024:8118 https://access.redhat.com/errata/RHSA-2024:8118

Comment 5 errata-xmlrpc 2024-10-16 15:02:05 UTC
This issue has been addressed in the following products:

  Red Hat Build of OpenJDK 11.0.25

Via RHSA-2024:8123 https://access.redhat.com/errata/RHSA-2024:8123

Comment 6 errata-xmlrpc 2024-10-16 15:02:13 UTC
This issue has been addressed in the following products:

  Red Hat Build of OpenJDK 11.0.25

Via RHSA-2024:8122 https://access.redhat.com/errata/RHSA-2024:8122

Comment 7 errata-xmlrpc 2024-10-16 15:03:02 UTC
This issue has been addressed in the following products:

  Red Hat Build of OpenJDK 8u432

Via RHSA-2024:8119 https://access.redhat.com/errata/RHSA-2024:8119

Comment 8 errata-xmlrpc 2024-10-16 15:12:07 UTC
This issue has been addressed in the following products:

  Red Hat Build of OpenJDK 17.0.13

Via RHSA-2024:8125 https://access.redhat.com/errata/RHSA-2024:8125

Comment 9 errata-xmlrpc 2024-10-16 15:12:22 UTC
This issue has been addressed in the following products:

  Red Hat Build of OpenJDK 17.0.13

Via RHSA-2024:8126 https://access.redhat.com/errata/RHSA-2024:8126

Comment 10 errata-xmlrpc 2024-10-16 15:16:31 UTC
This issue has been addressed in the following products:

  Red Hat Build of OpenJDK 21.0.5

Via RHSA-2024:8128 https://access.redhat.com/errata/RHSA-2024:8128

Comment 11 errata-xmlrpc 2024-10-16 15:16:39 UTC
This issue has been addressed in the following products:

  Red Hat Build of OpenJDK 21.0.4

Via RHSA-2024:8129 https://access.redhat.com/errata/RHSA-2024:8129

Comment 12 errata-xmlrpc 2024-10-16 15:37:26 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions
  Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions
  Red Hat Enterprise Linux 8.6 Telecommunications Update Service
  Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.4 Update Services for SAP Solutions
  Red Hat Enterprise Linux 8.4 Telecommunications Update Service
  Red Hat Enterprise Linux 8
  Red Hat Enterprise Linux 8.8 Extended Update Support
  Red Hat Enterprise Linux 9.2 Extended Update Support
  Red Hat Enterprise Linux 9

Via RHSA-2024:8124 https://access.redhat.com/errata/RHSA-2024:8124

Comment 13 errata-xmlrpc 2024-10-16 18:45:43 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8
  Red Hat Enterprise Linux 8.8 Extended Update Support
  Red Hat Enterprise Linux 8.2 Advanced Update Support
  Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.4 Update Services for SAP Solutions
  Red Hat Enterprise Linux 8.4 Telecommunications Update Service
  Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions
  Red Hat Enterprise Linux 8.6 Telecommunications Update Service
  Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions
  Red Hat Enterprise Linux 9.2 Extended Update Support
  Red Hat Enterprise Linux 9

Via RHSA-2024:8117 https://access.redhat.com/errata/RHSA-2024:8117

Comment 14 errata-xmlrpc 2024-10-17 14:13:13 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7 Extended Lifecycle Support

Via RHSA-2024:8116 https://access.redhat.com/errata/RHSA-2024:8116

Comment 17 Mauro Matteo Cascella 2024-10-21 16:01:39 UTC
Relevant excerpt from release notes:

-> New Default Limits in the JDK HTTP Implementations (JDK-8328286 (not public))
New, default limits have been added to HTTP in the JDK.

The JDK built-in implementation of the URL protocol handler for HTTP (HttpURLConnection) now has a default limit on the maximum response headers size that will be accepted from a remote party. The limit is set by default at 384kB (393216 bytes) and is computed as the cumulative size of all header names and header values plus an overhead of 32 bytes per header name value pair.

The default value of the limit can be changed by specifying a positive value with the jdk.http.maxHeaderSize system property on the command line, or in the conf/net.properties file. A negative or zero value is interpreted as no limit. If the limit is exceeded, the request will fail with a protocol exception.

The JDK built-in implementation of the com.sun.net.httpserver.HttpServer implements a similar limit for the maximum request header size the server is prepared to accept. The HttpServer limit can be changed by specifying a positive value with the sun.net.httpserver.maxReqHeaderSize system property on the command line. A negative or zero value is interpreted as no limit. The limit is set by default at 384kB (393216 bytes) and the size is computed in the same way as explained above. If the limit is exceeded, the connection is closed.