NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🦀 crates.io
Not in CISA KEV

toodee is vulnerable to Heap Buffer Overflow through its DrainCol DestructorGHSA-pfp7-vxgr-83pw

Fix: antonmarsden/toodee@e6e16d5

GHSA-pfp7-vxgr-83pw is a remote code execution vulnerability in toodee. A fix is available for toodee — see the affected versions and patch details below.

Also known asRUSTSEC-2025-0062
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 28, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🦀toodee

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

An off-by-one error in the DrainCol::drop destructor could cause an unsafe memory copy operation to exceed the bounds of the associated vector.

The error was related to the size of the data being copied in one of the ptr::copy invocations inside the destructor.

When removing the first column from a TooDee object, the DrainCol return object could cause a heap buffer overflow vulnerability when it is dropped.

The issue was fixed in commit e6e16d5 by reducing the copied size by one.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.iotoodee≥ 0.2.0&&< 0.6.00.6.0cargo update -p toodee --precise 0.6.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update toodee to 0.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pfp7-vxgr-83pw is resolved across your whole dependency graph.

  3. 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

An off-by-one error in the `DrainCol::drop` destructor could cause an unsafe memory copy operation to exceed the bounds of the associated vector. The error was related to the size of the data being copied in one of the `ptr::copy` invocations inside the destructor. When removing the first column from a TooDee object, the DrainCol return object could cause a heap buffer overflow vulnerability when it is dropped. The issue was fixed in commit `e6e16d5` by reducing the copied size by one.
O3 Security · Impact-Aware SCA

Is GHSA-pfp7-vxgr-83pw in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works
toodee is vulnerable to Heap Buffer Overflow through its…