How severe is GHSA-rcx8-48pc-v9q8?

No CVSS score has been assigned to GHSA-rcx8-48pc-v9q8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rcx8-48pc-v9q8?

GHSA-rcx8-48pc-v9q8 affects the following packages: mail-internals (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-rcx8-48pc-v9q8?

The records we use list no patched version of mail-internals for GHSA-rcx8-48pc-v9q8. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-rcx8-48pc-v9q8 in my crates.io dependencies?

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

How do I mitigate GHSA-rcx8-48pc-v9q8 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-rcx8-48pc-v9q8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-rcx8-48pc-v9q8 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-rcx8-48pc-v9q8 published, and has it been updated?

GHSA-rcx8-48pc-v9q8 was published on August 24, 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

mail-internals use-after-free vulnerability in `vec_insert_bytes`GHSA-rcx8-48pc-v9q8

GHSA-rcx8-48pc-v9q8 is a security vulnerability in mail-internals. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asRUSTSEC-2023-0054

Published

Aug 24, 2023

Updated

Nov 8, 2023

Affected

1 pkg

Patched

None yet

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

🦀mail-internals

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

Incorrect reallocation logic in the function vec_insert_bytes causes a use-after-free.

This function does not have to be called directly to trigger the vulnerability because many methods on EncodingWriter call this function internally.

The mail-* suite is unmaintained and the upstream sources have been actively vandalised. A fixed mail-internals-ng (and mail-headers-ng and mail-core-ng) crate has been published which fixes this, and a dependency on another unsound crate.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`mail-internals`	≥ 0.2.0	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mail-internals, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of mail-internals for GHSA-rcx8-48pc-v9q8. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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

Incorrect reallocation logic in the function [`vec_insert_bytes`](https://docs.rs/mail-internals/0.2.3/mail_internals/utils/fn.vec_insert_bytes.html) causes a use-after-free. This function does not have to be called directly to trigger the vulnerability because many methods on [`EncodingWriter`](https://docs.rs/mail-internals/0.2.3/mail_internals/encoder/struct.EncodingWriter.html) call this function internally. The mail-\* suite is unmaintained and the upstream sources have been actively vandalised. A fixed `mail-internals-ng` (and `mail-headers-ng` and `mail-core-ng`) crate has been publis

O3 Security · Impact-Aware SCA

Is GHSA-rcx8-48pc-v9q8 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works