Skip to content

Client secret not mandatory

Low
RyuLindow published GHSA-f2rf-8mwf-6jfh Jun 9, 2023

Package

nuget UmbracoIdentityExtensions (NuGet)

Affected versions

2.0.0 and older

Patched versions

2.0.0 and older

Description

Impact

What kind of vulnerability is it? Who is impacted?

Neither the https://github.com/umbraco/UmbracoIdentityExtensions/blob/master/build/ActiveDirectory.Readme.txt or https://shazwazza.com/post/configuring-azure-active-directory-login-with-umbraco-members/ requires the developer to enter the Client secret, as it's optional in this repository.

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.

Patches

_Has the problem been patched?

Yes

References

Are there any links users can visit to find out more?

PR resolving this issue

https://docs.umbraco.com/umbraco-cms/reference/security/external-login-providers

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

CVE ID

CVE-2023-32312

Weaknesses

No CWEs

Credits