Vulnerability in amphp/http (CVE-2024-2653)

Summary

Vulnerability in amphp/http (CVE-2024-2653). Risk of unauthorized operations or information disclosure. Exploitable via CONTINUATION. Mitigation: upgrade to 1.7.3 or later.

Original description

The description as published by the source.

amphp/http will collect HTTP/2 CONTINUATION frames in an unbounded buffer and will not check the header size limit until it has received the END_HEADERS flag, resulting in an OOM crash. amphp/http-client and amphp/http-server are indirectly affected if they're used with an unpatched version of amphp/http. Early versions of amphp/http-client with HTTP/2 support (v4.0.0-rc10 to 4.0.0) are also directly affected.

Acknowledgements

Thank you to Bartek Nowotarski for reporting the vulnerability.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2024-2653 has been found in amphp/http.
Attackers can target a specific entry point like CONTINUATION over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade amphp/http to 1.7.3 or later.
If unsure, ask your IT team or search "amphp/http CVE-2024-2653" on the vendor's site.

CVE-2024-2653 (amphp/http)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: CONTINUATION / END_HEADERS
Patched: 1.7.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in amphp/http. Attackers reach the vulnerable code path via CONTINUATION without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of amphp/http. Attack surface: CONTINUATION / END_HEADERS.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.7.3.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'amphp/http' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'amphp/http' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で amphp/http を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade amphp/http to 1.7.3
```
ステージング環境で 1.7.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Packagist amphp/http

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.7.3"}]}]

Packagist amphp/http-client

[{"type":"ECOSYSTEM","events":[{"introduced":"4.0.0-rc10"},{"last_affected":"4.0.0"}]}]