Loading HuntDB...

Issuer not verified from obtained token in user_oidc

Medium
N
Nextcloud
Submitted None

Team Summary

Official summary from Nextcloud

https://github.com/nextcloud/security-advisories/security/advisories/GHSA-xx3h-v363-q36j

Reported by rullzer

Vulnerability Details

Technical details and impact analysis

As per OIDC spec the issues of the token should be verified to match the issuer obtained in the discovery phase. https://openid.net/specs/openid-connect-core-1_0.html#IDTokenValidation (step 2) Very similar to the aud check in https://github.com/nextcloud/user_oidc/blob/main/lib/Controller/LoginController.php There are some more steps in that document that I don't think are currently implemented correctly. However I do not have an OIDC setup to check/verify. So might be worth it to have a look. ## Impact Without verifying the issuer a MITM is possible.

Report Details

Additional information and metadata

State

Closed

Substate

Resolved

Bounty

$250.00

Submitted