Vulnerability in github.com/swift-server/async-http-client (CVE-2023-0040)
Summary
Vulnerability in github.com/swift-server/async-http-client (CVE-2023-0040). Data can be tampered with by attackers. Mitigation: upgrade to 1.4.1 or later.
Original description
The description as published by the source.
Versions of Async HTTP Client prior to 1.13.2 are vulnerable to a form of targeted request manipulation called CRLF injection. This vulnerability was the result of insufficient validation of HTTP header field values before sending them to the network. Users are vulnerable if they pass untrusted data into HTTP header field values without prior sanitisation. Common use-cases here might be to place usernames from a database into HTTP header fields.
This vulnerability allows attackers to inject new HTTP header fields, or entirely new requests, into the data stream. This can cause requests to be understood very differently by the remote server than was intended. In general, this is unlikely to result in data disclosure, but it can result in a number of logical errors and other misbehaviours.
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-2023-0040 has been found in github.com/swift-server/async-http-client.
Data can be tampered with by attackers.
What to do: upgrade github.com/swift-server/async-http-client to 1.4.1 or later.
If unsure, ask your IT team or search "github.com/swift-server/async-http-client CVE-2023-0040" on the vendor's site.
CVE-2023-0040 (github.com/swift-server/async-http-client) — CWE-74
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.4.1 — 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.
A vulnerability (CWE-74) exists in github.com/swift-server/async-http-client.
Check the vendor advisory for the affected versions of github.com/swift-server/async-http-client.
Severity: ?. Data can be tampered with by attackers.
Update to 1.4.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/swift-server/async-http-client' . 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
-
1Identify exposure identify
grep -r 'github.com/swift-server/async-http-client' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/swift-server/async-http-clientを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/swift-server/async-http-client to 1.4.1ステージング環境で 1.4.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com