Client secret not mandatory in UmbracoIdentityExtensions
Vulnerability Description
UmbracoIdentityExtensions is an Umbraco add-on package that enables easy extensibility points for ASP.Net Identity integration. In affected versions client secrets are not required which may expose some endpoints to untrusted actors. Since Umbraco is not a single-page application, the implicit flow is not safe. For traditional MVC applications, it is recommended to use the authorization code flow, which requires the client to authenticate with the authorization server using a client secret. This flow provides better security, as it involves exchanging an authorization code for an access token and/or ID token, rather than directly returning tokens in the URL fragment. This issue has been patched in commit `e792429f9` and a release to Nuget is pending. Users are advised to upgrade when possible.
Impact Analysis
Refer to official advisory for detailed impact metrics.
Remediation
Ensure systems are updated to the latest vendor-supplied patch levels.
Am I Vulnerable?
Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2023-32312
Credits & Attribution
No credits recorded in the NVD database.
References
- https://github.com/umbraco/UmbracoIdentityExtensions/security/advisories/GHSA-f2rf-8mwf-6jfh
- https://github.com/umbraco/UmbracoIdentityExtensions/pull/53
- https://github.com/umbraco/UmbracoIdentityExtensions/commit/e792429f9d1fa25c1ba4f7a61d23ee02fedd6dc9
- https://docs.umbraco.com/umbraco-cms/reference/security/external-login-providers
More from umbraco
View All →Affected Vendor
umbraco
View all reports →