A remote attacker can supply specially crafted transfer-encoding chunks to Eclipse Jetty that may bypass the authorization checks of an intermediary caching proxy.

In Eclipse Jetty, versions 9.2.x and older, 9.3.x (all configurations), and 9.4.x (non-default configuration with RFC2616 compliance enabled), transfer-encoding chunks are handled poorly. The chunk length parsing was vulnerable to an integer overflow. Thus a large chunk size could be interpreted as a smaller chunk size and content sent as chunk body could be interpreted as a pipelined request. If Jetty was deployed behind an intermediary that imposed some authorization and that intermediary allowed arbitrarily large chunks to be passed on unchanged, then this flaw could be used to bypass the authorization imposed by the intermediary as the fake pipelined request would not be interpreted by the intermediary as a request.

Notes:

Brocade SANnav contains the affected open source routines, but these routines are not in the execute path accessible to users. While Brocade SANnav is not vulnerable to this CVE, a security update is being provided in SANnav versions v2.2.2a and v2.3.0 to remove the vulnerable component

Products Confirmed Not Affected

No Brocade Fibre Channel products are affected by this vulnerability

Solution

While Brocade SANnav is not exploitable, a security update is provided in SANnav v2.2.2a and v2.3.0 to remove the vulnerable components.