Описание
Token reuse in Ory fosite
Impact
When using client authentication method "private_key_jwt" [1], OpenId specification says the following about assertion jti:
A unique identifier for the token, which can be used to prevent reuse of the token. These tokens MUST only be used once, unless conditions for reuse were negotiated between the parties
Hydra does not seem to check the uniqueness of this jti value. Here is me sending the same token request twice, hence with the same jti assertion, and getting two access tokens:
Patches
This issue is patched in 0.31.0.
Workarounds
Do not allow clients to use private_key_jwt.
References
https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication
Ссылки
- https://github.com/ory/fosite/security/advisories/GHSA-v3q9-2p3m-7g43
- https://nvd.nist.gov/vuln/detail/CVE-2020-15222
- https://github.com/ory/fosite/commit/0c9e0f6d654913ad57c507dd9a36631e1858a3e9
- https://github.com/ory/fosite/releases/tag/v0.31.0
- https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication
- https://pkg.go.dev/vuln/GO-2021-0110
Пакеты
github.com/ory/fosite
< 0.31.0
0.31.0
Связанные уязвимости
In ORY Fosite (the security first OAuth2 & OpenID Connect framework for Go) before version 0.31.0, when using "private_key_jwt" authentication the uniqueness of the `jti` value is not checked. When using client authentication method "private_key_jwt", OpenId specification says the following about assertion `jti`: "A unique identifier for the token, which can be used to prevent reuse of the token. These tokens MUST only be used once, unless conditions for reuse were negotiated between the parties". Hydra does not seem to check the uniqueness of this `jti` value. This problem is fixed in version 0.31.0.