GHSA-g588-cjg3-6g78 json
Steamworks game clients/servers using P2P authentication vulnerable to denial of service
published 6mo ago modified 6mo ago also RUSTSEC-2026-0121
- 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
Processing the raw `ValidateAuthTicketResponse_t` callback data panics when the `m_eAuthSessionResponse` field is `k_EAuthSessionResponseAuthTicketNetworkIdentityFailure`. This can lead to denial of service in game clients and servers using the `begin_authentication_session` API to authenticate players if a malicious game client sends an authentication ticket with a network identity that does not match that of the verifier.
Patch / fix
- crates.io steamworks 0.13.1
Is GHSA-g588-cjg3-6g78 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 | steamworks | <0.13.1 >=0.0.0-0, <0.13.1 |
0.13.1 |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
github.com
/Noxime/steamworks-rs/issues/321
web, report
-
github.com
/Noxime/steamworks-rs
package
-
rustsec.org
/advisories/RUSTSEC-2026-0121.html
web, advisory
-
crates.io
/crates/steamworks
package
Sources
- GitHub Advisory GHSA-g588-cjg3-6g78
- OSV RUSTSEC-2026-0121
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.