645 matches found
Header Splitting Attack
firefox:sid is vulnerable to header splitting attack. Firefox incorrectly accepted a newline in a HTTP/3 header, interpreting it as two separate headers, allowing a header splitting attack against servers using HTTP/3...
USN-5047-1 firefox vulnerability
It was discovered that Firefox could be made to incorrectly accept newlines in HTTP/3 response headers. If a user were tricked into opening a specially crafted website, an attacker could exploit this to conduct header splitting attacks...
USN-5047-1: Firefox vulnerability
It was discovered that Firefox could be made to incorrectly accept newlines in HTTP/3 response headers. If a user were tricked into opening a specially crafted website, an attacker could exploit this to conduct header splitting attacks...
Ubuntu 18.04 LTS / 20.04 LTS : Firefox vulnerability (USN-5047-1)
The remote Ubuntu 18.04 LTS / 20.04 LTS host has packages installed that are affected by a vulnerability as referenced in the USN-5047-1 advisory. It was discovered that Firefox could be made to incorrectly accept newlines in HTTP/3 response headers. If a user were tricked into opening a speciall...
CVE-2021-29991
The Mozilla Foundation Security Advisory describes this flaw as: Firefox incorrectly accepted a newline in a HTTP/3 header, interpretting it as two separate headers. This allowed for a header splitting attack against servers using HTTP/3...
CVE-2021-29991
Firefox incorrectly accepted a newline in a HTTP/3 header, interpretting it as two separate headers. This allowed for a header splitting attack against servers using HTTP/3. This vulnerability affects Firefox 91.0.1 and Thunderbird 91.0.1...
UBUNTU-CVE-2021-29991
Firefox incorrectly accepted a newline in a HTTP/3 header, interpretting it as two separate headers. This allowed for a header splitting attack against servers using HTTP/3. This vulnerability affects Firefox 91.0.1 and Thunderbird 91.0.1...
Mozilla Firefox < 91.0.1
The version of Firefox installed on the remote Windows host is prior to 91.0.1. It is, therefore, affected by a vulnerability as referenced in the mfsa2021-37 advisory. - Firefox incorrectly accepted a newline in a HTTP/3 header, interpreting it as two separate headers. This allowed for a header...
Mozilla Thunderbird < 91.0.1
The version of Thunderbird installed on the remote macOS or Mac OS X host is prior to 91.0.1. It is, therefore, affected by a vulnerability as referenced in the mfsa2021-37 advisory. - Firefox incorrectly accepted a newline in a HTTP/3 header, interpreting it as two separate headers. This allowed...
Mozilla Firefox < 91.0.1
The version of Firefox installed on the remote macOS or Mac OS X host is prior to 91.0.1. It is, therefore, affected by a vulnerability as referenced in the mfsa2021-37 advisory. - Firefox incorrectly accepted a newline in a HTTP/3 header, interpreting it as two separate headers. This allowed for...
Security Vulnerabilities fixed in Firefox 91.0.1 and Thunderbird 91.0.1 — Mozilla
Firefox incorrectly accepted a newline in a HTTP/3 header, interpreting it as two separate headers. This allowed for a header splitting attack against servers using HTTP/3...
PT-2021-5250
Name of the Vulnerable Software and Affected Versions Firefox versions prior to 91.0.1 Thunderbird versions prior to 91.0.1 Description The issue is related to the incorrect handling of HTTP requests, which can lead to a header splitting attack against servers using HTTP/3. This allows a remote...
h2o:h2o-fuzzer-http3: Heap-buffer-overflow in decode_header_value_literal
Project: https://github.com/h2o/h2o.git Detailed Report: https://oss-fuzz.com/testcase?key=4668461354713088 Project: h2o Fuzzing Engine: libFuzzer Fuzz Target: h2o-fuzzer-http3 Job Type: libfuzzerasanh2o Platform Id: linux Crash Type: Heap-buffer-overflow READ 1 Crash Address: 0x62800000bda9 Cras...
HTTP/3 and QUIC: Past, Present, and Future
You may have seen the announcements over the past two weeks -- the IETF QUIC RFCs have been published! That leads to a lot of questions, depending on how closely you've followed this space. You might be wondering what this means to you, or you might think QUIC has been an established thing for...
HTTP/3 and QUIC: Past, Present, and Future
You may have seen the announcements over the past two weeks -- the IETF QUIC RFCs have been published! That leads to a lot of questions, depending on how closely you've followed this space...
h2o -- uninitialised memory access in HTTP3
Emil Lerner reports: When receiving QUIC frames in certain order, HTTP/3 server-side implementation of h2o can be misguided to treat uninitialized memory as HTTP/3 frames that have been received. When h2o is used as a reverse proxy, an attacker can abuse this vulnerability to send internal state ...
HTTP/3: Ready to Land
Hi, my name is Mike Bishop; I'm the editor of the newest version of HTTP, HTTP/3. I'm part of Foundry, a team at Akamai that focuses on new and emerging technologies that will impact the future of the web. I've been involved in web standards since the early days of HTTP/2, and most of my work has...
A QUICk Introduction to HTTP/3
HTTP/3 is the newest iteration of the HTTP protocol that improves web security and performance...
