How severe is GHSA-fc4h-xcf3-qj5f?

No CVSS score has been assigned to GHSA-fc4h-xcf3-qj5f yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-fc4h-xcf3-qj5f?

GHSA-fc4h-xcf3-qj5f affects the following packages: matrix-sdk (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-fc4h-xcf3-qj5f?

Update matrix-sdk to 0.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fc4h-xcf3-qj5f is resolved across your whole dependency graph.

How do I detect GHSA-fc4h-xcf3-qj5f in my crates.io dependencies?

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

How do I mitigate GHSA-fc4h-xcf3-qj5f 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-fc4h-xcf3-qj5f?

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

Is GHSA-fc4h-xcf3-qj5f actively exploited in the wild?

No public exploit code has been indexed for GHSA-fc4h-xcf3-qj5f 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-fc4h-xcf3-qj5f published, and has it been updated?

GHSA-fc4h-xcf3-qj5f was published on October 25, 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

GHSA-fc4h-xcf3-qj5f — matrix-sdk

GHSA-fc4h-xcf3-qj5f is a security vulnerability in matrix-sdk. A fix is available for matrix-sdk — see the affected versions and patch details below.

matrix-sdk 0.6.0 logs access tokens

Also known asRUSTSEC-2022-0062

Published

Oct 25, 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

🦀matrix-sdk

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

When sending Matrix requests using an affected version of matrix-sdk in an application that writes logs using tracing-subscriber (in a way that includes fields of tracing spans such as tracing_subscribers default text output from the fmt module), these logs will contain the user's access token.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`matrix-sdk`	≥ 0.6.0&&< 0.6.2	0.6.2`cargo update -p matrix-sdk --precise 0.6.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for matrix-sdk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update matrix-sdk to 0.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fc4h-xcf3-qj5f 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-fc4h-xcf3-qj5f can be triaged on real exposure rather than presence alone.

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

Frequently Asked Questions

When sending Matrix requests using an affected version of `matrix-sdk` in an application that writes logs using `tracing-subscriber` (in a way that includes fields of tracing spans such as `tracing_subscriber`s default text output from the `fmt` module), these logs will contain the user's access token.

O3 Security · Impact-Aware SCA

Is GHSA-fc4h-xcf3-qj5f in your dependencies?

O3 Security finds GHSA-fc4h-xcf3-qj5f 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