First published: Thu Sep 13 2018(Updated: )
In some circumstances Undertow can serve data from a random ByteBuffer, this is due to an incomplete fix for UNDERTOW-438. Basically if all the headers are not written out in the first write() call then the code that handles flushing the buffer will always write out the full contents of the writevBuffer buffer, which may contain data from previous requests. Upstream bug: <a href="https://issues.jboss.org/browse/JBEAP-15428">https://issues.jboss.org/browse/JBEAP-15428</a> Upstream patch: <a href="https://github.com/jbossas/redhat-undertow/commit/e65ad5b410f95b166ff04f876e22f873e9b4ce62">https://github.com/jbossas/redhat-undertow/commit/e65ad5b410f95b166ff04f876e22f873e9b4ce62</a>
Affected Software | Affected Version | How to fix |
---|---|---|
Undertow |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-1628702 is classified as moderate.
To fix REDHAT-BUG-1628702, update to the latest patched version of Red Hat Undertow.
REDHAT-BUG-1628702 is caused by an incomplete fix for a previous issue, leading to improper data serving from a random ByteBuffer.
All versions of Red Hat Undertow prior to the patch addressing REDHAT-BUG-1628702 are affected.
Currently, there are no known workarounds for REDHAT-BUG-1628702 other than applying the fix.