Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
CVE ID: CVE-2021-41238 State: PUBLISHED Published: 2021-11-02T18:05:11 Last Updated: 2024-08-04T03:08:31.508Z Severity: HIGH (CVSS 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L) Vendors: HangfireIO Products: Hangfire Problem Types: CWE-862 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
rs 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. De
e 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. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/HangfireIO/Hangfire/security/advisories/GHSA-7rq6-7gv8-c37h - https://github.com/HangfireIO/Hang
s: - https://github.com/HangfireIO/Hangfire/security/advisories/GHSA-7rq6-7gv8-c37h - https://github.com/HangfireIO/Hangfire/issues/1958
CVE ID: CVE-2021-41239 State: PUBLISHED Published: 2022-03-08T18:05:12.000Z Last Updated: 2025-04-23T18:58:33.406Z Severity: MEDIUM (CVSS 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) Vendors: nextcloud Products: security-advisories Problem Types: CWE-200 Description: Nextcloud server is a self hosted system designed to provide cloud style services. In affected versions the User Status API did not consider the user enumeration settings by the administrator. This allowed a user to enumerate other users on the instance, even when user listings where disabled. It is recommended that the Nextcloud Server is upgraded to 20.0.14, 21.0.6 or 22.2.1. There are no known workarounds. Additional Ana
ended that the Nextcloud Server is upgraded to 20.0.14, 21.0.6 or 22.2.1. There are no known workarounds. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/nextcloud/security-advisories/security/advisories/GHSA-g722-cm3h-8wrx - https://github.com/nextcloud/server/issues/27122 - https://github.com/nextcloud/server/pull/29260 - https://security.gentoo.org/glsa/202208-17
CVE ID: CVE-2021-41241 State: PUBLISHED Published: 2022-03-08T18:25:10.000Z Last Updated: 2025-04-23T18:58:26.893Z Severity: MEDIUM (CVSS 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) Vendors: nextcloud Products: security-advisories Problem Types: CWE-863 Description: Nextcloud server is a self hosted system designed to provide cloud style services. The groupfolders application for Nextcloud allows sharing a folder with a group of people. In addition, it allows setting "advanced permissions" on subfolders, for example, a user could be granted access to the groupfolder but not specific subfolders. Due to a lacking permission check in affected versions, a user could still access these subf
ut not specific subfolders. Due to a lacking permission check in affected versions, a user could still access these subfolders by copying the groupfolder to another location. It is recommended that the Nextcloud Server is upgraded to 20.0.14, 21.0.6 or 22.2.1. Users unable to upgrade should disable the "groupfolders" application in the admin settings. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/nextcloud/security-advisories/security/advisories/GHSA-m4wp-r357-4q94 - https://github.com/nextcloud/groupfolders/issues/1692 - https://github.com/nextcloud/server/pull/29362 - https://security.gentoo.org/glsa/202208-17
CVE ID: CVE-2021-41242 State: PUBLISHED Published: 2021-12-10T22:25:13 Last Updated: 2024-08-04T03:08:31.500Z Severity: HIGH (CVSS 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H) Vendors: OpenOLAT Products: OpenOLAT Problem Types: CWE-23 Description: OpenOlat is a web-basedlearning management system. A path traversal vulnerability exists in OpenOlat prior to versions 15.5.12 and 16.0.5. By providing a filename that contains a relative path as a parameter in some REST methods, it is possible to create directory structures and write files anywhere on the target system. The attack could be used to write files anywhere in the web root folder or outside, depending on the configuration of the sy
attack could be used to write files anywhere in the web root folder or outside, depending on the configuration of the system and the properly configured permission of the application server user. The attack requires an OpenOlat user account, an enabled REST API and the rights on a business object to call the vulnerable REST calls. The problem is fixed in version 15.5.12 and 16.0.5. There is a workaround available. The vulnerability requires the REST module to be enabled. Disabling the REST module or limiting the REST module via some firewall or web-server access rules to be accessed only be trusted systems will mitigate the risk. Additional Analyst Notes: - CVE Program Container: References:
accessed only be trusted systems will mitigate the risk. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/OpenOLAT/OpenOLAT/security/advisories/GHSA-62hv-rfp4-hmrm - https://github.com/OpenOLAT/OpenOLAT/commit/336d5ce80681be61a0bbf4f73d2af5d1ff67e93a - https://github.com/OpenOLAT/OpenOLAT/commit/c450df7d7ffe6afde39ebca6da9136f1caa16ec4 - https://jira.openolat.org/browse/OO-5819
CVE ID: CVE-2021-41243 State: PUBLISHED Published: 2021-11-26T17:55:09 Last Updated: 2024-08-04T03:08:31.498Z Severity: CRITICAL (CVSS 9.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L) Vendors: baserproject Products: basercms Problem Types: CWE-78 Description: There is a Potential Zip Slip Vulnerability and OS Command Injection Vulnerability on the management system of baserCMS. Users with permissions to upload files may upload crafted zip files which may execute arbitrary commands on the host operating system. This is a vulnerability that needs to be addressed when the management system is used by an unspecified number of users. If you are eligible, please update to the new version as soon
agement system is used by an unspecified number of users. If you are eligible, please update to the new version as soon as possible. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/baserproject/basercms/security/advisories/GHSA-7rpc-9m88-cf9w - https://github.com/baserproject/basercms/commit/9088b99c329d1faff3a2f1269f37b9a9d8d5f6ff
CVE ID: CVE-2021-41244 State: PUBLISHED Published: 2021-11-15T20:05:11 Last Updated: 2024-08-04T03:08:31.510Z Severity: CRITICAL (CVSS 9.1 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H) Vendors: grafana Products: grafana Problem Types: CWE-610 Description: Grafana is an open-source platform for monitoring and observability. In affected versions when the fine-grained access control beta feature is enabled and there is more than one organization in the Grafana instance admins are able to access users from other organizations. Grafana 8.0 introduced a mechanism which allowed users with the Organization Admin role to list, add, remove, and update users’ roles in other organizations in which they
ers with the Organization Admin role to list, add, remove, and update users’ roles in other organizations in which they are not an admin. With fine-grained access control enabled, organization admins can list, add, remove and update users' roles in another organization, where they do not have organization admin role. All installations between v8.0 and v8.2.3 that have fine-grained access control beta enabled and more than one organization should be upgraded as soon as possible. If you cannot upgrade, you should turn off the fine-grained access control using a feature flag. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/grafana/grafana/security/advisories/
Additional Analyst Notes: - CVE Program Container: References: - https://github.com/grafana/grafana/security/advisories/GHSA-mpwp-42x6-4wmx - https://grafana.com/blog/2021/11/15/grafana-8.2.4-released-with-security-fixes/ - http://www.openwall.com/lists/oss-security/2021/11/15/1 - https://security.netapp.com/advisory/ntap-20211223-0001/
CVE ID: CVE-2021-41245 State: PUBLISHED Published: 2022-04-05T15:05:11.000Z Last Updated: 2025-04-22T18:17:28.995Z Severity: MEDIUM (CVSS 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N) Vendors: Combodo Products: iTop Problem Types: CWE-352 Description: Combodo iTop is a web based IT Service Management tool. In versions prior to 2.7.6 and 3.0.0, CSRF tokens generated by `privUITransactionFile` aren't properly checked. Versions 2.7.6 and 3.0.0 contain a patch for this issue. As a workaround, use the session implementation by adding in the iTop config file. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/Combodo/iTop/security/advis
st Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/Combodo/iTop/security/advisories/GHSA-33pr-5776-9jqf - https://github.com/Combodo/iTop/commit/7757f1f2d2330d49a3ebb40194f5ec4c8eaf8186 - https://huntr.dev/bounties/0a39630d-f4b9-4468-86d8-aea3b02f91ae
CVE ID: CVE-2021-41246 State: PUBLISHED Published: 2021-12-09T15:55:10 Last Updated: 2024-08-04T03:08:31.551Z Severity: MEDIUM (CVSS 4.6 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N) Vendors: auth0 Products: express-openid-connect Problem Types: CWE-384 Description: Express OpenID Connect is express JS middleware implementing sign on for Express web apps using OpenID Connect. Versions before and including `2.5.1` do not regenerate the session id and session cookie when user logs in. This behavior opens up the application to various session fixation vulnerabilities. Versions `2.5.2` contains a patch for this issue. Additional Analyst Notes: - CVE Program Container: References: - https://githu
`2.5.2` contains a patch for this issue. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/auth0/express-openid-connect/security/advisories/GHSA-7rg2-qxmf-hhx9 - https://github.com/auth0/express-openid-connect/commit/5ab67ff2bd84f76674066b5e129b43ab5f2f430f - https://github.com/auth0/express-openid-connect/releases/tag/v2.5.2
CVE ID: CVE-2021-41247 State: PUBLISHED Published: 2021-11-04T17:15:11 Last Updated: 2024-08-04T03:08:31.580Z Severity: LOW (CVSS 3.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N) Vendors: jupyterhub Products: jupyterhub Problem Types: CWE-613 Description: JupyterHub is an open source multi-user server for Jupyter notebooks. In affected versions users who have multiple JupyterLab tabs open in the same browser session, may see incomplete logout from the single-user server, as fresh credentials (for the single-user server only, not the Hub) reinstated after logout, if another active JupyterLab session is open while the logout takes place. Upgrade to JupyterHub 1.5. For distributed deployments,
active JupyterLab session is open while the logout takes place. Upgrade to JupyterHub 1.5. For distributed deployments, it is jupyterhub in the _user_ environment that needs patching. There are no patches necessary in the Hub environment. The only workaround is to make sure that only one JupyterLab tab is open when you log out. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/jupyterhub/jupyterhub/security/advisories/GHSA-cw7p-q79f-m2v7 - https://github.com/jupyterhub/jupyterhub/commit/5ac9e7f73a6e1020ffddc40321fc53336829fe27
CVE ID: CVE-2021-41248 State: PUBLISHED Published: 2021-11-04T20:15:11 Last Updated: 2024-08-04T03:08:31.617Z Severity: HIGH (CVSS 7.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L) Vendors: graphql Products: graphiql Problem Types: CWE-79 Description: GraphiQL is the reference implementation of this monorepo, GraphQL IDE, an official project under the GraphQL Foundation. All versions of graphiql older than graphiql@1.4.7 are vulnerable to compromised HTTP schema introspection responses or schema prop values with malicious GraphQL type names, exposing a dynamic XSS attack surface that can allow code injection on operation autocomplete. In order for the attack to take place, the user must load
rface that can allow code injection on operation autocomplete. In order for the attack to take place, the user must load a vulnerable schema in graphiql. There are a number of ways that can occur. By default, the schema URL is not attacker-controllable in graphiql or in its suggested implementations or examples, leaving only very complex attack vectors. If a custom implementation of graphiql's fetcher allows the schema URL to be set dynamically, such as a URL query parameter like ?endpoint= in graphql-playground, or a database provided value, then this custom graphiql implementation is vulnerable to phishing attacks, and thus much more readily available, low or no privelege level xss attacks
mentation is vulnerable to phishing attacks, and thus much more readily available, low or no privelege level xss attacks. The URLs could look like any generic looking graphql schema URL. It should be noted that desktop clients such as Altair, Insomnia, Postwoman, do not appear to be impacted by this. This vulnerability does not impact codemirror-graphql, monaco-graphql or other dependents, as it exists in onHasCompletion.ts in graphiql. It does impact all forks of graphiql, and every released version of graphiql. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/graphql/graphiql/security/advisories/GHSA-x4r7-m2q9-69c8 - https://github.com/graphql/graphql-pla
: - https://github.com/graphql/graphiql/security/advisories/GHSA-x4r7-m2q9-69c8 - https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7 - https://github.com/graphql/graphiql/commit/cb237eeeaf7333c4954c752122261db7520f7bf4
CVE ID: CVE-2021-41249 State: PUBLISHED Published: 2021-11-04T20:05:12 Last Updated: 2024-08-04T03:08:31.577Z Severity: HIGH (CVSS 7.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L) Vendors: graphql Products: graphql-playground Problem Types: CWE-79 Description: GraphQL Playground is a GraphQL IDE for development of graphQL focused applications. All versions of graphql-playground-react older than graphql-playground-react@1.7.28 are vulnerable to compromised HTTP schema introspection responses or schema prop values with malicious GraphQL type names, exposing a dynamic XSS attack surface that can allow code injection on operation autocomplete. In order for the attack to take place, the user mus
ack surface that can allow code injection on operation autocomplete. In order for the attack to take place, the user must load a malicious schema in graphql-playground. There are several ways this can occur, including by specifying the URL to a malicious schema in the endpoint query parameter. If a user clicks on a link to a GraphQL Playground installation that specifies a malicious server, arbitrary JavaScript can run in the user's browser, which can be used to exfiltrate user credentials or other harmful goals. If you are using graphql-playground-react directly in your client app, upgrade to version 1.7.28 or later. Additional Analyst Notes: - CVE Program Container: References: - https://g
ient app, upgrade to version 1.7.28 or later. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7 - https://github.com/graphql/graphiql/security/advisories/GHSA-x4r7-m2q9-69c8 - https://github.com/graphql/graphql-playground/commit/b8a956006835992f12c46b90384a79ab82bcadad
CVE ID: CVE-2021-41250 State: PUBLISHED Published: 2021-11-05T22:45:11 Last Updated: 2024-08-04T03:08:31.640Z Severity: MEDIUM (CVSS 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N) Vendors: python-discord Products: bot Problem Types: CWE-20 Description: Python discord bot is the community bot for the Python Discord community. In affected versions when a non-blacklisted URL and an otherwise triggering filter token is included in the same message the token filter does not trigger. This means that by including any non-blacklisted URL moderation filters can be bypassed. This issue has been resolved in commit 67390298852513d13e0213870e50fb3cff1424e0 Additional Analyst Notes: - CVE Program Conta
issue has been resolved in commit 67390298852513d13e0213870e50fb3cff1424e0 Additional Analyst Notes: - CVE Program Container: References: - https://github.com/python-discord/bot/security/advisories/GHSA-j8c3-8x46-8pp6 - https://github.com/python-discord/bot/commit/67390298852513d13e0213870e50fb3cff1424e0
CVE ID: CVE-2021-41251 State: PUBLISHED Published: 2021-11-05T22:50:12 Last Updated: 2024-08-04T03:08:31.645Z Severity: MEDIUM (CVSS 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N) Vendors: SAP Products: cloud-sdk-js Problem Types: CWE-200 Description: @sap-cloud-sdk/core contains the core functionality of the SAP Cloud SDK as well as the SAP Business Technology Platform abstractions. This affects applications on SAP Business Technology Platform that use the SAP Cloud SDK and enabled caching of destinations. In affected versions and in some cases, when user information was missing, destinations were cached without user information, allowing other users to retrieve the same destination with
s missing, destinations were cached without user information, allowing other users to retrieve the same destination with its permissions. By default, destination caching is disabled. The security for caching has been increased. The changes are released in version 1.52.0. Users unable to upgrade are advised to disable destination caching (it is disabled by default). Additional Analyst Notes: - CVE Program Container: References: - https://github.com/SAP/cloud-sdk-js/security/advisories/GHSA-gp2f-254m-rh32 - https://github.com/SAP/cloud-sdk-js/pull/1769 - https://github.com/SAP/cloud-sdk-js/pull/1770
CVE ID: CVE-2021-41252 State: PUBLISHED Published: 2021-11-16T18:05:10 Last Updated: 2024-08-04T03:08:31.511Z Severity: HIGH (CVSS 7.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N) Vendors: getkirby Products: kirby Problem Types: CWE-79 Description: Kirby is an open source file structured CMS ### Impact Kirby's writer field stores its formatted content as HTML code. Unlike with other field types, it is not possible to escape HTML special characters against cross-site scripting (XSS) attacks, otherwise the formatting would be lost. If the user is logged in to the Panel, a harmful script can for example trigger requests to Kirby's API with the permissions of the victim. Because the writer fiel
rmful script can for example trigger requests to Kirby's API with the permissions of the victim. Because the writer field did not securely sanitize its contents on save, it was possible to inject malicious HTML code into the content file by sending it to Kirby's API directly without using the Panel. This malicious HTML code would then be displayed on the site frontend and executed in the browsers of site visitors and logged in users who are browsing the site. Attackers must be in your group of authenticated Panel users in order to exploit this weakness. Users who do not make use of the writer field are not affected. This issue has been patched in Kirby 3.5.8 by sanitizing all writer field co
e use of the writer field are not affected. This issue has been patched in Kirby 3.5.8 by sanitizing all writer field contents on the backend whenever the content is modified via Kirby's API. Please update to this or a later version to fix the vulnerability. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/getkirby/kirby/security/advisories/GHSA-x7j7-qp7j-hw3q - https://github.com/getkirby/kirby/commit/25fc5c6b330442e6433c99befc688f3698c5d1fc - https://github.com/getkirby/kirby/releases/tag/3.5.8
CVE ID: CVE-2021-41253 State: PUBLISHED Published: 2021-11-08T21:45:11 Last Updated: 2024-08-04T03:08:31.619Z Severity: MEDIUM (CVSS 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) Vendors: zyantific Products: zydis Problem Types: CWE-122, CWE-457 Description: Zydis is an x86/x86-64 disassembler library. Users of Zydis versions v3.2.0 and older that use the string functions provided in `zycore` in order to append untrusted user data to the formatter buffer within their custom formatter hooks can run into heap buffer overflows. Older versions of Zydis failed to properly initialize the string object within the formatter buffer, forgetting to initialize a few fields, leaving their value to ch
itialize the string object within the formatter buffer, forgetting to initialize a few fields, leaving their value to chance. This could then in turn cause zycore functions like `ZyanStringAppend` to make incorrect calculations for the new target size, resulting in heap memory corruption. This does not affect the regular uncustomized Zydis formatter, because Zydis internally doesn't use the string functions in zycore that act upon these fields. However, because the zycore string functions are the intended way to work with the formatter buffer for users of the library that wish to extend the formatter, we still consider this to be a vulnerability in Zydis. This bug is patched starting in vers
ish to extend the formatter, we still consider this to be a vulnerability in Zydis. This bug is patched starting in version 3.2.1. As a workaround, users may refrain from using zycore string functions in their formatter hooks until updating to a patched version. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/zyantific/zydis/security/advisories/GHSA-q42v-hv86-3m4g - https://github.com/zyantific/zydis/commit/55dd08c210722aed81b38132f5fd4a04ec1943b5 - https://huntr.dev/bounties/96b0a482-7041-45b1-9327-c6a4a8f32d3a - https://huntr.dev/bounties/d2536d7d-36ce-4723-928c-98d1ee039784
CVE ID: CVE-2021-41254 State: PUBLISHED Published: 2021-11-12T17:45:10 Last Updated: 2024-08-04T03:08:31.648Z Severity: HIGH (CVSS 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) Vendors: fluxcd Products: kustomize-controller Problem Types: CWE-78 Description: kustomize-controller is a Kubernetes operator, specialized in running continuous delivery pipelines for infrastructure and workloads defined with Kubernetes manifests and assembled with Kustomize. Users that can create Kubernetes Secrets, Service Accounts and Flux Kustomization objects, could execute commands inside the kustomize-controller container by embedding a shell script in a Kubernetes Secret. This can be used to run `kubectl