react/http: Unbounded HTTP Client Response Header Buffering Leads to Memory Exhaustion DoS

Why it is Amber

• CVSS 7.5 high
• Remotely exploitable without logging in
• On your watchlist: Composer

Affected packages

References

• https://github.com/advisories/GHSA-g4f2-2pf3-2pwj
• https://github.com/reactphp/http/security/advisories/GHSA-g4f2-2pf3-2pwj
• https://github.com/reactphp/http/commit/2558622d0b76227c60c61eac8a61572cb6638e8c
• https://github.com/reactphp/http/releases/tag/v1.11.1
• https://github.com/advisories/GHSA-g4f2-2pf3-2pwj

Original description

react/http is an event-driven, streaming HTTP client and server implementation for ReactPHP. From 1.0.0 until 1.11.1, React\Http\Browser uses ClientRequestStream::handleData() to append response-header bytes to an internal buffer without enforcing a size limit. A remote server can send a valid status line and partial header, withhold the \r\n\r\n or \n\n header terminator, and continue streaming data so the buffer grows for the life of the connection. Applications that fetch attacker-controlled or attacker-influenced URLs, including URLs reached through redirects, can exhaust PHP memory_limit and crash the event-loop or worker process. Confidentiality and integrity are unaffected. This issue is fixed in version 1.11.1.