| Package | Affected versions | Patched versions |
|---|---|---|
| org.eclipse.jetty:jetty-server | ≥ 9.3.0, < 9.3.24.v20180605< 9.2.25.v20180606 | 9.3.24.v201806059.2.25.v20180606 |
| jetty | ≥ 9.3.0, < 9.3.24≥ 9.4.0, < 9.4.11≤ 9.2.26 | 9.3.249.4.11 |
| xp p9000 command view | ≥ 8.4.0-00, < 8.6.2-00 | 8.6.2-00 |
| e-series santricity os controller | ≥ 11.0, ≤ 11.50.1 | |
| oncommand system manager | = 3.x | |
| oncommand unified manager | < 5.2.4 | 5.2.4 |
| snap creator framework | < 4.3.3 | 4.3.3 |
| snapcenter | < 4.1p3 | 4.1p3 |
| snapmanager | < 3.4.2 | 3.4.2 |
| rest data services | = 11.2.0.4= 12.1.0.2= 12.2.0.1= 18c | |
| retail xstore point of service | = 15.0= 16.0= 17.0= 7.1 |
In Eclipse Jetty, versions 9.2.x and older, 9.3.x, 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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free