Headline
GHSA-hmg4-wwm5-p999: Umbraco Allows User Enumeration Feasible Based On Management API Timing and Response Codes
Impact
Based on an analysis of response codes and timing of Umbraco 14+ management API responses, it’s possible to determine whether an account exists.
Patches
Will be patched in 14.3.2 and 15.1.2.
Workarounds
None available.
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.