How severe is GHSA-w4f8-fxq2-j35v?

No CVSS score has been assigned to GHSA-w4f8-fxq2-j35v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w4f8-fxq2-j35v?

GHSA-w4f8-fxq2-j35v affects the following packages: github.com/google/fscrypt (Go). Ecosystems affected: Go.

How do I fix GHSA-w4f8-fxq2-j35v?

Update github.com/google/fscrypt to 0.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w4f8-fxq2-j35v is resolved across your whole dependency graph.

How do I detect GHSA-w4f8-fxq2-j35v in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/google/fscrypt. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-w4f8-fxq2-j35v 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-w4f8-fxq2-j35v?

O3 pinpoints whether GHSA-w4f8-fxq2-j35v is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-w4f8-fxq2-j35v actively exploited in the wild?

No public exploit code has been indexed for GHSA-w4f8-fxq2-j35v 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-w4f8-fxq2-j35v published, and has it been updated?

GHSA-w4f8-fxq2-j35v was published on March 1, 2022. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-w4f8-fxq2-j35v

Possible privilege escalation via bash completion script

Published

Mar 1, 2022

Updated

Mar 1, 2022

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐹github.com/google/fscrypt

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

The bash completion script for fscrypt through v0.3.2 allows injection of commands via crafted mountpoint paths, allowing privilege escalation under a specific set of circumstances. A local user who has control over mountpoint paths could potentially escalate their privileges if they create a malicious mountpoint path and if the system administrator happens to be using the fscrypt bash completion script to complete mountpoint paths. We recommend upgrading to v0.3.3 or above.

For more details, see CVE-2022-25328.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/google/fscrypt`	all versions	0.3.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/google/fscrypt. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/google/fscrypt to 0.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w4f8-fxq2-j35v 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.
How O3 protects you
O3 pinpoints whether GHSA-w4f8-fxq2-j35v is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-w4f8-fxq2-j35v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The bash completion script for `fscrypt` through v0.3.2 allows injection of commands via crafted mountpoint paths, allowing privilege escalation under a specific set of circumstances. A local user who has control over mountpoint paths could potentially escalate their privileges if they create a malicious mountpoint path and if the system administrator happens to be using the `fscrypt` bash completion script to complete mountpoint paths. We recommend upgrading to v0.3.3 or above. For more details, see [CVE-2022-25328](https://www.cve.org/CVERecord?id=CVE-2022-25328).

O3 Security · Impact-Aware SCA

Is GHSA-w4f8-fxq2-j35v in your dependencies?

O3 detects GHSA-w4f8-fxq2-j35v across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works