ASSERT-KTH/go_vulnerabilities_2019_2024 · Datasets at Hugging Face

id stringlengths 13 16	published stringlengths 19 19	modified timestamp[ns]	details stringlengths 30 3.87k	severity listlengths 1 1 ⌀	repo_url stringlengths 23 68	cwes sequencelengths 0 1	commits sequencelengths 1 4
CVE-2022-38870	2022-10-25T17:15:55	2025-01-14T11:09:12.436222	Free5gc v3.2.1 is vulnerable to Information disclosure.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]	https://github.com/free5gc/free5gc	[]	[ "04340eb8493ba98178ecc725e38ed8677f08d16e" ]
CVE-2022-43677	2022-10-24T14:15:53	2025-01-14T11:13:19.150155	In free5GC 3.2.1, a malformed NGAP message can crash the AMF and NGAP decoders via an index-out-of-range panic in aper.GetBitString.	[ { "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]	https://github.com/free5gc/free5gc	[]	[ "04340eb8493ba98178ecc725e38ed8677f08d16e" ]
CVE-2023-46324	2023-10-23T01:15:07	2025-01-14T12:02:36.373894	pkg/suci/suci.go in free5GC udm before 1.2.0, when Go before 1.19 is used, allows an Invalid Curve Attack because it may compute a shared secret via an uncompressed public key that has not been validated. An attacker can send arbitrary SUCIs to the UDM, which tries to decrypt them via both its private key and the attacker's public key.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]	https://github.com/free5gc/udm	[]	[ "dd730c193e4f2fefc6d4f9620f2a2452c89f93fd" ]
CVE-2022-36078	2022-09-02T13:15:08	2025-01-14T11:03:57.904685	Binary provides encoding/decoding in Borsh and other formats. The vulnerability is a memory allocation vulnerability that can be exploited to allocate slices in memory with (arbitrary) excessive size value, which can either exhaust available memory or crash the whole program. When using `github.com/gagliardetto/binary` to parse unchecked (or wrong type of) data from untrusted sources of input (e.g. the blockchain) into slices, it's possible to allocate memory with excessive size. When `dec.Decode(&val)` method is used to parse data into a structure that is or contains slices of values, the length of the slice was previously read directly from the data itself without any checks on the size of it, and then a slice was allocated. This could lead to an overflow and an allocation of memory with excessive size value. Users should upgrade to `v0.7.1` or higher. A workaround is not to rely on the `dec.Decode(&val)` function to parse the data, but to use a custom `UnmarshalWithDecoder()` method that reads and checks the length of any slice.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]	https://github.com/gagliardetto/binary	[]	[ "2b2638040b6d1921df7e9247b441a630ba80d517" ]
CVE-2023-44392	2023-10-09T20:15:10	2025-01-15T04:59:09.456035	Garden provides automation for Kubernetes development and testing. Prior tov ersions 0.13.17 and 0.12.65, Garden has a dependency on the cryo library, which is vulnerable to code injection due to an insecure implementation of deserialization. Garden stores serialized objects using cryo in the Kubernetes `ConfigMap` resources prefixed with `test-result` and `run-result` to cache Garden test and run results. These `ConfigMaps` are stored either in the `garden-system` namespace or the configured user namespace. When a user invokes the command `garden test` or `garden run` objects stored in the `ConfigMap` are retrieved and deserialized. This can be used by an attacker with access to the Kubernetes cluster to store malicious objects in the `ConfigMap`, which can trigger a remote code execution on the users machine when cryo deserializes the object. In order to exploit this vulnerability, an attacker must have access to the Kubernetes cluster used to deploy garden remote environments. Further, a user must actively invoke either a `garden test` or `garden run` which has previously cached results. The issue has been patched in Garden versions `0.13.17` (Bonsai) and `0.12.65` (Acorn). Only Garden versions prior to these are vulnerable. No known workarounds are available.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/garden-io/garden	[]	[ "af5fea7e2fe52d33cefd77a4130706b3f7f16fe8" ]
CVE-2022-24829	2022-04-11T20:15:20	2025-01-15T02:18:12.455858	Garden is an automation platform for Kubernetes development and testing. In versions prior to 0.12.39 multiple endpoints did not require authentication. In some operating modes this allows for an attacker to gain access to the application erroneously. The configuration is leaked through the /api endpoint on the local server that is responsible for serving the Garden dashboard. At the moment, this server is accessible to 0.0.0.0 which makes it accessible to anyone on the same network (or anyone on the internet if they are on a public, static IP). This may lead to the ability to compromise credentials, secrets or environment variables. Users are advised to upgrade to version 0.12.39 as soon as possible. Users unable to upgrade should use a firewall blocking access to port 9777 from all untrusted network machines.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/garden-io/garden	[]	[ "af5fea7e2fe52d33cefd77a4130706b3f7f16fe8" ]
CVE-2017-11671	2017-07-26T21:29:00	2025-01-14T07:20:52.551768	Under certain circumstances, the ix86_expand_builtin function in i386.c in GNU Compiler Collection (GCC) version 4.6, 4.7, 4.8, 4.9, 5 before 5.5, and 6 before 6.4 will generate instruction sequences that clobber the status flag of the RDRAND and RDSEED intrinsics before it can be read, potentially causing failures of these instructions to go unreported. This could potentially lead to less randomness in random number generation.	[ { "score": "CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "type": "CVSS_V3" } ]	https://github.com/gcc-mirror/gcc	[]	[ "4cf01c09fe137b7a70b9879ca396823615962eb3" ]
CVE-2023-37786	2023-07-13T17:15:09	2025-01-14T11:50:06.576066	Multiple cross-site scripting (XSS) vulnerabilities in Geeklog v2.2.2 allow attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Mail Settings[backend], Mail Settings[host], Mail Settings[port] and Mail Settings[auth] parameters of the /admin/configuration.php.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]	https://github.com/geeklog-core/geeklog	[]	[ "ef48c658c253a8d0ed28209ba8d5471489dcb472" ]
CVE-2023-37787	2023-07-13T17:15:09	2025-01-14T11:50:06.639398	Multiple cross-site scripting (XSS) vulnerabilities in Geeklog v2.2.2 allow attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Rule and Route parameters of /admin/router.php.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]	https://github.com/geeklog-core/geeklog	[]	[ "ef48c658c253a8d0ed28209ba8d5471489dcb472" ]
CVE-2023-46058	2023-10-24T00:15:08	2025-01-14T12:02:48.012313	Cross Site Scripting (XSS) vulnerability in Geeklog-Core geeklog v.2.2.2 allows a remote attacker to execute arbitrary code via a crafted payload to the grp_desc parameter of the admin/group.php component.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]	https://github.com/geeklog-core/geeklog	[]	[ "ef48c658c253a8d0ed28209ba8d5471489dcb472" ]
CVE-2023-46059	2023-10-24T00:15:08	2025-01-14T12:02:47.599381	Cross Site Scripting (XSS) vulnerability in Geeklog-Core geeklog v.2.2.2 allows a remote attacker to execute arbitrary code via a crafted payload to the Service, and website URL to Ping parameters of the admin/trackback.php component.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]	https://github.com/geeklog-core/geeklog	[]	[ "ef48c658c253a8d0ed28209ba8d5471489dcb472" ]
CVE-2021-38197	2021-08-08T16:15:07	2025-01-14T09:29:13.838335	unarr.go in go-unarr (aka Go bindings for unarr) 0.1.1 allows Directory Traversal via ../ in a pathname within a TAR archive.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/gen2brain/go-unarr	[]	[ "a9c9a14faa9e11d8ca8ba5b98d0d4f82215ce17c" ]
CVE-2023-28424	2023-03-20T13:15:11	2025-01-14T11:37:08.234912	Soko if the code that powers packages.gentoo.org. Prior to version 1.0.2, the two package search handlers, `Search` and `SearchFeed`, implemented in `pkg/app/handler/packages/search.go`, are affected by a SQL injection via the `q` parameter. As a result, unauthenticated attackers can execute arbitrary SQL queries on `https://packages.gentoo.org/`. It was also demonstrated that primitive was enough to gain code execution in the context of the PostgreSQL container. The issue was addressed in commit `4fa6e4b619c0362728955b6ec56eab0e0cbf1e23y` of version 1.0.2 using prepared statements to interpolate user-controlled data in SQL queries.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/gentoo/soko	[]	[ "0e8a1a49290b7b08f31c603d3895f60bb38d5bb7" ]
CVE-2023-26033	2023-02-25T00:15:11	2025-01-14T11:35:10.778979	Gentoo soko is the code that powers packages.gentoo.org. Versions prior to 1.0.1 are vulnerable to SQL Injection, leading to a Denial of Service. If the user selects (in user preferences) the "Recently Visited Packages" view for the index page, the value of the `search_history` cookie is used as a base64 encoded comma separated list of atoms. These are string loaded directly into the SQL query with `atom = '%s'` format string. As a result, any user can modify the browser's cookie value and inject most SQL queries. A proof of concept malformed cookie was generated that wiped the database or changed it's content. On the database, only public data is stored, so there is no confidentiality issues to site users. If it is known that the database was modified, a full restoration of data is possible by performing a full database wipe and performing full update of all components. This issue is patched with commit id 5ae9ca83b73. Version 1.0.1 contains the patch. If users are unable to upgrade immediately, the following workarounds may be applied: (1.) Use a proxy to always drop the `search_history` cookie until upgraded. The impact on user experience is low. (2.) Sanitize to the value of `search_history` cookie after base64 decoding it.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/gentoo/soko	[]	[ "0e8a1a49290b7b08f31c603d3895f60bb38d5bb7" ]
CVE-2020-26772	2021-09-08T21:15:09	2025-01-14T08:41:45.609331	Command Injection in PPGo_Jobs v2.8.0 allows remote attackers to execute arbitrary code via the 'AjaxRun()' function.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/george518/ppgo_job	[]	[ "d1aef8d5e1c7fec896c604d45f8c37565b68aa0d" ]
CVE-2023-32691	2023-05-30T04:15:09	2025-02-19T03:33:24.966650	gost (GO Simple Tunnel) is a simple tunnel written in golang. Sensitive secrets such as passwords, token and API keys should be compared only using a constant-time comparison function. Untrusted input, sourced from a HTTP header, is compared directly with a secret. Since this comparison is not secure, an attacker can mount a side-channel timing attack to guess the password. As a workaround, this can be easily fixed using a constant time comparing function such as `crypto/subtle`'s `ConstantTimeCompare`.	[ { "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]	https://github.com/ginuerzh/gost	[]	[ "729d0e70005607dc7c69fc1de62fd8fe21f85355" ]
CVE-2022-41953	2023-01-17T22:15:10	2025-02-19T03:32:09.079842	Git GUI is a convenient graphical tool that comes with Git for Windows. Its target audience is users who are uncomfortable with using Git on the command-line. Git GUI has a function to clone repositories. Immediately after the local clone is available, Git GUI will automatically post-process it, among other things running a spell checker called `aspell.exe` if it was found. Git GUI is implemented as a Tcl/Tk script. Due to the unfortunate design of Tcl on Windows, the search path when looking for an executable _always includes the current directory_. Therefore, malicious repositories can ship with an `aspell.exe` in their top-level directory which is executed by Git GUI without giving the user a chance to inspect it first, i.e. running untrusted code. This issue has been addressed in version 2.39.1. Users are advised to upgrade. Users unable to upgrade should avoid using Git GUI for cloning. If that is not a viable option, at least avoid cloning from untrusted sources.	[ { "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/git-for-windows/git	[]	[ "34d5217584ee4722d0c0b07ed6c8f1f01ad157c3" ]
CVE-2023-29011	2023-04-25T21:15:10	2025-02-19T03:34:57.132947	Git for Windows, the Windows port of Git, ships with an executable called `connect.exe`, which implements a SOCKS5 proxy that can be used to connect e.g. to SSH servers via proxies when certain ports are blocked for outgoing connections. The location of `connect.exe`'s config file is hard-coded as `/etc/connectrc` which will typically be interpreted as `C:\etc\connectrc`. Since `C:\etc` can be created by any authenticated user, this makes `connect.exe` susceptible to malicious files being placed there by other users on the same multi-user machine. The problem has been patched in Git for Windows v2.40.1. As a workaround, create the folder `etc` on all drives where Git commands are run, and remove read/write access from those folders. Alternatively, watch out for malicious `<drive>:\etc\connectrc` files on multi-user machines.	[ { "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/git-for-windows/git	[]	[ "34d5217584ee4722d0c0b07ed6c8f1f01ad157c3" ]
CVE-2023-29012	2023-04-25T21:15:10	2025-02-19T03:34:53.636718	Git for Windows is the Windows port of Git. Prior to version 2.40.1, any user of Git CMD who starts the command in an untrusted directory is impacted by an Uncontrolles Search Path Element vulnerability. Maliciously-placed `doskey.exe` would be executed silently upon running Git CMD. The problem has been patched in Git for Windows v2.40.1. As a workaround, avoid using Git CMD or, if using Git CMD, avoid starting it in an untrusted directory.	[ { "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/git-for-windows/git	[]	[ "34d5217584ee4722d0c0b07ed6c8f1f01ad157c3" ]
CVE-2023-22743	2023-02-14T21:15:12	2025-02-19T03:32:16.302893	Git for Windows is the Windows port of the revision control system Git. Prior to Git for Windows version 2.39.2, by carefully crafting DLL and putting into a subdirectory of a specific name living next to the Git for Windows installer, Windows can be tricked into side-loading said DLL. This potentially allows users with local write access to place malicious payloads in a location where automated upgrades might run the Git for Windows installer with elevation. Version 2.39.2 contains a patch for this issue. Some workarounds are available. Never leave untrusted files in the Downloads folder or its sub-folders before executing the Git for Windows installer, or move the installer into a different directory before executing it.	[ { "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/git-for-windows/git	[]	[ "34d5217584ee4722d0c0b07ed6c8f1f01ad157c3" ]
CVE-2023-23618	2023-02-14T21:15:13	2025-01-15T04:44:16.870186	Git for Windows is the Windows port of the revision control system Git. Prior to Git for Windows version 2.39.2, when `gitk` is run on Windows, it potentially runs executables from the current directory inadvertently, which can be exploited with some social engineering to trick users into running untrusted code. A patch is available in version 2.39.2. As a workaround, avoid using `gitk` (or Git GUI's "Visualize History" functionality) in clones of untrusted repositories.	[ { "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/git-for-windows/git	[]	[ "34d5217584ee4722d0c0b07ed6c8f1f01ad157c3" ]
CVE-2022-24767	2022-04-12T18:15:09	2025-02-19T03:28:39.686857	GitHub: Git for Windows' uninstaller vulnerable to DLL hijacking when run under the SYSTEM user account.	[ { "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/git-for-windows/git	[]	[ "34d5217584ee4722d0c0b07ed6c8f1f01ad157c3" ]
CVE-2022-31012	2022-07-12T21:15:09	2025-02-19T03:28:14.067124	Git for Windows is a fork of Git that contains Windows-specific patches. This vulnerability in versions prior to 2.37.1 lets Git for Windows' installer execute a binary into `C:\mingw64\bin\git.exe` by mistake. This only happens upon a fresh install, not when upgrading Git for Windows. A patch is included in version 2.37.1. Two workarounds are available. Create the `C:\mingw64` folder and remove read/write access from this folder, or disallow arbitrary authenticated users to create folders in `C:\`.	[ { "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/git-for-windows/git	[]	[ "34d5217584ee4722d0c0b07ed6c8f1f01ad157c3" ]
CVE-2016-9274	2016-11-11T17:59:00	2025-02-19T02:18:24.635802	Untrusted search path vulnerability in Git 1.x for Windows allows local users to gain privileges via a Trojan horse git.exe file in the current working directory. NOTE: 2.x is unaffected.	[ { "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/git-for-windows/git	[]	[ "34d5217584ee4722d0c0b07ed6c8f1f01ad157c3" ]
CVE-2021-32638	2021-05-25T17:15:08	2025-01-15T01:55:09.659316	Github's CodeQL action is provided to run CodeQL-based code scanning on non-GitHub CI/CD systems and requires a GitHub access token to connect to a GitHub repository. The runner and its documentation previously suggested passing the GitHub token as a command-line parameter to the process instead of reading it from a file, standard input, or an environment variable. This approach made the token visible to other processes on the same machine, for example in the output of the `ps` command. If the CI system publicly exposes the output of `ps`, for example by logging the output, then the GitHub access token can be exposed beyond the scope intended. Users of the CodeQL runner on 3rd-party systems, who are passing a GitHub token via the `--github-auth` flag, are affected. This applies to both GitHub.com and GitHub Enterprise users. Users of the CodeQL Action on GitHub Actions are not affected. The `--github-auth` flag is now considered insecure and deprecated. The undocumented `--external-repository-token` flag has been removed. To securely provide a GitHub access token to the CodeQL runner, users should do one of the following instead: Use the `--github-auth-stdin` flag and pass the token on the command line via standard input OR set the `GITHUB_TOKEN` environment variable to contain the token, then call the command without passing in the token. The old flag remains present for backwards compatibility with existing workflows. If the user tries to specify an access token using the `--github-auth` flag, there is a deprecation warning printed to the terminal that directs the user to one of the above options. All CodeQL runner releases codeql-bundle-20210304 onwards contain the patches. We recommend updating to a recent version of the CodeQL runner, storing a token in your CI system's secret storage mechanism, and passing the token to the CodeQL runner using `--github-auth-stdin` or the `GITHUB_TOKEN` environment variable. If still using the old flag, ensure that process output, such as from `ps`, is not persisted in CI logs.	[ { "score": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]	https://github.com/github/codeql-action	[]	[ "0dc37c7260df8e43e9d5a7d4455662fda84240b3" ]
CVE-2025-24362	2025-01-24T18:15:32	2025-01-25T01:57:57.337756	In some circumstances, debug artifacts uploaded by the CodeQL Action after a failed code scanning workflow run may contain the environment variables from the workflow run, including any secrets that were exposed as environment variables to the workflow. Users with read access to the repository would be able to access this artifact, containing any secrets from the environment. This vulnerability is patched in CodeQL Action version 3.28.3 or later, or CodeQL CLI version 2.20.3 or later. For some affected workflow runs, the exposed environment variables in the debug artifacts included a valid `GITHUB_TOKEN` for the workflow run, which has access to the repository in which the workflow ran, and all the permissions specified in the workflow or job. The `GITHUB_TOKEN` is valid until the job completes or 24 hours has elapsed, whichever comes first. Environment variables are exposed only from workflow runs that satisfy all of the following conditions: - Code scanning workflow configured to scan the Java/Kotlin languages. - Running in a repository containing Kotlin source code. - Running with debug artifacts enabled. - Using CodeQL Action versions <= 3.28.2, and CodeQL CLI versions >= 2.9.2 (May 2022) and <= 2.20.2. - The workflow run fails before the CodeQL database is finalized within the `github/codeql-action/analyze` step. - Running in any GitHub environment: GitHub.com, GitHub Enterprise Cloud, and GitHub Enterprise Server. Note: artifacts are only accessible to users within the same GitHub environment with access to the scanned repo. The `GITHUB_TOKEN` exposed in this way would only have been valid for workflow runs that satisfy all of the following conditions, in addition to the conditions above: - Using CodeQL Action versions >= 3.26.11 (October 2024) and <= 3.28.2, or >= 2.26.11 and < 3. - Running in GitHub.com or GitHub Enterprise Cloud only (not valid on GitHub Enterprise Server). In rare cases during advanced setup, logging of environment variables may also occur during database creation of Java, Swift, and C/C++. Please read the corresponding CodeQL CLI advisory GHSA-gqh3-9prg-j95m for more details. In CodeQL CLI versions >= 2.9.2 and <= 2.20.2, the CodeQL Kotlin extractor logs all environment variables by default into an intermediate file during the process of creating a CodeQL database for Kotlin code. This is a part of the CodeQL CLI and is invoked by the CodeQL Action for analyzing Kotlin repositories. On Actions, the environment variables logged include GITHUB_TOKEN, which grants permissions to the repository being scanned. The intermediate file containing environment variables is deleted when finalizing the database, so it is not included in a successfully created database. It is, however, included in the debug artifact that is uploaded on a failed analysis run if the CodeQL Action was invoked in debug mode. Therefore, under these specific circumstances (incomplete database creation using the CodeQL Action in debug mode) an attacker with access to the debug artifact would gain unauthorized access to repository secrets from the environment, including both the `GITHUB_TOKEN` and any user-configured secrets made available via environment variables. The impact of the `GITHUB_TOKEN` leaked in this environment is limited: - For workflows on GitHub.com and GitHub Enterprise Cloud using CodeQL Action versions >= 3.26.11 and <= 3.28.2, or >= 2.26.11 and < 3, which in turn use the `actions/artifacts v4` library, the debug artifact is uploaded before the workflow job completes. During this time the `GITHUB_TOKEN` is still valid, providing an opportunity for attackers to gain access to the repository. - For all other workflows, the debug artifact is uploaded after the workflow job completes, at which point the leaked `GITHUB_TOKEN` has been revoked and cannot be used to access the repository.	null	https://github.com/github/codeql-action	[]	[ "0dc37c7260df8e43e9d5a7d4455662fda84240b3" ]
CVE-2022-2251	2023-01-17T21:15:12	2025-01-14T10:46:01.712029	Improper sanitization of branch names in GitLab Runner affecting all versions prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2 allows a user who creates a branch with a specially crafted name and gets another user to trigger a pipeline to execute commands in the runner as that other user.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/gitlabhq/gitlab-runner	[]	[ "7178588dc1e747941d1c5b9da759c0c00b6aaa96" ]
CVE-2020-13295	2020-08-10T14:15:13	2025-01-14T08:17:32.671855	For GitLab Runner before 13.0.12, 13.1.6, 13.2.3, by replacing dockerd with a malicious server, the Shared Runner is susceptible to SSRF.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/gitlabhq/gitlab-runner	[]	[ "a998cacdcee3e1b21cbb23526f5e7da54e53e047" ]
CVE-2024-21583	2024-07-19T05:15:10	2025-01-15T05:06:39.853501	Versions of the package github.com/gitpod-io/gitpod/components/server/go/pkg/lib before main-gha.27122; versions of the package github.com/gitpod-io/gitpod/components/ws-proxy/pkg/proxy before main-gha.27122; versions of the package github.com/gitpod-io/gitpod/install/installer/pkg/components/auth before main-gha.27122; versions of the package github.com/gitpod-io/gitpod/install/installer/pkg/components/public-api-server before main-gha.27122; versions of the package github.com/gitpod-io/gitpod/install/installer/pkg/components/server before main-gha.27122; versions of the package @gitpod/gitpod-protocol before 0.1.5-main-gha.27122 are vulnerable to Cookie Tossing due to a missing __Host- prefix on the _gitpod_io_jwt2_ session cookie. This allows an adversary who controls a subdomain to set the value of the cookie on the Gitpod control plane, which can be assigned to an attacker’s own JWT so that specific actions taken by the victim (such as connecting a new Github organization) are actioned by the attackers session.	null	https://github.com/gitpod-io/gitpod	[]	[ "3c0afbafa50dd1e66f385e091fa49c873405faa8" ]
CVE-2023-0957	2023-03-03T08:15:08	2025-01-15T04:38:47.903024	An issue was discovered in Gitpod versions prior to release-2022.11.2.16. There is a Cross-Site WebSocket Hijacking (CSWSH) vulnerability that allows attackers to make WebSocket connections to the Gitpod JSONRPC server using a victim’s credentials, because the Origin header is not restricted. This can lead to the extraction of data from workspaces, to a full takeover of the workspace.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/gitpod-io/gitpod	[]	[ "3c0afbafa50dd1e66f385e091fa49c873405faa8" ]
CVE-2023-32766	2023-06-05T15:15:09	2025-01-31T20:00:51.301146	Gitpod before 2022.11.3 allows XSS because redirection can occur for some protocols outside of the trusted set of three (vscode: vscode-insiders: jetbrains-gateway:).	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]	https://github.com/gitpod-io/gitpod	[]	[ "3c0afbafa50dd1e66f385e091fa49c873405faa8" ]
CVE-2021-35206	2021-06-22T14:15:09	2025-01-15T02:00:03.884948	Gitpod before 0.6.0 allows unvalidated redirects.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]	https://github.com/gitpod-io/gitpod	[]	[ "3c0afbafa50dd1e66f385e091fa49c873405faa8" ]
CVE-2020-36559	2022-12-27T22:15:11	2025-01-15T01:45:28.647399	Due to improper sanitization of user input, HTTPEngine.Handle allows for directory traversal, allowing an attacker to read files outside of the target directory that the server has permission to read.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]	https://github.com/go-aah/aah	[]	[ "def102ffcb9e1d3b029a2c3d884ed6407d9a1389" ]
CVE-2022-42980	2022-10-17T07:15:08	2025-02-19T03:28:19.149066	go-admin (aka GO Admin) 2.0.12 uses the string go-admin as a production JWT key.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/go-admin-team/go-admin	[]	[ "012202478905438be61b0ae3958d4f31df4d340c" ]
CVE-2020-12666	2020-05-05T22:15:13	2025-01-14T08:16:17.156212	macaron before 1.3.7 has an open redirect in the static handler, as demonstrated by the http://127.0.0.1:4000//example.com/ URL.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]	https://github.com/go-macaron/macaron	[]	[ "bbb5ca29768e04c2d5f344c235909f44c8dd0fdd" ]
CVE-2022-46959	2023-01-23T05:15:18	2025-01-14T11:16:29.309697	An issue in the component /admin/backups/work-dir of Sonic v1.0.4 allows attackers to execute a directory traversal.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N", "type": "CVSS_V3" } ]	https://github.com/go-sonic/sonic	[]	[ "ec9c203b2721db0589fb8daa2e1f9bba0d4e82ee" ]
CVE-2020-26294	2021-01-04T19:15:15	2025-01-15T01:44:52.494575	Vela is a Pipeline Automation (CI/CD) framework built on Linux container technology written in Golang. In Vela compiler before version 0.6.1 there is a vulnerability which allows exposure of server configuration. It impacts all users of Vela. An attacker can use Sprig's `env` function to retrieve configuration information, see referenced GHSA for an example. This has been fixed in version 0.6.1. In addition to upgrading, it is recommended to rotate all secrets.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "type": "CVSS_V3" } ]	https://github.com/go-vela/compiler	[]	[ "f7912c5019d2994e619f2a77d949d0996617c44a" ]
CVE-2024-28236	2024-03-12T21:15:59	2025-02-19T03:37:15.888400	Vela is a Pipeline Automation (CI/CD) framework built on Linux container technology written in Golang. Vela pipelines can use variable substitution combined with insensitive fields like `parameters`, `image` and `entrypoint` to inject secrets into a plugin/image and — by using common substitution string manipulation — can bypass log masking and expose secrets without the use of the commands block. This unexpected behavior primarily impacts secrets restricted by the "no commands" option. This can lead to unintended use of the secret value, and increased risk of exposing the secret during image execution bypassing log masking. To exploit this the pipeline author must be supplying the secrets to a plugin that is designed in such a way that will print those parameters in logs. Plugin parameters are not designed for sensitive values and are often intentionally printed throughout execution for informational/debugging purposes. Parameters should therefore be treated as insensitive. While Vela provides secrets masking, secrets exposure is not entirely solved by the masking process. A docker image (plugin) can easily expose secrets if they are not handled properly, or altered in some way. There is a responsibility on the end-user to understand how values injected into a plugin are used. This is a risk that exists for many CICD systems (like GitHub Actions) that handle sensitive runtime variables. Rather, the greater risk is that users who restrict a secret to the "no commands" option and use image restriction can still have their secret value exposed via substitution tinkering, which turns the image and command restrictions into a false sense of security. This issue has been addressed in version 0.23.2. Users are advised to upgrade. Users unable to upgrade should not provide sensitive values to plugins that can potentially expose them, especially in `parameters` that are not intended to be used for sensitive values, ensure plugins (especially those that utilize shared secrets) follow best practices to avoid logging parameters that are expected to be sensitive, minimize secrets with `pull_request` events enabled, as this allows users to change pipeline configurations and pull in secrets to steps not typically part of the CI process, make use of the build approval setting, restricting builds from untrusted users, and limit use of shared secrets, as they are less restrictive to access by nature.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]	https://github.com/go-vela/server	[]	[ "5a3ffe34701a1451192376bb87e8a03ad361a5ed" ]
CVE-2021-21432	2021-04-09T18:15:13	2025-01-15T01:47:36.105601	Vela is a Pipeline Automation (CI/CD) framework built on Linux container technology written in Golang. An authentication mechanism added in version 0.7.0 enables some malicious user to obtain secrets utilizing the injected credentials within the `~/.netrc` file. Refer to the referenced GitHub Security Advisory for complete details. This is fixed in version 0.7.5.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]	https://github.com/go-vela/server	[]	[ "5a3ffe34701a1451192376bb87e8a03ad361a5ed" ]
CVE-2022-39395	2022-11-10T18:15:10	2025-02-19T03:29:46.997185	Vela is a Pipeline Automation (CI/CD) framework built on Linux container technology written in Golang. In Vela Server and Vela Worker prior to version 0.16.0 and Vela UI prior to version 0.17.0, some default configurations for Vela allow exploitation and container breakouts. Users should upgrade to Server 0.16.0, Worker 0.16.0, and UI 0.17.0 to fix the issue. After upgrading, Vela administrators will need to explicitly change the default settings to configure Vela as desired. Some of the fixes will interrupt existing workflows and will require Vela administrators to modify default settings. However, not applying the patch (or workarounds) will continue existing risk exposure. Some workarounds are available. Vela administrators can adjust the worker's `VELA_RUNTIME_PRIVILEGED_IMAGES` setting to be explicitly empty, leverage the `VELA_REPO_ALLOWLIST` setting on the server component to restrict access to a list of repositories that are allowed to be enabled, and/or audit enabled repositories and disable pull_requests if they are not needed.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/go-vela/server	[]	[ "5a3ffe34701a1451192376bb87e8a03ad361a5ed" ]
CVE-2019-25073	2022-12-27T22:15:11	2025-01-15T01:40:47.689671	Improper path sanitization in github.com/goadesign/goa before v3.0.9, v2.0.10, or v1.4.3 allow remote attackers to read files outside of the intended directory.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]	https://github.com/goadesign/goa	[]	[ "c562182dfa2a4ee68d7e08f8bc882606bebef5a1" ]
CVE-2024-38513	2024-07-01T19:15:05	2025-01-15T05:16:27.672456	Fiber is an Express-inspired web framework written in Go A vulnerability present in versions prior to 2.52.5 is a session middleware issue in GoFiber versions 2 and above. This vulnerability allows users to supply their own session_id value, resulting in the creation of a session with that key. If a website relies on the mere presence of a session for security purposes, this can lead to significant security risks, including unauthorized access and session fixation attacks. All users utilizing GoFiber's session middleware in the affected versions are impacted. The issue has been addressed in version 2.52.5. Users are strongly encouraged to upgrade to version 2.52.5 or higher to mitigate this vulnerability. Users who are unable to upgrade immediately can apply the following workarounds to reduce the risk: Either implement additional validation to ensure session IDs are not supplied by the user and are securely generated by the server, or regularly rotate session IDs and enforce strict session expiration policies.	null	https://github.com/gofiber/fiber	[]	[ "0e9593886c2cb51dd78d1946eac620c8c83bf90a" ]
CVE-2024-25124	2024-02-21T21:15:09	2025-02-06T00:59:10.754724	Fiber is a web framework written in go. Prior to version 2.52.1, the CORS middleware allows for insecure configurations that could potentially expose the application to multiple CORS-related vulnerabilities. Specifically, it allows setting the Access-Control-Allow-Origin header to a wildcard (`*`) while also having the Access-Control-Allow-Credentials set to true, which goes against recommended security best practices. The impact of this misconfiguration is high as it can lead to unauthorized access to sensitive user data and expose the system to various types of attacks listed in the PortSwigger article linked in the references. Version 2.52.1 contains a patch for this issue. As a workaround, users may manually validate the CORS configurations in their implementation to ensure that they do not allow a wildcard origin when credentials are enabled. The browser fetch api, as well as browsers and utilities that enforce CORS policies, are not affected by this.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/gofiber/fiber	[]	[ "0e9593886c2cb51dd78d1946eac620c8c83bf90a" ]
CVE-2023-41338	2023-09-08T19:15:43	2025-01-15T04:59:19.885090	Fiber is an Express inspired web framework built in the go language. Versions of gofiber prior to 2.49.2 did not properly restrict access to localhost. This issue impacts users of our project who rely on the `ctx.IsFromLocal` method to restrict access to localhost requests. If exploited, it could allow unauthorized access to resources intended only for localhost. Setting `X-Forwarded-For: 127.0.0.1` in a request from a foreign host, will result in true for `ctx.IsFromLocal`. Access is limited to the scope of the affected process. This issue has been patched in version `2.49.2` with commit `b8c9ede6`. Users are advised to upgrade. There are no known workarounds to remediate this vulnerability without upgrading to the patched version.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "type": "CVSS_V3" } ]	https://github.com/gofiber/fiber	[]	[ "0e9593886c2cb51dd78d1946eac620c8c83bf90a" ]
CVE-2023-45128	2023-10-16T21:15:11	2025-01-15T05:00:44.174477	Fiber is an express inspired web framework written in Go. A Cross-Site Request Forgery (CSRF) vulnerability has been identified in the application, which allows an attacker to inject arbitrary values and forge malicious requests on behalf of a user. This vulnerability can allow an attacker to inject arbitrary values without any authentication, or perform various malicious actions on behalf of an authenticated user, potentially compromising the security and integrity of the application. The vulnerability is caused by improper validation and enforcement of CSRF tokens within the application. This issue has been addressed in version 2.50.0 and users are advised to upgrade. Users should take additional security measures like captchas or Two-Factor Authentication (2FA) and set Session cookies with SameSite=Lax or SameSite=Secure, and the Secure and HttpOnly attributes as defense in depth measures. There are no known workarounds for this vulnerability.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/gofiber/fiber	[]	[ "0e9593886c2cb51dd78d1946eac620c8c83bf90a" ]
CVE-2023-45141	2023-10-16T21:15:11	2025-02-19T03:35:55.069799	Fiber is an express inspired web framework written in Go. A Cross-Site Request Forgery (CSRF) vulnerability has been identified in the application, which allows an attacker to obtain tokens and forge malicious requests on behalf of a user. This can lead to unauthorized actions being taken on the user's behalf, potentially compromising the security and integrity of the application. The vulnerability is caused by improper validation and enforcement of CSRF tokens within the application. This vulnerability has been addressed in version 2.50.0 and users are advised to upgrade. Users should take additional security measures like captchas or Two-Factor Authentication (2FA) and set Session cookies with SameSite=Lax or SameSite=Secure, and the Secure and HttpOnly attributes.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/gofiber/fiber	[]	[ "0e9593886c2cb51dd78d1946eac620c8c83bf90a" ]
CVE-2020-15111	2020-07-20T18:15:12	2025-02-19T03:09:33.426508	In Fiber before version 1.12.6, the filename that is given in c.Attachment() (https://docs.gofiber.io/ctx#attachment) is not escaped, and therefore vulnerable for a CRLF injection attack. I.e. an attacker could upload a custom filename and then give the link to the victim. With this filename, the attacker can change the name of the downloaded file, redirect to another site, change the authorization header, etc. A possible workaround is to serialize the input before passing it to ctx.Attachment().	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N", "type": "CVSS_V3" } ]	https://github.com/gofiber/fiber	[]	[ "0e9593886c2cb51dd78d1946eac620c8c83bf90a" ]
CVE-2024-22199	2024-01-11T18:15:45	2025-01-15T05:06:49.773657	This package provides universal methods to use multiple template engines with the Fiber web framework using the Views interface. This vulnerability specifically impacts web applications that render user-supplied data through this template engine, potentially leading to the execution of malicious scripts in users' browsers when visiting affected web pages. The vulnerability has been addressed, the template engine now defaults to having autoescape set to `true`, effectively mitigating the risk of XSS attacks.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]	https://github.com/gofiber/template	[]	[ "fd5a1ab847ebbf537447561827f310ba70fd0998" ]
CVE-2024-44625	2024-11-15T17:15:20	2025-02-19T03:38:16.534051	Gogs <=0.13.0 is vulnerable to Directory Traversal via the editFilePost function of internal/route/repo/editor.go.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2022-1884	2024-11-15T11:15:07	2025-02-19T03:25:59.708390	A remote command execution vulnerability exists in gogs/gogs versions <=0.12.7 when deployed on a Windows server. The vulnerability arises due to improper validation of the `tree_path` parameter during file uploads. An attacker can set `tree_path=.git.` to upload a file into the .git directory, allowing them to write or rewrite the `.git/config` file. If the `core.sshCommand` is set, this can lead to remote command execution.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2024-39931	2024-07-04T16:15:02	2025-02-19T03:38:29.681021	Gogs through 0.13.0 allows deletion of internal files.	null	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2024-39933	2024-07-04T16:15:02	2025-02-19T03:38:27.787272	Gogs through 0.13.0 allows argument injection during the tagging of a new release.	null	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2024-39930	2024-07-04T16:15:02	2025-02-19T03:38:29.577175	The built-in SSH server of Gogs through 0.13.0 allows argument injection in internal/ssh/ssh.go, leading to remote code execution. Authenticated attackers can exploit this by opening an SSH connection and sending a malicious --split-string env request if the built-in SSH server is activated. Windows installations are unaffected.	null	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2024-39932	2024-07-04T16:15:02	2025-02-19T03:38:28.446130	Gogs through 0.13.0 allows argument injection during the previewing of changes.	null	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2024-54148	2024-12-23T16:15:07	2025-01-15T05:16:46.592921	Gogs is an open source self-hosted Git service. A malicious user is able to commit and edit a crafted symlink file to a repository to gain SSH access to the server. The vulnerability is fixed in 0.13.1.	null	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2024-55947	2024-12-23T16:15:07	2025-01-15T05:17:07.214438	Gogs is an open source self-hosted Git service. A malicious user is able to write a file to an arbitrary path on the server to gain SSH access to the server. The vulnerability is fixed in 0.13.1.	null	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2022-2024	2023-02-25T08:15:09	2025-01-15T02:13:41.071350	OS Command Injection in GitHub repository gogs/gogs prior to 0.12.11.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2022-0870	2022-03-11T11:15:07	2025-01-15T02:11:48.021536	Server-Side Request Forgery (SSRF) in GitHub repository gogs/gogs prior to 0.12.5.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2022-0415	2022-03-21T11:15:10	2025-01-15T02:10:17.955039	Remote Command Execution in uploading repository file in GitHub repository gogs/gogs prior to 0.12.6.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2022-0871	2022-03-11T12:15:07	2025-01-15T02:11:48.138995	Missing Authorization in GitHub repository gogs/gogs prior to 0.12.5.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2022-1285	2022-06-01T06:15:07	2025-01-15T02:12:37.475749	Server-Side Request Forgery (SSRF) in GitHub repository gogs/gogs prior to 0.12.8.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2021-32546	2022-06-02T14:15:28	2025-02-19T03:18:44.849947	Missing input validation in internal/db/repo_editor.go in Gogs before 0.12.8 allows an attacker to execute code remotely. An unprivileged attacker (registered user) can overwrite the Git configuration in his repository. This leads to Remote Command Execution, because that configuration can contain an option such as sshCommand, which is executed when a master branch is a remote branch (using an ssh:// URI). The remote branch can also be configured by editing the Git configuration file. One can create a new file in a new repository, using the GUI, with "\" as its name, and then rename this file to .git/config with the custom configuration content (and then save it).	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2022-1993	2022-06-09T17:15:08	2025-01-15T02:14:12.077734	Path Traversal in GitHub repository gogs/gogs prior to 0.12.9.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2022-1986	2022-06-09T17:15:08	2025-01-15T02:14:10.823292	OS Command Injection in GitHub repository gogs/gogs prior to 0.12.9.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2022-1992	2022-06-09T17:15:08	2025-01-15T02:14:12.806003	Path Traversal in GitHub repository gogs/gogs prior to 0.12.9.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2022-31038	2022-06-09T17:15:09	2025-01-15T02:21:26.690449	Gogs is an open source self-hosted Git service. In versions of gogs prior to 0.12.9 `DisplayName` does not filter characters input from users, which leads to an XSS vulnerability when directly displayed in the issue list. This issue has been resolved in commit 155cae1d which sanitizes `DisplayName` prior to display to the user. All users of gogs are advised to upgrade. Users unable to upgrade should check their users' display names for malicious characters.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2022-1464	2022-05-05T14:15:08	2025-01-15T02:13:08.994782	Stored xss bug in GitHub repository gogs/gogs prior to 0.12.7. As the repo is public , any user can view the report and when open the attachment then xss is executed. This bug allow executed any javascript code in victim account .	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2022-32174	2022-10-11T15:15:09	2025-02-19T03:27:59.689657	In Gogs, versions v0.6.5 through v0.12.10 are vulnerable to Stored Cross-Site Scripting (XSS) that leads to an account takeover.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2019-14544	2019-08-02T22:15:14	2025-02-19T02:48:16.736934	routes/api/v1/api.go in Gogs 0.11.86 lacks permission checks for routes: deploy keys, collaborators, and hooks.	[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2018-18925	2018-11-04T05:29:00	2025-02-19T02:29:18.992883	Gogs 0.11.66 allows remote code execution because it does not properly validate session IDs, as demonstrated by a ".." session-file forgery in the file session provider in file.go. This is related to session ID handling in the go-macaron/session code for Macaron.	[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2018-15193	2018-08-08T02:29:00	2025-02-19T02:30:59.632079	A CSRF vulnerability in the admin panel in Gogs through 0.11.53 allows remote attackers to execute admin operations via a crafted issue / link.	[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2018-15178	2018-08-08T00:29:02	2025-02-19T02:31:05.448124	Open redirect vulnerability in Gogs before 0.12 allows remote attackers to redirect users to arbitrary websites and conduct phishing attacks via an initial /\ substring in the user/login redirect_to parameter, related to the function isValidRedirect in routes/user/auth.go.	[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2018-17031	2018-09-14T02:29:00	2025-02-19T02:32:01.453419	In Gogs 0.11.53, an attacker can use a crafted .eml file to trigger MIME type sniffing, which leads to XSS, as demonstrated by Internet Explorer, because an "X-Content-Type-Options: nosniff" header is not sent.	[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2018-16409	2018-09-03T19:29:01	2025-02-19T02:31:38.356917	In Gogs 0.11.53, an attacker can use migrate to send arbitrary HTTP GET requests, leading to SSRF.	[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2018-20303	2018-12-20T00:29:00	2025-01-15T01:34:46.849824	In pkg/tool/path.go in Gogs before 0.11.82.1218, a directory traversal in the file-upload functionality can allow an attacker to create a file under data/sessions on the server, a similar issue to CVE-2018-18925.	[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2020-14958	2020-06-21T20:15:09	2025-01-15T01:43:12.862514	In Gogs 0.11.91, MakeEmailPrimary in models/user_mail.go lacks a "not the owner of the email" check.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2020-9329	2020-02-21T22:15:10	2025-02-19T03:14:08.649534	Gogs through 0.11.91 allows attackers to violate the admin-specified repo-creation policy due to an internal/db/repo.go race condition.	[ { "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2020-15867	2020-10-16T14:15:11	2025-02-19T03:08:54.037282	The git hook feature in Gogs 0.5.5 through 0.12.2 allows for authenticated remote code execution. There can be a privilege escalation if access to this hook feature is granted to a user who does not have administrative privileges. NOTE: because this is mentioned in the documentation but not in the UI, it could be considered a "Product UI does not Warn User of Unsafe Actions" issue.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/gogs/gogs	[]	[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]
CVE-2019-9047	2019-02-23T21:29:00	2025-01-14T08:08:55.540826	GoRose v1.0.4 has SQL Injection when the order_by or group_by parameter can be controlled.	[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/gohouse/gorose	[]	[ "5aeebf3335499bae38b9292594d8c2e44d5a0b4f" ]
CVE-2024-1394	2024-03-21T13:00:08	2025-01-15T05:04:55.042523	A memory leak flaw was found in Golang in the RSA encrypting/decrypting code, which might lead to a resource exhaustion vulnerability using attacker-controlled inputs. The memory leak happens in github.com/golang-fips/openssl/openssl/rsa.go#L113. The objects leaked are pkey and ctx. That function uses named return parameters to free pkey and ctx if there is an error initializing the context or setting the different properties. All return statements related to error cases follow the "return nil, nil, fail(...)" pattern, meaning that pkey and ctx will be nil inside the deferred function that should free them.	null	https://github.com/golang-fips/openssl	[]	[ "576fe0d377882f8d0fd6537762ef2ff7918facc8" ]
CVE-2023-39533	2023-08-08T19:15:10	2025-01-15T04:57:45.053991	go-libp2p is the Go implementation of the libp2p Networking Stack. Prior to versions 0.27.8, 0.28.2, and 0.29.1 malicious peer can use large RSA keys to run a resource exhaustion attack & force a node to spend time doing signature verification of the large key. This vulnerability is present in the core/crypto module of go-libp2p and can occur during the Noise handshake and the libp2p x509 extension verification step. To prevent this attack, go-libp2p versions 0.27.8, 0.28.2, and 0.29.1 restrict RSA keys to <= 8192 bits. To protect one's application, it is necessary to update to these patch releases and to use the updated Go compiler in 1.20.7 or 1.19.12. There are no known workarounds for this issue.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]	https://github.com/golang/go	[]	[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]
CVE-2023-39321	2023-09-08T17:15:28	2025-01-14T11:53:51.569394	Processing an incomplete post-handshake message for a QUIC connection can cause a panic.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]	https://github.com/golang/go	[]	[ "c19c4c566c63818dfd059b352e52c4710eecf14d" ]
CVE-2023-39322	2023-09-08T17:15:28	2025-01-14T11:53:48.411384	QUIC connections do not set an upper bound on the amount of data buffered when reading post-handshake messages, allowing a malicious QUIC connection to cause unbounded memory growth. With fix, connections now consistently reject messages larger than 65KiB in size.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]	https://github.com/golang/go	[]	[ "c19c4c566c63818dfd059b352e52c4710eecf14d" ]
CVE-2023-39320	2023-09-08T17:15:27	2025-01-14T11:53:47.557953	The go.mod toolchain directive, introduced in Go 1.21, can be leveraged to execute scripts and binaries relative to the root of the module when the "go" command was executed within the module. This applies to modules downloaded using the "go" command from the module proxy, as well as modules downloaded directly using VCS software.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/golang/go	[]	[ "c19c4c566c63818dfd059b352e52c4710eecf14d" ]
CVE-2021-27919	2021-03-11T00:15:12	2025-01-14T09:03:21.246988	archive/zip in Go 1.16.x before 1.16.1 allows attackers to cause a denial of service (panic) upon attempted use of the Reader.Open API for a ZIP archive in which ../ occurs at the beginning of any filename.	[ { "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]	https://github.com/golang/go	[]	[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]
CVE-2021-41772	2021-11-08T06:15:08	2025-01-14T09:56:23.518683	Go before 1.16.10 and 1.17.x before 1.17.3 allows an archive/zip Reader.Open panic via a crafted ZIP archive containing an invalid name or an empty filename field.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]	https://github.com/golang/go	[]	[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]
CVE-2022-28327	2022-04-20T10:15:08	2025-01-14T10:54:26.847954	The generic P-256 feature in crypto/elliptic in Go before 1.17.9 and 1.18.x before 1.18.1 allows a panic via long scalar input.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]	https://github.com/golang/go	[]	[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]
CVE-2022-27536	2022-04-20T10:15:07	2025-01-14T10:55:46.776794	Certificate.Verify in crypto/x509 in Go 1.18.x before 1.18.1 can be caused to panic on macOS when presented with certain malformed certificates. This allows a remote TLS server to cause a TLS client to panic.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]	https://github.com/golang/go	[]	[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]
CVE-2022-24675	2022-04-20T10:15:07	2025-01-14T10:51:42.835696	encoding/pem in Go before 1.17.9 and 1.18.x before 1.18.1 has a Decode stack overflow via a large amount of PEM data.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]	https://github.com/golang/go	[]	[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]
CVE-2022-30634	2022-07-15T20:15:08	2025-01-14T10:58:38.836773	Infinite loop in Read in crypto/rand before Go 1.17.11 and Go 1.18.3 on Windows allows attacker to cause an indefinite hang by passing a buffer larger than 1 << 32 - 1 bytes.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]	https://github.com/golang/go	[]	[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]
CVE-2022-29804	2022-08-10T20:15:34	2025-01-14T10:57:48.849102	Incorrect conversion of certain invalid paths to valid, absolute paths in Clean in path/filepath before Go 1.17.11 and Go 1.18.3 on Windows allows potential directory traversal attack.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]	https://github.com/golang/go	[]	[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]
CVE-2022-30580	2022-08-10T20:15:40	2025-01-14T10:58:25.441009	Code injection in Cmd.Start in os/exec before Go 1.17.11 and Go 1.18.3 allows execution of any binaries in the working directory named either "..com" or "..exe" by calling Cmd.Run, Cmd.Start, Cmd.Output, or Cmd.CombinedOutput when Cmd.Path is unset.	[ { "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/golang/go	[]	[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]
CVE-2019-6486	2019-01-24T05:29:00	2025-01-15T01:41:55.132651	Go before 1.10.8 and 1.11.x before 1.11.5 mishandles P-521 and P-384 elliptic curves, which allows attackers to cause a denial of service (CPU consumption) or possibly conduct ECDH private key recovery attacks.	[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H", "type": "CVSS_V3" } ]	https://github.com/golang/go	[]	[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]
CVE-2019-9741	2019-03-13T08:29:00	2025-01-14T08:10:36.159298	An issue was discovered in net/http in Go 1.11.5. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the second argument to http.NewRequest with \r\n followed by an HTTP header or a Redis command.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]	https://github.com/golang/go	[]	[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]
CVE-2019-9634	2019-03-08T15:29:00	2025-01-14T08:11:30.629254	Go through 1.12 on Windows misuses certain LoadLibrary functionality, leading to DLL injection.	[ { "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/golang/go	[]	[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]
CVE-2019-14809	2019-08-13T21:15:11	2025-01-14T07:48:56.145100	net/url in Go before 1.11.13 and 1.12.x before 1.12.8 mishandles malformed hosts in URLs, leading to an authorization bypass in some applications. This is related to a Host field with a suffix appearing in neither Hostname() nor Port(), and is related to a non-numeric port number. For example, an attacker can compose a crafted javascript:// URL that results in a hostname of google.com.	[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/golang/go	[]	[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]
CVE-2019-16276	2019-09-30T19:15:08	2025-01-14T07:51:26.422181	Go before 1.12.10 and 1.13.x before 1.13.1 allow HTTP Request Smuggling.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "type": "CVSS_V3" } ]	https://github.com/golang/go	[]	[ "3a1b4e75f8b6c1b57db73bccf7ca871bf1a97ca9", "66330d8c6c0a23b7eb48688f9954264e48b039da" ]
CVE-2019-11888	2019-05-13T05:29:01	2025-01-14T07:10:42.302005	Go through 1.12.5 on Windows mishandles process creation with a nil environment in conjunction with a non-nil token, which allows attackers to obtain sensitive information or gain privileges.	[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/golang/go	[]	[ "3a1b4e75f8b6c1b57db73bccf7ca871bf1a97ca9", "66330d8c6c0a23b7eb48688f9954264e48b039da" ]
CVE-2019-17596	2019-10-24T22:15:10	2025-01-14T07:53:38.532590	Go before 1.12.11 and 1.3.x before 1.13.2 can panic upon an attempt to process network traffic containing an invalid DSA public key. There are several attack scenarios, such as traffic from a client to a server that verifies client certificates.	[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]	https://github.com/golang/go	[]	[ "3a1b4e75f8b6c1b57db73bccf7ca871bf1a97ca9" ]
CVE-2016-5386	2016-07-19T02:00:18	2025-01-14T06:37:36.349952	The net/http package in Go through 1.6 does not attempt to address RFC 3875 section 4.1.18 namespace conflicts and therefore does not protect CGI applications from the presence of untrusted client data in the HTTP_PROXY environment variable, which might allow remote attackers to redirect a CGI application's outbound HTTP traffic to an arbitrary proxy server via a crafted Proxy header in an HTTP request, aka an "httpoxy" issue.	[ { "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]	https://github.com/golang/go	[]	[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]

CVE-2022-38870

2022-10-25T17:15:55

2025-01-14T11:09:12.436222

Free5gc v3.2.1 is vulnerable to Information disclosure.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]

https://github.com/free5gc/free5gc

[]

[ "04340eb8493ba98178ecc725e38ed8677f08d16e" ]

CVE-2022-43677

2022-10-24T14:15:53

2025-01-14T11:13:19.150155

In free5GC 3.2.1, a malformed NGAP message can crash the AMF and NGAP decoders via an index-out-of-range panic in aper.GetBitString.

[ { "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]

https://github.com/free5gc/free5gc

[]

[ "04340eb8493ba98178ecc725e38ed8677f08d16e" ]

CVE-2023-46324

2023-10-23T01:15:07

2025-01-14T12:02:36.373894

pkg/suci/suci.go in free5GC udm before 1.2.0, when Go before 1.19 is used, allows an Invalid Curve Attack because it may compute a shared secret via an uncompressed public key that has not been validated. An attacker can send arbitrary SUCIs to the UDM, which tries to decrypt them via both its private key and the attacker's public key.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]

https://github.com/free5gc/udm

[]

[ "dd730c193e4f2fefc6d4f9620f2a2452c89f93fd" ]

CVE-2022-36078

2022-09-02T13:15:08

2025-01-14T11:03:57.904685

Binary provides encoding/decoding in Borsh and other formats. The vulnerability is a memory allocation vulnerability that can be exploited to allocate slices in memory with (arbitrary) excessive size value, which can either exhaust available memory or crash the whole program. When using `github.com/gagliardetto/binary` to parse unchecked (or wrong type of) data from untrusted sources of input (e.g. the blockchain) into slices, it's possible to allocate memory with excessive size. When `dec.Decode(&val)` method is used to parse data into a structure that is or contains slices of values, the length of the slice was previously read directly from the data itself without any checks on the size of it, and then a slice was allocated. This could lead to an overflow and an allocation of memory with excessive size value. Users should upgrade to `v0.7.1` or higher. A workaround is not to rely on the `dec.Decode(&val)` function to parse the data, but to use a custom `UnmarshalWithDecoder()` method that reads and checks the length of any slice.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]

https://github.com/gagliardetto/binary

[]

[ "2b2638040b6d1921df7e9247b441a630ba80d517" ]

CVE-2023-44392

2023-10-09T20:15:10

2025-01-15T04:59:09.456035

Garden provides automation for Kubernetes development and testing. Prior tov ersions 0.13.17 and 0.12.65, Garden has a dependency on the cryo library, which is vulnerable to code injection due to an insecure implementation of deserialization. Garden stores serialized objects using cryo in the Kubernetes `ConfigMap` resources prefixed with `test-result` and `run-result` to cache Garden test and run results. These `ConfigMaps` are stored either in the `garden-system` namespace or the configured user namespace. When a user invokes the command `garden test` or `garden run` objects stored in the `ConfigMap` are retrieved and deserialized. This can be used by an attacker with access to the Kubernetes cluster to store malicious objects in the `ConfigMap`, which can trigger a remote code execution on the users machine when cryo deserializes the object. In order to exploit this vulnerability, an attacker must have access to the Kubernetes cluster used to deploy garden remote environments. Further, a user must actively invoke either a `garden test` or `garden run` which has previously cached results. The issue has been patched in Garden versions `0.13.17` (Bonsai) and `0.12.65` (Acorn). Only Garden versions prior to these are vulnerable. No known workarounds are available.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/garden-io/garden

[]

[ "af5fea7e2fe52d33cefd77a4130706b3f7f16fe8" ]

CVE-2022-24829

2022-04-11T20:15:20

2025-01-15T02:18:12.455858

Garden is an automation platform for Kubernetes development and testing. In versions prior to 0.12.39 multiple endpoints did not require authentication. In some operating modes this allows for an attacker to gain access to the application erroneously. The configuration is leaked through the /api endpoint on the local server that is responsible for serving the Garden dashboard. At the moment, this server is accessible to 0.0.0.0 which makes it accessible to anyone on the same network (or anyone on the internet if they are on a public, static IP). This may lead to the ability to compromise credentials, secrets or environment variables. Users are advised to upgrade to version 0.12.39 as soon as possible. Users unable to upgrade should use a firewall blocking access to port 9777 from all untrusted network machines.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/garden-io/garden

[]

[ "af5fea7e2fe52d33cefd77a4130706b3f7f16fe8" ]

CVE-2017-11671

2017-07-26T21:29:00

2025-01-14T07:20:52.551768

Under certain circumstances, the ix86_expand_builtin function in i386.c in GNU Compiler Collection (GCC) version 4.6, 4.7, 4.8, 4.9, 5 before 5.5, and 6 before 6.4 will generate instruction sequences that clobber the status flag of the RDRAND and RDSEED intrinsics before it can be read, potentially causing failures of these instructions to go unreported. This could potentially lead to less randomness in random number generation.

[ { "score": "CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "type": "CVSS_V3" } ]

https://github.com/gcc-mirror/gcc

[]

[ "4cf01c09fe137b7a70b9879ca396823615962eb3" ]

CVE-2023-37786

2023-07-13T17:15:09

2025-01-14T11:50:06.576066

Multiple cross-site scripting (XSS) vulnerabilities in Geeklog v2.2.2 allow attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Mail Settings[backend], Mail Settings[host], Mail Settings[port] and Mail Settings[auth] parameters of the /admin/configuration.php.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]

https://github.com/geeklog-core/geeklog

[]

[ "ef48c658c253a8d0ed28209ba8d5471489dcb472" ]

CVE-2023-37787

2023-07-13T17:15:09

2025-01-14T11:50:06.639398

Multiple cross-site scripting (XSS) vulnerabilities in Geeklog v2.2.2 allow attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Rule and Route parameters of /admin/router.php.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]

https://github.com/geeklog-core/geeklog

[]

[ "ef48c658c253a8d0ed28209ba8d5471489dcb472" ]

CVE-2023-46058

2023-10-24T00:15:08

2025-01-14T12:02:48.012313

Cross Site Scripting (XSS) vulnerability in Geeklog-Core geeklog v.2.2.2 allows a remote attacker to execute arbitrary code via a crafted payload to the grp_desc parameter of the admin/group.php component.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]

https://github.com/geeklog-core/geeklog

[]

[ "ef48c658c253a8d0ed28209ba8d5471489dcb472" ]

CVE-2023-46059

2023-10-24T00:15:08

2025-01-14T12:02:47.599381

Cross Site Scripting (XSS) vulnerability in Geeklog-Core geeklog v.2.2.2 allows a remote attacker to execute arbitrary code via a crafted payload to the Service, and website URL to Ping parameters of the admin/trackback.php component.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]

https://github.com/geeklog-core/geeklog

[]

[ "ef48c658c253a8d0ed28209ba8d5471489dcb472" ]

CVE-2021-38197

2021-08-08T16:15:07

2025-01-14T09:29:13.838335

unarr.go in go-unarr (aka Go bindings for unarr) 0.1.1 allows Directory Traversal via ../ in a pathname within a TAR archive.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/gen2brain/go-unarr

[]

[ "a9c9a14faa9e11d8ca8ba5b98d0d4f82215ce17c" ]

CVE-2023-28424

2023-03-20T13:15:11

2025-01-14T11:37:08.234912

Soko if the code that powers packages.gentoo.org. Prior to version 1.0.2, the two package search handlers, `Search` and `SearchFeed`, implemented in `pkg/app/handler/packages/search.go`, are affected by a SQL injection via the `q` parameter. As a result, unauthenticated attackers can execute arbitrary SQL queries on `https://packages.gentoo.org/`. It was also demonstrated that primitive was enough to gain code execution in the context of the PostgreSQL container. The issue was addressed in commit `4fa6e4b619c0362728955b6ec56eab0e0cbf1e23y` of version 1.0.2 using prepared statements to interpolate user-controlled data in SQL queries.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/gentoo/soko

[]

[ "0e8a1a49290b7b08f31c603d3895f60bb38d5bb7" ]

CVE-2023-26033

2023-02-25T00:15:11

2025-01-14T11:35:10.778979

Gentoo soko is the code that powers packages.gentoo.org. Versions prior to 1.0.1 are vulnerable to SQL Injection, leading to a Denial of Service. If the user selects (in user preferences) the "Recently Visited Packages" view for the index page, the value of the `search_history` cookie is used as a base64 encoded comma separated list of atoms. These are string loaded directly into the SQL query with `atom = '%s'` format string. As a result, any user can modify the browser's cookie value and inject most SQL queries. A proof of concept malformed cookie was generated that wiped the database or changed it's content. On the database, only public data is stored, so there is no confidentiality issues to site users. If it is known that the database was modified, a full restoration of data is possible by performing a full database wipe and performing full update of all components. This issue is patched with commit id 5ae9ca83b73. Version 1.0.1 contains the patch. If users are unable to upgrade immediately, the following workarounds may be applied: (1.) Use a proxy to always drop the `search_history` cookie until upgraded. The impact on user experience is low. (2.) Sanitize to the value of `search_history` cookie after base64 decoding it.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/gentoo/soko

[]

[ "0e8a1a49290b7b08f31c603d3895f60bb38d5bb7" ]

CVE-2020-26772

2021-09-08T21:15:09

2025-01-14T08:41:45.609331

Command Injection in PPGo_Jobs v2.8.0 allows remote attackers to execute arbitrary code via the 'AjaxRun()' function.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/george518/ppgo_job

[]

[ "d1aef8d5e1c7fec896c604d45f8c37565b68aa0d" ]

CVE-2023-32691

2023-05-30T04:15:09

2025-02-19T03:33:24.966650

gost (GO Simple Tunnel) is a simple tunnel written in golang. Sensitive secrets such as passwords, token and API keys should be compared only using a constant-time comparison function. Untrusted input, sourced from a HTTP header, is compared directly with a secret. Since this comparison is not secure, an attacker can mount a side-channel timing attack to guess the password. As a workaround, this can be easily fixed using a constant time comparing function such as `crypto/subtle`'s `ConstantTimeCompare`.

[ { "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]

https://github.com/ginuerzh/gost

[]

[ "729d0e70005607dc7c69fc1de62fd8fe21f85355" ]

CVE-2022-41953

2023-01-17T22:15:10

2025-02-19T03:32:09.079842

Git GUI is a convenient graphical tool that comes with Git for Windows. Its target audience is users who are uncomfortable with using Git on the command-line. Git GUI has a function to clone repositories. Immediately after the local clone is available, Git GUI will automatically post-process it, among other things running a spell checker called `aspell.exe` if it was found. Git GUI is implemented as a Tcl/Tk script. Due to the unfortunate design of Tcl on Windows, the search path when looking for an executable _always includes the current directory_. Therefore, malicious repositories can ship with an `aspell.exe` in their top-level directory which is executed by Git GUI without giving the user a chance to inspect it first, i.e. running untrusted code. This issue has been addressed in version 2.39.1. Users are advised to upgrade. Users unable to upgrade should avoid using Git GUI for cloning. If that is not a viable option, at least avoid cloning from untrusted sources.

[ { "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/git-for-windows/git

[]

[ "34d5217584ee4722d0c0b07ed6c8f1f01ad157c3" ]

CVE-2023-29011

2023-04-25T21:15:10

2025-02-19T03:34:57.132947

Git for Windows, the Windows port of Git, ships with an executable called `connect.exe`, which implements a SOCKS5 proxy that can be used to connect e.g. to SSH servers via proxies when certain ports are blocked for outgoing connections. The location of `connect.exe`'s config file is hard-coded as `/etc/connectrc` which will typically be interpreted as `C:\etc\connectrc`. Since `C:\etc` can be created by any authenticated user, this makes `connect.exe` susceptible to malicious files being placed there by other users on the same multi-user machine. The problem has been patched in Git for Windows v2.40.1. As a workaround, create the folder `etc` on all drives where Git commands are run, and remove read/write access from those folders. Alternatively, watch out for malicious `<drive>:\etc\connectrc` files on multi-user machines.

[ { "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/git-for-windows/git

[]

[ "34d5217584ee4722d0c0b07ed6c8f1f01ad157c3" ]

CVE-2023-29012

2023-04-25T21:15:10

2025-02-19T03:34:53.636718

Git for Windows is the Windows port of Git. Prior to version 2.40.1, any user of Git CMD who starts the command in an untrusted directory is impacted by an Uncontrolles Search Path Element vulnerability. Maliciously-placed `doskey.exe` would be executed silently upon running Git CMD. The problem has been patched in Git for Windows v2.40.1. As a workaround, avoid using Git CMD or, if using Git CMD, avoid starting it in an untrusted directory.

[ { "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/git-for-windows/git

[]

[ "34d5217584ee4722d0c0b07ed6c8f1f01ad157c3" ]

CVE-2023-22743

2023-02-14T21:15:12

2025-02-19T03:32:16.302893

Git for Windows is the Windows port of the revision control system Git. Prior to Git for Windows version 2.39.2, by carefully crafting DLL and putting into a subdirectory of a specific name living next to the Git for Windows installer, Windows can be tricked into side-loading said DLL. This potentially allows users with local write access to place malicious payloads in a location where automated upgrades might run the Git for Windows installer with elevation. Version 2.39.2 contains a patch for this issue. Some workarounds are available. Never leave untrusted files in the Downloads folder or its sub-folders before executing the Git for Windows installer, or move the installer into a different directory before executing it.

[ { "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/git-for-windows/git

[]

[ "34d5217584ee4722d0c0b07ed6c8f1f01ad157c3" ]

CVE-2023-23618

2023-02-14T21:15:13

2025-01-15T04:44:16.870186

Git for Windows is the Windows port of the revision control system Git. Prior to Git for Windows version 2.39.2, when `gitk` is run on Windows, it potentially runs executables from the current directory inadvertently, which can be exploited with some social engineering to trick users into running untrusted code. A patch is available in version 2.39.2. As a workaround, avoid using `gitk` (or Git GUI's "Visualize History" functionality) in clones of untrusted repositories.

[ { "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/git-for-windows/git

[]

[ "34d5217584ee4722d0c0b07ed6c8f1f01ad157c3" ]

CVE-2022-24767

2022-04-12T18:15:09

2025-02-19T03:28:39.686857

GitHub: Git for Windows' uninstaller vulnerable to DLL hijacking when run under the SYSTEM user account.

[ { "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/git-for-windows/git

[]

[ "34d5217584ee4722d0c0b07ed6c8f1f01ad157c3" ]

CVE-2022-31012

2022-07-12T21:15:09

2025-02-19T03:28:14.067124

Git for Windows is a fork of Git that contains Windows-specific patches. This vulnerability in versions prior to 2.37.1 lets Git for Windows' installer execute a binary into `C:\mingw64\bin\git.exe` by mistake. This only happens upon a fresh install, not when upgrading Git for Windows. A patch is included in version 2.37.1. Two workarounds are available. Create the `C:\mingw64` folder and remove read/write access from this folder, or disallow arbitrary authenticated users to create folders in `C:\`.

[ { "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/git-for-windows/git

[]

[ "34d5217584ee4722d0c0b07ed6c8f1f01ad157c3" ]

CVE-2016-9274

2016-11-11T17:59:00

2025-02-19T02:18:24.635802

Untrusted search path vulnerability in Git 1.x for Windows allows local users to gain privileges via a Trojan horse git.exe file in the current working directory. NOTE: 2.x is unaffected.

[ { "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/git-for-windows/git

[]

[ "34d5217584ee4722d0c0b07ed6c8f1f01ad157c3" ]

CVE-2021-32638

2021-05-25T17:15:08

2025-01-15T01:55:09.659316

Github's CodeQL action is provided to run CodeQL-based code scanning on non-GitHub CI/CD systems and requires a GitHub access token to connect to a GitHub repository. The runner and its documentation previously suggested passing the GitHub token as a command-line parameter to the process instead of reading it from a file, standard input, or an environment variable. This approach made the token visible to other processes on the same machine, for example in the output of the `ps` command. If the CI system publicly exposes the output of `ps`, for example by logging the output, then the GitHub access token can be exposed beyond the scope intended. Users of the CodeQL runner on 3rd-party systems, who are passing a GitHub token via the `--github-auth` flag, are affected. This applies to both GitHub.com and GitHub Enterprise users. Users of the CodeQL Action on GitHub Actions are not affected. The `--github-auth` flag is now considered insecure and deprecated. The undocumented `--external-repository-token` flag has been removed. To securely provide a GitHub access token to the CodeQL runner, users should **do one of the following instead**: Use the `--github-auth-stdin` flag and pass the token on the command line via standard input OR set the `GITHUB_TOKEN` environment variable to contain the token, then call the command without passing in the token. The old flag remains present for backwards compatibility with existing workflows. If the user tries to specify an access token using the `--github-auth` flag, there is a deprecation warning printed to the terminal that directs the user to one of the above options. All CodeQL runner releases codeql-bundle-20210304 onwards contain the patches. We recommend updating to a recent version of the CodeQL runner, storing a token in your CI system's secret storage mechanism, and passing the token to the CodeQL runner using `--github-auth-stdin` or the `GITHUB_TOKEN` environment variable. If still using the old flag, ensure that process output, such as from `ps`, is not persisted in CI logs.

[ { "score": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]

https://github.com/github/codeql-action

[]

[ "0dc37c7260df8e43e9d5a7d4455662fda84240b3" ]

CVE-2025-24362

2025-01-24T18:15:32

2025-01-25T01:57:57.337756

In some circumstances, debug artifacts uploaded by the CodeQL Action after a failed code scanning workflow run may contain the environment variables from the workflow run, including any secrets that were exposed as environment variables to the workflow. Users with read access to the repository would be able to access this artifact, containing any secrets from the environment. This vulnerability is patched in CodeQL Action version 3.28.3 or later, or CodeQL CLI version 2.20.3 or later. For some affected workflow runs, the exposed environment variables in the debug artifacts included a valid `GITHUB_TOKEN` for the workflow run, which has access to the repository in which the workflow ran, and all the permissions specified in the workflow or job. The `GITHUB_TOKEN` is valid until the job completes or 24 hours has elapsed, whichever comes first. Environment variables are exposed only from workflow runs that satisfy all of the following conditions: - Code scanning workflow configured to scan the Java/Kotlin languages. - Running in a repository containing Kotlin source code. - Running with debug artifacts enabled. - Using CodeQL Action versions <= 3.28.2, and CodeQL CLI versions >= 2.9.2 (May 2022) and <= 2.20.2. - The workflow run fails before the CodeQL database is finalized within the `github/codeql-action/analyze` step. - Running in any GitHub environment: GitHub.com, GitHub Enterprise Cloud, and GitHub Enterprise Server. Note: artifacts are only accessible to users within the same GitHub environment with access to the scanned repo. The `GITHUB_TOKEN` exposed in this way would only have been valid for workflow runs that satisfy all of the following conditions, in addition to the conditions above: - Using CodeQL Action versions >= 3.26.11 (October 2024) and <= 3.28.2, or >= 2.26.11 and < 3. - Running in GitHub.com or GitHub Enterprise Cloud only (not valid on GitHub Enterprise Server). In rare cases during advanced setup, logging of environment variables may also occur during database creation of Java, Swift, and C/C++. Please read the corresponding CodeQL CLI advisory GHSA-gqh3-9prg-j95m for more details. In CodeQL CLI versions >= 2.9.2 and <= 2.20.2, the CodeQL Kotlin extractor logs all environment variables by default into an intermediate file during the process of creating a CodeQL database for Kotlin code. This is a part of the CodeQL CLI and is invoked by the CodeQL Action for analyzing Kotlin repositories. On Actions, the environment variables logged include GITHUB_TOKEN, which grants permissions to the repository being scanned. The intermediate file containing environment variables is deleted when finalizing the database, so it is not included in a successfully created database. It is, however, included in the debug artifact that is uploaded on a failed analysis run if the CodeQL Action was invoked in debug mode. Therefore, under these specific circumstances (incomplete database creation using the CodeQL Action in debug mode) an attacker with access to the debug artifact would gain unauthorized access to repository secrets from the environment, including both the `GITHUB_TOKEN` and any user-configured secrets made available via environment variables. The impact of the `GITHUB_TOKEN` leaked in this environment is limited: - For workflows on GitHub.com and GitHub Enterprise Cloud using CodeQL Action versions >= 3.26.11 and <= 3.28.2, or >= 2.26.11 and < 3, which in turn use the `actions/artifacts v4` library, the debug artifact is uploaded before the workflow job completes. During this time the `GITHUB_TOKEN` is still valid, providing an opportunity for attackers to gain access to the repository. - For all other workflows, the debug artifact is uploaded after the workflow job completes, at which point the leaked `GITHUB_TOKEN` has been revoked and cannot be used to access the repository.

null

https://github.com/github/codeql-action

[]

[ "0dc37c7260df8e43e9d5a7d4455662fda84240b3" ]

CVE-2022-2251

2023-01-17T21:15:12

2025-01-14T10:46:01.712029

Improper sanitization of branch names in GitLab Runner affecting all versions prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2 allows a user who creates a branch with a specially crafted name and gets another user to trigger a pipeline to execute commands in the runner as that other user.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/gitlabhq/gitlab-runner

[]

[ "7178588dc1e747941d1c5b9da759c0c00b6aaa96" ]

CVE-2020-13295

2020-08-10T14:15:13

2025-01-14T08:17:32.671855

For GitLab Runner before 13.0.12, 13.1.6, 13.2.3, by replacing dockerd with a malicious server, the Shared Runner is susceptible to SSRF.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/gitlabhq/gitlab-runner

[]

[ "a998cacdcee3e1b21cbb23526f5e7da54e53e047" ]

CVE-2024-21583

2024-07-19T05:15:10

2025-01-15T05:06:39.853501

Versions of the package github.com/gitpod-io/gitpod/components/server/go/pkg/lib before main-gha.27122; versions of the package github.com/gitpod-io/gitpod/components/ws-proxy/pkg/proxy before main-gha.27122; versions of the package github.com/gitpod-io/gitpod/install/installer/pkg/components/auth before main-gha.27122; versions of the package github.com/gitpod-io/gitpod/install/installer/pkg/components/public-api-server before main-gha.27122; versions of the package github.com/gitpod-io/gitpod/install/installer/pkg/components/server before main-gha.27122; versions of the package @gitpod/gitpod-protocol before 0.1.5-main-gha.27122 are vulnerable to Cookie Tossing due to a missing __Host- prefix on the _gitpod_io_jwt2_ session cookie. This allows an adversary who controls a subdomain to set the value of the cookie on the Gitpod control plane, which can be assigned to an attacker’s own JWT so that specific actions taken by the victim (such as connecting a new Github organization) are actioned by the attackers session.

null

https://github.com/gitpod-io/gitpod

[]

[ "3c0afbafa50dd1e66f385e091fa49c873405faa8" ]

CVE-2023-0957

2023-03-03T08:15:08

2025-01-15T04:38:47.903024

An issue was discovered in Gitpod versions prior to release-2022.11.2.16. There is a Cross-Site WebSocket Hijacking (CSWSH) vulnerability that allows attackers to make WebSocket connections to the Gitpod JSONRPC server using a victim’s credentials, because the Origin header is not restricted. This can lead to the extraction of data from workspaces, to a full takeover of the workspace.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/gitpod-io/gitpod

[]

[ "3c0afbafa50dd1e66f385e091fa49c873405faa8" ]

CVE-2023-32766

2023-06-05T15:15:09

2025-01-31T20:00:51.301146

Gitpod before 2022.11.3 allows XSS because redirection can occur for some protocols outside of the trusted set of three (vscode: vscode-insiders: jetbrains-gateway:).

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]

https://github.com/gitpod-io/gitpod

[]

[ "3c0afbafa50dd1e66f385e091fa49c873405faa8" ]

CVE-2021-35206

2021-06-22T14:15:09

2025-01-15T02:00:03.884948

Gitpod before 0.6.0 allows unvalidated redirects.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]

https://github.com/gitpod-io/gitpod

[]

[ "3c0afbafa50dd1e66f385e091fa49c873405faa8" ]

CVE-2020-36559

2022-12-27T22:15:11

2025-01-15T01:45:28.647399

Due to improper sanitization of user input, HTTPEngine.Handle allows for directory traversal, allowing an attacker to read files outside of the target directory that the server has permission to read.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]

https://github.com/go-aah/aah

[]

[ "def102ffcb9e1d3b029a2c3d884ed6407d9a1389" ]

CVE-2022-42980

2022-10-17T07:15:08

2025-02-19T03:28:19.149066

go-admin (aka GO Admin) 2.0.12 uses the string go-admin as a production JWT key.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/go-admin-team/go-admin

[]

[ "012202478905438be61b0ae3958d4f31df4d340c" ]

CVE-2020-12666

2020-05-05T22:15:13

2025-01-14T08:16:17.156212

macaron before 1.3.7 has an open redirect in the static handler, as demonstrated by the http://127.0.0.1:4000//example.com/ URL.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]

https://github.com/go-macaron/macaron

[]

[ "bbb5ca29768e04c2d5f344c235909f44c8dd0fdd" ]

CVE-2022-46959

2023-01-23T05:15:18

2025-01-14T11:16:29.309697

An issue in the component /admin/backups/work-dir of Sonic v1.0.4 allows attackers to execute a directory traversal.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N", "type": "CVSS_V3" } ]

https://github.com/go-sonic/sonic

[]

[ "ec9c203b2721db0589fb8daa2e1f9bba0d4e82ee" ]

CVE-2020-26294

2021-01-04T19:15:15

2025-01-15T01:44:52.494575

Vela is a Pipeline Automation (CI/CD) framework built on Linux container technology written in Golang. In Vela compiler before version 0.6.1 there is a vulnerability which allows exposure of server configuration. It impacts all users of Vela. An attacker can use Sprig's `env` function to retrieve configuration information, see referenced GHSA for an example. This has been fixed in version 0.6.1. In addition to upgrading, it is recommended to rotate all secrets.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "type": "CVSS_V3" } ]

https://github.com/go-vela/compiler

[]

[ "f7912c5019d2994e619f2a77d949d0996617c44a" ]

CVE-2024-28236

2024-03-12T21:15:59

2025-02-19T03:37:15.888400

Vela is a Pipeline Automation (CI/CD) framework built on Linux container technology written in Golang. Vela pipelines can use variable substitution combined with insensitive fields like `parameters`, `image` and `entrypoint` to inject secrets into a plugin/image and — by using common substitution string manipulation — can bypass log masking and expose secrets without the use of the commands block. This unexpected behavior primarily impacts secrets restricted by the "no commands" option. This can lead to unintended use of the secret value, and increased risk of exposing the secret during image execution bypassing log masking. **To exploit this** the pipeline author must be supplying the secrets to a plugin that is designed in such a way that will print those parameters in logs. Plugin parameters are not designed for sensitive values and are often intentionally printed throughout execution for informational/debugging purposes. Parameters should therefore be treated as insensitive. While Vela provides secrets masking, secrets exposure is not entirely solved by the masking process. A docker image (plugin) can easily expose secrets if they are not handled properly, or altered in some way. There is a responsibility on the end-user to understand how values injected into a plugin are used. This is a risk that exists for many CICD systems (like GitHub Actions) that handle sensitive runtime variables. Rather, the greater risk is that users who restrict a secret to the "no commands" option and use image restriction can still have their secret value exposed via substitution tinkering, which turns the image and command restrictions into a false sense of security. This issue has been addressed in version 0.23.2. Users are advised to upgrade. Users unable to upgrade should not provide sensitive values to plugins that can potentially expose them, especially in `parameters` that are not intended to be used for sensitive values, ensure plugins (especially those that utilize shared secrets) follow best practices to avoid logging parameters that are expected to be sensitive, minimize secrets with `pull_request` events enabled, as this allows users to change pipeline configurations and pull in secrets to steps not typically part of the CI process, make use of the build approval setting, restricting builds from untrusted users, and limit use of shared secrets, as they are less restrictive to access by nature.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]

https://github.com/go-vela/server

[]

[ "5a3ffe34701a1451192376bb87e8a03ad361a5ed" ]

CVE-2021-21432

2021-04-09T18:15:13

2025-01-15T01:47:36.105601

Vela is a Pipeline Automation (CI/CD) framework built on Linux container technology written in Golang. An authentication mechanism added in version 0.7.0 enables some malicious user to obtain secrets utilizing the injected credentials within the `~/.netrc` file. Refer to the referenced GitHub Security Advisory for complete details. This is fixed in version 0.7.5.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]

https://github.com/go-vela/server

[]

[ "5a3ffe34701a1451192376bb87e8a03ad361a5ed" ]

CVE-2022-39395

2022-11-10T18:15:10

2025-02-19T03:29:46.997185

Vela is a Pipeline Automation (CI/CD) framework built on Linux container technology written in Golang. In Vela Server and Vela Worker prior to version 0.16.0 and Vela UI prior to version 0.17.0, some default configurations for Vela allow exploitation and container breakouts. Users should upgrade to Server 0.16.0, Worker 0.16.0, and UI 0.17.0 to fix the issue. After upgrading, Vela administrators will need to explicitly change the default settings to configure Vela as desired. Some of the fixes will interrupt existing workflows and will require Vela administrators to modify default settings. However, not applying the patch (or workarounds) will continue existing risk exposure. Some workarounds are available. Vela administrators can adjust the worker's `VELA_RUNTIME_PRIVILEGED_IMAGES` setting to be explicitly empty, leverage the `VELA_REPO_ALLOWLIST` setting on the server component to restrict access to a list of repositories that are allowed to be enabled, and/or audit enabled repositories and disable pull_requests if they are not needed.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/go-vela/server

[]

[ "5a3ffe34701a1451192376bb87e8a03ad361a5ed" ]

CVE-2019-25073

2022-12-27T22:15:11

2025-01-15T01:40:47.689671

Improper path sanitization in github.com/goadesign/goa before v3.0.9, v2.0.10, or v1.4.3 allow remote attackers to read files outside of the intended directory.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]

https://github.com/goadesign/goa

[]

[ "c562182dfa2a4ee68d7e08f8bc882606bebef5a1" ]

CVE-2024-38513

2024-07-01T19:15:05

2025-01-15T05:16:27.672456

Fiber is an Express-inspired web framework written in Go A vulnerability present in versions prior to 2.52.5 is a session middleware issue in GoFiber versions 2 and above. This vulnerability allows users to supply their own session_id value, resulting in the creation of a session with that key. If a website relies on the mere presence of a session for security purposes, this can lead to significant security risks, including unauthorized access and session fixation attacks. All users utilizing GoFiber's session middleware in the affected versions are impacted. The issue has been addressed in version 2.52.5. Users are strongly encouraged to upgrade to version 2.52.5 or higher to mitigate this vulnerability. Users who are unable to upgrade immediately can apply the following workarounds to reduce the risk: Either implement additional validation to ensure session IDs are not supplied by the user and are securely generated by the server, or regularly rotate session IDs and enforce strict session expiration policies.

null

https://github.com/gofiber/fiber

[]

[ "0e9593886c2cb51dd78d1946eac620c8c83bf90a" ]

CVE-2024-25124

2024-02-21T21:15:09

2025-02-06T00:59:10.754724

Fiber is a web framework written in go. Prior to version 2.52.1, the CORS middleware allows for insecure configurations that could potentially expose the application to multiple CORS-related vulnerabilities. Specifically, it allows setting the Access-Control-Allow-Origin header to a wildcard (`*`) while also having the Access-Control-Allow-Credentials set to true, which goes against recommended security best practices. The impact of this misconfiguration is high as it can lead to unauthorized access to sensitive user data and expose the system to various types of attacks listed in the PortSwigger article linked in the references. Version 2.52.1 contains a patch for this issue. As a workaround, users may manually validate the CORS configurations in their implementation to ensure that they do not allow a wildcard origin when credentials are enabled. The browser fetch api, as well as browsers and utilities that enforce CORS policies, are not affected by this.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/gofiber/fiber

[]

[ "0e9593886c2cb51dd78d1946eac620c8c83bf90a" ]

CVE-2023-41338

2023-09-08T19:15:43

2025-01-15T04:59:19.885090

Fiber is an Express inspired web framework built in the go language. Versions of gofiber prior to 2.49.2 did not properly restrict access to localhost. This issue impacts users of our project who rely on the `ctx.IsFromLocal` method to restrict access to localhost requests. If exploited, it could allow unauthorized access to resources intended only for localhost. Setting `X-Forwarded-For: 127.0.0.1` in a request from a foreign host, will result in true for `ctx.IsFromLocal`. Access is limited to the scope of the affected process. This issue has been patched in version `2.49.2` with commit `b8c9ede6`. Users are advised to upgrade. There are no known workarounds to remediate this vulnerability without upgrading to the patched version.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "type": "CVSS_V3" } ]

https://github.com/gofiber/fiber

[]

[ "0e9593886c2cb51dd78d1946eac620c8c83bf90a" ]

CVE-2023-45128

2023-10-16T21:15:11

2025-01-15T05:00:44.174477

Fiber is an express inspired web framework written in Go. A Cross-Site Request Forgery (CSRF) vulnerability has been identified in the application, which allows an attacker to inject arbitrary values and forge malicious requests on behalf of a user. This vulnerability can allow an attacker to inject arbitrary values without any authentication, or perform various malicious actions on behalf of an authenticated user, potentially compromising the security and integrity of the application. The vulnerability is caused by improper validation and enforcement of CSRF tokens within the application. This issue has been addressed in version 2.50.0 and users are advised to upgrade. Users should take additional security measures like captchas or Two-Factor Authentication (2FA) and set Session cookies with SameSite=Lax or SameSite=Secure, and the Secure and HttpOnly attributes as defense in depth measures. There are no known workarounds for this vulnerability.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/gofiber/fiber

[]

[ "0e9593886c2cb51dd78d1946eac620c8c83bf90a" ]

CVE-2023-45141

2023-10-16T21:15:11

2025-02-19T03:35:55.069799

Fiber is an express inspired web framework written in Go. A Cross-Site Request Forgery (CSRF) vulnerability has been identified in the application, which allows an attacker to obtain tokens and forge malicious requests on behalf of a user. This can lead to unauthorized actions being taken on the user's behalf, potentially compromising the security and integrity of the application. The vulnerability is caused by improper validation and enforcement of CSRF tokens within the application. This vulnerability has been addressed in version 2.50.0 and users are advised to upgrade. Users should take additional security measures like captchas or Two-Factor Authentication (2FA) and set Session cookies with SameSite=Lax or SameSite=Secure, and the Secure and HttpOnly attributes.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/gofiber/fiber

[]

[ "0e9593886c2cb51dd78d1946eac620c8c83bf90a" ]

CVE-2020-15111

2020-07-20T18:15:12

2025-02-19T03:09:33.426508

In Fiber before version 1.12.6, the filename that is given in c.Attachment() (https://docs.gofiber.io/ctx#attachment) is not escaped, and therefore vulnerable for a CRLF injection attack. I.e. an attacker could upload a custom filename and then give the link to the victim. With this filename, the attacker can change the name of the downloaded file, redirect to another site, change the authorization header, etc. A possible workaround is to serialize the input before passing it to ctx.Attachment().

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N", "type": "CVSS_V3" } ]

https://github.com/gofiber/fiber

[]

[ "0e9593886c2cb51dd78d1946eac620c8c83bf90a" ]

CVE-2024-22199

2024-01-11T18:15:45

2025-01-15T05:06:49.773657

This package provides universal methods to use multiple template engines with the Fiber web framework using the Views interface. This vulnerability specifically impacts web applications that render user-supplied data through this template engine, potentially leading to the execution of malicious scripts in users' browsers when visiting affected web pages. The vulnerability has been addressed, the template engine now defaults to having autoescape set to `true`, effectively mitigating the risk of XSS attacks.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]

https://github.com/gofiber/template

[]

[ "fd5a1ab847ebbf537447561827f310ba70fd0998" ]

CVE-2024-44625

2024-11-15T17:15:20

2025-02-19T03:38:16.534051

Gogs <=0.13.0 is vulnerable to Directory Traversal via the editFilePost function of internal/route/repo/editor.go.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2022-1884

2024-11-15T11:15:07

2025-02-19T03:25:59.708390

A remote command execution vulnerability exists in gogs/gogs versions <=0.12.7 when deployed on a Windows server. The vulnerability arises due to improper validation of the `tree_path` parameter during file uploads. An attacker can set `tree_path=.git.` to upload a file into the .git directory, allowing them to write or rewrite the `.git/config` file. If the `core.sshCommand` is set, this can lead to remote command execution.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2024-39931

2024-07-04T16:15:02

2025-02-19T03:38:29.681021

Gogs through 0.13.0 allows deletion of internal files.

null

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2024-39933

2024-07-04T16:15:02

2025-02-19T03:38:27.787272

Gogs through 0.13.0 allows argument injection during the tagging of a new release.

null

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2024-39930

2024-07-04T16:15:02

2025-02-19T03:38:29.577175

The built-in SSH server of Gogs through 0.13.0 allows argument injection in internal/ssh/ssh.go, leading to remote code execution. Authenticated attackers can exploit this by opening an SSH connection and sending a malicious --split-string env request if the built-in SSH server is activated. Windows installations are unaffected.

null

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2024-39932

2024-07-04T16:15:02

2025-02-19T03:38:28.446130

Gogs through 0.13.0 allows argument injection during the previewing of changes.

null

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2024-54148

2024-12-23T16:15:07

2025-01-15T05:16:46.592921

Gogs is an open source self-hosted Git service. A malicious user is able to commit and edit a crafted symlink file to a repository to gain SSH access to the server. The vulnerability is fixed in 0.13.1.

null

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2024-55947

2024-12-23T16:15:07

2025-01-15T05:17:07.214438

Gogs is an open source self-hosted Git service. A malicious user is able to write a file to an arbitrary path on the server to gain SSH access to the server. The vulnerability is fixed in 0.13.1.

null

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2022-2024

2023-02-25T08:15:09

2025-01-15T02:13:41.071350

OS Command Injection in GitHub repository gogs/gogs prior to 0.12.11.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2022-0870

2022-03-11T11:15:07

2025-01-15T02:11:48.021536

Server-Side Request Forgery (SSRF) in GitHub repository gogs/gogs prior to 0.12.5.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2022-0415

2022-03-21T11:15:10

2025-01-15T02:10:17.955039

Remote Command Execution in uploading repository file in GitHub repository gogs/gogs prior to 0.12.6.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2022-0871

2022-03-11T12:15:07

2025-01-15T02:11:48.138995

Missing Authorization in GitHub repository gogs/gogs prior to 0.12.5.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2022-1285

2022-06-01T06:15:07

2025-01-15T02:12:37.475749

Server-Side Request Forgery (SSRF) in GitHub repository gogs/gogs prior to 0.12.8.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2021-32546

2022-06-02T14:15:28

2025-02-19T03:18:44.849947

Missing input validation in internal/db/repo_editor.go in Gogs before 0.12.8 allows an attacker to execute code remotely. An unprivileged attacker (registered user) can overwrite the Git configuration in his repository. This leads to Remote Command Execution, because that configuration can contain an option such as sshCommand, which is executed when a master branch is a remote branch (using an ssh:// URI). The remote branch can also be configured by editing the Git configuration file. One can create a new file in a new repository, using the GUI, with "\" as its name, and then rename this file to .git/config with the custom configuration content (and then save it).

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2022-1993

2022-06-09T17:15:08

2025-01-15T02:14:12.077734

Path Traversal in GitHub repository gogs/gogs prior to 0.12.9.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2022-1986

2022-06-09T17:15:08

2025-01-15T02:14:10.823292

OS Command Injection in GitHub repository gogs/gogs prior to 0.12.9.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2022-1992

2022-06-09T17:15:08

2025-01-15T02:14:12.806003

Path Traversal in GitHub repository gogs/gogs prior to 0.12.9.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2022-31038

2022-06-09T17:15:09

2025-01-15T02:21:26.690449

Gogs is an open source self-hosted Git service. In versions of gogs prior to 0.12.9 `DisplayName` does not filter characters input from users, which leads to an XSS vulnerability when directly displayed in the issue list. This issue has been resolved in commit 155cae1d which sanitizes `DisplayName` prior to display to the user. All users of gogs are advised to upgrade. Users unable to upgrade should check their users' display names for malicious characters.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2022-1464

2022-05-05T14:15:08

2025-01-15T02:13:08.994782

Stored xss bug in GitHub repository gogs/gogs prior to 0.12.7. As the repo is public , any user can view the report and when open the attachment then xss is executed. This bug allow executed any javascript code in victim account .

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2022-32174

2022-10-11T15:15:09

2025-02-19T03:27:59.689657

In Gogs, versions v0.6.5 through v0.12.10 are vulnerable to Stored Cross-Site Scripting (XSS) that leads to an account takeover.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2019-14544

2019-08-02T22:15:14

2025-02-19T02:48:16.736934

routes/api/v1/api.go in Gogs 0.11.86 lacks permission checks for routes: deploy keys, collaborators, and hooks.

[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2018-18925

2018-11-04T05:29:00

2025-02-19T02:29:18.992883

Gogs 0.11.66 allows remote code execution because it does not properly validate session IDs, as demonstrated by a ".." session-file forgery in the file session provider in file.go. This is related to session ID handling in the go-macaron/session code for Macaron.

[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2018-15193

2018-08-08T02:29:00

2025-02-19T02:30:59.632079

A CSRF vulnerability in the admin panel in Gogs through 0.11.53 allows remote attackers to execute admin operations via a crafted issue / link.

[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2018-15178

2018-08-08T00:29:02

2025-02-19T02:31:05.448124

Open redirect vulnerability in Gogs before 0.12 allows remote attackers to redirect users to arbitrary websites and conduct phishing attacks via an initial /\ substring in the user/login redirect_to parameter, related to the function isValidRedirect in routes/user/auth.go.

[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2018-17031

2018-09-14T02:29:00

2025-02-19T02:32:01.453419

In Gogs 0.11.53, an attacker can use a crafted .eml file to trigger MIME type sniffing, which leads to XSS, as demonstrated by Internet Explorer, because an "X-Content-Type-Options: nosniff" header is not sent.

[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2018-16409

2018-09-03T19:29:01

2025-02-19T02:31:38.356917

In Gogs 0.11.53, an attacker can use migrate to send arbitrary HTTP GET requests, leading to SSRF.

[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2018-20303

2018-12-20T00:29:00

2025-01-15T01:34:46.849824

In pkg/tool/path.go in Gogs before 0.11.82.1218, a directory traversal in the file-upload functionality can allow an attacker to create a file under data/sessions on the server, a similar issue to CVE-2018-18925.

[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2020-14958

2020-06-21T20:15:09

2025-01-15T01:43:12.862514

In Gogs 0.11.91, MakeEmailPrimary in models/user_mail.go lacks a "not the owner of the email" check.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2020-9329

2020-02-21T22:15:10

2025-02-19T03:14:08.649534

Gogs through 0.11.91 allows attackers to violate the admin-specified repo-creation policy due to an internal/db/repo.go race condition.

[ { "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2020-15867

2020-10-16T14:15:11

2025-02-19T03:08:54.037282

The git hook feature in Gogs 0.5.5 through 0.12.2 allows for authenticated remote code execution. There can be a privilege escalation if access to this hook feature is granted to a user who does not have administrative privileges. NOTE: because this is mentioned in the documentation but not in the UI, it could be considered a "Product UI does not Warn User of Unsafe Actions" issue.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/gogs/gogs

[]

[ "91441c3fb29d8ead645d8fffa4658d749d5b3fc3" ]

CVE-2019-9047

2019-02-23T21:29:00

2025-01-14T08:08:55.540826

GoRose v1.0.4 has SQL Injection when the order_by or group_by parameter can be controlled.

[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/gohouse/gorose

[]

[ "5aeebf3335499bae38b9292594d8c2e44d5a0b4f" ]

CVE-2024-1394

2024-03-21T13:00:08

2025-01-15T05:04:55.042523

A memory leak flaw was found in Golang in the RSA encrypting/decrypting code, which might lead to a resource exhaustion vulnerability using attacker-controlled inputs. The memory leak happens in github.com/golang-fips/openssl/openssl/rsa.go#L113. The objects leaked are pkey and ctx. That function uses named return parameters to free pkey and ctx if there is an error initializing the context or setting the different properties. All return statements related to error cases follow the "return nil, nil, fail(...)" pattern, meaning that pkey and ctx will be nil inside the deferred function that should free them.

null

https://github.com/golang-fips/openssl

[]

[ "576fe0d377882f8d0fd6537762ef2ff7918facc8" ]

CVE-2023-39533

2023-08-08T19:15:10

2025-01-15T04:57:45.053991

go-libp2p is the Go implementation of the libp2p Networking Stack. Prior to versions 0.27.8, 0.28.2, and 0.29.1 malicious peer can use large RSA keys to run a resource exhaustion attack & force a node to spend time doing signature verification of the large key. This vulnerability is present in the core/crypto module of go-libp2p and can occur during the Noise handshake and the libp2p x509 extension verification step. To prevent this attack, go-libp2p versions 0.27.8, 0.28.2, and 0.29.1 restrict RSA keys to <= 8192 bits. To protect one's application, it is necessary to update to these patch releases and to use the updated Go compiler in 1.20.7 or 1.19.12. There are no known workarounds for this issue.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]

https://github.com/golang/go

[]

[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]

CVE-2023-39321

2023-09-08T17:15:28

2025-01-14T11:53:51.569394

Processing an incomplete post-handshake message for a QUIC connection can cause a panic.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]

https://github.com/golang/go

[]

[ "c19c4c566c63818dfd059b352e52c4710eecf14d" ]

CVE-2023-39322

2023-09-08T17:15:28

2025-01-14T11:53:48.411384

QUIC connections do not set an upper bound on the amount of data buffered when reading post-handshake messages, allowing a malicious QUIC connection to cause unbounded memory growth. With fix, connections now consistently reject messages larger than 65KiB in size.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]

https://github.com/golang/go

[]

[ "c19c4c566c63818dfd059b352e52c4710eecf14d" ]

CVE-2023-39320

2023-09-08T17:15:27

2025-01-14T11:53:47.557953

The go.mod toolchain directive, introduced in Go 1.21, can be leveraged to execute scripts and binaries relative to the root of the module when the "go" command was executed within the module. This applies to modules downloaded using the "go" command from the module proxy, as well as modules downloaded directly using VCS software.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/golang/go

[]

[ "c19c4c566c63818dfd059b352e52c4710eecf14d" ]

CVE-2021-27919

2021-03-11T00:15:12

2025-01-14T09:03:21.246988

archive/zip in Go 1.16.x before 1.16.1 allows attackers to cause a denial of service (panic) upon attempted use of the Reader.Open API for a ZIP archive in which ../ occurs at the beginning of any filename.

[ { "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]

https://github.com/golang/go

[]

[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]

CVE-2021-41772

2021-11-08T06:15:08

2025-01-14T09:56:23.518683

Go before 1.16.10 and 1.17.x before 1.17.3 allows an archive/zip Reader.Open panic via a crafted ZIP archive containing an invalid name or an empty filename field.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]

https://github.com/golang/go

[]

[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]

CVE-2022-28327

2022-04-20T10:15:08

2025-01-14T10:54:26.847954

The generic P-256 feature in crypto/elliptic in Go before 1.17.9 and 1.18.x before 1.18.1 allows a panic via long scalar input.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]

https://github.com/golang/go

[]

[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]

CVE-2022-27536

2022-04-20T10:15:07

2025-01-14T10:55:46.776794

Certificate.Verify in crypto/x509 in Go 1.18.x before 1.18.1 can be caused to panic on macOS when presented with certain malformed certificates. This allows a remote TLS server to cause a TLS client to panic.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]

https://github.com/golang/go

[]

[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]

CVE-2022-24675

2022-04-20T10:15:07

2025-01-14T10:51:42.835696

encoding/pem in Go before 1.17.9 and 1.18.x before 1.18.1 has a Decode stack overflow via a large amount of PEM data.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]

https://github.com/golang/go

[]

[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]

CVE-2022-30634

2022-07-15T20:15:08

2025-01-14T10:58:38.836773

Infinite loop in Read in crypto/rand before Go 1.17.11 and Go 1.18.3 on Windows allows attacker to cause an indefinite hang by passing a buffer larger than 1 << 32 - 1 bytes.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]

https://github.com/golang/go

[]

[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]

CVE-2022-29804

2022-08-10T20:15:34

2025-01-14T10:57:48.849102

Incorrect conversion of certain invalid paths to valid, absolute paths in Clean in path/filepath before Go 1.17.11 and Go 1.18.3 on Windows allows potential directory traversal attack.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]

https://github.com/golang/go

[]

[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]

CVE-2022-30580

2022-08-10T20:15:40

2025-01-14T10:58:25.441009

Code injection in Cmd.Start in os/exec before Go 1.17.11 and Go 1.18.3 allows execution of any binaries in the working directory named either "..com" or "..exe" by calling Cmd.Run, Cmd.Start, Cmd.Output, or Cmd.CombinedOutput when Cmd.Path is unset.

[ { "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/golang/go

[]

[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]

CVE-2019-6486

2019-01-24T05:29:00

2025-01-15T01:41:55.132651

Go before 1.10.8 and 1.11.x before 1.11.5 mishandles P-521 and P-384 elliptic curves, which allows attackers to cause a denial of service (CPU consumption) or possibly conduct ECDH private key recovery attacks.

[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H", "type": "CVSS_V3" } ]

https://github.com/golang/go

[]

[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]

CVE-2019-9741

2019-03-13T08:29:00

2025-01-14T08:10:36.159298

An issue was discovered in net/http in Go 1.11.5. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the second argument to http.NewRequest with \r\n followed by an HTTP header or a Redis command.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]

https://github.com/golang/go

[]

[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]

CVE-2019-9634

2019-03-08T15:29:00

2025-01-14T08:11:30.629254

Go through 1.12 on Windows misuses certain LoadLibrary functionality, leading to DLL injection.

[ { "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/golang/go

[]

[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]

CVE-2019-14809

2019-08-13T21:15:11

2025-01-14T07:48:56.145100

net/url in Go before 1.11.13 and 1.12.x before 1.12.8 mishandles malformed hosts in URLs, leading to an authorization bypass in some applications. This is related to a Host field with a suffix appearing in neither Hostname() nor Port(), and is related to a non-numeric port number. For example, an attacker can compose a crafted javascript:// URL that results in a hostname of google.com.

[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/golang/go

[]

[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]

CVE-2019-16276

2019-09-30T19:15:08

2025-01-14T07:51:26.422181

Go before 1.12.10 and 1.13.x before 1.13.1 allow HTTP Request Smuggling.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "type": "CVSS_V3" } ]

https://github.com/golang/go

[]

[ "3a1b4e75f8b6c1b57db73bccf7ca871bf1a97ca9", "66330d8c6c0a23b7eb48688f9954264e48b039da" ]

CVE-2019-11888

2019-05-13T05:29:01

2025-01-14T07:10:42.302005

Go through 1.12.5 on Windows mishandles process creation with a nil environment in conjunction with a non-nil token, which allows attackers to obtain sensitive information or gain privileges.

[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/golang/go

[]

[ "3a1b4e75f8b6c1b57db73bccf7ca871bf1a97ca9", "66330d8c6c0a23b7eb48688f9954264e48b039da" ]

CVE-2019-17596

2019-10-24T22:15:10

2025-01-14T07:53:38.532590

Go before 1.12.11 and 1.3.x before 1.13.2 can panic upon an attempt to process network traffic containing an invalid DSA public key. There are several attack scenarios, such as traffic from a client to a server that verifies client certificates.

[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]

https://github.com/golang/go

[]

[ "3a1b4e75f8b6c1b57db73bccf7ca871bf1a97ca9" ]

CVE-2016-5386

2016-07-19T02:00:18

2025-01-14T06:37:36.349952

The net/http package in Go through 1.6 does not attempt to address RFC 3875 section 4.1.18 namespace conflicts and therefore does not protect CGI applications from the presence of untrusted client data in the HTTP_PROXY environment variable, which might allow remote attackers to redirect a CGI application's outbound HTTP traffic to an arbitrary proxy server via a crafted Proxy header in an HTTP request, aka an "httpoxy" issue.

[ { "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]

https://github.com/golang/go

[]

[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]