How severe is GHSA-gfgm-chr3-x6px?

No CVSS score has been assigned to GHSA-gfgm-chr3-x6px yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gfgm-chr3-x6px?

GHSA-gfgm-chr3-x6px affects the following packages: prettytable-rs (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-gfgm-chr3-x6px?

Update prettytable-rs to 0.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gfgm-chr3-x6px is resolved across your whole dependency graph.

How do I detect GHSA-gfgm-chr3-x6px in my crates.io dependencies?

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

How do I mitigate GHSA-gfgm-chr3-x6px 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-gfgm-chr3-x6px actively exploited in the wild?

No public exploit code has been indexed for GHSA-gfgm-chr3-x6px 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-gfgm-chr3-x6px published, and has it been updated?

GHSA-gfgm-chr3-x6px was published on December 30, 2022 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

prettytable-rs: Force cast a &Vec<T> to &[T] may lead to undefined behaviorGHSA-gfgm-chr3-x6px

GHSA-gfgm-chr3-x6px is a security vulnerability in prettytable-rs. A fix is available for prettytable-rs — see the affected versions and patch details below.

Also known asRUSTSEC-2022-0074

Published

Dec 30, 2022

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

🦀prettytable-rs

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

In function Table::as_ref, a reference of vector is force cast to slice. There are multiple problems here:

To guarantee the size is correct, we have to first do Vec::shrink_to_fit. The function requires a mutable reference, so we have to force cast from immutable to mutable, which is undefined behavior (UB).
Even if (1) is sound, &Vec<T> and &[T] still might not have the same layout. Treating them equally may lead to undefinted behavior (UB).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`prettytable-rs`	all versions	0.10.0`cargo update -p prettytable-rs --precise 0.10.0`

Detection & mitigation playbook

Open-source dependency

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

In function `Table::as_ref`, a reference of vector is force cast to slice. There are multiple problems here: 1. To guarantee the size is correct, we have to first do `Vec::shrink_to_fit`. The function requires a mutable reference, so we have to force cast from immutable to mutable, which is undefined behavior (UB). 2. Even if (1) is sound, `&Vec<T>` and `&[T]` still might not have the same layout. Treating them equally may lead to undefinted behavior (UB).

O3 Security · Impact-Aware SCA

Is GHSA-gfgm-chr3-x6px in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works