How severe is GHSA-5x36-7567-3cw6?

No CVSS score has been assigned to GHSA-5x36-7567-3cw6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5x36-7567-3cw6?

GHSA-5x36-7567-3cw6 affects the following packages: partial_sort (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-5x36-7567-3cw6?

Update partial_sort to 0.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5x36-7567-3cw6 is resolved across your whole dependency graph.

How do I detect GHSA-5x36-7567-3cw6 in my crates.io dependencies?

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

How do I mitigate GHSA-5x36-7567-3cw6 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is GHSA-5x36-7567-3cw6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5x36-7567-3cw6 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-5x36-7567-3cw6 published, and has it been updated?

GHSA-5x36-7567-3cw6 was published on February 28, 2023 and was last updated on November 8, 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

partial_sort contains Out-of-bounds Read in release modeGHSA-5x36-7567-3cw6

GHSA-5x36-7567-3cw6 is a security vulnerability in partial_sort. A fix is available for partial_sort — see the affected versions and patch details below.

Also known asRUSTSEC-2023-0016

Published

Feb 28, 2023

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀partial_sort

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

Affected versions of this crate were using a debug assertion to validate the last parameter of partial_sort(). This would allow invalid inputs to cause an out-of-bounds read instead of immediately panicking, when compiled without debug assertions.

All writes are bounds-checked, so the out-of-bounds memory access is read-only. This also means that the first attempted out-of-bounds write will panic, limiting the possible reads.

The accessible region is further limited by an initial bounds-checked read at (last / 2) - 1, i.e., it is proportional to the size of the vector.

This bug has been fixed in v0.2.0.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`partial_sort`	all versions	0.2.0`cargo update -p partial_sort --precise 0.2.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for partial_sort, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update partial_sort to 0.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5x36-7567-3cw6 is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

Affected versions of this crate were using a debug assertion to validate the `last` parameter of `partial_sort()`. This would allow invalid inputs to cause an out-of-bounds read instead of immediately panicking, when compiled without debug assertions. All writes are bounds-checked, so the out-of-bounds memory access is read-only. This also means that the first attempted out-of-bounds write will panic, limiting the possible reads. The accessible region is further limited by an initial bounds-checked read at `(last / 2) - 1`, i.e., it is proportional to the size of the vector. This bug has be

O3 Security · Impact-Aware SCA

Is GHSA-5x36-7567-3cw6 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works