How severe is GHSA-r6ww-5963-7r95?

GHSA-r6ww-5963-7r95 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-r6ww-5963-7r95?

GHSA-r6ww-5963-7r95 affects the following packages: github.com/grpc/grpc-swift (SwiftURL). Ecosystems affected: SwiftURL.

How do I fix GHSA-r6ww-5963-7r95?

Update github.com/grpc/grpc-swift to 1.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r6ww-5963-7r95 is resolved across your whole dependency graph.

How do I detect GHSA-r6ww-5963-7r95 in my SwiftURL dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grpc/grpc-swift. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-r6ww-5963-7r95 if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-r6ww-5963-7r95?

O3 pinpoints whether GHSA-r6ww-5963-7r95 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-r6ww-5963-7r95 actively exploited in the wild?

No public exploit code has been indexed for GHSA-r6ww-5963-7r95 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-r6ww-5963-7r95?

GHSA-r6ww-5963-7r95 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 62th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-r6ww-5963-7r95?

GHSA-r6ww-5963-7r95 is classified as Reachable Assertion (CWE-617). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-r6ww-5963-7r95 published, and has it been updated?

GHSA-r6ww-5963-7r95 was published on June 9, 2023 and was last updated on February 9, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-r6ww-5963-7r95: Denial of Service via reachable assertion…

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk62th percentile+0.80%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

📦github.com/grpc/grpc-swift

Real-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

A grpc-swift server is vulnerable to a denial of service attack via a reachable assertion. This was due to incorrect logic when handling GOAWAY frames.

The attack is low-effort: it takes very little resources to construct and send the required sequence of frames. The impact on availability is high as the server will crash, dropping all in flight connections and requests.

The issue was discovered by automated fuzz testing and is resolved by fixing the relevant state handling code.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦SwiftURL	`github.com/grpc/grpc-swift`	all versions	1.7.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grpc/grpc-swift. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/grpc/grpc-swift to 1.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r6ww-5963-7r95 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 pinpoints whether GHSA-r6ww-5963-7r95 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-r6ww-5963-7r95. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A grpc-swift server is vulnerable to a denial of service attack via a reachable assertion. This was due to incorrect logic when handling `GOAWAY` frames. The attack is low-effort: it takes very little resources to construct and send the required sequence of frames. The impact on availability is high as the server will crash, dropping all in flight connections and requests. The issue was discovered by automated fuzz testing and is resolved by fixing the relevant state handling code.

O3 Security · Impact-Aware SCA

Is GHSA-r6ww-5963-7r95 in your dependencies?

O3 detects GHSA-r6ww-5963-7r95 across SwiftURL dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-r6ww-5963-7r95