Skip to content

http2: fix a error in the check for frame->hd.type (related to CVE-2025-23085) #57644

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
aduh95 merged 3 commits into from
Apr 9, 2025
Merged

http2: fix a error in the check for frame->hd.type (related to CVE-2025-23085) #57644

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2d3a1fd
http2: fix an error in an if condition in 1b693fa
hgqxjj Mar 27, 2025
cf86853
http2:correct http2 header frame content
hgqxjj Apr 1, 2025
2279ad5
http2: correct comments
hgqxjj Apr 1, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
http2: fix an error in an if condition in 1b693fa 
According to the description above, this should be
checking whether frame->hd.type is NGHTTP2_GOAWAY,
and the value of NGHTTP2_GOAWAY is 0x07. However,
it is written as 0x03 here, which I think
it is an error.
  • Loading branch information
@hgqxjj
hgqxjj committed Apr 1, 2025
commit 2d3a1fd89ae199086a63a820385bbedec2b09435
2 changes: 1 addition & 1 deletion src/node_http2.cc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1206,7 +1206,7 @@ int Http2Session::OnFrameNotSent(nghttp2_session* handle,
// closed but the Http2Session will still be up causing a memory leak.
// Therefore, if the GOAWAY frame couldn't be send due to
// ERR_SESSION_CLOSING we should force close from our side.
if (frame->hd.type != 0x03) {
if (frame->hd.type != NGHTTP2_GOAWAY) {
return 0;
}
}
Expand Down