{"answers":{"affected":"2 open source packages ship an affected version, including Hangfire.Core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-41238 in the wild and no public exploit code.","fix":"Upgrade Hangfire.Core to 1.7.26 or later.","what":"CVE-2021-41238 is a high-severity vulnerability in HangfireIO Hangfire, published on 2 Nov 2021."},"fix_prompt":"Check this codebase for CVE-2021-41238 and fix it if it is affected.\n\nWhat it is: CVE-2021-41238 is a high-severity vulnerability in HangfireIO Hangfire, published on 2 Nov 2021. \nExploitation: There is no known exploitation of CVE-2021-41238 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- Hangfire.Core (NuGet): affected from 1.7.25; fixed in 1.7.26\n- Hangfire.Core (NuGet): affected from 1.7.25; fixed in 1.7.26\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-41238/ (Markdown: https://insights.sbomify.com/CVE-2021-41238/index.md)","id":"CVE-2021-41238","markdown":"https://insights.sbomify.com/CVE-2021-41238/index.md","name":"CVE-2021-41238","record":{"aliases":["GHSA-7rq6-7gv8-c37h"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[{"product":"hangfire","vendor":"hangfire"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"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.","ecosystems":["NuGet"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Missing Authorization with Default Settings in Dashboard UI","id":"CVE-2021-41238","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"NuGet","product":null,"products":[],"type":null,"year":"2021"},"n_packages":2,"n_references":2,"next":{"headline":"User enumeration setting not respected in Nextcloud server","id":"CVE-2021-41239"},"packages":[{"ecosystem":"NuGet","fixed":["1.7.26"],"introduced":["1.7.25"],"last_affected":[],"package":"Hangfire.Core","purl":null,"source":"GHSA-7rq6-7gv8-c37h"},{"ecosystem":"NuGet","fixed":["1.7.26"],"introduced":["1.7.25"],"last_affected":[],"package":"Hangfire.Core","purl":"pkg:nuget/Hangfire.Core","source":"GHSA-7rq6-7gv8-c37h"}],"prev":{"headline":"XSS vulnerability in oro/platform","id":"CVE-2021-41236"},"products":["Hangfire"],"published":"2021-11-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["HangfireIO"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2021-41238/"}