How severe is GHSA-rfhg-rjfp-9q8q?

No CVSS score has been assigned to GHSA-rfhg-rjfp-9q8q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rfhg-rjfp-9q8q?

GHSA-rfhg-rjfp-9q8q affects the following packages: s2n-quic (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-rfhg-rjfp-9q8q?

Update s2n-quic to 1.25.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rfhg-rjfp-9q8q is resolved across your whole dependency graph.

How do I detect GHSA-rfhg-rjfp-9q8q in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for s2n-quic, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-rfhg-rjfp-9q8q 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.

Is GHSA-rfhg-rjfp-9q8q actively exploited in the wild?

No public exploit code has been indexed for GHSA-rfhg-rjfp-9q8q 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.

When was GHSA-rfhg-rjfp-9q8q published, and has it been updated?

GHSA-rfhg-rjfp-9q8q was published on July 24, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

Potential denial of service after connection migrationGHSA-rfhg-rjfp-9q8q

Fix: aws/s2n-quic@73a8142

GHSA-rfhg-rjfp-9q8q is a security vulnerability in s2n-quic. A fix is available for s2n-quic — see the affected versions and patch details below.

Published

Jul 24, 2023

Updated

Jul 24, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jul 24, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀s2n-quic

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

Impact

An issue in s2n-quic results in the endpoint shutting down due to a combination of peer-initiated connection migration and duplicate new connection ID frames being received. No AWS services are affected by this issue, and customers of AWS services do not need to take action.

Impacted versions: <=v1.24.0

Patches

The patch is included in v1.25.0.

Workarounds

There is no workaround. Applications using s2n-quic should upgrade their application to the most recent release of s2n-quic.

If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page or directly via email to [email protected]. Please do not create a public GitHub issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`s2n-quic`	all versions	1.25.0`cargo update -p s2n-quic --precise 1.25.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for s2n-quic, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update s2n-quic to 1.25.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rfhg-rjfp-9q8q 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.

Frequently Asked Questions

### Impact An issue in s2n-quic results in the endpoint shutting down due to a combination of peer-initiated connection migration and duplicate new connection ID frames being received. No AWS services are affected by this issue, and customers of AWS services do not need to take action. Impacted versions: <=v1.24.0 ### Patches The patch is included in v1.25.0. ### Workarounds There is no workaround. Applications using s2n-quic should upgrade their application to the most recent release of s2n-quic. If you have any questions or comments about this advisory we ask that you contact AWS/Amazon S

O3 Security · Impact-Aware SCA

Is GHSA-rfhg-rjfp-9q8q in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works