Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
inject invalidated HTML code into these additional fields, which is then stored in the service `user_metdata` payload (using the `name` property). Verification emails, when applicable, are generated using this metadata. It is therefor possible for an actor to craft a malicious link by injecting HTML, which is then rendered as the recipient's name within the delivered email template. You are impacted by this vulnerability if you are using `auth0-lock` version `11.32.2` or lower and are using the “additional signup fields” feature in your application. Upgrade to version `11.33.0`. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/auth
33.0`. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/auth0/lock/security/advisories/GHSA-7ww6-75fj-jcj7 - https://github.com/auth0/lock/commit/79ae557d331274b114848150f19832ae341771b1
CVE ID: CVE-2022-29173 State: PUBLISHED Published: 2022-05-05T22:30:12.000Z Last Updated: 2025-04-23T18:31:00.276Z Severity: HIGH (CVSS 8 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H) Vendors: theupdateframework Products: go-tuf Problem Types: CWE-354 Description: go-tuf is a Go implementation of The Update Framework (TUF). go-tuf does not correctly implement the client workflow for updating the metadata files for roles other than the root role. Specifically, checks for rollback attacks are not implemented correctly meaning an attacker can cause clients to install software that is older than the software which the client previously knew to be available, and may include software with known vu
that is older than the software which the client previously knew to be available, and may include software with known vulnerabilities. In more detail, the client code of go-tuf has several issues in regards to preventing rollback attacks: 1. It does not take into account the content of any previously trusted metadata, if available, before proceeding with updating roles other than the root role (i.e., steps 5.4.3.1 and 5.5.5 of the detailed client workflow). This means that any form of version verification done on the newly-downloaded metadata is made using the default value of zero, which always passes. 2. For both timestamp and snapshot roles, go-tuf saves these metadata files as trusted be
of zero, which always passes. 2. For both timestamp and snapshot roles, go-tuf saves these metadata files as trusted before verifying if the version of the metafiles they refer to is correct (i.e., steps 5.5.4 and 5.6.4 of the detailed client workflow). A fix is available in version 0.3.0 or newer. No workarounds are known for this issue apart from upgrading. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-66x3-6cw3-v5gj - https://github.com/theupdateframework/go-tuf/commit/ed6788e710fc3093a7ecc2d078bf734c0f200d8d
CVE ID: CVE-2022-29174 State: PUBLISHED Published: 2022-05-17T20:45:10.000Z Last Updated: 2025-04-23T18:25:30.812Z Severity: HIGH (CVSS 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) Vendors: Countly Products: countly-server Problem Types: CWE-640 Description: countly-server is the server-side part of Countly, a product analytics solution. Prior to versions 22.03.7 and 21.11.4, a malicious actor who knows an account email address/username and full name specified in the database is capable of guessing the password reset token. The actor may use this information to reset the password and take over the account. The problem has been patched in Countly Server version 22.03.7 for servers using
he password and take over the account. The problem has been patched in Countly Server version 22.03.7 for servers using the new user interface and in 21.11.4 for servers using the old user interface. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/Countly/countly-server/security/advisories/GHSA-98vh-wqw5-p23v - https://github.com/Countly/countly-server/commit/2bfa1ee1fa46e9bb007cf8687ad197ab9c604999
CVE ID: CVE-2022-29175 State: REJECTED Published: 2022-05-05T22:15:11 Last Updated: 2022-05-16T19:30:09 Description: No description available.
CVE ID: CVE-2022-29176 State: PUBLISHED Published: 2022-05-05T22:05:10.000Z Last Updated: 2025-04-23T18:31:05.888Z Severity: CRITICAL (CVSS 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) Vendors: rubygems Products: rubygems.org Problem Types: CWE-862 Description: Rubygems is a package registry used to supply software for the Ruby language ecosystem. Due to a bug in the yank action, it was possible for any RubyGems.org user to remove and replace certain gems even if that user was not authorized to do so. To be vulnerable, a gem needed: one or more dashes in its name creation within 30 days OR no updates for over 100 days At present, we believe this vulnerability has not been exploited. Rub
ion within 30 days OR no updates for over 100 days At present, we believe this vulnerability has not been exploited. RubyGems.org sends an email to all gem owners when a gem version is published or yanked. We have not received any support emails from gem owners indicating that their gem has been yanked without authorization. An audit of gem changes for the last 18 months did not find any examples of this vulnerability being used in a malicious way. A deeper audit for any possible use of this exploit is ongoing, and we will update this advisory once it is complete. Using Bundler in --frozen or --deployment mode in CI and during deploys, as the Bundler team has always recommended, will guarant
dler in --frozen or --deployment mode in CI and during deploys, as the Bundler team has always recommended, will guarantee that your application does not silently switch to versions created using this exploit. To audit your application history for possible past exploits, review your Gemfile.lock and look for gems whose platform changed when the version number did not change. For example, gemname-3.1.2 updating to gemname-3.1.2-java could indicate a possible abuse of this vulnerability. RubyGems.org has been patched and is no longer vulnerable to this issue as of the 5th of May 2022. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/r
May 2022. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/rubygems/rubygems.org/security/advisories/GHSA-hccv-rwq6-vh79 - https://hackerone.com/bugs?subject=rubygems&report_id=1559856 - https://security.netapp.com/advisory/ntap-20220616-0002/
CVE ID: CVE-2022-29177 State: PUBLISHED Published: 2022-05-20T16:20:10.000Z Last Updated: 2025-04-23T18:24:38.893Z 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: ethereum Products: go-ethereum Problem Types: CWE-400 Description: Go Ethereum is the official Golang implementation of the Ethereum protocol. Prior to version 1.10.17, a vulnerable node, if configured to use high verbosity logging, can be made to crash when handling specially crafted p2p messages sent from an attacker node. Version 1.10.17 contains a patch that addresses the problem. As a workaround, setting loglevel to default level (`INFO`) makes the node not vulnerable to this attack. Additiona
lem. As a workaround, setting loglevel to default level (`INFO`) makes the node not vulnerable to this attack. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/ethereum/go-ethereum/security/advisories/GHSA-wjxw-gh3m-7pm5 - https://github.com/ethereum/go-ethereum/pull/24507
CVE ID: CVE-2022-29178 State: PUBLISHED Published: 2022-05-20T18:15:12.000Z Last Updated: 2025-04-23T18:24:33.303Z Severity: HIGH (CVSS 8.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) Vendors: cilium Products: cilium Problem Types: CWE-276 Description: Cilium is open source software for providing and securing network connectivity and loadbalancing between application workloads. Cilium prior to versions 1.9.16, 1.10.11, and 1.11.15 contains an incorrect default permissions vulnerability. Operating Systems with users belonging to the group ID 1000 can access the API of Cilium via Unix domain socket available on the host where Cilium is running. This could allow malicious users to compromise
um via Unix domain socket available on the host where Cilium is running. This could allow malicious users to compromise integrity as well as system availability on that host. The problem has been fixed and the patch is available in versions 1.9.16, 1.10.11, and 1.11.5. A potential workaround is to modify Cilium's DaemonSet to run with a certain command, which can be found in the GitHub Security Advisory for this vulnerability. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/cilium/cilium/security/advisories/GHSA-6p8v-8cq8-v2r3 - https://github.com/cilium/cilium/releases/tag/v1.10.11 - https://github.com/cilium/cilium/releases/tag/v
p8v-8cq8-v2r3 - https://github.com/cilium/cilium/releases/tag/v1.10.11 - https://github.com/cilium/cilium/releases/tag/v1.11.5 - https://github.com/cilium/cilium/releases/tag/v1.9.16
CVE ID: CVE-2022-29179 State: PUBLISHED Published: 2022-05-20T18:30:12.000Z Last Updated: 2025-04-23T18:24:28.294Z Severity: HIGH (CVSS 7.5 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H) Vendors: cilium Products: cilium Problem Types: CWE-269 Description: Cilium is open source software for providing and securing network connectivity and loadbalancing between application workloads. Prior to versions 1.9.16, 1.10.11, and 1.11.15, if an attacker is able to perform a container escape of a container running as root on a host where Cilium is installed, the attacker can escalate privileges to cluster admin by using Cilium's Kubernetes service account. The problem has been fixed and the patch is avai
ivileges to cluster admin by using Cilium's Kubernetes service account. The problem has been fixed and the patch is available in versions 1.9.16, 1.10.11, and 1.11.5. There are no known workarounds available. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/cilium/cilium/releases/tag/v1.10.11 - https://github.com/cilium/cilium/releases/tag/v1.11.5 - https://github.com/cilium/cilium/releases/tag/v1.9.16 - https://github.com/cilium/cilium/security/advisories/GHSA-fmrf-gvjp-5j5g
CVE ID: CVE-2022-29180 State: PUBLISHED Published: 2022-05-07T03:40:09.000Z Last Updated: 2025-04-23T18:27:10.983Z Severity: MEDIUM (CVSS 5.9 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N) Vendors: charmbracelet Products: charm Problem Types: CWE-918 Description: A vulnerability in which attackers could forge HTTP requests to manipulate the `charm` data directory to access or delete anything on the server. This has been patched and is available in release [v0.12.1](https://github.com/charmbracelet/charm/releases/tag/v0.12.1). We recommend that all users running self-hosted `charm` instances update immediately. This vulnerability was found in-house and we haven't been notified of any potential
charm` instances update immediately. This vulnerability was found in-house and we haven't been notified of any potential exploiters. ### Additional notes * Encrypted user data uploaded to the Charm server is safe as Charm servers cannot decrypt user data. This includes filenames, paths, and all key-value data. * Users running the official Charm [Docker images](https://github.com/charmbracelet/charm/blob/main/docker.md) are at minimal risk because the exploit is limited to the containerized filesystem. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/charmbracelet/charm/security/advisories/GHSA-4wpp-w5r4-7v5v - https://github.com/cha
t: References: - https://github.com/charmbracelet/charm/security/advisories/GHSA-4wpp-w5r4-7v5v - https://github.com/charmbracelet/charm/commit/3c90668f955c7ce5ef721e4fc9faee7053232fd3
CVE ID: CVE-2022-29181 State: PUBLISHED Published: 2022-05-20T00:00:00.000Z Last Updated: 2025-05-27T14:51:01.821Z Severity: HIGH (CVSS 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H) Vendors: sparklemotion Products: nokogiri Problem Types: CWE-241 Description: Nokogiri is an open source XML and HTML library for Ruby. Nokogiri prior to version 1.13.6 does not type-check all inputs into the XML and HTML4 SAX parsers, allowing specially crafted untrusted inputs to cause illegal memory access errors (segfault) or reads from unrelated memory. Version 1.13.6 contains a patch for this issue. As a workaround, ensure the untrusted input is a `String` by calling `#to_s` or equivalent. Additional An
or this issue. As a workaround, ensure the untrusted input is a `String` by calling `#to_s` or equivalent. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-xh29-r2w5-wx8m - https://github.com/sparklemotion/nokogiri/commit/83cc451c3f29df397caa890afc3b714eae6ab8f7 - https://github.com/sparklemotion/nokogiri/commit/db05ba9a1bd4b90aa6c76742cf6102a7c7297267 - https://github.com/sparklemotion/nokogiri/releases/tag/v1.13.6 - https://securitylab.github.com/advisories/GHSL-2022-031_GHSL-2022-032_Nokogiri
CVE ID: CVE-2022-29182 State: PUBLISHED Published: 2022-05-20T19:05:12.000Z Last Updated: 2025-04-23T18:24:22.250Z 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: gocd Products: gocd Problem Types: CWE-79 Description: GoCD is a continuous delivery server. GoCD versions 19.11.0 through 21.4.0 (inclusive) are vulnerable to a Document Object Model (DOM)-based cross-site scripting attack via a pipeline run's Stage Details > Graphs tab. It is possible for a malicious script on a attacker-hosted site to execute script that will run within the user's browser context and GoCD session via abuse of a messaging channel used for communication between with the parent pag
r's browser context and GoCD session via abuse of a messaging channel used for communication between with the parent page and the stage details graph's iframe. This could allow an attacker to steal a GoCD user's session cookies and/or execute malicious code in the user's context. This issue is fixed in GoCD 22.1.0. There are currently no known workarounds. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/gocd/gocd/releases/tag/22.1.0 - https://www.gocd.org/releases/#22-1-0 - https://github.com/gocd/gocd/security/advisories/GHSA-qcg6-4q44-3589 - https://github.com/gocd/gocd/pull/10190/commits/a256d05de1445e6c77843f098581fc6a66fe4477
CVE ID: CVE-2022-29183 State: PUBLISHED Published: 2022-05-20T19:10:11.000Z Last Updated: 2025-04-23T18:24:15.129Z Severity: MEDIUM (CVSS 4.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N) Vendors: gocd Products: gocd Problem Types: CWE-79 Description: GoCD is a continuous delivery server. GoCD versions 20.2.0 until 21.4.0 are vulnerable to reflected cross-site scripting via abuse of the pipeline comparison function's error handling to render arbitrary HTML into the returned page. This could allow an attacker to trick a victim into executing code which would allow the attacker to operate on, or gain control over the same resources as the victim had access to. This issue is fixed in GoCD 21.4.
er to operate on, or gain control over the same resources as the victim had access to. This issue is fixed in GoCD 21.4.0. As a workaround, block access to `/go/compare/.*` prior to GoCD Server via a reverse proxy, web application firewall or equivalent, which would prevent use of the pipeline comparison function. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/gocd/gocd/security/advisories/GHSA-3vvq-q4qv-x2gf - https://github.com/gocd/gocd/pull/9829/commits/bda81084c0401234b168437cf35a63390e3064d1 - https://github.com/gocd/gocd/releases/tag/21.4.0 - https://www.gocd.org/releases/#21-4-0
CVE ID: CVE-2022-29184 State: PUBLISHED Published: 2022-05-20T19:25:14.000Z Last Updated: 2025-04-23T18:24:09.245Z 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: gocd Products: gocd Problem Types: CWE-77, CWE-88 Description: GoCD is a continuous delivery server. In GoCD versions prior to 22.1.0, it is possible for existing authenticated users who have permissions to edit or create pipeline materials or pipeline configuration repositories to get remote code execution capability on the GoCD server via configuring a malicious branch name which abuses Mercurial hooks/aliases to exploit a command injection weakness. An attacker would require access to an account w
abuses Mercurial hooks/aliases to exploit a command injection weakness. An attacker would require access to an account with existing GoCD administration permissions to either create/edit (`hg`-based) configuration repositories; create/edit pipelines and their (`hg`-based) materials; or, where "pipelines-as-code" configuration repositories are used, to commit malicious configuration to such an external repository which will be automatically parsed into a pipeline configuration and (`hg`) material definition by the GoCD server. This issue is fixed in GoCD 22.1.0. As a workaround, users who do not use/rely upon Mercurial materials can uninstall/remove the `hg`/Mercurial binary from the underlyi
und, users who do not use/rely upon Mercurial materials can uninstall/remove the `hg`/Mercurial binary from the underlying GoCD Server operating system or Docker image. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/gocd/gocd/releases/tag/22.1.0 - https://www.gocd.org/releases/#22-1-0 - https://github.com/gocd/gocd/security/advisories/GHSA-vf5r-r7j2-cf2h - https://github.com/gocd/gocd/commit/37d35115db2ada2190173f9413cfe1bc6c295ecb
CVE ID: CVE-2022-29185 State: PUBLISHED Published: 2022-05-20T19:30:12.000Z Last Updated: 2025-04-23T18:24:00.911Z Severity: MEDIUM (CVSS 4.2 CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:N/A:N) Vendors: constantoine Products: totp-rs Problem Types: CWE-208, CWE-203 Description: totp-rs is a Rust library that permits the creation of 2FA authentification tokens per time-based one-time password (TOTP). Prior to version 1.1.0, token comparison was not constant time, and could theorically be used to guess value of an TOTP token, and thus reuse it in the same time window. The attacker would have to know the password beforehand nonetheless. Starting with patched version 1.1.0, the library uses constant-t
would have to know the password beforehand nonetheless. Starting with patched version 1.1.0, the library uses constant-time comparison. There are currently no known workarounds. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/constantoine/totp-rs/security/advisories/GHSA-8vxv-2g8p-2249 - https://github.com/constantoine/totp-rs/issues/13 - https://github.com/constantoine/totp-rs/releases/tag/v1.1.0
CVE ID: CVE-2022-29186 State: PUBLISHED Published: 2022-05-20T20:20:11.000Z Last Updated: 2025-04-23T18:23:50.364Z 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: rundeck Products: rundeck Problem Types: CWE-321 Description: Rundeck is an open source automation service with a web console, command line tools and a WebAPI. Rundeck community and rundeck-enterprise docker images contained a pre-generated SSH keypair. If the id_rsa.pub public key of the keypair was copied to authorized_keys files on remote host, those hosts would allow access to anyone with the exposed private credentials. This misconfiguration only impacts Rundeck Docker instances of PagerDuty
to anyone with the exposed private credentials. This misconfiguration only impacts Rundeck Docker instances of PagerDuty® Process Automation On Prem (formerly Rundeck) version 4.0 and earlier, not Debian, RPM or .WAR. Additionally, the id_rsa.pub file would have to be copied from the Docker image filesystem contents without overwriting it and used to configure SSH access on a host. A patch on Rundeck's `main` branch has removed the pre-generated SSH key pair, but it does not remove exposed keys that have been configured. To patch, users must run a script on hosts in their environment to search for exposed keys and rotate them. Two workarounds are available: Do not use any pre-existing public
nvironment to search for exposed keys and rotate them. Two workarounds are available: Do not use any pre-existing public key file from the rundeck docker images to allow SSH access by adding it to authorized_keys files and, if you have copied the public key file included in the docker image, remove it from any authorized_keys files. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/rundeck/rundeck/security/advisories/GHSA-qxjx-xr2m-hgqx - https://github.com/rundeck/rundeck/commit/16ef7a70b202492f9fbb54d8af4bb8ea0afa10ad
CVE ID: CVE-2022-29187 State: PUBLISHED Published: 2022-07-12T00:00:00 Last Updated: 2024-08-03T06:17:54.233Z Severity: HIGH (CVSS 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) Vendors: git Products: git Problem Types: CWE-282, CWE-427 Description: Git is a distributed revision control system. Git prior to versions 2.37.1, 2.36.2, 2.35.4, 2.34.4, 2.33.4, 2.32.3, 2.31.4, and 2.30.5, is vulnerable to privilege escalation in all platforms. An unsuspecting user could still be affected by the issue reported in CVE-2022-24765, for example when navigating as root into a shared tmp directory that is owned by them, but where an attacker could create a git repository. Versions 2.37.1, 2.36.2, 2.35
tmp directory that is owned by them, but where an attacker could create a git repository. Versions 2.37.1, 2.36.2, 2.35.4, 2.34.4, 2.33.4, 2.32.3, 2.31.4, and 2.30.5 contain a patch for this issue. The simplest way to avoid being affected by the exploit described in the example is to avoid running git as root (or an Administrator in Windows), and if needed to reduce its use to a minimum. While a generic workaround is not possible, a system could be hardened from the exploit described in the example by removing any such repository if it exists already and creating one as root to block any future attacks. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/git/
ot to block any future attacks. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/git/git/security/advisories/GHSA-j342-m5hw-rr3v - https://github.blog/2022-04-12-git-security-vulnerability-announced - https://lore.kernel.org/git/xmqqv8s2fefi.fsf%40gitster.g/T/#u - http://www.openwall.com/lists/oss-security/2022/07/14/1 - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/TRZG5CDUQ27OWTPC5MQOR4UASNXHWEZS/ - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/DDI325LOO2XBDDKLINOAQJEG6MHAURZE/ - https://support.apple.com/kb/HT213496 - http://seclists.org/fulldisclosure/2
message/DDI325LOO2XBDDKLINOAQJEG6MHAURZE/ - https://support.apple.com/kb/HT213496 - http://seclists.org/fulldisclosure/2022/Nov/1 - https://lists.debian.org/debian-lts-announce/2022/12/msg00025.html - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/DIKWISWUDFT2FAITYIA6372BVLH3OOOC/ - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/YROCMBWYFKRSS64PO6FUNM6L7LKBUKVW/ - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HVOLER2PIGMHPQMDGG4RDE2KZB74QLA2/ - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UDZ
GG4RDE2KZB74QLA2/ - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UDZRZAL7QULOB6V7MKT66MOMWJLBJPX4/ - https://security.gentoo.org/glsa/202312-15 - https://security.gentoo.org/glsa/202401-17