How severe is GHSA-hxq4-mx37-fqvg?

No CVSS score has been assigned to GHSA-hxq4-mx37-fqvg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hxq4-mx37-fqvg?

GHSA-hxq4-mx37-fqvg affects the following packages: s2n-quic (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-hxq4-mx37-fqvg?

Update s2n-quic to 1.23.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hxq4-mx37-fqvg is resolved across your whole dependency graph.

How do I detect GHSA-hxq4-mx37-fqvg 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-hxq4-mx37-fqvg 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-hxq4-mx37-fqvg?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hxq4-mx37-fqvg can be triaged on real exposure rather than presence alone.

Is GHSA-hxq4-mx37-fqvg actively exploited in the wild?

No public exploit code has been indexed for GHSA-hxq4-mx37-fqvg 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-hxq4-mx37-fqvg published, and has it been updated?

GHSA-hxq4-mx37-fqvg was published on June 30, 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

GHSA-hxq4-mx37-fqvg — s2n-quic

Fix: aws/s2n-quic@4b1d417

GHSA-hxq4-mx37-fqvg is a security vulnerability in s2n-quic. A fix is available for s2n-quic — see the affected versions and patch details below.

s2n-quic potential denial of service vulnerability when receiving empty UDP packets

Published

Jun 30, 2023

Updated

Jun 30, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jun 30, 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 after receiving an empty UDP packet on a connection.

No AWS services are affected by this issue and customers of AWS services do not need to take action. Applications using s2n-quic should upgrade their application to the most recent release of s2n-quic.

Impacted version: s2n-quic v1.22.0.

Patches

The patch is included in s2n-quic v1.23.0.

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`	≥ 1.22.0&&< 1.23.0	1.23.0`cargo update -p s2n-quic --precise 1.23.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.23.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hxq4-mx37-fqvg 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-hxq4-mx37-fqvg can be triaged on real exposure rather than presence alone.

Tailored to GHSA-hxq4-mx37-fqvg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact An issue in s2n-quic results in the endpoint shutting down after receiving an empty UDP packet on a connection. No AWS services are affected by this issue and customers of AWS services do not need to take action. Applications using s2n-quic should upgrade their application to the most recent release of s2n-quic. Impacted version: s2n-quic v1.22.0. ### Patches The patch is included in s2n-quic [v1.23.0](https://github.com/aws/s2n-quic/releases/tag/v1.23.0). If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our [vulnerabil

O3 Security · Impact-Aware SCA

Is GHSA-hxq4-mx37-fqvg in your dependencies?

O3 Security finds GHSA-hxq4-mx37-fqvg across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works