Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
CVE ID: CVE-2021-43776 State: PUBLISHED Published: 2021-11-26T18:15:10 Last Updated: 2024-08-04T04:03:08.688Z Severity: HIGH (CVSS 7.4 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N) Vendors: backstage Products: backstage Problem Types: CWE-79 Description: Backstage is an open platform for building developer portals. In affected versions the auth-backend plugin allows a malicious actor to trick another user into visiting a vulnerable URL that executes an XSS attack. This attack can potentially allow the attacker to exfiltrate access tokens or other secrets from the user's browser. The default CSP does prevent this attack, but it is expected that some deployments have these policies disabled du
wser. The default CSP does prevent this attack, but it is expected that some deployments have these policies disabled due to incompatibilities. This is vulnerability is patched in version `0.4.9` of `@backstage/plugin-auth-backend`. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/backstage/backstage/security/advisories/GHSA-w7fj-336r-vw49 - https://github.com/backstage/backstage/tree/master/plugins/auth-backend
CVE ID: CVE-2021-43777 State: PUBLISHED Published: 2021-11-23T23:30:10 Last Updated: 2024-08-04T04:03:08.609Z Severity: MEDIUM (CVSS 6.8 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N) Vendors: getredash Products: redash Problem Types: CWE-352 Description: Redash is a package for data visualization and sharing. In Redash version 10.0 and prior, the implementation of Google Login (via OAuth) incorrectly uses the `state` parameter to pass the next URL to redirect the user to after login. The `state` parameter should be used for a Cross-Site Request Forgery (CSRF) token, not a static and easily predicted value. This vulnerability does not affect users who do not use Google Login for their instanc
tatic and easily predicted value. This vulnerability does not affect users who do not use Google Login for their instance of Redash. A patch in the `master` and `release/10.x.x` branches addresses this by replacing `Flask-Oauthlib` with `Authlib` which automatically provides and validates a CSRF token for the state variable. The new implementation stores the next URL on the user session object. As a workaround, one may disable Google Login to mitigate the vulnerability. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/getredash/redash/security/advisories/GHSA-vhc7-w7r8-8m34 - https://github.com/getredash/redash/commit/da696ff7f84787cbf85967460fac52886cbe063
rity/advisories/GHSA-vhc7-w7r8-8m34 - https://github.com/getredash/redash/commit/da696ff7f84787cbf85967460fac52886cbe063e
CVE ID: CVE-2021-43778 State: PUBLISHED Published: 2021-11-24T18:50:10.000Z Last Updated: 2025-09-08T15:26:50.189Z Severity: CRITICAL (CVSS 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) Vendors: pluginsGLPI Products: barcode Problem Types: CWE-22 Description: Barcode is a GLPI plugin for printing barcodes and QR codes. GLPI instances version 2.x prior to version 2.6.1 with the barcode plugin installed are vulnerable to a path traversal vulnerability. This issue was patched in version 2.6.1. As a workaround, delete the `front/send.php` file. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/pluginsGLPI/barcode/security/advisories/GHSA-2pjh-h828-wcw9 - htt
VE Program Container: References: - https://github.com/pluginsGLPI/barcode/security/advisories/GHSA-2pjh-h828-wcw9 - https://github.com/pluginsGLPI/barcode/commit/428c3d9adfb446e8492b1c2b7affb3d34072ff46 - https://github.com/hansmach1ne/MyExploits/tree/main/Path%20Traversal%20in%20GLPI%20Barcode%20plugin - https://github.com/pluginsGLPI/barcode/releases/tag/2.6.1
CVE ID: CVE-2021-43779 State: PUBLISHED Published: 2022-01-05T18:45:11.000Z Last Updated: 2025-09-08T15:33:16.901Z Severity: CRITICAL (CVSS 9.9 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:H) Vendors: pluginsGLPI Products: addressing Problem Types: CWE-20 Description: GLPI is an open source IT Asset Management, issue tracking system and service desk system. The GLPI addressing plugin in versions < 2.9.1 suffers from authenticated Remote Code Execution vulnerability, allowing access to the server's underlying operating system using command injection abuse of functionality. There is no workaround for this issue and users are advised to upgrade or to disable the addressing plugin. Additional Anal
re is no workaround for this issue and users are advised to upgrade or to disable the addressing plugin. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/pluginsGLPI/addressing/security/advisories/GHSA-q5fp-xpr8-77jh - https://github.com/pluginsGLPI/addressing/commit/6f55964803054a5acb5feda92c7c7f1d91ab5366 - https://github.com/hansmach1ne/MyExploits/tree/main/RCE_GLPI_addressing_plugin
CVE ID: CVE-2021-43780 State: PUBLISHED Published: 2021-11-23T23:55:10 Last Updated: 2024-08-04T04:03:08.620Z Severity: MEDIUM (CVSS 6.8 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N) Vendors: getredash Products: redash Problem Types: CWE-918 Description: Redash is a package for data visualization and sharing. In versions 10.0 and priorm the implementation of URL-loading data sources like JSON, CSV, or Excel is vulnerable to advanced methods of Server Side Request Forgery (SSRF). These vulnerabilities are only exploitable on installations where a URL-loading data source is enabled. As of time of publication, the `master` and `release/10.x.x` branches address this by applying the Advocate libr
nabled. As of time of publication, the `master` and `release/10.x.x` branches address this by applying the Advocate library for making http requests instead of the requests library directly. Users should upgrade to version 10.0.1 to receive this patch. There are a few workarounds for mitigating the vulnerability without upgrading. One can disable the vulnerable data sources entirely, by adding the following env variable to one's configuration, making them unavailable inside the webapp. One can switch any data source of certain types (viewable in the GitHub Security Advisory) to be `View Only` for all groups on the Settings > Groups > Data Sources screen. For users unable to update an admin m
) to be `View Only` for all groups on the Settings > Groups > Data Sources screen. For users unable to update an admin may modify Redash's configuration through environment variables to mitigate this issue. Depending on the version of Redash, an admin may also need to run a CLI command to re-encrypt some fields in the database. The `master` and `release/10.x.x` branches as of time of publication have removed the default value for `REDASH_COOKIE_SECRET`. All future releases will also require this to be set explicitly. For existing installations, one will need to ensure that explicit values are set for the `REDASH_COOKIE_SECRET` and `REDASH_SECRET_KEY `variables. Additional Analyst Notes: - CV
explicit values are set for the `REDASH_COOKIE_SECRET` and `REDASH_SECRET_KEY `variables. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/getredash/redash/security/advisories/GHSA-fcpv-hgq6-87h7 - https://github.com/getredash/redash/commit/61bbb5aa7a23a93f2f93710005f71bc972826099
CVE ID: CVE-2021-43781 State: PUBLISHED Published: 2021-12-06T17:45:10 Last Updated: 2024-08-04T04:03:08.806Z Severity: MEDIUM (CVSS 6.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) Vendors: inveniosoftware Products: invenio-drafts-resources Problem Types: CWE-862 Description: Invenio-Drafts-Resources is a submission/deposit module for Invenio, a software framework for research data management. Invenio-Drafts-Resources prior to versions 0.13.7 and 0.14.6 does not properly check permissions when a record is published. The vulnerability is exploitable in a default installation of InvenioRDM. An authenticated a user is able via REST API calls to publish draft records of other users if they kno
on of InvenioRDM. An authenticated a user is able via REST API calls to publish draft records of other users if they know the record identifier and the draft validates (e.g. all require fields filled out). An attacker is not able to modify the data in the record, and thus e.g. *cannot* change a record from restricted to public. The problem is patched in Invenio-Drafts-Resources v0.13.7 and 0.14.6, which is part of InvenioRDM v6.0.1 and InvenioRDM v7.0 respectively. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/inveniosoftware/invenio-drafts-resources/security/advisories/GHSA-xr38-w74q-r8jv - https://github.com/inveniosoftware/invenio-drafts-resources/com
afts-resources/security/advisories/GHSA-xr38-w74q-r8jv - https://github.com/inveniosoftware/invenio-drafts-resources/commit/039b0cff1ad4b952000f4d8c3a93f347108b6626
CVE ID: CVE-2021-43782 State: PUBLISHED Published: 2021-12-15T19:30:14 Last Updated: 2024-08-04T04:03:08.971Z Severity: MEDIUM (CVSS 6.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L) Vendors: Enalean Products: tuleap Problem Types: CWE-90, CWE-74 Description: Tuleap is a Libre and Open Source tool for end to end traceability of application and system developments. This is a follow up to GHSA-887w-pv2r-x8pm/CVE-2021-41276, the initial fix was incomplete. Tuleap does not sanitize properly the search filter built from the ldap_id attribute of a user during the daily synchronization. A malicious user could force accounts to be suspended or take over another account by forcing the update of the l
ation. A malicious user could force accounts to be suspended or take over another account by forcing the update of the ldap_uid attribute. Note that the malicious user either need to have site administrator capability on the Tuleap instance or be an LDAP operator with the capability to create/modify account. The Tuleap instance needs to have the LDAP plugin activated and enabled for this issue to be exploitable. The following versions contain the fix: Tuleap Community Edition 13.2.99.83, Tuleap Enterprise Edition 13.1-6, and Tuleap Enterprise Edition 13.2-4. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/Enalean/tuleap/security/advisories/GHSA-cwv9-hhm4-j
yst Notes: - CVE Program Container: References: - https://github.com/Enalean/tuleap/security/advisories/GHSA-cwv9-hhm4-jr84 - https://github.com/Enalean/tuleap/security/advisories/GHSA-887w-pv2r-x8pm - https://github.com/Enalean/tuleap/commit/64e77561eba9f8233199c2962b3497ed7294a7d2 - https://tuleap.net/plugins/git/tuleap/tuleap/stable?a=commit&h=64e77561eba9f8233199c2962b3497ed7294a7d2 - https://tuleap.net/plugins/tracker/?aid=24168
CVE ID: CVE-2021-43783 State: PUBLISHED Published: 2021-11-29T19:20:09 Last Updated: 2024-08-04T04:03:08.643Z Severity: HIGH (CVSS 8.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L) Vendors: backstage Products: backstage Problem Types: CWE-22 Description: @backstage/plugin-scaffolder-backend is the backend for the default Backstage software templates. In affected versions a malicious actor with write access to a registered scaffolder template is able to manipulate the template in a way that writes files to arbitrary paths on the scaffolder-backend host instance. This vulnerability can in some situation also be exploited through user input when executing a template, meaning you do not need wri
bility can in some situation also be exploited through user input when executing a template, meaning you do not need write access to the templates. This method will not allow the attacker to control the contents of the injected file however, unless the template is also crafted in a specific way that gives control of the file contents. This vulnerability is fixed in version `0.15.14` of the `@backstage/plugin-scaffolder-backend`. This attack is mitigated by restricting access and requiring reviews when registering or modifying scaffolder templates. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/backstage/backstage/security/advisories/GHSA-mg3m-f475-28hv -
- CVE Program Container: References: - https://github.com/backstage/backstage/security/advisories/GHSA-mg3m-f475-28hv - https://github.com/backstage/backstage/commit/f9352ab606367cd9efc6ff048915c70ed3013b7f
CVE ID: CVE-2021-43784 State: PUBLISHED Published: 2021-12-06T00:00:00 Last Updated: 2024-10-15T17:14:20.240Z Severity: MEDIUM (CVSS 6 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L) Vendors: opencontainers Products: runc Problem Types: CWE-190 Description: runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. In runc, netlink is used internally as a serialization system for specifying the relevant container configuration to the `C` portion of the code (responsible for the based namespace setup of containers). In all versions of runc prior to 1.0.3, the encoder did not handle the possibility of an integer overflow in the 16-bit length field for the
unc prior to 1.0.3, the encoder did not handle the possibility of an integer overflow in the 16-bit length field for the byte array attribute type, meaning that a large enough malicious byte array attribute could result in the length overflowing and the attribute contents being parsed as netlink messages for container configuration. This vulnerability requires the attacker to have some control over the configuration of the container and would allow the attacker to bypass the namespace restrictions of the container by simply adding their own netlink payload which disables all namespaces. The main users impacted are those who allow untrusted images with untrusted configurations to run on their
l namespaces. The main users impacted are those who allow untrusted images with untrusted configurations to run on their machines (such as with shared cloud infrastructure). runc version 1.0.3 contains a fix for this bug. As a workaround, one may try disallowing untrusted namespace paths from your container. It should be noted that untrusted namespace paths would allow the attacker to disable namespace protections entirely even in the absence of this bug. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/opencontainers/runc/security/advisories/GHSA-v95c-p5hm-xq8f - https://github.com/opencontainers/runc/commit/9c444070ec7bb83995dbc01
ers/runc/security/advisories/GHSA-v95c-p5hm-xq8f - https://github.com/opencontainers/runc/commit/9c444070ec7bb83995dbc0185da68284da71c554 - https://github.com/opencontainers/runc/commit/d72d057ba794164c3cce9451a00b72a78b25e1ae - https://github.com/opencontainers/runc/commit/f50369af4b571e358f20b139eea52d612eb55eed - https://bugs.chromium.org/p/project-zero/issues/detail?id=2241 - https://lists.debian.org/debian-lts-announce/2021/12/msg00005.html - https://lists.debian.org/debian-lts-announce/2024/02/msg00005.html
CVE ID: CVE-2021-43785 State: PUBLISHED Published: 2021-11-26T18:20:11 Last Updated: 2024-08-04T04:03:08.932Z Severity: HIGH (CVSS 7.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L) Vendors: joeattardi Products: emoji-button Problem Types: CWE-79 Description: @joeattardi/emoji-button is a Vanilla JavaScript emoji picker component. In affected versions there are two vectors for XSS attacks: a URL for a custom emoji, and an i18n string. In both of these cases, a value can be crafted such that it can insert a `script` tag into the page and execute malicious code. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/joeattardi/emoji-button/security/advisories/GHSA-f
lyst Notes: - CVE Program Container: References: - https://github.com/joeattardi/emoji-button/security/advisories/GHSA-f34m-x9pj-62vq - https://github.com/joeattardi/emoji-button/commit/05970c09180cd27fff493e998ac5bf0468b1bb16 - https://github.com/joeattardi/emoji-button/commit/fe54bef107eb3f74873a4018f2ff49fa124c6a2e
CVE ID: CVE-2021-43786 State: PUBLISHED Published: 2021-11-29T19:30:17 Last Updated: 2024-08-04T04:03:08.931Z Severity: CRITICAL (CVSS 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) Vendors: NodeBB Products: NodeBB Problem Types: CWE-287 Description: Nodebb is an open source Node.js based forum software. In affected versions incorrect logic present in the token verification step unintentionally allowed master token access to the API. The vulnerability has been patch as of v1.18.5. Users are advised to upgrade as soon as possible. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/NodeBB/NodeBB/releases/tag/v1.18.5 - https://github.com/NodeBB/NodeBB/securit
ontainer: References: - https://github.com/NodeBB/NodeBB/releases/tag/v1.18.5 - https://github.com/NodeBB/NodeBB/security/advisories/GHSA-hf2m-j98r-4fqw - https://github.com/NodeBB/NodeBB/commit/04dab1d550cdebf4c1567bca9a51f8b9ca48a500 - https://blog.sonarsource.com/nodebb-remote-code-execution-with-one-shot/
CVE ID: CVE-2021-43787 State: PUBLISHED Published: 2021-11-29T19:30:11 Last Updated: 2024-08-04T04:03:08.858Z Severity: CRITICAL (CVSS 9 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H) Vendors: NodeBB Products: NodeBB Problem Types: CWE-79, CWE-1321 Description: Nodebb is an open source Node.js based forum software. In affected versions a prototype pollution vulnerability in the uploader module allowed a malicious user to inject arbitrary data (i.e. javascript) into the DOM, theoretically allowing for an account takeover when used in conjunction with a path traversal vulnerability disclosed at the same time as this report. The vulnerability has been patched as of v1.18.5. Users are advised to
ility disclosed at the same time as this report. The vulnerability has been patched as of v1.18.5. Users are advised to upgrade as soon as possible. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/NodeBB/NodeBB/security/advisories/GHSA-wx69-rvg3-x7fc - https://github.com/NodeBB/NodeBB/commit/1783f918bc19568f421473824461ff2ed7755e4c - https://github.com/NodeBB/NodeBB/releases/tag/v1.18.5 - https://blog.sonarsource.com/nodebb-remote-code-execution-with-one-shot/
CVE ID: CVE-2021-43788 State: PUBLISHED Published: 2021-11-29T19:35:12 Last Updated: 2024-08-04T04:03:08.978Z Severity: MEDIUM (CVSS 5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N) Vendors: NodeBB Products: NodeBB Problem Types: CWE-22 Description: Nodebb is an open source Node.js based forum software. Prior to v1.18.5, a path traversal vulnerability was present that allowed users to access JSON files outside of the expected `languages/` directory. The vulnerability has been patched as of v1.18.5. Users are advised to upgrade as soon as possible. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/NodeBB/NodeBB/releases/tag/v1.18.5 - https://github.com/NodeBB/
CVE Program Container: References: - https://github.com/NodeBB/NodeBB/releases/tag/v1.18.5 - https://github.com/NodeBB/NodeBB/security/advisories/GHSA-pfj7-2qfw-vwgm - https://github.com/NodeBB/NodeBB/commit/c8b2fc46dc698db687379106b3f01c71b80f495f - https://blog.sonarsource.com/nodebb-remote-code-execution-with-one-shot/
CVE ID: CVE-2021-43789 State: PUBLISHED Published: 2021-12-07T16:45:12 Last Updated: 2024-08-04T04:03:08.643Z Severity: HIGH (CVSS 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) Vendors: PrestaShop Products: PrestaShop Problem Types: CWE-89 Description: PrestaShop is an Open Source e-commerce web application. Versions of PrestaShop prior to 1.7.8.2 are vulnerable to blind SQL injection using search filters with `orderBy` and `sortOrder` parameters. The problem is fixed in version 1.7.8.2. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/PrestaShop/PrestaShop/security/advisories/GHSA-6xxj-gcjq-wgf4 - https://github.com/PrestaShop/PrestaShop/issues/26623 -
/PrestaShop/PrestaShop/security/advisories/GHSA-6xxj-gcjq-wgf4 - https://github.com/PrestaShop/PrestaShop/issues/26623 - https://github.com/PrestaShop/PrestaShop/releases/tag/1.7.8.2
CVE ID: CVE-2021-43790 State: PUBLISHED Published: 2021-11-29T23:55:10 Last Updated: 2024-08-04T04:03:08.681Z Severity: HIGH (CVSS 8.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H) Vendors: bytecodealliance Products: lucet Problem Types: CWE-416 Description: Lucet is a native WebAssembly compiler and runtime. There is a bug in the main branch of `lucet-runtime` affecting all versions published to crates.io that allows a use-after-free in an Instance object that could result in memory corruption, data race, or other related issues. This bug was introduced early in the development of Lucet and is present in all releases. As a result of this bug, and dependent on the memory backing for the Inst
pment of Lucet and is present in all releases. As a result of this bug, and dependent on the memory backing for the Instance objects, it is possible to trigger a use-after-free when the Instance is dropped. Users should upgrade to the main branch of the Lucet repository. Lucet no longer provides versioned releases on crates.io. There is no way to remediate this vulnerability without upgrading. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/bytecodealliance/lucet/security/advisories/GHSA-hf79-8hjp-rrvq - https://github.com/bytecodealliance/lucet/commit/7c7757c772fb709c61b1442bcc1e1fbee97bf4a8 - https://crates.io/crates/lucet-runtime
CVE ID: CVE-2021-43791 State: PUBLISHED Published: 2021-12-02T00:15:11 Last Updated: 2024-08-04T04:03:08.967Z Severity: MEDIUM (CVSS 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N) Vendors: zulip Products: zulip Problem Types: CWE-613 Description: Zulip is an open source group chat application that combines real-time chat with threaded conversations. In affected versions expiration dates on the confirmation objects associated with email invitations were not enforced properly in the new account registration flow. A confirmation link takes a user to the check_prereg_key_and_redirect endpoint, before getting redirected to POST to /accounts/register/. The problem was that validation was happen
_redirect endpoint, before getting redirected to POST to /accounts/register/. The problem was that validation was happening in the check_prereg_key_and_redirect part and not in /accounts/register/ - meaning that one could submit an expired confirmation key and be able to register. The issue is fixed in Zulip 4.8. There are no known workarounds and users are advised to upgrade as soon as possible. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/zulip/zulip/security/advisories/GHSA-wj76-pcqr-mf9f - https://github.com/zulip/zulip/commit/a014ef75a3a0ed7f24ebb157632ba58751e732c6
CVE ID: CVE-2021-43792 State: PUBLISHED Published: 2021-12-01T19:35:17 Last Updated: 2024-08-04T04:03:08.901Z 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: discourse Products: discourse Problem Types: CWE-200 Description: Discourse is an open source discussion platform. In affected versions a vulnerability affects users of tag groups who use the "Tags are visible only to the following groups" feature. A tag group may only allow a certain group (e.g. staff) to view certain tags. Users who were tracking or watching the tags via /preferences/tags, then have their staff status revoked will still see notifications related to the tag, but will not see the tag on
/tags, then have their staff status revoked will still see notifications related to the tag, but will not see the tag on each topic. This issue has been patched in stable version 2.7.11. Users are advised to upgrade as soon as possible. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/discourse/discourse/security/advisories/GHSA-pq2x-vq37-8522 - https://github.com/discourse/discourse/commit/cdaf7f4bb3ec268238e4c29a14bb73fad56574b4 - https://meta.discourse.org/t/non-forum-staff-getting-notifications-for-staff-only-tags/184895