GHSA-xvr7-p2c6-j83w — swift-nio-http2
GHSA-xvr7-p2c6-j83w is a security vulnerability in github.com/apple/swift-nio-http2. A fix is available for github.com/apple/swift-nio-http2 — see the affected versions and patch details below.
swift-nio-http2 affected by HTTP/2 MadeYouReset vulnerability
Real-World Exposure
github.com/apple/swift-nio-http2Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects SwiftURL packages — download data is not available via public APIs for these ecosystems.
Description
The HTTP/2 MadeYouReset vulnerability has a mild effect on swift-nio-http2.
swift-nio-http2 mostly protects against MadeYouReset by using a number of existing denial-of-service prevention patterns that we added in response to the RapidReset vulnerabilities. The result is that servers are not vulnerable to naive attacks based on MadeYouReset, and the naive PoC examples do not affect swift-nio-http2.
However, in 1.38.0 we added some defense-in-depth measures as a precautionary measure that detect clients behaving "weirdly". These defense in depth measures tackle resource drain attacks where attackers interleave attack traffic with legitimate traffic to try to evade our existing DoS prevention mechanisms.
We recommend all adopters move to 1.38.0 as soon as possible to mitigate against more sophisticated attacks that may appear in the future.
We are very grateful to @galbarnahum, @AnatBB, and @YanivRL for their reporting and assistance with our process.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦SwiftURL | github.com/apple/swift-nio-http2 | all versions | 1.38.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/apple/swift-nio-http2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/apple/swift-nio-http2 to 1.38.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xvr7-p2c6-j83w is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-xvr7-p2c6-j83w can be triaged on real exposure rather than presence alone.
Tailored to GHSA-xvr7-p2c6-j83w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-xvr7-p2c6-j83w in your dependencies?
O3 Security finds GHSA-xvr7-p2c6-j83w across SwiftURL dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.