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-2016-3959
2016-05-23T19:59:04
2025-01-14T06:31:21.075963
The Verify function in crypto/dsa/dsa.go in Go before 1.5.4 and 1.6.x before 1.6.1 does not properly check parameters passed to the big integer library, which might allow remote attackers to cause a denial of service (infinite loop) via a crafted public key to a program that uses HTTPS client certificates or SSH server libraries.
[ { "score": "CVSS:3.0/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-2016-3958
2016-05-23T19:59:03
2025-01-14T06:31:56.452421
Untrusted search path vulnerability in Go before 1.5.4 and 1.6.x before 1.6.1 on Windows allows local users to gain privileges via a Trojan horse DLL in the current working directory, related to use of the LoadLibrary function.
[ { "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
[]
[ "27d5c0ede5b4411089f4bf52a41dd2f4eed36123" ]
CVE-2018-7187
2018-02-16T17:29:00
2025-01-14T07:37:45.503298
The "go get" implementation in Go 1.9.4, when the -insecure command-line option is used, does not validate the import path (get/vcs.go only checks for "://" anywhere in the string), which allows remote attackers to execute arbitrary OS commands via a crafted web site.
[ { "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/golang/go
[]
[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]
CVE-2018-6574
2018-02-07T21:29:00
2025-01-14T07:39:27.553897
Go before 1.8.7, Go 1.9.x before 1.9.4, and Go 1.10 pre-releases before Go 1.10rc2 allow "go get" remote command execution during source code build, by leveraging the gcc or clang plugin feature, because -fplugin= and -plugin= arguments were not blocked.
[ { "score": "CVSS:3.0/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-2018-16875
2018-12-14T14:29:00
2025-01-14T07:25:50.068474
The crypto/x509 package of Go before 1.10.6 and 1.11.x before 1.11.3 does not limit the amount of work performed for each chain verification, which might allow attackers to craft pathological inputs leading to a CPU denial of service. Go TLS servers accepting client certificates and TLS clients are affected.
[ { "score": "CVSS:3.0/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-2018-16873
2018-12-14T14:29:00
2025-01-14T07:25:40.581552
In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and the import path of a malicious Go package, or a package that imports it directly or indirectly. Specifically, it is only vulnerable in GOPATH mode, but not in module mode (the distinction is documented at https://golang.org/cmd/go/#hdr-Module_aware_go_get). Using custom domains, it's possible to arrange things so that a Git repository is cloned to a folder named ".git" by using a vanity import path that ends with "/.git". If the Git repository root contains a "HEAD" file, a "config" file, an "objects" directory, a "refs" directory, with some work to ensure the proper ordering of operations, "go get -u" can be tricked into considering the parent directory as a repository root, and running Git commands on it. That will use the "config" file in the original Git repository root for its configuration, and if that config file contains malicious commands, they will execute on the system running "go get -u".
[ { "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-2018-16874
2018-12-14T14:29:00
2025-01-14T07:25:42.774548
In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to directory traversal when executed with the import path of a malicious Go package which contains curly braces (both '{' and '}' characters). Specifically, it is only vulnerable in GOPATH mode, but not in module mode (the distinction is documented at https://golang.org/cmd/go/#hdr-Module_aware_go_get). The attacker can cause an arbitrary filesystem write, which can lead to code execution.
[ { "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-2020-0601
2020-01-14T23:15:30
2025-02-07T17:54:38.479343
A spoofing vulnerability exists in the way Windows CryptoAPI (Crypt32.dll) validates Elliptic Curve Cryptography (ECC) certificates.An attacker could exploit the vulnerability by using a spoofed code-signing certificate to sign a malicious executable, making it appear the file was from a trusted, legitimate source, aka 'Windows CryptoAPI Spoofing Vulnerability'.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N", "type": "CVSS_V3" } ]
https://github.com/golang/go
[]
[ "3a1b4e75f8b6c1b57db73bccf7ca871bf1a97ca9" ]
CVE-2020-7919
2020-03-16T21:15:12
2025-01-14T08:47:55.175185
Go before 1.12.16 and 1.13.x before 1.13.7 (and the crypto/cryptobyte package before 0.0.0-20200124225646-8b5121be2f68 for Go) allows attacks on clients (resulting in a panic) via a malformed X.509 certificate.
[ { "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-2020-14039
2020-07-17T16:15:11
2025-01-14T08:21:28.284256
In Go before 1.13.13 and 1.14.x before 1.14.5, Certificate.Verify may lack a check on the VerifyOptions.KeyUsages EKU requirements (if VerifyOptions.Roots equals nil and the installation is on Windows). Thus, X.509 certificate verification is incomplete.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N", "type": "CVSS_V3" } ]
https://github.com/golang/go
[]
[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]
CVE-2017-8932
2017-07-06T16:29:00
2025-01-15T01:30:25.836165
A bug in the standard library ScalarMult implementation of curve P-256 for amd64 architectures in Go before 1.7.6 and 1.8.x before 1.8.2 causes incorrect results to be generated for specific input points. An adaptive attack can be mounted to progressively extract the scalar input to ScalarMult by submitting crafted points and observing failures to the derive correct output. This leads to a full key recovery attack against static ECDH, as used in popular JWT libraries.
[ { "score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]
https://github.com/golang/go
[]
[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]
CVE-2017-15041
2017-10-05T21:29:00
2025-01-14T07:07:55.689666
Go before 1.8.4 and 1.9.x before 1.9.1 allows "go get" remote command execution. Using custom domains, it is possible to arrange things so that example.com/pkg1 points to a Subversion repository but example.com/pkg1/pkg2 points to a Git repository. If the Subversion repository includes a Git checkout in its pkg2 directory and some other work is done to ensure the proper ordering of operations, "go get" can be tricked into reusing this Git checkout for the fetch of code from pkg2. If the Subversion repository's Git checkout has malicious commands in .git/hooks/, they will execute on the system running "go get."
[ { "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
[]
[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]
CVE-2017-1000097
2017-10-05T01:29:03
2025-01-14T06:56:54.148595
On Darwin, user's trust preferences for root certificates were not honored. If the user had a root certificate loaded in their Keychain that was explicitly not trusted, a Go program would still verify a connection using that root certificate.
[ { "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
[]
[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]
CVE-2017-1000098
2017-10-05T01:29:03
2025-01-14T06:56:47.427670
The net/http package's Request.ParseMultipartForm method starts writing to temporary files once the request body size surpasses the given "maxMemory" limit. It was possible for an attacker to generate a multipart request crafted such that the server ran out of file descriptors.
[ { "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-2017-15042
2017-10-05T21:29:00
2025-01-14T07:07:51.081293
An unintended cleartext issue exists in Go before 1.8.4 and 1.9.x before 1.9.1. RFC 4954 requires that, during SMTP, the PLAIN auth scheme must only be used on network connections secured with TLS. The original implementation of smtp.PlainAuth in Go 1.0 enforced this requirement, and it was documented to do so. In 2013, upstream issue #5184, this was changed so that the server may decide whether PLAIN is acceptable. The result is that if you set up a man-in-the-middle SMTP server that doesn't advertise STARTTLS and does advertise that PLAIN auth is OK, the smtp.PlainAuth implementation sends the username and password.
[ { "score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]
https://github.com/golang/go
[]
[ "66330d8c6c0a23b7eb48688f9954264e48b039da" ]
CVE-2021-22538
2021-03-31T21:15:16
2025-01-15T01:47:51.716877
A privilege escalation vulnerability impacting the Google Exposure Notification Verification Server (versions prior to 0.23.1), allows an attacker who (1) has UserWrite permissions and (2) is using a carefully crafted request or malicious proxy, to create another user with higher privileges than their own. This occurs due to insufficient checks on the allowed set of permissions. The new user creation event would be captured in the Event Log.
[ { "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/google/exposure-notifications-verification-server
[]
[ "f2b04559ca6e195a2561487d0b35b997e66d152c" ]
CVE-2021-22565
2021-12-09T13:15:08
2025-01-14T08:55:10.100656
An attacker could prematurely expire a verification code, making it unusable by the patient, making the patient unable to upload their TEKs to generate exposure notifications. We recommend upgrading the Exposure Notification server to V1.1.2 or greater.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L", "type": "CVSS_V3" } ]
https://github.com/google/exposure-notifications-verification-server
[]
[ "f2b04559ca6e195a2561487d0b35b997e66d152c" ]
CVE-2020-35864
2020-12-31T10:15:15
2025-02-19T03:11:47.195063
An issue was discovered in the flatbuffers crate through 2020-04-11 for Rust. read_scalar (and read_scalar_at) can transmute values without unsafe blocks.
[ { "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/google/flatbuffers
[]
[ "6df40a2471737b27271bdd9b900ab5f3aec746c7" ]
CVE-2020-8918
2020-08-11T19:15:17
2025-01-14T08:50:27.943695
An improperly initialized 'migrationAuth' value in Google's go-tpm TPM1.2 library versions prior to 0.3.0 can lead an eavesdropping attacker to discover the auth value for a key created with CreateWrapKey. An attacker listening in on the channel can collect both 'encUsageAuth' and 'encMigrationAuth', and then can calculate 'usageAuth ^ encMigrationAuth' as the 'migrationAuth' can be guessed for all keys created with CreateWrapKey. TPM2.0 is not impacted by this. We recommend updating your library to 0.3.0 or later, or, if you cannot update, to call CreateWrapKey with a random 20-byte value for 'migrationAuth'.
[ { "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N", "type": "CVSS_V3" } ]
https://github.com/google/go-tpm
[]
[ "b2c8857856f7516bb35d299c6b5d19f64e4ad579" ]
CVE-2022-31055
2022-06-13T16:15:08
2025-01-15T02:21:26.494878
kCTF is a Kubernetes-based infrastructure for capture the flag (CTF) competitions. Prior to version 1.6.0, the kctf cluster set-src-ip-ranges was broken and allowed traffic from any IP. The problem has been patched in v1.6.0. As a workaround, those who want to test challenges privately can mark them as `public: false` and use `kctf chal debug port-forward` to connect.
[ { "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/google/kctf
[]
[ "9d1f2a5f86e9a7c66805b090829c330b0abf71d1" ]
CVE-2020-8929
2020-10-19T13:15:13
2025-01-15T01:47:10.654131
A mis-handling of invalid unicode characters in the Java implementation of Tink versions prior to 1.5 allows an attacker to change the ID part of a ciphertext, which result in the creation of a second ciphertext that can decrypt to the same plaintext. This can be a problem with encrypting deterministic AEAD with a single key, and rely on a unique ciphertext-per-plaintext.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N", "type": "CVSS_V3" } ]
https://github.com/google/tink
[]
[ "693d0e143c3d61cb2976883c6b9261d1b4f0263c" ]
CVE-2023-30845
2023-04-26T21:15:09
2025-01-15T04:51:49.691413
ESPv2 is a service proxy that provides API management capabilities using Google Service Infrastructure. ESPv2 2.20.0 through 2.42.0 contains an authentication bypass vulnerability. API clients can craft a malicious `X-HTTP-Method-Override` header value to bypass JWT authentication in specific cases. ESPv2 allows malicious requests to bypass authentication if both the conditions are true: The requested HTTP method is **not** in the API service definition (OpenAPI spec or gRPC `google.api.http` proto annotations, and the specified `X-HTTP-Method-Override` is a valid HTTP method in the API service definition. ESPv2 will forward the request to your backend without checking the JWT. Attackers can craft requests with a malicious `X-HTTP-Method-Override` value that allows them to bypass specifying JWTs. Restricting API access with API keys works as intended and is not affected by this vulnerability. Upgrade deployments to release v2.43.0 or higher to receive a patch. This release ensures that JWT authentication occurs, even when the caller specifies `x-http-method-override`. `x-http-method-override` is still supported by v2.43.0+. API clients can continue sending this header to ESPv2.
[ { "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/googlecloudplatform/esp-v2
[]
[ "d75445e1f30244a5c6690196d338c44a29abe55a" ]
CVE-2023-27475
2023-03-07T18:15:09
2025-01-15T04:48:15.916132
Goutil is a collection of miscellaneous functionality for the go language. In versions prior to 0.6.0 when users use fsutil.Unzip to unzip zip files from a malicious attacker, they may be vulnerable to path traversal. This vulnerability is known as a ZipSlip. This issue has been fixed in version 0.6.0, users are advised to upgrade. There are no known workarounds for this issue.
[ { "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/gookit/goutil
[]
[ "7526dca133db0dff4a50bf8bea42cf13ad702bca" ]
CVE-2022-45003
2023-03-22T21:15:17
2025-02-19T03:28:30.038815
Gophish through 0.12.1 allows attackers to cause a Denial of Service (DoS) via a crafted payload involving autofocus.
[ { "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/gophish/gophish
[]
[ "f95e9554c7cefd8bd0e772af8a19436090311e8c" ]
CVE-2022-45004
2023-03-22T21:15:18
2025-02-19T03:28:32.303791
Gophish through 0.12.1 was discovered to contain a cross-site scripting (XSS) vulnerability via a crafted landing page.
[ { "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/gophish/gophish
[]
[ "f95e9554c7cefd8bd0e772af8a19436090311e8c" ]
CVE-2022-25295
2022-09-11T14:15:08
2025-02-19T03:23:19.120577
This affects the package github.com/gophish/gophish before 0.12.0. The Open Redirect vulnerability exists in the next query parameter. The application uses url.Parse(r.FormValue("next")) to extract path and eventually redirect user to a relative URL, but if next parameter starts with multiple backslashes like \\\\\\example.com, browser will redirect user to http://example.com.
[ { "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/gophish/gophish
[]
[ "f95e9554c7cefd8bd0e772af8a19436090311e8c" ]
CVE-2019-16146
2019-09-09T13:15:11
2025-01-14T07:47:26.595339
Gophish through 0.8.0 allows XSS via a username.
[ { "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/gophish/gophish
[]
[ "f95e9554c7cefd8bd0e772af8a19436090311e8c" ]
CVE-2020-24710
2020-10-28T20:15:13
2025-01-15T01:44:23.880965
Gophish before 0.11.0 allows SSRF attacks.
[ { "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/gophish/gophish
[]
[ "f95e9554c7cefd8bd0e772af8a19436090311e8c" ]
CVE-2020-24712
2020-10-28T20:15:13
2025-01-15T01:44:22.608739
Cross Site Scripting (XSS) vulnerability in Gophish before 0.11.0 via the IMAP Host field on the account settings page.
[ { "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/gophish/gophish
[]
[ "f95e9554c7cefd8bd0e772af8a19436090311e8c" ]
CVE-2020-24711
2020-10-28T20:15:13
2025-01-15T01:44:24.551897
The Reset button on the Account Settings page in Gophish before 0.11.0 allows attackers to cause a denial of service via a clickjacking attack
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]
https://github.com/gophish/gophish
[]
[ "f95e9554c7cefd8bd0e772af8a19436090311e8c" ]
CVE-2020-24707
2020-10-28T20:15:13
2025-01-15T01:44:25.548270
Gophish before 0.11.0 allows the creation of CSV sheets that contain malicious content.
[ { "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/gophish/gophish
[]
[ "f95e9554c7cefd8bd0e772af8a19436090311e8c" ]
CVE-2020-24713
2020-10-28T20:15:13
2025-02-19T03:11:59.039474
Gophish through 0.10.1 does not invalidate the gophish cookie upon logout.
[ { "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/gophish/gophish
[]
[ "f95e9554c7cefd8bd0e772af8a19436090311e8c" ]
CVE-2020-24708
2020-10-28T20:15:13
2025-01-15T01:44:24.785912
Cross Site Scripting (XSS) vulnerability in Gophish before 0.11.0 via the Host field on the send profile form.
[ { "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/gophish/gophish
[]
[ "f95e9554c7cefd8bd0e772af8a19436090311e8c" ]
CVE-2020-24709
2020-10-28T20:15:13
2025-02-19T03:12:00.951083
Cross Site Scripting (XSS) vulnerability in Gophish through 0.10.1 via a crafted landing page or email template.
[ { "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/gophish/gophish
[]
[ "f95e9554c7cefd8bd0e772af8a19436090311e8c" ]
CVE-2024-23840
2024-01-30T17:15:11
2025-01-15T05:08:25.654051
GoReleaser builds Go binaries for several platforms, creates a GitHub release and then pushes a Homebrew formula to a tap repository. `goreleaser release --debug` log shows secret values used in the in the custom publisher. This vulnerability is fixed in 1.24.0.
[ { "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]
https://github.com/goreleaser/goreleaser
[]
[ "3ec68fbf8c3a1b16ca0f69aeccfb93765685b643" ]
CVE-2023-32698
2023-05-30T04:15:10
2025-01-15T04:53:22.799015
nFPM is an alternative to fpm. The file permissions on the checked-in files were not maintained. Hence, when nfpm packaged the files (without extra config for enforcing it’s own permissions) files could go out with bad permissions (chmod 666 or 777). Anyone using nfpm for creating packages without checking/setting file permissions before packaging could result in bad permissions for files/folders.
[ { "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N", "type": "CVSS_V3" } ]
https://github.com/goreleaser/nfpm
[]
[ "3f9527977cc5dee860fab221e23e2290063c3045" ]
CVE-2020-27813
2020-12-02T01:15:12
2025-01-14T08:42:08.392762
An integer overflow vulnerability exists with the length of websocket frames received via a websocket connection. An attacker would use this flaw to cause a denial of service attack on an HTTP Server allowing websocket connections.
[ { "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/gorilla/websocket
[]
[ "66b9c49e59c6c48f0ffce28c2d8b8a5678502c6d" ]
CVE-2024-21527
2024-07-19T05:15:10
2025-01-15T05:06:19.465869
Versions of the package github.com/gotenberg/gotenberg/v8/pkg/gotenberg before 8.1.0; versions of the package github.com/gotenberg/gotenberg/v8/pkg/modules/chromium before 8.1.0; versions of the package github.com/gotenberg/gotenberg/v8/pkg/modules/webhook before 8.1.0 are vulnerable to Server-side Request Forgery (SSRF) via the /convert/html endpoint when a request is made to a file via localhost, such as <iframe src="\\localhost/etc/passwd">. By exploiting this vulnerability, an attacker can achieve local file inclusion, allowing of sensitive files read on the host system. Workaround An alternative is using either or both --chromium-deny-list and --chromium-allow-list flags.
null
https://github.com/gotenberg/gotenberg
[]
[ "3472d42cddcf439226c477c0180fab6d34f86fc3" ]
CVE-2022-46181
2022-12-29T19:15:08
2025-01-14T11:15:56.590483
Gotify server is a simple server for sending and receiving messages in real-time per WebSocket. Versions prior to 2.2.2 contain an XSS vulnerability that allows authenticated users to upload .html files. An attacker could execute client side scripts **if** another user opened a link. The attacker could potentially take over the account of the user that clicked the link. The Gotify UI won't natively expose such a malicious link, so an attacker has to get the user to open the malicious link in a context outside of Gotify. The vulnerability has been fixed in version 2.2.2. As a workaround, you can block access to non image files via a reverse proxy in the `./image` directory.
[ { "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/gotify/server
[]
[ "022603ddf92d43d23dd3f70ad263591e24defda5" ]
CVE-2024-8572
2024-09-08T08:15:13
2024-10-08T04:25:42.678140
A vulnerability was found in Gouniverse GoLang CMS 1.4.0. It has been declared as problematic. This vulnerability affects the function PageRenderHtmlByAlias of the file FrontendHandler.go. The manipulation of the argument alias leads to cross site scripting. The attack can be initiated remotely. Upgrading to version 1.4.1 is able to address this issue. The patch is identified as 3e661cdfb4beeb9fe2ad507cdb8104c0b17d072c. It is recommended to upgrade the affected component.
[ { "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/gouniverse/cms
[]
[ "fd264b105c3fb062c9601092f68a6e1babc97a10" ]
CVE-2024-8996
2024-09-25T17:15:19
2025-02-19T03:39:04.915538
Unquoted Search Path or Element vulnerability in Grafana Agent (Flow mode) on Windows allows Privilege Escalation from Local User to SYSTEM This issue affects Agent Flow: before 0.43.2
[ { "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/grafana/agent
[]
[ "cd07588d52a3a47a651f523618d2e193bc76338f" ]
CVE-2021-41090
2021-12-08T17:15:11
2025-01-15T02:04:37.143317
Grafana Agent is a telemetry collector for sending metrics, logs, and trace data to the opinionated Grafana observability stack. Prior to versions 0.20.1 and 0.21.2, inline secrets defined within a metrics instance config are exposed in plaintext over two endpoints: metrics instance configs defined in the base YAML file are exposed at `/-/config` and metrics instance configs defined for the scraping service are exposed at `/agent/api/v1/configs/:key`. Inline secrets will be exposed to anyone being able to reach these endpoints. If HTTPS with client authentication is not configured, these endpoints are accessible to unauthenticated users. Secrets found in these sections are used for delivering metrics to a Prometheus Remote Write system, authenticating against a system for discovering Prometheus targets, and authenticating against a system for collecting metrics. This does not apply for non-inlined secrets, such as `*_file` based secrets. This issue is patched in Grafana Agent versions 0.20.1 and 0.21.2. A few workarounds are available. Users who cannot upgrade should use non-inline secrets where possible. Users may also desire to restrict API access to Grafana Agent with some combination of restricting the network interfaces Grafana Agent listens on through `http_listen_address` in the `server` block, configuring Grafana Agent to use HTTPS with client authentication, and/or using firewall rules to restrict external access to Grafana Agent's API.
[ { "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/grafana/agent
[]
[ "cd07588d52a3a47a651f523618d2e193bc76338f" ]
CVE-2024-8975
2024-09-25T17:15:19
2025-01-14T12:17:48.861248
Unquoted Search Path or Element vulnerability in Grafana Alloy on Windows allows Privilege Escalation from Local User to SYSTEM This issue affects Alloy: before 1.3.3, from 1.4.0-rc.0 through 1.4.0-rc.1.
[ { "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/grafana/alloy
[]
[ "8ce3a6d3b7bcf071e48198bed9c5d0cac0c68790" ]
CVE-2023-4457
2023-10-16T10:15:12
2025-01-14T12:00:29.430098
Grafana is an open-source platform for monitoring and observability. The Google Sheets data source plugin for Grafana, versions 0.9.0 to 1.2.2 are vulnerable to an information disclosure vulnerability. The plugin did not properly sanitize error messages, making it potentially expose the Google Sheet API-key that is configured for the data source. This vulnerability was fixed in version 1.2.2.
[ { "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/grafana/google-sheets-datasource
[]
[ "af0624499d61f934f39998db65be093df1edf9d9" ]
CVE-2021-36156
2021-08-03T15:15:08
2025-01-14T09:20:32.196811
An issue was discovered in Grafana Loki through 2.2.1. The header value X-Scope-OrgID is used to construct file paths for rules files, and if crafted to conduct directory traversal such as ae ../../sensitive/path/in/deployment pathname, then Loki will attempt to parse a rules file at that location and include some of the contents in the error message.
[ { "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/grafana/loki
[]
[ "babea82ef558c4b4dc685fd4ca677de1f0a7ee8f" ]
CVE-2022-46156
2022-11-30T22:15:10
2025-01-15T04:01:21.857312
The Synthetic Monitoring Agent for Grafana's Synthetic Monitoring application provides probe functionality and executes network checks for monitoring remote targets. Users running the Synthetic Monitoring agent prior to version 0.12.0 in their local network are impacted. The authentication token used to communicate with the Synthetic Monitoring API is exposed through a debugging endpoint. This token can be used to retrieve the Synthetic Monitoring checks created by the user and assigned to the agent identified with that token. The Synthetic Monitoring API will reject connections from already-connected agents, so access to the token does not guarantee access to the checks. Version 0.12.0 contains a fix. Users are advised to rotate the agent tokens. After upgrading to version v0.12.0 or later, it's recommended that users of distribution packages review the configuration stored in `/etc/synthetic-monitoring/synthetic-monitoring-agent.conf`, specifically the `API_TOKEN` variable which has been renamed to `SM_AGENT_API_TOKEN`. As a workaround for previous versions, it's recommended that users review the agent settings and set the HTTP listening address in a manner that limits the exposure, for example, localhost or a non-routed network, by using the command line parameter `-listen-address`, e.g. `-listen-address localhost:4050`.
[ { "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N", "type": "CVSS_V3" } ]
https://github.com/grafana/synthetic-monitoring-agent
[]
[ "2c4c0edb365f002472292b4b60260b2f974cb23c" ]
CVE-2021-41393
2021-09-18T16:15:07
2025-02-19T03:24:45.985924
Teleport before 4.4.11, 5.x before 5.2.4, 6.x before 6.2.12, and 7.x before 7.1.1 allows forgery of SSH host certificates in some situations.
[ { "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/gravitational/teleport
[]
[ "4f53e33e61cd069c329f2a0c8b98415b0c6dfda1" ]
CVE-2021-41395
2021-09-18T16:15:07
2025-02-19T03:24:36.371398
Teleport before 6.2.12 and 7.x before 7.1.1 allows attackers to control a database connection string, in some situations, via a crafted database name or username.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N", "type": "CVSS_V3" } ]
https://github.com/gravitational/teleport
[]
[ "ba028927b1ad0529350d3d31b5762642e103dd39" ]
CVE-2021-41394
2021-09-18T16:15:07
2025-02-19T03:24:27.652504
Teleport before 4.4.11, 5.x before 5.2.4, 6.x before 6.2.12, and 7.x before 7.1.1 allows alteration of build artifacts in some situations.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N", "type": "CVSS_V3" } ]
https://github.com/gravitational/teleport
[]
[ "4f53e33e61cd069c329f2a0c8b98415b0c6dfda1" ]
CVE-2022-36633
2022-08-24T13:15:08
2025-01-14T11:06:29.100432
Teleport 9.3.6 is vulnerable to Command injection leading to Remote Code Execution. An attacker can craft a malicious ssh agent installation link by URL encoding a bash escape with carriage return line feed. This url encoded payload can be used in place of a token and sent to a user in a social engineering attack. This is fully unauthenticated attack utilizing the trusted teleport server to deliver the payload.
[ { "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/gravitational/teleport
[]
[ "4f53e33e61cd069c329f2a0c8b98415b0c6dfda1" ]
CVE-2022-38599
2022-12-08T17:15:10
2025-01-14T11:10:40.213129
Teleport v3.2.2, Teleport v3.5.6-rc6, and Teleport v3.6.3-b2 was discovered to contain an information leak via the /user/get-role-list web interface.
[ { "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/gravitational/teleport
[]
[ "4f53e33e61cd069c329f2a0c8b98415b0c6dfda1" ]
CVE-2023-32078
2023-08-24T22:15:10
2025-01-15T04:53:20.307202
Netmaker makes networks with WireGuard. An Insecure Direct Object Reference (IDOR) vulnerability was found in versions prior to 0.17.1 and 0.18.6 in the user update function. By specifying another user's username, it was possible to update the other user's password. The issue is patched in 0.17.1 and fixed in 0.18.6. If Users are using 0.17.1, they should run `docker pull gravitl/netmaker:v0.17.1` and `docker-compose up -d`. This will switch them to the patched users. If users are using v0.18.0-0.18.5, they should upgrade to v0.18.6 or later. As a workaround, someone using version 0.17.1 can pull the latest docker image of the backend and restart the server.
[ { "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/gravitl/netmaker
[]
[ "af1067c453e1dd6a14866696c49a282c7c327921" ]
CVE-2023-32079
2023-08-24T23:15:08
2025-02-19T03:32:43.291309
Netmaker makes networks with WireGuard. A Mass assignment vulnerability was found in versions prior to 0.17.1 and 0.18.6 that allows a non-admin user to escalate privileges to those of an admin user. The issue is patched in 0.17.1 and fixed in 0.18.6. If Users are using 0.17.1, they should run `docker pull gravitl/netmaker:v0.17.1` and `docker-compose up -d`. This will switch them to the patched users If users are using v0.18.0-0.18.5, they should upgrade to v0.18.6 or later. As a workaround, someone using version 0.17.1 can pull the latest docker image of the backend and restart the server.
[ { "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/gravitl/netmaker
[]
[ "af1067c453e1dd6a14866696c49a282c7c327921" ]
CVE-2023-32077
2023-08-24T22:15:08
2025-01-15T04:53:42.181635
Netmaker makes networks with WireGuard. Prior to versions 0.17.1 and 0.18.6, hardcoded DNS key usage has been found in Netmaker allowing unauth users to interact with DNS API endpoints. The issue is patched in 0.17.1 and fixed in 0.18.6. If users are using 0.17.1, they should run `docker pull gravitl/netmaker:v0.17.1` and `docker-compose up -d`. This will switch them to the patched users. If users are using v0.18.0-0.18.5, they should upgrade to v0.18.6 or later. As a workaround, someone who is using version 0.17.1 can pull the latest docker image of the backend and restart the server.
[ { "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/gravitl/netmaker
[]
[ "af1067c453e1dd6a14866696c49a282c7c327921" ]
CVE-2022-36110
2022-09-09T20:15:11
2025-02-19T03:28:43.664761
Netmaker makes networks with WireGuard. Prior to version 0.15.1, Improper Authorization functions lead to non-privileged users running privileged API calls. If someone adds users to the Netmaker platform who do not have admin privileges, they can use their auth tokens to run admin-level functions via the API. This problem has been patched in v0.15.1.
[ { "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/gravitl/netmaker
[]
[ "af1067c453e1dd6a14866696c49a282c7c327921" ]
CVE-2022-23650
2022-02-18T22:15:13
2025-01-15T02:18:45.455178
Netmaker is a platform for creating and managing virtual overlay networks using WireGuard. Prior to versions 0.8.5, 0.9.4, and 010.0, there is a hard-coded cryptographic key in the code base which can be exploited to run admin commands on a remote server if the exploiter know the address and username of the admin. This effects the server (netmaker) component, and not clients. This has been patched in Netmaker v0.8.5, v0.9.4, and v0.10.0. There are currently no known workarounds.
[ { "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/gravitl/netmaker
[]
[ "af1067c453e1dd6a14866696c49a282c7c327921" ]
CVE-2022-0664
2022-02-18T14:15:07
2025-01-15T02:12:49.826464
Use of Hard-coded Cryptographic Key in Go github.com/gravitl/netmaker prior to 0.8.5,0.9.4,0.10.0,0.10.1.
[ { "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/gravitl/netmaker
[]
[ "af1067c453e1dd6a14866696c49a282c7c327921" ]
CVE-2023-52430
2024-02-12T23:15:08
2025-02-19T03:35:00.127958
The caddy-security plugin 1.1.20 for Caddy allows reflected XSS via a GET request to a URL that contains an XSS payload and begins with either a /admin or /settings/mfa/delete/ substring.
[ { "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/greenpau/caddy-security
[]
[ "98bdd6b04a6af2a7d2d8198f21dd28cbb951dbb2" ]
CVE-2024-21495
2024-02-17T05:15:09
2025-01-15T05:05:47.231625
Versions of the package github.com/greenpau/caddy-security before 1.0.42 are vulnerable to Insecure Randomness due to using an insecure random number generation library which could possibly be predicted via a brute-force search. Attackers could use the potentially predictable nonce value used for authentication purposes in the OAuth flow to conduct OAuth replay attacks. In addition, insecure randomness is used while generating multifactor authentication (MFA) secrets and creating API keys in the database package.
null
https://github.com/greenpau/go-authcrunch
[]
[ "50f3edc60f01348d580c769761097734f4f0527e" ]
CVE-2023-1428
2023-06-09T11:15:09
2025-02-19T03:31:06.869957
There exists an vulnerability causing an abort() to be called in gRPC.  The following headers cause gRPC's C++ implementation to abort() when called via http2: te: x (x != trailers) :scheme: x (x != http, https) grpclb_client_stats: x (x == anything) On top of sending one of those headers, a later header must be sent that gets the total header size past 8KB. We recommend upgrading past git commit 2485fa94bd8a723e5c977d55a3ce10b301b437f8 or v1.53 and above.
[ { "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/grpc/grpc
[]
[ "fe494ff4104b6f6a78117ab2da71d29c93053267" ]
CVE-2020-7768
2020-11-11T11:15:10
2025-02-19T03:16:26.836724
The package grpc before 1.24.4; the package @grpc/grpc-js before 1.1.8 are vulnerable to Prototype Pollution via loadPackageDefinition.
[ { "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/grpc/grpc
[]
[ "fe494ff4104b6f6a78117ab2da71d29c93053267" ]
CVE-2023-24623
2023-01-30T05:15:10
2025-01-15T04:43:55.976664
Paranoidhttp before 0.3.0 allows SSRF because [::] is equivalent to the 127.0.0.1 address, but does not match the filter for private addresses.
[ { "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/hakobe/paranoidhttp
[]
[ "a5a8577d76f0b1a4f76f7e1bfef66c876eefb15e" ]
CVE-2023-37475
2023-07-17T17:15:10
2025-01-15T04:55:45.846126
Hamba avro is a go lang encoder/decoder implementation of the avro codec specification. In affected versions a well-crafted string passed to avro's `github.com/hamba/avro/v2.Unmarshal()` can throw a `fatal error: runtime: out of memory` which is unrecoverable and can cause denial of service of the consumer of avro. The root cause of the issue is that avro uses part of the input to `Unmarshal()` to determine the size when creating a new slice and hence an attacker may consume arbitrary amounts of memory which in turn may cause the application to crash. This issue has been addressed in commit `b4a402f4` which has been included in release version `2.13.0`. Users are advised to upgrade. There are no known workarounds for this vulnerability.
[ { "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/hamba/avro
[]
[ "3abfe1e6382c5dccf2e1a00260c51a64bc1f1ca1" ]
CVE-2024-1052
2024-02-05T21:15:11
2025-02-19T03:36:24.938877
Boundary and Boundary Enterprise (“Boundary”) is vulnerable to session hijacking through TLS certificate tampering. An attacker with privileges to enumerate active or pending sessions, obtain a private key pertaining to a session, and obtain a valid trust on first use (TOFU) token may craft a TLS certificate to hijack an active session and gain access to the underlying service or application.
[ { "score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/hashicorp/boundary
[]
[ "ad9a47a7f937581edf4fd1edea3332d55d243a01" ]
CVE-2023-0690
2023-02-08T19:15:11
2025-02-19T03:30:36.609169
HashiCorp Boundary from 0.10.0 through 0.11.2 contain an issue where when using a PKI-based worker with a Key Management Service (KMS) defined in the configuration file, new credentials created after an automatic rotation may not have been encrypted via the intended KMS. This would result in the credentials being stored in plaintext on the Boundary PKI worker’s disk. This issue is fixed in version 0.12.0.
[ { "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N", "type": "CVSS_V3" } ]
https://github.com/hashicorp/boundary
[]
[ "ad9a47a7f937581edf4fd1edea3332d55d243a01" ]
CVE-2022-36130
2022-09-01T02:15:07
2025-02-19T03:28:15.849548
HashiCorp Boundary up to 0.10.1 did not properly perform data integrity checks to ensure the resources were associated with the correct scopes, allowing potential privilege escalation for authorized users of another scope. Fixed in Boundary 0.10.2.
[ { "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/hashicorp/boundary
[]
[ "ad9a47a7f937581edf4fd1edea3332d55d243a01" ]
CVE-2022-36182
2022-10-27T13:15:10
2025-02-19T03:28:14.862097
Hashicorp Boundary v0.8.0 is vulnerable to Clickjacking which allow for the interception of login credentials, re-direction of users to malicious sites, or causing users to perform malicious actions on the site.
[ { "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/hashicorp/boundary
[]
[ "ad9a47a7f937581edf4fd1edea3332d55d243a01" ]
CVE-2022-38149
2022-08-17T15:15:08
2025-02-19T03:29:34.244437
HashiCorp Consul Template up to 0.27.2, 0.28.2, and 0.29.1 may expose the contents of Vault secrets in the error returned by the *template.Template.Execute method, when given a template using Vault secret contents incorrectly. Fixed in 0.27.3, 0.28.3, and 0.29.2.
[ { "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/hashicorp/consul-template
[]
[ "4525703f9dd1347a38446e137d56de94dcd06ee7" ]
CVE-2022-29810
2022-04-27T06:15:40
2025-01-15T02:20:31.016008
The Hashicorp go-getter library before 1.5.11 does not redact an SSH key from a URL query parameter.
[ { "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]
https://github.com/hashicorp/go-getter
[]
[ "23702d0c00e2ee7ad769ac9956c0f2d22b6cd983" ]
CVE-2021-30476
2021-04-22T17:15:07
2025-02-19T03:18:15.079534
HashiCorp Terraform’s Vault Provider (terraform-provider-vault) did not correctly configure GCE-type bound labels for Vault’s GCP auth method. Fixed in 2.19.1.
[ { "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/hashicorp/terraform-provider-vault
[]
[ "93cac347e234e52b7edf008deaa752e2043735c9" ]
CVE-2023-5834
2023-10-27T22:15:09
2025-01-14T12:08:31.226207
HashiCorp Vagrant's Windows installer targeted a custom location with a non-protected path that could be junctioned, introducing potential for unauthorized file system writes. Fixed in Vagrant 2.4.0.
[ { "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/hashicorp/vagrant
[]
[ "ee2f0e2a705288bfeef33a0a3432b2e0c4cb8a7b" ]
CVE-2022-42717
2022-10-11T23:15:10
2025-01-14T11:12:51.289638
An issue was discovered in Hashicorp Packer before 2.3.1. The recommended sudoers configuration for Vagrant on Linux is insecure. If the host has been configured according to this documentation, non-privileged users on the host can leverage a wildcard in the sudoers configuration to execute arbitrary commands as root.
[ { "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/hashicorp/vagrant
[]
[ "ee2f0e2a705288bfeef33a0a3432b2e0c4cb8a7b" ]
CVE-2020-24359
2020-08-20T17:15:10
2025-01-14T08:38:55.997981
HashiCorp vault-ssh-helper up to and including version 0.1.6 incorrectly accepted Vault-issued SSH OTPs for the subnet in which a host's network interface was located, rather than the specific IP address assigned to that interface. Fixed in 0.2.0.
[ { "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/hashicorp/vault-ssh-helper
[]
[ "299268b7e4608481c62b073e0126b4d6f92174eb" ]
CVE-2023-27588
2023-03-14T18:15:10
2025-01-15T05:00:53.983472
Hasura is an open-source product that provides users GraphQL or REST APIs. A path traversal vulnerability has been discovered within Hasura GraphQL Engine prior to versions 1.3.4, 2.55.1, 2.20.1, and 2.21.0-beta1. Projects running on Hasura Cloud were not vulnerable. Self-hosted Hasura Projects with deployments that are publicly exposed and not protected by a WAF or other HTTP protection layer should be upgraded to version 1.3.4, 2.55.1, 2.20.1, or 2.21.0-beta1 to receive a patch.
[ { "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/hasura/graphql-engine
[]
[ "e7e4f480d519171a694a5c8d2541bd6b642beaa7" ]
CVE-2022-46792
2022-12-08T06:15:08
2025-01-14T11:28:28.964054
Hasura GraphQL Engine before 2.15.2 mishandles row-level authorization in the Update Many API for Postgres backends. The fixed versions are 2.10.2, 2.11.3, 2.12.1, 2.13.2, 2.14.1, and 2.15.2. (Versions before 2.10.0 are unaffected.)
[ { "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/hasura/graphql-engine
[]
[ "d490b0ad7c988b71cc90656a495345f2aaed21ea" ]
CVE-2019-1020015
2019-07-29T13:15:12
2025-01-15T01:48:50.040049
graphql-engine (aka Hasura GraphQL Engine) before 1.0.0-beta.3 mishandles the audience check while verifying JWT.
[ { "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/hasura/graphql-engine
[]
[ "e7e4f480d519171a694a5c8d2541bd6b642beaa7" ]
CVE-2020-10763
2020-11-24T17:15:10
2025-01-14T08:13:18.380653
An information-disclosure flaw was found in the way Heketi before 10.1.0 logs sensitive information. This flaw allows an attacker with local access to the Heketi server to read potentially sensitive information such as gluster-block passwords.
[ { "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]
https://github.com/heketi/heketi
[]
[ "e0ec337aa22a2ddbd89a5e2338280f621c371755" ]
CVE-2017-15104
2017-12-18T19:29:00
2025-01-14T07:06:31.865397
An access flaw was found in Heketi 5, where the heketi.json configuration file was world readable. An attacker having local access to the Heketi server could read plain-text passwords from the heketi.json file.
[ { "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/heketi/heketi
[]
[ "e0ec337aa22a2ddbd89a5e2338280f621c371755" ]
CVE-2017-15103
2017-12-18T19:29:00
2025-01-14T07:06:32.438322
A security-check flaw was found in the way the Heketi 5 server API handled user requests. An authenticated Heketi user could send specially crafted requests to the Heketi server, resulting in remote command execution as the user running Heketi server and possibly privilege escalation.
[ { "score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/heketi/heketi
[]
[ "e0ec337aa22a2ddbd89a5e2338280f621c371755" ]
CVE-2023-23314
2023-01-23T05:15:18
2025-01-14T11:32:11.409694
An arbitrary file upload vulnerability in the /api/upload component of zdir v3.2.0 allows attackers to execute arbitrary code via a crafted .ssh file.
[ { "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/helloxz/zdir
[]
[ "5d60295193fff9f27199a421c98d55aafcf065fa" ]
CVE-2022-2321
2022-07-05T19:15:07
2025-01-15T02:15:22.649225
Improper Restriction of Excessive Authentication Attempts in GitHub repository heroiclabs/nakama prior to 3.13.0. This results in login brute-force attacks.
[ { "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/heroiclabs/nakama
[]
[ "f5e935d682ea903f48f1c7a3dc27141b77304358" ]
CVE-2022-2306
2022-07-05T09:15:08
2025-01-15T02:15:21.284452
Old session tokens can be used to authenticate to the application and send authenticated requests.
[ { "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/heroiclabs/nakama
[]
[ "f5e935d682ea903f48f1c7a3dc27141b77304358" ]
CVE-2020-36517
2022-03-10T17:41:21
2025-01-14T08:48:23.364636
An information leak in Nabu Casa Home Assistant Operating System and Home Assistant Supervised 2022.03 allows a DNS operator to gain knowledge about internal network resources via the hardcoded DNS resolver configuration.
[ { "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/home-assistant/plugin-dns
[]
[ "96a587bba9afec5efa0ea0685d29bcf6ee4a44b8" ]
CVE-2022-25850
2022-05-01T16:15:08
2025-01-15T02:18:54.917054
The package github.com/hoppscotch/proxyscotch before 1.0.0 are vulnerable to Server-side Request Forgery (SSRF) when interceptor mode is set to proxy. It occurs when an HTTP request is made by a backend server to an untrusted URL submitted by a user. It leads to a leakage of sensitive information from the server.
[ { "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/hoppscotch/proxyscotch
[]
[ "f8f664b7045ba570629a1128cce8c686921abb1c" ]
CVE-2024-35232
2024-05-24T21:15:59
2025-01-15T05:14:01.997635
github.com/huandu/facebook is a Go package that fully supports the Facebook Graph API with file upload, batch request and marketing API. access_token can be exposed in error message on fail in HTTP request. This issue has been patched in version 2.7.2.
null
https://github.com/huandu/facebook
[]
[ "1591be276561bbdb019c0279f1d33cb18a650e1b" ]
CVE-2024-45054
2024-08-28T20:15:08
2024-10-08T04:22:24.997237
Hwameistor is an HA local storage system for cloud-native stateful workloads. This ClusterRole has * verbs of * resources. If a malicious user can access the worker node which has hwameistor's deployment, he/she can abuse these excessive permissions to do whatever he/she likes to the whole cluster, resulting in a cluster-level privilege escalation. This issue has been patched in version 0.14.6. All users are advised to upgrade. Users unable to upgrade should update and limit the ClusterRole using security-role.
[ { "score": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/hwameistor/hwameistor
[]
[ "7837b4ed9c7a51507bae5c075b32ffd490720d93" ]
CVE-2019-12496
2019-05-31T11:29:02
2025-02-19T02:42:03.711367
An issue was discovered in Hybrid Group Gobot before 1.13.0. The mqtt subsystem skips verification of root CA certificates by default.
[ { "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/hybridgroup/gobot
[]
[ "ed531980b4efe72c4fd9e768171855de3af2d718" ]
CVE-2018-9862
2018-04-09T16:29:00
2025-01-14T07:41:54.225764
util.c in runV 1.0.0 for Docker mishandles a numeric username, which allows attackers to obtain root access by leveraging the presence of an initial numeric value on an /etc/passwd line, and then issuing a "docker exec" command with that value in the -u argument, a similar issue to CVE-2016-3697.
[ { "score": "CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/hyperhq/runv
[]
[ "cc051a6f77fb678ca3c1609e8c1519bbfd858e60" ]
CVE-2024-45244
2024-08-25T02:15:03
2024-10-30T20:45:42.146689
Hyperledger Fabric through 2.5.9 does not verify that a request has a timestamp within the expected time window.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N", "type": "CVSS_V3" } ]
https://github.com/hyperledger/fabric
[]
[ "242b1e34ed6df3e6228e41e4447149e63ff02547" ]
CVE-2023-46132
2023-11-14T21:15:11
2025-02-19T03:33:25.730623
Hyperledger Fabric is an open source permissioned distributed ledger framework. Combining two molecules to one another, called "cross-linking" results in a molecule with a chemical formula that is composed of all atoms of the original two molecules. In Fabric, one can take a block of transactions and cross-link the transactions in a way that alters the way the peers parse the transactions. If a first peer receives a block B and a second peer receives a block identical to B but with the transactions being cross-linked, the second peer will parse transactions in a different way and thus its world state will deviate from the first peer. Orderers or peers cannot detect that a block has its transactions cross-linked, because there is a vulnerability in the way Fabric hashes the transactions of blocks. It simply and naively concatenates them, which is insecure and lets an adversary craft a "cross-linked block" (block with cross-linked transactions) which alters the way peers process transactions. For example, it is possible to select a transaction and manipulate a peer to completely avoid processing it, without changing the computed hash of the block. Additional validations have been added in v2.2.14 and v2.5.5 to detect potential cross-linking issues before processing blocks. Users are advised to upgrade. There are no known workarounds for this vulnerability.
[ { "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/hyperledger/fabric
[]
[ "242b1e34ed6df3e6228e41e4447149e63ff02547" ]
CVE-2021-43669
2021-11-18T16:15:09
2025-01-14T09:59:49.824221
A vulnerability has been detected in HyperLedger Fabric v1.4.0, v2.0.0, v2.0.1, v2.3.0. It can easily break down as many orderers as the attacker wants. This bug can be leveraged by constructing a message whose header is invalid to the interface Order. This bug has been admitted and fixed by the developers of Fabric.
[ { "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/hyperledger/fabric
[]
[ "242b1e34ed6df3e6228e41e4447149e63ff02547" ]
CVE-2021-43667
2021-11-18T16:15:09
2025-01-14T09:59:48.412281
A vulnerability has been detected in HyperLedger Fabric v1.4.0, v2.0.0, v2.1.0. This bug can be leveraged by constructing a message whose payload is nil and sending this message with the method 'forwardToLeader'. This bug has been admitted and fixed by the developers of Fabric. If leveraged, any leader node will crash.
[ { "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/hyperledger/fabric
[]
[ "242b1e34ed6df3e6228e41e4447149e63ff02547" ]
CVE-2022-45196
2022-11-12T20:15:09
2025-01-14T11:15:57.640131
Hyperledger Fabric 2.3 allows attackers to cause a denial of service (orderer crash) by repeatedly sending a crafted channel tx with the same Channel name. NOTE: the official Fabric with Raft prevents exploitation via a locking mechanism and a check for names that already exist.
[ { "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/hyperledger/fabric
[]
[ "242b1e34ed6df3e6228e41e4447149e63ff02547" ]
CVE-2022-31121
2022-07-07T18:15:09
2025-01-15T02:22:08.409021
Hyperledger Fabric is a permissioned distributed ledger framework. In affected versions if a consensus client sends a malformed consensus request to an orderer it may crash the orderer node. A fix has been added in commit 0f1835949 which checks for missing consensus messages and returns an error to the consensus client should the message be missing. Users are advised to upgrade to versions 2.2.7 or v2.4.5. 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/hyperledger/fabric
[]
[ "242b1e34ed6df3e6228e41e4447149e63ff02547" ]
CVE-2022-36023
2022-08-18T16:15:08
2025-01-14T11:03:28.080666
Hyperledger Fabric is an enterprise-grade permissioned distributed ledger framework for developing solutions and applications. If a gateway client application sends a malformed request to a gateway peer it may crash the peer node. Version 2.4.6 checks for the malformed gateway request and returns an error to the gateway client. There are no known workarounds, users must upgrade to version 2.4.6.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L", "type": "CVSS_V3" } ]
https://github.com/hyperledger/fabric
[]
[ "242b1e34ed6df3e6228e41e4447149e63ff02547" ]
CVE-2023-37265
2023-07-17T21:15:09
2025-01-15T04:55:25.902025
CasaOS is an open-source Personal Cloud system. Due to a lack of IP address verification an unauthenticated attackers can execute arbitrary commands as `root` on CasaOS instances. The problem was addressed by improving the detection of client IP addresses in `391dd7f`. This patch is part of CasaOS 0.4.4. Users should upgrade to CasaOS 0.4.4. If they can't, they should temporarily restrict access to CasaOS to untrusted users, for instance by not exposing it publicly.
[ { "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/icewhaletech/casaos-gateway
[]
[ "f76b6bcd949be30867b2c3829cbeb94b0c354aef" ]
CVE-2024-24765
2024-03-06T18:15:46
2025-01-15T05:08:46.753707
CasaOS-UserService provides user management functionalities to CasaOS. Prior to version 0.4.7, path filtering of the URL for user avatar image files was not strict, making it possible to get any file on the system. This could allow an unauthorized actor to access, for example, the CasaOS user database, and possibly obtain system root privileges. Version 0.4.7 fixes this issue.
null
https://github.com/icewhaletech/casaos-userservice
[]
[ "4d2b65e34c6d01800273009d60756205c08cb0c3" ]
CVE-2024-24767
2024-03-06T18:15:46
2025-01-15T05:08:50.781222
CasaOS-UserService provides user management functionalities to CasaOS. Starting in version 0.4.4.3 and prior to version 0.4.7, CasaOS doesn't defend against password brute force attacks, which leads to having full access to the server. The web application lacks control over the login attempts. This vulnerability allows attackers to get super user-level access over the server. Version 0.4.7 contains a patch for this issue.
null
https://github.com/icewhaletech/casaos-userservice
[]
[ "4d2b65e34c6d01800273009d60756205c08cb0c3" ]
CVE-2024-24766
2024-03-06T19:15:07
2025-01-15T05:08:49.544722
CasaOS-UserService provides user management functionalities to CasaOS. Starting in version 0.4.4.3 and prior to version 0.4.7, the Casa OS Login page disclosed the username enumeration vulnerability in the login page. An attacker can enumerate the CasaOS username using the application response. If the username is incorrect application gives the error `**User does not exist**`. If the password is incorrect application gives the error `**Invalid password**`. Version 0.4.7 fixes this issue.
null
https://github.com/icewhaletech/casaos-userservice
[]
[ "4d2b65e34c6d01800273009d60756205c08cb0c3" ]
CVE-2024-28232
2024-04-01T17:15:45
2025-01-15T05:11:02.502552
Go package IceWhaleTech/CasaOS-UserService provides user management functionalities to CasaOS. The Casa OS Login page has disclosed the username enumeration vulnerability in the login page which was patched in version 0.4.7. This issue in CVE-2024-28232 has been patched in version 0.4.8 but that version has not yet been uploaded to Go's package manager.
null
https://github.com/icewhaletech/casaos-userservice
[]
[ "4d2b65e34c6d01800273009d60756205c08cb0c3" ]