How severe is GHSA-v363-rrf2-5fmj?

No CVSS score has been assigned to GHSA-v363-rrf2-5fmj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v363-rrf2-5fmj?

GHSA-v363-rrf2-5fmj affects the following packages: ferris-says (crates.io), ferris-says (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-v363-rrf2-5fmj?

No patched version of ferris-says has shipped for GHSA-v363-rrf2-5fmj yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-v363-rrf2-5fmj in my crates.io dependencies?

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

How do I mitigate GHSA-v363-rrf2-5fmj 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-v363-rrf2-5fmj?

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

Is GHSA-v363-rrf2-5fmj actively exploited in the wild?

No public exploit code has been indexed for GHSA-v363-rrf2-5fmj 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-v363-rrf2-5fmj published, and has it been updated?

GHSA-v363-rrf2-5fmj was published on January 17, 2024 and was last updated on February 10, 2024. 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-v363-rrf2-5fmj — ferris-says

Fix: rust-lang/ferris-says#21

GHSA-v363-rrf2-5fmj is a security vulnerability in ferris-says. A fix is available for ferris-says — see the affected versions and patch details below.

ferris-says has undefined behavior when not using UTF-8

Also known asRUSTSEC-2024-0001

Published

Jan 17, 2024

Updated

Feb 10, 2024

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Exploitation data as of Feb 10, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🦀ferris-says🦀ferris-says

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 receive a &[u8] from the caller through a safe API, and pass it directly to the unsafe str::from_utf8_unchecked function.

The behavior of ferris_says::say is undefined if the bytes from the caller don't happen to be valid UTF-8.

The flaw was corrected in ferris-says#21 by using the safe str::from_utf8 instead, and returning an error on invalid input. However this fix has not yet been published to crates.io as a patch version for 0.2.

Separately, ferris-says#32 has introduced a different API for version 0.3 which accepts input as &str rather than &[u8], so is unaffected by this bug.

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`ferris-says`	≥ 0.1.2	No fix
🦀crates.io	`ferris-says`	≥ 0.3.0&&< 0.3.1	0.3.1`cargo update -p ferris-says --precise 0.3.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ferris-says, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of ferris-says has shipped for GHSA-v363-rrf2-5fmj yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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-v363-rrf2-5fmj can be triaged on real exposure rather than presence alone.

Tailored to GHSA-v363-rrf2-5fmj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected versions receive a `&[u8]` from the caller through a safe API, and pass it directly to the unsafe `str::from_utf8_unchecked` function. The behavior of `ferris_says::say` is undefined if the bytes from the caller don't happen to be valid UTF-8. The flaw was corrected in [ferris-says#21] by using the safe `str::from_utf8` instead, and returning an error on invalid input. However this fix has not yet been published to crates.io as a patch version for 0.2. Separately, [ferris-says#32] has introduced a different API for version 0.3 which accepts input as `&str` rather than `&[u8]`, so i

O3 Security · Impact-Aware SCA

Is GHSA-v363-rrf2-5fmj in your dependencies?

O3 Security finds GHSA-v363-rrf2-5fmj 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