First published: Mon Feb 15 2016(Updated: )
A vulnerability was found in a way nghttp2 processes incoming packets. Nghttpd, nghttp, and libnghttp2_asio applications do not limit the memory usage for the incoming HTTP header field. If peer sends specially crafted HTTP/2 HEADERS frames and CONTINUATION frames, they will crash with out of memory error. Upstream report and fix: <a href="https://github.com/tatsuhiro-t/nghttp2/releases/tag/v1.7.1">https://github.com/tatsuhiro-t/nghttp2/releases/tag/v1.7.1</a>
Credit: cret@cert.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/nghttp2 | <1.7.1 | 1.7.1 |
CentOS Libnghttp2 | <1.7.1 | |
Red Hat Fedora | =22 | |
Red Hat Fedora | =23 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-1544 is classified as a medium severity vulnerability affecting nghttp2 applications.
Exploiting CVE-2016-1544 can lead to application crashes due to out of memory errors when processing malicious HTTP/2 packets.
To fix CVE-2016-1544, update nghttp2 to version 1.7.1 or later.
CVE-2016-1544 affects nghttp2, nghttpd, and libnghttp2_asio versions prior to 1.7.1.
There are no known workarounds for CVE-2016-1544, so updating to the fixed version is recommended.