Missing Authorization with Default Settings in Dashboard UI

Hangfire is an open source system to perform background job processing in a .NET or .NET Core applications. No Windows Service or separate process required. Dashboard UI in Hangfire.Core uses authorization filters to protect it from showing sensitive data to unauthorized users. By default when no custom authorization filters specified, `LocalRequestsOnlyAuthorizationFilter` filter is being used to allow only local requests and prohibit all the remote requests to provide sensible, protected by default settings. However due to the recent changes, in version 1.7.25 no authorization filters are used by default, allowing remote requests to succeed. If you are using `UseHangfireDashboard` method with default `DashboardOptions.Authorization` property value, then your installation is impacted. If any other authorization filter is specified in the `DashboardOptions.Authorization` property, the you are not impacted. Patched versions (1.7.26) are available both on Nuget.org and as a tagged release on the github repo. Default authorization rules now prohibit remote requests by default again by including the `LocalRequestsOnlyAuthorizationFilter` filter to the default settings. Please upgrade to the newest version in order to mitigate the issue. For users who are unable to upgrade it is possible to mitigate the issue by using the `LocalRequestsOnlyAuthorizationFilter` explicitly when configuring the Dashboard UI.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

授权机制缺失

Hangfire 安全漏洞

Hangfire是在ASP.NET 应用程序中执行即发即忘、延迟和重复作业的极其简单的方法。支持 CPU 和 I/O 密集型、长时间运行和短期运行的作业。不需要 Windows 服务/任务计划程序。由 Redis、SQL Server、SQL Azure 和 MSMQ 提供支持。 Hangfire 存在安全漏洞，该漏洞默认设置下不使用授权过滤器，允许未经授权的攻击者远程请求成功并查看敏感数据。

N/A

N/A