GHSA-fc4h-xcf3-qj5f json
matrix-sdk 0.6.0 logs access tokens
published 4y ago modified 3y ago also RUSTSEC-2022-0062
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- crates.io matrix-sdk 0.6.2
Is GHSA-fc4h-xcf3-qj5f in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | matrix-sdk | >=0.6.0, <0.6.2 |
0.6.2 |
References
-
github.com
/matrix-org/matrix-rust-sdk/issues/1110
web, report
-
github.com
/matrix-org/matrix-rust-sdk
package
-
rustsec.org
/advisories/RUSTSEC-2022-0062.html
web, advisory
-
crates.io
/crates/matrix-sdk
package
Sources
- GitHub Advisory GHSA-fc4h-xcf3-qj5f
- OSV RUSTSEC-2022-0062
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.