The vulnerability stems from improper handling of HTTP/2 CONTINUATION frames in affected amphp/http-client versions. The advisory explicitly states that CONTINUATION frames are buffered without size checks until END_HEADERS is received. The HTTP/2 connection handler (Http2Connection) is responsible for frame processing. The handleHeaders method (or equivalent) would logically process header-related frames, including CONTINUATION, and manage the buffer. The lack of incremental size validation during frame accumulation matches the described vulnerability mechanism. While exact function names aren't explicitly provided in advisories, the HTTP/2 connection handling code is the clear candidate based on the vulnerability's nature and HTTP/2 protocol specifics.