Date: Sun, 25 Aug 2019 18:34:49 +0000 (UTC) From: Dave Cottlehuber <dch@FreeBSD.org> To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r509834 - head/security/vuxml Message-ID: <201908251834.x7PIYnoO096055@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: dch Date: Sun Aug 25 18:34:49 2019 New Revision: 509834 URL: https://svnweb.freebsd.org/changeset/ports/509834 Log: security/vuxml: Document multiple vulnerabilities in www/h2o* http://blog.kazuhooku.com/2019/08/h2o-version-226-230-beta2-released.html PR: 239843 Reported by: Kazuho Oku Approved by: jrm (mentor, implicit) Security: CVE-2019-9512 Security: CVE-2019-9514 Security: CVE-2019-9515 Sponsored by: SkunkWerks, GmbH Modified: head/security/vuxml/vuln.xml Modified: head/security/vuxml/vuln.xml ============================================================================== --- head/security/vuxml/vuln.xml Sun Aug 25 18:31:35 2019 (r509833) +++ head/security/vuxml/vuln.xml Sun Aug 25 18:34:49 2019 (r509834) @@ -58,6 +58,76 @@ Notes: * Do not forget port variants (linux-f10-libxml2, libxml2, etc.) --> <vuxml xmlns="http://www.vuxml.org/apps/vuxml-1">; + <vuln vid="72a5579e-c765-11e9-8052-0028f8d09152"> + <topic>h2o -- multiple HTTP/2 vulnerabilities</topic> + <affects> + <package> + <name>h2o-devel</name> + <range><lt>2.3.0.b2</lt></range> + </package> + </affects> + <description> + <body xmlns="http://www.w3.org/1999/xhtml">; + <p>Jonathon Loomey of Netflix reports:</p> + <blockquote cite="https://www.kb.cert.org/vuls/id/605641/">; + <p>HTTP/2 implementations do not robustly handle abnormal traffic and resource exhaustion</p> + <p>Recently, a series of DoS attack vulnerabilities have been reported on a broad range of HTTP/2 stacks. Among the vulnerabilities, H2O is exposed to the following:</p> + <ul> + <li>CVE-2019-9512 "Ping Flood": The attacker sends continual pings to an HTTP/2 peer, causing the peer to build an internal queue of responses. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both, potentially leading to a denial of service.</li> + <li>CVE-2019-9514 "Reset Flood": The attacker opens a number of streams and sends an invalid request over each stream that should solicit a stream of RST_STREAM frames from the peer. Depending on how the peer queues the RST_STREAM frames, this can consume excess memory, CPU, or both, potentially leading to a denial of service.</li> + <li>CVE-2019-9515 "Settings Flood": The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame is almost equivalent in behavior to a ping. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both, potentially leading to a denial of service.</li> + </ul> + </blockquote> + </body> + </description> + <references> + <url>https://github.com/h2o/h2o/issues/2090</url>; + <url>https://www.kb.cert.org/vuls/id/605641/</url>; + <cvename>CVE-2019-9512</cvename> + <cvename>CVE-2019-9514</cvename> + <cvename>CVE-2019-9515</cvename> + </references> + <dates> + <discovery>2019-08-13</discovery> + <entry>2019-08-25</entry> + </dates> + </vuln> + + <vuln vid="73b1e734-c74e-11e9-8052-0028f8d09152"> + <topic>h2o -- multiple HTTP/2 vulnerabilities</topic> + <affects> + <package> + <name>h2o</name> + <range><lt>2.2.6</lt></range> + </package> + </affects> + <description> + <body xmlns="http://www.w3.org/1999/xhtml">; + <p>Jonathon Loomey of Netflix reports:</p> + <blockquote cite="https://www.kb.cert.org/vuls/id/605641/">; + <p>HTTP/2 implementations do not robustly handle abnormal traffic and resource exhaustion</p> + <p>Recently, a series of DoS attack vulnerabilities have been reported on a broad range of HTTP/2 stacks. Among the vulnerabilities, H2O is exposed to the following:</p> + <ul> + <li>CVE-2019-9512 "Ping Flood": The attacker sends continual pings to an HTTP/2 peer, causing the peer to build an internal queue of responses. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both, potentially leading to a denial of service.</li> + <li>CVE-2019-9514 "Reset Flood": The attacker opens a number of streams and sends an invalid request over each stream that should solicit a stream of RST_STREAM frames from the peer. Depending on how the peer queues the RST_STREAM frames, this can consume excess memory, CPU, or both, potentially leading to a denial of service.</li> + <li>CVE-2019-9515 "Settings Flood": The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame is almost equivalent in behavior to a ping. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both, potentially leading to a denial of service.</li> + </ul> + </blockquote> + </body> + </description> + <references> + <url>https://github.com/h2o/h2o/issues/2090</url>; + <url>https://www.kb.cert.org/vuls/id/605641/</url>; + <cvename>CVE-2019-9512</cvename> + <cvename>CVE-2019-9514</cvename> + <cvename>CVE-2019-9515</cvename> + </references> + <dates> + <discovery>2019-08-13</discovery> + <entry>2019-08-25</entry> + </dates> + </vuln> + <vuln vid="e7392840-c520-11e9-a4ef-0800274e5f20"> <topic>gitea -- multiple vulnerabilities</topic> <affects>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201908251834.x7PIYnoO096055>