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-6rg3-8h8x-5xfv | Unchecked hostname resolution could allow access to local network resources by users outside the local network | ### Impact
A newly implemented route allowing users to download files from remote endpoints was not properly verifying the destination hostname for user provided URLs. This would allow malicious users to potentially access resources on local networks that would otherwise be inaccessible.
This vulnerability requires valid authentication credentials and is therefore **not exploitable by unauthenticated users**. If you are running an instance for yourself or other trusted individuals this impact is unlikely to be of major concern to you. However, you should still upgrade for security sake.
### Patches
Users should upgrade to the latest version of Wings.
### Workarounds
There is no workaround available that does not involve modifying Panel or Wings code.
| null | 2021-10-05T17:24:11Z | 2021-06-23T18:04:50Z | MODERATE | null | {'CWE-441', 'CWE-284'} | {'https://github.com/pterodactyl/wings', 'https://github.com/pterodactyl/wings/security/advisories/GHSA-6rg3-8h8x-5xfv'} | null |
Go | GHSA-cpgw-2wxr-pww3 | Open Redirect | Open redirect vulnerability in Gogs before 0.12 allows remote attackers to redirect users to arbitrary websites and conduct phishing attacks via an initial /\ substring in the user/login redirect_to parameter, related to the function isValidRedirect in routes/user/auth.go. | {'CVE-2018-15178'} | 2021-05-20T20:55:39Z | 2021-06-29T18:32:39Z | MODERATE | null | {'CWE-601'} | {'https://github.com/gogs/gogs/pull/5365', 'https://nvd.nist.gov/vuln/detail/CVE-2018-15178', 'https://github.com/gogs/gogs/commit/1f247cf8139cb483276cd8dd06385a800ce9d4b2', 'https://github.com/gogs/gogs/issues/5364'} | null |
Go | GHSA-7h6j-2268-fhcm | Improper Certificate Handling | configurationwatcher.go in Traefik 2.x before 2.1.4 and TraefikEE 2.0.0 mishandles the purging of certificate contents from providers before logging. | {'CVE-2020-9321'} | 2021-08-02T22:19:23Z | 2021-09-02T22:00:01Z | MODERATE | null | {'CWE-200', 'CWE-295'} | {'https://github.com/containous/traefik/releases/tag/v2.1.4', 'https://github.com/containous/traefik/pull/6281', 'https://nvd.nist.gov/vuln/detail/CVE-2020-9321'} | null |
Go | GHSA-p2j5-3f4c-224r | Improper Input Validation in HashiCorp Consul | HashiCorp Consul and Consul Enterprise did not appropriately enforce scope for local tokens issued by a primary data center, where replication to a secondary data center was not enabled. Introduced in 1.4.0, fixed in 1.6.6 and 1.7.4. | {'CVE-2020-13170'} | 2021-05-12T22:01:59Z | 2021-05-18T18:21:21Z | MODERATE | null | {'CWE-20'} | {'https://github.com/hashicorp/consul/blob/v1.6.6/CHANGELOG.md', 'https://github.com/hashicorp/consul/pull/8068', 'https://github.com/hashicorp/consul/commit/242994a016a181d6c62a5bb83189716ad13d4216', 'https://nvd.nist.gov/vuln/detail/CVE-2020-13170', 'https://github.com/hashicorp/consul/blob/v1.7.4/CHANGELOG.md'} | null |
Go | GHSA-wxjg-p59j-6c92 | Command injection in github.com/google/fscrypt | The bash_completion script for fscrypt allows injection of commands via crafted mountpoint paths, allowing privilege escalation under a specific set of circumstances. A local user who has control over mountpoint paths could potentially escalate their privileges if they create a malicious mountpoint path and if the system administrator happens to be using the fscrypt bash completion script to complete mountpoint paths. We recommend upgrading to version 0.3.3 or above | {'CVE-2022-25328'} | 2022-03-08T18:26:50Z | 2022-02-26T00:00:44Z | MODERATE | null | {'CWE-78'} | {'https://github.com/google/fscrypt/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-25328', 'https://github.com/google/fscrypt/pull/346'} | null |
Go | GHSA-jwvr-vv7p-gpwq | Privilege escalation for users with create/update permissions in Global Roles in Rancher | ### Impact
This vulnerability affects customers who utilize non-admin users that are able to create or edit [Global Roles](https://rancher.com/docs/rancher/v2.6/en/admin-settings/rbac/). The most common use case for this scenario is the [`restricted-admin`](https://rancher.com/docs/rancher/v2.6/en/admin-settings/rbac/global-permissions/#restricted-admin) role.
A flaw was discovered in Rancher versions from 2.5.0 up to and including 2.5.12 and from 2.6.0 up to and including 2.6.3 which allows users who have create or update permissions on Global Roles to escalate their permissions, or those of another user, to admin-level permissions. Global Roles grant users Rancher-wide permissions, such as the ability to create clusters. In the identified versions of Rancher, when users are given permission to edit or create Global Roles, they are not restricted to only granting permissions which they already posses.
The privilege escalation can be taken advantage of in two ways by users with create or update permissions on Global Roles (including the `restricted-admin`):
1. Editing the global `admin` role to make it the default for new users, then creating a new user that will be elevated to the global `admin` role.
2. Creating a new global role with permissions already possessed by the `restricted-admin`, assigning this new role to a user, then modifying the global role to grant additional administrive like permissions (`'*'`) to the elevated user.
### Patches
Patched versions include releases 2.5.13, 2.6.4 and later versions.
### Workarounds
Limit access in Rancher to trusted users. There is not a direct mitigation besides upgrading to the patched Rancher versions.
**Note:** If you have users who have create or edit permissions on Global Roles but are not admin users (for example, the `restricted-admin`), it is highly advised to review the roles and users created by those users for possible privilege escalations.
### For more information
If you have any questions or comments about this advisory:
* Reach out to [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.
* Open an issue in [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository.
* Verify our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/). | {'CVE-2021-36784'} | 2022-05-02T19:39:35Z | 2022-05-02T19:39:35Z | MODERATE | null | {'CWE-285', 'CWE-269'} | {'https://github.com/rancher/rancher/releases/tag/v2.5.13', 'https://github.com/rancher/rancher/releases/tag/v2.6.4', 'github.com/rancher/rancher', 'https://github.com/rancher/rancher/security/advisories/GHSA-jwvr-vv7p-gpwq'} | null |
Go | GHSA-9r5x-fjv3-q6h4 | Incorrect Access Control in github.com/nats-io/jwt and github.com/nats-io/nats-server/v2 | NATS Server 2.x before 2.2.0 and JWT library before 2.0.1 have Incorrect Access Control because Import Token bindings are mishandled. | {'CVE-2021-3127'} | 2021-05-12T20:34:10Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-863', 'CWE-284'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-3127', 'https://github.com/nats-io/jwt/pull/149/commits/a826c77dc9d2671c961b75ceefdb439c41029866', 'https://advisories.nats.io/CVE/CVE-2021-3127.txt', 'https://github.com/nats-io/nats-server/commit/423b79440c80c863de9f4e20548504e6c5d5e403'} | null |
Go | GO-2021-0051 | null | Due to improper santization of user input on Windows, the static file handler
allows for directory traversal, allowing an attacker to read files outside of
the target directory that the server has permission to read.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/labstack/echo/commit/4422e3b66b9fd498ed1ae1d0242d660d0ed3faaa', 'https://github.com/labstack/echo/pull/1718'} | null |
Go | GHSA-q9x4-q76f-5h5j | Unauthenticated users can exploit an enumeration vulnerability in Harbor (CVE-2019-19030) | # Impact
Sean Wright from Secureworks has discovered an enumeration vulnerability. An attacker can make use of the Harbor API to make unauthenticated calls to the Harbor instance. Based on the HTTP status code in the response, an attacker is then able to work out which resources exist, and which do not. This would likely be accomplished by either providing a wordlist or enumerating through a sequence an
unauthenticated attacker is able to enumerate resources on the system. This provides them with information such as existing projects, repositories, etc.
The vulnerability was immediately fixed by the Harbor team.
# Issue
The following API resources where found to be vulnerable to enumeration attacks:
/api/chartrepo/{repo}/prov (POST)
/api/chartrepo/{repo}/charts (GET, POST)
/api/chartrepo/{repo}/charts/{name} (GET, DELETE)
/api/chartrepo/{repo}/charts/{name}/{version} (GET, DELETE)
/api/labels?name={name}&scope=p (GET)
/api/repositories?project_id={id} (GET)
/api/repositories/{repo_name}/ (GET, PUT, DELETE)
/api/repositories/{repo_name}/tags (GET)
/api/repositories/{repo_name}/tags/{tag}/manifest?version={version} (GET)
/api/repositories/{repo_name/{tag}/labels (GET)
/api/projects?project_name={name} (HEAD)
/api/projects/{project_id}/summary (GET)
/api/projects/{project_id}/logs (GET)
/api/projects/{project_id} (GET, PUT, DELETE)
/api/projects/{project_id}/metadatas (GET, POST)
/api/projects/{project_id}/metadatas/{metadata_name} (GET, PUT)
# Known Attack Vectors
Successful exploitation of this issue will lead to bad actors identifying which resources exist in Harbor without requiring authentication for the Harbor API.
# Patches
If your product uses the affected releases of Harbor, update to version 1.10.3 or 2.0.1 to patch this issue immediately.
https://github.com/goharbor/harbor/releases/tag/v1.10.3
https://github.com/goharbor/harbor/releases/tag/v2.0.1
# Workarounds
There is no known workaround
# 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 | {'CVE-2019-19030'} | 2021-05-24T18:52:37Z | 2022-02-11T23:17:25Z | LOW | null | null | {'https://github.com/goharbor/harbor/security/advisories/GHSA-q9x4-q76f-5h5j'} | null |
Go | GHSA-r9w6-rhh9-7v53 | Incorrect Authorization in HashiCorp Consul | HashiCorp Consul and Consul Enterprise 1.4.1 through 1.6.2 did not uniformly enforce ACLs across all API endpoints, resulting in potential unintended information disclosure. Fixed in 1.6.3. | {'CVE-2020-7955'} | 2021-07-27T15:08:01Z | 2021-07-28T17:57:57Z | MODERATE | null | {'CWE-863'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-7955', 'https://www.hashicorp.com/blog/category/consul/', 'https://github.com/hashicorp/consul/issues/7160'} | null |
Go | GHSA-65f3-3278-7m65 | Improper Authorization in Gogs | ### Impact
Expired PAM accounts and accounts with expired passwords are continued to be seen as valid. Installations use PAM as authentication sources are affected.
### Patches
Expired PAM accounts and accounts with expired passwords are no longer being seen as valid. Users should upgrade to 0.12.5 or the latest 0.13.0+dev.
### Workarounds
In addition to marking PAM accounts as expired, also disable/lock them. Running `usermod -L <username>` will add an exclamation mark to the password hash and would result in wrong passwords responses when trying to login.
### References
https://huntr.dev/bounties/ea82cfc9-b55c-41fe-ae58-0d0e0bd7ab62/
### For more information
If you have any questions or comments about this advisory, please post on https://github.com/gogs/gogs/issues/6810.
| {'CVE-2022-0871'} | 2022-03-14T22:58:34Z | 2022-03-12T00:00:34Z | HIGH | null | {'CWE-863', 'CWE-285'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0871', 'https://github.com/gogs/gogs', 'https://huntr.dev/bounties/ea82cfc9-b55c-41fe-ae58-0d0e0bd7ab62', 'https://github.com/gogs/gogs/commit/64102be2c90e1b47dbdd379873ba76c80d4b0e78'} | null |
Go | GHSA-6g5f-f5pm-mjrg | Vulnerability in Istio | Istio 1.1.x through 1.1.6 has Incorrect Access Control. | {'CVE-2019-12243'} | 2021-05-17T15:53:48Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-284'} | {'https://istio.io/about/notes/', 'https://istio.io/blog/2019/cve-2019-12243/', 'https://nvd.nist.gov/vuln/detail/CVE-2019-12243'} | null |
Go | GHSA-qhm4-jxv7-j9pq | Allocation of Resources Without Limits or Throttling and Uncontrolled Memory Allocation in Kubernetes | The Kubelet component in versions 1.15.0-1.15.9, 1.16.0-1.16.6, and 1.17.0-1.17.2 has been found to be vulnerable to a denial of service attack via the kubelet API, including the unauthenticated HTTP read-only API typically served on port 10255, and the authenticated HTTPS API typically served on port 10250. | {'CVE-2020-8551'} | 2021-05-06T21:53:58Z | 2022-02-15T01:57:18Z | LOW | null | {'CWE-789'} | {'https://github.com/kubernetes/kubernetes/pull/87913', 'https://github.com/kubernetes/kubernetes/commit/9802bfcec0580169cffce2a3d468689a407fa7dc', 'https://security.netapp.com/advisory/ntap-20200413-0003/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8551', 'https://github.com/kubernetes/kubernetes/issues/89377', 'https://groups.google.com/forum/#!topic/kubernetes-security-announce/2UOlsba2g0s', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3SOCLOPTSYABTE4CLTSPDIFE6ZZZR4LX/'} | null |
Go | GHSA-82hx-w2r5-c2wq | Allocation of Resources Without Limits or Throttling and Uncontrolled Memory Allocation in Kubernetes | The Kubernetes API server component in versions prior to 1.15.9, 1.16.0-1.16.6, and 1.17.0-1.17.2 has been found to be vulnerable to a denial of service attack via successful API requests. | {'CVE-2020-8552'} | 2021-05-06T21:48:16Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-789', 'CWE-400'} | {'https://github.com/kubernetes/kubernetes/commit/5978856c4c7f10737a11c9540fe60b8475beecbb', 'https://security.netapp.com/advisory/ntap-20200413-0003/', 'https://groups.google.com/forum/#!topic/kubernetes-security-announce/2UOlsba2g0s', 'https://github.com/kubernetes/kubernetes/pull/87669', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3SOCLOPTSYABTE4CLTSPDIFE6ZZZR4LX/', 'https://github.com/kubernetes/kubernetes/issues/89378', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8552'} | null |
Go | GHSA-fqh4-rh59-xhvf | Denial of service | The package `github.com/pires/go-proxyproto` before 0.5.0 are vulnerable to Denial of Service (DoS) via the parseVersion1() function. The reader in this package is a default bufio.Reader wrapping a net.Conn. It will read from the connection until it finds a newline. Since no limits are implemented in the code, a deliberately malformed V1 header could be used to exhaust memory in a server process using this code - and create a DoS. This can be exploited by sending a stream starting with PROXY and continuing to send data (which does not contain a newline) until the target stops acknowledging. The risk here is small, because only trusted sources should be allowed to send proxy protocol headers. | {'CVE-2021-23351'} | 2021-05-18T21:03:39Z | 2021-05-18T21:07:43Z | MODERATE | null | {'CWE-400'} | {'https://github.com/pires/go-proxyproto/pull/71', 'https://github.com/pires/go-proxyproto/commit/7f48261db810703d173f27f3309a808cc2b49b8b', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4BNVGJMVI3ZTZ675EFPUHPGXCKCGSX46/', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMPIRESGOPROXYPROTO-1081577', 'https://github.com/pires/go-proxyproto/issues/69', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23351', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/C36IBVOZXRTWM7MGTRUTOM56P5RR74VU/'} | null |
Go | GO-2021-0092 | null | Uniqueness of JWT IDs (jti) are not checked, allowing the JWT to be
replayed.
| {'CVE-2020-15222'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/ory/fosite/commit/0c9e0f6d654913ad57c507dd9a36631e1858a3e9', 'https://github.com/ory/fosite/security/advisories/GHSA-v3q9-2p3m-7g43'} | null |
Go | GHSA-ccxc-vr6p-4858 | Improper Certificate Validation in Cosign | ### Impact
Cosign can be manipulated to claim that an entry for a signature exists in the Rekor transparency log even if it doesn't. This requires the attacker to have pull and push permissions for the signature in OCI. This can happen with both standard signing with a keypair and "keyless signing" with Fulcio.
#### Signing with a keypair
<details>
To reproduce this vulnerability, create a keypair and sign an image. Don't store the signature in Rekor:
```
$ cosign generate-key-pair
$ cosign sign --key cosign.key IMAGE
```
If an attacker has access to the signature in OCI, they can manipulate cosign into believing the entry was stored in Rekor even though it wasn't. To accomplish this, the attacker needs to:
1. Pull the signature image
2. Annotate the signature image with any valid Rekor bundle under the `dev.sigstore.cosign/bundle` annotation
3. Push the signature image back to OCI
Verification then prints out the following:
```
$ cosign verify [--key] [IMAGE]
Verification for [IMAGE] --
The following checks were performed on each of these signatures:
- The cosign claims were validated
- Existence of the claims in the transparency log was verified offline
- The signatures were verified against the specified public key
- Any certificates were verified against the Fulcio roots.
[…]
```
The claim that `Existence of the claims in the transparency log was verified offline` is inaccurate since an entry for this image doesn't exist in the log.
The claim that `Any certificates were verified against the Fulcio roots.` is technically correct but since there were no certificates that should be explicitly called out.
</details>
#### "Keyless signing" with an OIDC flow
<details>
To reproduce this vulnerability, sign the image with a Fulcio identity. Don't store the signature in Rekor:
```
$ COSIGN_EXPERIMENTAL=1 cosign sign IMAGE
[...]
IMAGE appears to be a private repository, please confirm uploading to the transparency log at "https://rekor.sigstore.dev" [Y/N]: n
```
Then, create a keypair and sign the image again. Store an entry for the signature in Rekor:
```
$ cosign generate-key-pair
$ COSIGN_EXPERIMENTAL=1 cosign sign --key cosign.key IMAGE
Enter password for private key: IMAGE appears to be a private repository, please confirm uploading to the transparency log at "https://rekor.sigstore.dev" [Y/N]: y
```
If an attacker has access to the signature in OCI, they can manipulate cosign into believing the entry was stored in Rekor even though it wasn't. To accomplish this, the attacker needs to:
1. Pull the signature image
2. Copy the rekor bundle from the second signature into the first signature under the `dev.sigstore.cosign/bundle` annotation
3. Push the signature image back to OCI
_Note: For this to work, both signatures must occur during the valid lifespan of the certificate (~20 minutes)._
Verification then prints out the following:
```
$ cosign verify [--key] [IMAGE]
Verification for [IMAGE] --
The following checks were performed on each of these signatures:
- The cosign claims were validated
- Existence of the claims in the transparency log was verified offline
- The signatures were verified against the specified public key
- Any certificates were verified against the Fulcio roots.
[…]
```
The claim that `Existence of the claims in the transparency log was verified offline` is inaccurate since an entry for this image doesn't exist in the log.
The claim that `Any certificates were verified against the Fulcio roots.` is technically correct but since there were no certificates that should be explicitly called out.
</details>
### Patches
The vulnerability has been patched in v1.5.2 of cosign.
The `signature` in the `signedEntryTimestamp` provided by Rekor is now compared to the `signature` that is being verified. If these don't match, then an error is returned. If a valid bundle is copied to a different signature, verification should fail.
Cosign output now only informs the user that certificates were verified if a certificate was in fact verified.
### Workarounds
The only workaround is upgrading.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [cosign](https://github.com/sigstore/cosign)
* Send us a message on [Slack](https://sigstore.slack.com/). Invite link [here](https://join.slack.com/t/sigstore/shared_invite/zt-mhs55zh0-XmY3bcfWn4XEyMqUUutbUQ).
### Thank you
Thank you to @mtrmac for finding and reporting this vulnerability.
Thank you to everyone who worked on fixing this:
* @nsmith5
* @znewman01
* @dlorenc
* @mattmoor
* @priyawadhwa
| {'CVE-2022-23649'} | 2022-03-08T18:26:05Z | 2022-02-22T19:34:09Z | LOW | null | {'CWE-295'} | {'https://github.com/sigstore/cosign/releases/tag/v1.5.2', 'https://github.com/sigstore/cosign/', 'https://github.com/sigstore/cosign/commit/96d410a6580e4e81d24d112a0855c70ca3fb5b49', 'https://github.com/sigstore/cosign/security/advisories/GHSA-ccxc-vr6p-4858', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23649'} | null |
Go | GO-2020-0036 | null | Due to unbounded aliasing, a crafted YAML file can cause consumption
of significant system resources. If parsing user supplied input, this
may be used as a denial of service vector.
| {'CVE-2019-11254'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/go-yaml/yaml/pull/555', 'https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18496', 'https://github.com/go-yaml/yaml/commit/53403b58ad1b561927d19068c655246f2db79d48'} | null |
Go | GHSA-jr9c-h74f-2v28 | Improper Authorization in Gitea | Gitea 1.16.3 and prior is vulnerable to improper authorization. A patch is available and is anticipated to be part of the 1.16.4 release. | {'CVE-2022-0905'} | 2022-03-28T22:24:29Z | 2022-03-11T00:02:35Z | MODERATE | null | {'CWE-863', 'CWE-285'} | {'https://huntr.dev/bounties/8d221f92-b2b1-4878-bc31-66ff272e5ceb', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0905', 'https://github.com/go-gitea/gitea/commit/1314f38b59748397b3429fb9bc9f9d6bac85d2f2', 'https://github.com/go-gitea/gitea'} | null |
Go | GHSA-c72p-9xmj-rx3w | Archive package allows chmod of file outside of unpack target directory | ## Impact
A bug was found in containerd where pulling and extracting a specially-crafted container image can result in Unix file permission changes for existing files in the host’s filesystem. Changes to file permissions can deny access to the expected owner of the file, widen access to others, or set extended bits like setuid, setgid, and sticky. This bug does not directly allow files to be read, modified, or executed without an additional cooperating process.
## Patches
This bug has been fixed in containerd 1.5.4 and 1.4.8. Users should update to these versions as soon as they are released. Running containers do not need to be restarted.
## Workarounds
Ensure you only pull images from trusted sources.
Linux security modules (LSMs) like SELinux and AppArmor can limit the files potentially affected by this bug through policies and profiles that prevent containerd from interacting with unexpected files.
## For more information
If you have any questions or comments about this advisory:
* [Open an issue](https://github.com/containerd/containerd/issues/new/choose)
* Email us at security@containerd.io if you think you’ve found a security bug. | {'CVE-2021-32760'} | 2021-10-21T13:16:22Z | 2021-07-26T21:17:45Z | MODERATE | null | {'CWE-668'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-32760', 'https://github.com/containerd/containerd', 'https://github.com/containerd/containerd/releases/tag/v1.5.4', 'https://github.com/containerd/containerd/security/advisories/GHSA-c72p-9xmj-rx3w', 'https://github.com/containerd/containerd/releases/tag/v1.4.8', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DDMNDPJJTP3J5GOEDB66F6MGXUTRG3Y3/'} | null |
Go | GHSA-xcqr-9h24-vrgw | Improper Restriction of Excessive Authentication Attempts in Argo API | As of v1.5.0, the Argo API does not implement anti-automation measures such as rate limiting, account lockouts, or other anti-bruteforce measures. Attackers can submit an unlimited number of authentication attempts without consequence. | {'CVE-2020-8827'} | 2021-07-26T21:13:31Z | 2021-07-26T21:19:37Z | HIGH | null | {'CWE-307'} | {'https://github.com/argoproj/argo/releases', 'https://github.com/argoproj/argo-cd/commit/35a7350b7444bcaf53ee0bb11b9d8e3ae4b717a1', 'https://www.soluble.ai/blog/argo-cves-2020', 'https://github.com/argoproj/argo-cd/pull/3369', 'https://argoproj.github.io/argo-cd/operator-manual/user-management/#disable-admin-user', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8827', 'https://argoproj.github.io/argo-cd/security_considerations/', 'https://github.com/argoproj/argo-cd/pull/3404'} | null |
Go | GHSA-wjm3-fq3r-5x46 | Denial of service | GJSON <1.6.5 allows attackers to cause a denial of service (remote) via crafted JSON. | {'CVE-2020-36066'} | 2021-05-18T21:00:38Z | 2021-05-18T21:07:54Z | MODERATE | null | {'CWE-400'} | {'https://github.com/tidwall/gjson/issues/195', 'https://github.com/tidwall/gjson/issues/195#issuecomment-755303148', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36066', 'https://github.com/tidwall/match/commit/c2f534168b739a7ec1821a33839fb2f029f26bbc'} | null |
Go | GHSA-8v99-48m9-c8pm | Incorrect Authorization in imgcrypt | Imgcrypt implements a function `CheckAuthorization()` that is supposed to check whether a user is authorized to access an encrypted image given the keys that the user has provided on the command line that would enable decryption of the image. The check is to prevent that a user can start a container from an image that has previously been decrypted by another user on the same system and therefore a decrypted version of the image layers may be already available in the cache locally.
The failure occurs when an image with a ManifestList is used and the architecture of the local host is not the first one in the ManifestList. In the version prior to the fix, only the first architecture in the list was tested, which may not have its layers available locally (were not pulled) since it cannot be run on the host architecture. Therefore, the verdict on unavailable layers was that the image could be run anticipating that image run failure would occur later due to the layers not being available. However, this verdict to allow the image to run lead to other architectures in the ManifestList be able to run an image without providing keys if that image had previously been decrypted. The fixed version now skips over irrelevant architectures and tests the Manifest of the local architecture, if available.
Known projects that use the `CheckAuthorization()` of imgcrypt is for example the ctr-enc client tool provided by imgcrypt. In this implementation, the call to `CheckAuthorization()` is used on the client side and could therefore also be easily circumvented by a modified client tool not calling this function.
In relation to the vulnerability in ctr-enc, affected environments would have to allow different users to invoke ctr-enc indirectly using some sort of management stack that gives user indirect access to ctr-enc.
The patch has been applied to imgcrypt v1.1.4. Workarounds may include usage of different namespaces for each remote user. | {'CVE-2022-24778'} | 2022-04-13T03:57:32Z | 2022-03-28T19:33:44Z | HIGH | null | {'CWE-863'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-24778', 'https://github.com/containerd/imgcrypt/security/advisories/GHSA-8v99-48m9-c8pm', 'https://github.com/containerd/imgcrypt/releases/tag/v1.1.4', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TAHAAOOA3KZJC2I5WHCR3XVBJBNWTWUE/', 'https://github.com/containerd/imgcrypt/commit/6fdd9818a4d8142107b7ecd767d839c9707700d9', 'https://github.com/containerd/imgcrypt', 'https://github.com/containerd/imgcrypt/issues/69', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZFTJR5CR5EOYDVOSBZEMLBHLJRTPJPUA/'} | null |
Go | GHSA-grj5-8x6q-hc9q | Path traversal in Grafana Loki | An issue was discovered in Grafana Loki through 2.2.1. The header value X-Scope-OrgID is used to construct file paths for rules files, and if crafted to conduct directory traversal such as ae ../../sensitive/path/in/deployment pathname, then Loki will attempt to parse a rules file at that location and include some of the contents in the error message. | {'CVE-2021-36156'} | 2021-09-08T18:11:29Z | 2021-09-02T22:00:40Z | MODERATE | null | {'CWE-22'} | {'https://github.com/grafana/loki/pull/4020#issue-694377133', 'https://github.com/grafana/loki/pull/4020', 'https://nvd.nist.gov/vuln/detail/CVE-2021-36156', 'https://github.com/grafana/loki/releases/tag/v2.3.0', 'https://github.com/grafana/loki'} | null |
Go | GHSA-qqc5-rgcc-cjqh | Information Disclosure in go.elastic.co/apm | The Elastic APM agent for Go versions before 1.11.0 can leak sensitive HTTP header information when logging the details during an application panic. Normally, the APM agent will sanitize sensitive HTTP header details before sending the information to the APM server. During an application panic it is possible the headers will not be sanitized before being sent. | {'CVE-2021-22133'} | 2021-05-07T22:01:55Z | 2021-05-18T18:34:18Z | LOW | null | {'CWE-532'} | {'https://github.com/elastic/apm-agent-go/commit/c5c7e21aa26a6def7790f74fbceed792ad47ef35', 'https://discuss.elastic.co/t/elastic-apm-agent-for-go-1-11-0-security-update/263252', 'https://nvd.nist.gov/vuln/detail/CVE-2021-22133', 'https://github.com/elastic/apm-agent-go/compare/v1.10.0...v1.11.0'} | null |
Go | GHSA-75qf-wgfj-v652 | Arbitrary File Write via Archive Extraction (Zip Slip) | This affects all versions up to and including version 7.0.0 of package github.com/u-root/u-root/pkg/tarutil. It is vulnerable to both leading and non-leading relative path traversal attacks in tar file extraction. | {'CVE-2020-7669'} | 2021-05-05T19:02:17Z | 2021-05-18T18:28:03Z | HIGH | null | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-7669', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMUROOTUROOTPKGTARUTIL-570428', 'https://github.com/u-root/u-root/pull/1817'} | null |
Go | GHSA-vmf7-hmh6-vv57 | Denial of Service in Go-Ethereum | A design flaw in all versions of Go-Ethereum allows an attacker node to send 5120 pending transactions of a high gas price from one account that all fully spend the full balance of the account to a victim Geth node, which can purge all of pending transactions in a victim node's memory pool and then occupy the memory pool to prevent new transactions from entering the pool, resulting in a denial of service (DoS). | {'CVE-2022-23328'} | 2022-03-18T20:06:58Z | 2022-03-05T00:00:46Z | HIGH | null | {'CWE-400'} | {'https://dl.acm.org/doi/pdf/10.1145/3460120.3485369', 'http://ethereum.com', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23328', 'https://github.com/ethereum/go-ethereum', 'http://go-ethereum.com', 'https://tristartom.github.io/docs/ccs21.pdf'} | null |
Go | GHSA-w4x5-jqq4-qc8x | SQL Injection in Cloud Native Computing Foundation Harbor | Cloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 allows SQL Injection via project quotas in the VMware Harbor Container Registry for the Pivotal Platform. | {'CVE-2019-19026'} | 2021-05-04T22:00:55Z | 2021-05-18T18:27:43Z | MODERATE | null | {'CWE-89'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-19026', 'https://tanzu.vmware.com/security/cve-2019-19026', 'https://github.com/goharbor/harbor/security/advisories', 'https://github.com/goharbor/harbor/security/advisories/GHSA-rh89-vvrg-fg64'} | null |
Go | GHSA-f5f7-6478-qm6p | Files or Directories Accessible to External Parties in kubernetes | A security issue was discovered in Kubernetes where a user may be able to create a container with subpath volume mounts to access files & directories outside of the volume, including on the host filesystem. | {'CVE-2021-25741'} | 2021-11-01T17:26:17Z | 2021-11-01T17:32:28Z | HIGH | null | {'CWE-20', 'CWE-552'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-25741', 'https://security.netapp.com/advisory/ntap-20211008-0006/', 'https://github.com/kubernetes/kubernetes/issues/104980', 'https://groups.google.com/g/kubernetes-security-announce/c/nyfdhK24H7s', 'https://github.com/bottlerocket-os/bottlerocket/security/advisories/GHSA-f5f7-6478-qm6p', 'https://github.com/kubernetes/kubernetes'} | null |
Go | GO-2021-0084 | null | Session data is stored using permissive permissions, allowing local users
with filesystem access to read arbitary data.
| {'CVE-2019-16354'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/beego/beego/pull/3975', 'https://github.com/beego/beego/commit/bac2b31afecc65d9a89f9e473b8006c5edc0c8d1', 'https://github.com/beego/beego/issues/3763'} | null |
Go | GHSA-j6wp-3859-vxfg | OIDC claims not updated from Identity Provider in Pomerium | ### Impact
Changes to the OIDC claims of a user after initial login are not reflected in policy evaluation when using [`allowed_idp_claims`](https://www.pomerium.com/reference/#allowed-idp-claims) as part of policy. If using `allowed_idp_claims` and a user's claims are changed, Pomerium can make incorrect authorization decisions.
### Patches
v0.15.6
### Workarounds
- Clear data on `databroker` service by clearing redis or restarting the in-memory databroker to force claims to be updated
### References
https://github.com/pomerium/pomerium/pull/2724
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Pomerium](https://github.com/pomerium/pomerium)
* Email us at [security@pomerium.com](mailto:security@pomerium.com)
| {'CVE-2021-41230'} | 2021-11-08T21:37:07Z | 2021-11-10T16:52:24Z | MODERATE | null | {'CWE-863'} | {'https://github.com/pomerium/pomerium/pull/2724', 'https://github.com/pomerium/pomerium/security/advisories/GHSA-j6wp-3859-vxfg', 'https://github.com/pomerium/pomerium', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41230'} | null |
Go | GHSA-5wjf-62hw-q78r | Excessive CPU usage | Envoy, which Pomerium is based on, incorrectly handles resetting of HTTP/2 streams with excessive complexity. This can lead to high CPU utilization when a large number of streams are reset.
### Impact
This can result in a DoS condition.
### Patches
Pomerium versions 0.14.8 and 0.15.1 contain an upgraded envoy binary with this vulnerability patched.
### Workarounds
N/A
### References
[envoy GSA](https://github.com/envoyproxy/envoy/security/advisories/GHSA-3xh3-33v5-chcc)
[envoy CVE](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32778)
[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-39204'} | 2021-09-10T16:33:46Z | 2021-09-10T17:54:13Z | HIGH | null | {'CWE-834'} | {'https://github.com/envoyproxy/envoy/security/advisories/GHSA-3xh3-33v5-chcc', 'https://groups.google.com/g/envoy-announce/c/5xBpsEZZDfE/m/wD05NZBbAgAJ', 'https://github.com/pomerium/pomerium', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39204', 'https://github.com/pomerium/pomerium/security/advisories/GHSA-5wjf-62hw-q78r'} | null |
Go | GHSA-f9fq-vjvh-779p | Improper Input Validation in vault-ssh-helper | HashiCorp vault-ssh-helper up to and including version 0.1.6 incorrectly accepted Vault-issued SSH OTPs for the subnet in which a host's network interface was located, rather than the specific IP address assigned to that interface. Fixed in 0.2.0. | {'CVE-2020-24359'} | 2021-05-12T20:21:27Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-20'} | {'https://github.com/hashicorp/vault-ssh-helper/commit/83effd08cbcbe4b993d776bd9b39465cd9e4603f', 'https://nvd.nist.gov/vuln/detail/CVE-2020-24359', 'https://github.com/hashicorp/vault-ssh-helper/releases', 'https://github.com/hashicorp/vault-ssh-helper/blob/master/CHANGELOG.md#020-august-19-2020'} | null |
Go | GHSA-h2fg-54x9-5qhq | Nil dereference in NATS JWT, DoS of nats-server | ## Problem Description
The NATS account system has an Operator trusted by the servers, which signs Accounts, and each Account can then create and sign Users within their account. The Operator should be able to safely issue Accounts to other entities which it does not fully trust.
A malicious Account could create and sign a User JWT with a state not created by the normal tooling, such that decoding by the NATS JWT library (written in Go) would attempt a nil dereference, aborting execution.
The NATS Server is known to be impacted by this.
## Affected versions
#### JWT library
* all versions prior to 1.1.0
#### NATS Server
* Version 2 prior to 2.1.9
## Impact
#### JWT library
* Programs would nil dereference and panic, aborting execution by default.
#### NATS server
* Denial of Service caused by process termination
## Workaround
If your NATS servers do not trust any accounts which are managed by untrusted entities, then malformed User credentials are unlikely to be encountered.
## Solution
Upgrade the JWT dependency in any application using it.
Upgrade the NATS server if using NATS Accounts. | {'CVE-2020-26521'} | 2022-02-11T23:43:13Z | 2022-02-11T23:43:13Z | LOW | null | {'CWE-476'} | {'http://www.openwall.com/lists/oss-security/2020/11/02/2', 'https://advisories.nats.io/CVE/CVE-2020-26521.txt', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VT67XCLIIBYRT762SVFBYFFTQFVSM3SI/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26521', 'https://github.com/nats-io/nats-server/commits/master', 'https://github.com/nats-io/jwt/security/advisories/GHSA-h2fg-54x9-5qhq', 'https://github.com/nats-io/nats-server/commit/9ff8bcde2e46009e98bd9e88f598af355f62c168'} | null |
Go | GHSA-vw47-mr44-3jf9 | Confused Deputy in Kubernetes | A security issue was discovered with Kubernetes that could enable users to send network traffic to locations they would otherwise not have access to via a confused deputy attack. | {'CVE-2021-25740'} | 2021-09-21T14:54:49Z | 2021-09-21T18:28:30Z | LOW | null | {'CWE-441', 'CWE-610'} | {'https://security.netapp.com/advisory/ntap-20211014-0001/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25740', 'https://github.com/kubernetes/kubernetes', 'https://groups.google.com/g/kubernetes-security-announce/c/WYE9ptrhSLE', 'https://github.com/kubernetes/kubernetes/issues/103675'} | null |
Go | GO-2020-0020 | null | Usage of the [`CORS`] handler may apply improper CORS headers, allowing
the requester to explicitly control the value of the Access-Control-Allow-Origin
header, which bypasses the expected behavior of the Same Origin Policy.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/gorilla/handlers/commit/90663712d74cb411cbef281bc1e08c19d1a76145', 'https://github.com/gorilla/handlers/pull/116'} | null |
Go | GHSA-4fc7-hc63-7fjg | Exposure of repository credentials to external third-party sources in Rancher | ### Impact
This issue only happens when the user configures access credentials to a private repository in Rancher inside `Apps & Marketplace > Repositories`. It affects Rancher versions 2.5.0 up to and including 2.5.11 and from 2.6.0 up to and including 2.6.2.
An insufficient check of the same-origin policy when downloading Helm charts from a configured private repository can lead to exposure of the repository credentials to a third-party provider. This exposure happens when the private repository:
1. Does an HTTP redirect to a third-party repository or external storage provider.
2. Downloads an icon resource for the chart hosted on a third-party provider.
The address of the private repository is not leaked, only the credentials are leaked in the HTTP `Authorization` header in base64 format.
With the patched versions, the default behavior now is to only send the private repository credentials when subdomain or domain hostname match when following the redirect or downloading external resources.
### Patches
Patched versions include releases 2.5.12, 2.6.3 and later versions.
### Workarounds
1. Update Rancher to a patched version.
2. Check the Helm charts in your configured private repository for possible redirects to third-party storage, and for Helm chart icons from third-party sources.
3. Evaluate any Helm chart that might lead to the mentioned scenario and change affected credentials if deemed necessary.
### References
Information about the same-origin check and how to disable it is available in Rancher [documentation](https://rancher.com/docs/rancher/v2.6/en/helm-charts/#repositories).
### For more information
If you have any questions or comments about this advisory:
* Reach out to [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.
* Open an issue in [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository.
* Verify our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/). | {'CVE-2021-36778'} | 2022-05-02T19:33:34Z | 2022-05-02T19:33:34Z | HIGH | null | {'CWE-200'} | {'https://github.com/rancher/rancher/security/advisories/GHSA-4fc7-hc63-7fjg', 'github.com/rancher/rancher'} | null |
Go | GHSA-6jqj-f58p-mrw3 | Denial of Service in TenderMint | ### Description
**Denial of Service**
Tendermint 0.33.0 and above allow block proposers to include signatures for the wrong block. This may happen naturally if you start a network, have it run for some time and restart it without changing the chainID. (It is a [misconfiguration](https://docs.tendermint.com/master/tendermint-core/using-tendermint.html) to reuse chainIDs.) Correct block proposers will accidentally include signatures for the wrong block if they see these signatures, and then commits won't validate, making all proposed blocks invalid. A malicious validator (even with a minimal amount of stake) can use this vulnerability to completely halt the network.
Tendermint 0.33.6 checks all the signatures are for the block with +2/3 majority before creating a commit.
**False Witness**
Tendermint 0.33.1 and above are no longer fully verifying commit signatures during block execution - they stop after +2/3. This means proposers can propose blocks that contain valid +2/3 signatures and then the rest of the signatures can be whatever they want. They can claim that all the other validators signed just by including a CommitSig with arbitrary signature data. While this doesn't seem to impact safety of Tendermint per se, it means that Commits may contain a lot of invalid data **.
_** This was already true of blocks, since they could include invalid txs filled with garbage, but in that case the application knew that they are invalid and could punish the proposer. But since applications didn't--and don't-- verify commit signatures directly (they trust Tendermint to do that), they won't be able to detect it._
This can impact incentivization logic in the application that depends on the LastCommitInfo sent in BeginBlock, which includes which validators signed. For instance, Gaia incentivizes proposers with a bonus for including more than +2/3 of the signatures. But a proposer can now claim that bonus just by including arbitrary data for the final -1/3 of validators without actually waiting for their signatures. There may be other tricks that can be played because of this.
Tendermint 0.33.6 verifies all the signatures during block execution ***.
_*** Please note that the light client does not check nil votes and exits as soon as 2/3+ of the signatures are checked._
### Impact
- All nodes
- The network stops due to having a commit with a wrong signature.
### Patches
- v0.33.6
### Workarounds
No workarounds.
### References
- https://github.com/tendermint/tendermint/issues/4926
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [tendermint/tendermint](https://github.com/tendermint/tendermint)
* Email us at [security@tendermint.com](mailto:security@tendermint.com)
More information can be found [here](https://tendermint.com/security/). | {'CVE-2020-15091'} | 2021-05-24T20:49:56Z | 2021-12-20T18:17:33Z | MODERATE | null | {'CWE-347'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15091', 'https://github.com/tendermint/tendermint/commit/480b995a31727593f58b361af979054d17d84340', 'https://github.com/tendermint/tendermint/security/advisories/GHSA-6jqj-f58p-mrw3', 'https://github.com/tendermint/tendermint/issues/4926'} | null |
Go | GHSA-6h3m-36w8-hv68 | Arbitrary file write in nats-server | (This document is canonically: <https://advisories.nats.io/CVE/CVE-2022-26652.txt>)
## Background
NATS.io is a high performance open source pub-sub distributed communication technology, built for the cloud, on-premise, IoT, and edge computing.
JetStream is the optional RAFT-based resilient persistent feature of NATS.
## Problem Description
The JetStream streams can be backed up and restored via NATS. The backup format is a tar archive file. Inadequate checks on the filenames within the archive file permit a so-called "Zip Slip" attack in the stream restore.
NATS nats-server through 2022-03-09 (fixed in release 2.7.4) did not correctly sanitize elements of the archive file, thus a user of NATS
could cause the NATS server to write arbitrary content to an attacker-controlled filename.
## Affected versions
NATS Server:
* 2.2.0 up to and including 2.7.3.
+ Introduced with JetStream Restore functionality
* Fixed with nats-io/nats-server: 2.7.4
* Docker image: nats <https://hub.docker.com/_/nats>
* NB users of OS package files from our releases: a change in goreleaser defaults, discovered late in the release process, moved the install directory from /usr/local/bin to /usr/bin; we are evaluating the correct solution for subsequent releases, but not recutting this release.
NATS Streaming Server
* 0.15.0 up to and including 0.24.2
* Fixed with nats-io/nats-streaming-server: 0.24.3
* Embeds a nats-server, but this server is the old approach which JetStream replaces, so unlikely (but not impossible) to be
configured with JS support
## Workarounds
* Disable JetStream for untrusted users.
* If only one NATS account uses JetStream, such that cross-user attacks are not an issue, and any user in that account with access to the JetStream API is fully trusted anyway, then appropriate sandboxing techniques will prevent exploit.
+ Eg, with systemd, the supplied util/nats-server-hardened.service example configuration demonstrates that NATS runs fine as an unprivileged user under ProtectSystem=strict and PrivateTmp=true restrictions; by only opening a ReadWritePaths hole for the JetStream storage area, the impact of this vulnerability is limited.
## Solution
Upgrade the NATS server to at least 2.7.4.
We fully support the util/nats-server-hardened.service configuration for running a NATS server and encourage this approach.
## Credits
This issue was reported (on 2022-03-07) to the NATS Maintainers by
Yiming Xiang, TIANJI LAB of NSFOCUS.
Thank you / 谢谢你！
| {'CVE-2022-26652'} | 2022-03-24T00:21:10Z | 2022-03-10T22:07:30Z | HIGH | null | {'CWE-22'} | {'http://www.openwall.com/lists/oss-security/2022/03/10/1', 'https://github.com/nats-io/nats-server/releases/tag/v2.7.4', 'https://github.com/nats-io/nats-server/security/advisories/GHSA-6h3m-36w8-hv68', 'https://advisories.nats.io/CVE/CVE-2022-26652.txt', 'https://github.com/nats-io/nats-server/pull/2917', 'https://github.com/nats-io/nats-streaming-server/releases/tag/v0.24.3', 'https://github.com/nats-io/nats-server', 'https://nvd.nist.gov/vuln/detail/CVE-2022-26652', 'https://github.com/nats-io/nats-server/releases'} | null |
Go | GHSA-74j8-88mm-7496 | Confused Deputy in Kubernetes | A security issue was discovered in Kubernetes where actors that control the responses of MutatingWebhookConfiguration or ValidatingWebhookConfiguration requests are able to redirect kube-apiserver requests to private networks of the apiserver. If that user can view kube-apiserver logs when the log level is set to 10, they can view the redirected responses and headers in the logs. | {'CVE-2020-8561'} | 2021-09-21T14:53:38Z | 2021-09-21T18:28:21Z | MODERATE | null | {'CWE-441', 'CWE-610'} | {'https://github.com/kubernetes/kubernetes/issues/104720', 'https://groups.google.com/g/kubernetes-security-announce/c/RV2IhwcrQsY', 'https://github.com/kubernetes/kubernetes', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8561', 'https://security.netapp.com/advisory/ntap-20211014-0002/'} | null |
Go | GHSA-58pf-pcwv-qg85 | Path traversal | This affects all versions of package github.com/u-root/u-root/pkg/uzip. It is vulnerable to both leading and non-leading relative path traversal attacks in zip file extraction. | {'CVE-2020-7665'} | 2021-05-18T20:51:25Z | 2021-05-18T21:08:28Z | MODERATE | null | {'CWE-22'} | {'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMUROOTUROOTPKGUZIP-570441', 'https://github.com/u-root/u-root/pull/1817', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7665'} | null |
Go | GHSA-8c26-wmh5-6g9v | Use of a Broken or Risky Cryptographic Algorithm in golang.org/x/crypto/ssh | golang.org/x/crypto/ssh versions 0.0.0-20220214200702-86341886e292 and prior in Go through 1.16.15 and 1.17.x through 1.17.8 allows an attacker to crash a server in certain circumstances involving AddHostKey. Version 0.0.0-20220315160706-3147a52a75dd includes a fix for the vulnerability and support for SHA-2. | {'CVE-2022-27191'} | 2022-03-30T18:48:41Z | 2022-03-19T00:01:02Z | HIGH | null | {'CWE-327'} | {'https://groups.google.com/g/golang-announce', 'https://nvd.nist.gov/vuln/detail/CVE-2022-27191', 'https://groups.google.com/g/golang-announce/c/-cp44ypCT5s', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/J5WPM42UR6XIBQNQPNQHM32X7S4LJTRX/', 'https://cs.opensource.google/go/x/crypto', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YHYRQB7TRMHDB3NEHW5XBRG7PPMUTPGV/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HHGBEGJ54DZZGTXFUQNS7ZIG3E624YAF/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QTFOIDHQRGNI4P6LYN6ILH5G443RYYKB/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZQNPPQWSTP2IX7SHE6TS4SP4EVMI5EZK/', 'https://security.netapp.com/advisory/ntap-20220429-0002/'} | null |
Go | GO-2020-0016 | null | An attacker can construct a series of bytes such that calling
[`Reader.Read`] on the bytes could cause an infinite loop. If
parsing user supplied input, this may be used as a denial of
service vector.
| {'CVE-2021-29482'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/ulikunitz/xz/commit/69c6093c7b2397b923acf82cb378f55ab2652b9b', 'https://github.com/ulikunitz/xz/security/advisories/GHSA-25xm-hr59-7c27', 'https://github.com/ulikunitz/xz/issues/35'} | null |
Go | GHSA-23fq-q7hc-993r | Improper Preservation of Permissions in HashiCorp Vault | HashiCorp Vault and Vault Enterprise 1.4.0 through 1.7.3 initialized an underlying database file associated with the Integrated Storage feature with excessively broad filesystem permissions. Fixed in Vault and Vault Enterprise 1.8.0. | {'CVE-2021-38553'} | 2021-08-30T17:16:42Z | 2021-08-30T17:22:53Z | CRITICAL | null | {'CWE-281'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-38553', 'https://discuss.hashicorp.com/t/hcsec-2021-20-vault-s-integrated-storage-backend-database-file-may-have-excessively-broad-permissions/28168', 'https://github.com/hashicorp/vault/'} | null |
Go | GHSA-hqxw-mm44-gc4r | Fragments in Path May Lead to Authorization Policy Bypass | ### Impact
Istio 1.11.0, 1.10.3 and below, and 1.9.7 and below contain a remotely exploitable vulnerability where an HTTP request with `#fragment` in the path may bypass Istio’s URI path based authorization policies.
### Patches
* Istio 1.11.1 and above
* Istio 1.10.4 and above
* Istio 1.9.8 and above
### Workarounds
A Lua filter may be written to normalize the path. This is similar to the Path normalization presented in the [Security Best Practices](https://istio.io/latest/docs/ops/best-practices/security/#case-normalization) guide.
### References
More details can be found in the [Istio Security Bulletin](https://istio.io/latest/news/security/istio-security-2021-008)
### For more information
If you have any questions or comments about this advisory, please email us at istio-security-vulnerability-reports@googlegroups.com
| {'CVE-2021-39156'} | 2021-10-21T14:27:59Z | 2021-08-30T16:16:14Z | HIGH | null | {'CWE-863'} | {'https://github.com/istio/istio/security/advisories/GHSA-hqxw-mm44-gc4r', 'https://github.com/istio/istio', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39156', 'https://istio.io/latest/news/security/istio-security-2021-008'} | null |
Go | GHSA-5m6c-jp6f-2vcv | Open Redirect in OAuth2 Proxy | ### Impact
As users can provide a redirect address for the proxy to send the authenticated user to at the end of the authentication flow. This is expected to be the original URL that the user was trying to access.
This redirect URL is checked within the proxy and validated before redirecting the user to prevent malicious actors providing redirects to potentially harmful sites. | {'CVE-2020-4037'} | 2021-05-24T20:58:18Z | 2021-12-20T17:58:59Z | MODERATE | null | {'CWE-601'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-4037', 'https://github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-5m6c-jp6f-2vcv', 'https://github.com/oauth2-proxy/oauth2-proxy/commit/ee5662e0f5001d76ec76562bb605abbd07c266a2', 'https://github.com/oauth2-proxy/oauth2-proxy/releases/tag/v6.0.0'} | null |
Go | GHSA-fv82-r8qv-ch4v | pomerium_signature is not verified in middleware in github.com/pomerium/pomerium | ### Impact
Some API endpoints under /.pomerium/ do not verify parameters with pomerium_signature. This could allow modifying parameters intended to be trusted to Pomerium.
The issue mainly affects routes responsible for sign in/out, but does not introduce an authentication bypass.
### Patches
Patched in v0.13.4
### For more information
If you have any questions or comments about this advisory
* Open an issue in [pomerium](http://github.com/pomerium/pomerium)
* Email us at [security@pomerium.com](mailto:security@pomerium.com) | {'CVE-2021-29652'} | 2021-05-20T20:47:18Z | 2021-05-21T16:24:22Z | HIGH | null | {'CWE-601'} | {'https://github.com/pomerium/pomerium/security/advisories/GHSA-fv82-r8qv-ch4v', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29652', 'https://github.com/pomerium/pomerium/pull/2048'} | null |
Go | GO-2020-0041 | null | Due to improper path santization, archives containing relative file
paths can cause files to be written (or overwritten) outside of the
target directory.
| {'CVE-2020-7668'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/unknwon/cae/commit/07971c00a1bfd9dc171c3ad0bfab5b67c2287e11', 'https://snyk.io/research/zip-slip-vulnerability'} | null |
Go | GHSA-jm34-xm8m-w958 | Open Redirect in oauth2_proxy | The Bitly oauth2_proxy in version 2.1 and earlier was affected by an open redirect vulnerability during the start and termination of the 2-legged OAuth flow. This issue was caused by improper input validation and a violation of RFC-6819 | {'CVE-2017-1000070'} | 2021-05-19T22:31:56Z | 2021-12-20T18:04:40Z | MODERATE | null | {'CWE-601'} | {'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-1000070', 'https://github.com/bitly/oauth2_proxy/issues/228', 'https://nvd.nist.gov/vuln/detail/CVE-2017-1000070', 'https://tools.ietf.org/html/rfc6819#section-5.2.3.5', 'https://github.com/bitly/oauth2_proxy/commit/289a6ccf463a425c7606178c510fc5eeb9c8b050', 'https://github.com/bitly/oauth2_proxy/pull/359'} | null |
Go | GHSA-m836-gxwq-j2pm | Improper Access Control in github.com/treeverse/lakefs | ### Impact
1. [medium] A user with write permissions to a portion of a repository may use the S3 gateway to copy any object in the repository if they know its name.
1. [medium] A user with permission to write any one of tags, branches, or commits on a repository may write all of them.
1. [low] A user with permission to read any one of tags, branches, or commits on a repository may read all of them.
1. [low] A user allowed to list objects in a repository _or_ read repository meta-data may retrieve graveler information about the location on underlying storage of all objects stored in any commit that they can view. If the user additionally has the capability to read underlying storage, they will be able to retrieve metadata associated with all objects in that commit.
### For more information
If you have any questions or comments about this advisory please:
* Email us at security@treeverse.io.
* Open an issue on https://github.com/treeverse/lakeFS/issues/new.
| null | 2021-10-27T18:58:30Z | 2021-10-28T16:27:03Z | MODERATE | null | {'CWE-284'} | {'https://github.com/treeverse/lakeFS/security/advisories/GHSA-m836-gxwq-j2pm', 'https://github.com/treeverse/lakeFS'} | null |
Go | GHSA-g9wh-3vrx-r7hg | OctoRPKI crashes when processing GZIP bomb returned via malicious repository | OctoRPKI tries to load the entire contents of a repository in memory, and in the case of a GZIP bomb, unzip it in memory, making it possible to create a repository that makes OctoRPKI run out of memory (and thus crash).
## Patches
## For more information
If you have any questions or comments about this advisory email us at security@cloudflare.com
| {'CVE-2021-3912'} | 2021-11-10T18:19:37Z | 2021-11-10T20:39:23Z | MODERATE | null | {'CWE-400'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-3912', 'https://github.com/cloudflare/cfrpki/security/advisories/GHSA-g9wh-3vrx-r7hg', 'github.com/cloudflare/cfrpki', 'https://www.debian.org/security/2022/dsa-5041'} | null |
Go | GO-2021-0071 | null | A race between chown and chmod operations during a container filesystem shift
may allow a user who can modify the filesystem to chmod an arbitary path of
their choice, rather than the expected path.
| {'CVE-2015-1340'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/lxc/lxd/pull/1189', 'https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1502270', 'https://github.com/lxc/lxd/commit/19c6961cc1012c8a529f20807328a9357f5034f4'} | null |
Go | GHSA-w6v2-qchm-grj7 | Insecure permissions on user namespace / fakeroot temporary rootfs in Singularity | ### Impact
Insecure permissions on temporary directories used in fakeroot or user namespace container execution.
When a Singularity action command (run, shell, exec) is run with the fakeroot or user namespace option, Singularity will extract a container image to a temporary sandbox directory. Due to insecure permissions on the temporary directory it is possible for any user with access to the system to read the contents of the image. Additionally, if the image contains a world-writable file or directory, it is possible for a user to inject arbitrary content into the running container.
### 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-25039'} | 2021-05-24T17:12:01Z | 2021-12-20T18:25:46Z | HIGH | null | {'CWE-732', 'CWE-668'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-25039', 'http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00070.html', 'https://medium.com/sylabs', 'https://github.com/hpcng/singularity/security/advisories/GHSA-w6v2-qchm-grj7', 'http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00088.html'} | null |
Go | GHSA-4mf2-f3wh-gvf2 | Subdomain checking of whitelisted domains could allow unintended redirects in oauth2-proxy | ### Impact
_What kind of vulnerability is it? Who is impacted?_
For users that use the whitelist domain feature, a domain that ended in a similar way to the intended domain could have been allowed as a redirect.
For example, if a whitelist domain was configured for `.example.com`, the intention is that subdomains of `example.com` are allowed.
Instead, `example.com` and `badexample.com` could also match.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
This is fixed in version 7.0.0 onwards.
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
Disable the whitelist domain feature and run separate OAuth2 Proxy instances for each subdomain.
# Original Issue Posted by @semoac:
Whitelist Domain feature is not working as expected because is not matching a dot to ensure the redirect is a subdomain.
## Expected Behavior
If whitelist domain is set to `.example.com` , then `hack.alienexample.com` should be rejected as a valid redirect.
## Current Behavior
The code is removing the `dot` from `.example.com` and only checking if the redirect string end with `example.com`
## Possible Solution
Here
https://github.com/oauth2-proxy/oauth2-proxy/blob/c377466411f2aee180a732187edb638f2f7e57fb/oauthproxy.go#L661
Include the dot when checking the string:
```
strings.HasSuffix(redirectHostname, "." + domainHostname)
```
## Steps to Reproduce (for bugs)
```
package main
import (
"fmt"
"strings"
)
func validOptionalPort(port string) bool {
if port == "" || port == ":*" {
return true
}
if port[0] != ':' {
return false
}
for _, b := range port[1:] {
if b < '0' || b > '9' {
return false
}
}
return true
}
func splitHostPort(hostport string) (host, port string) {
host = hostport
colon := strings.LastIndexByte(host, ':')
if colon != -1 && validOptionalPort(host[colon:]) {
host, port = host[:colon], host[colon+1:]
}
if strings.HasPrefix(host, "[") && strings.HasSuffix(host, "]") {
host = host[1 : len(host)-1]
}
return
}
func main() {
domain := ".example.com"
domainHostname, _ := splitHostPort(strings.TrimLeft(domain, "."))
redirectHostname := "https://hack.alienexample.com"
if (strings.HasPrefix(domain, ".") && strings.HasSuffix(redirectHostname, domainHostname)) { fmt.Println("This should not have happen.")}
}
```
Users of `github.com/oauth2-proxy/oauth2-proxy` are advised to update to `github.com/oauth2-proxy/oauth2-proxy/v7` | {'CVE-2021-21291'} | 2021-05-21T21:37:23Z | 2021-05-25T18:42:20Z | LOW | null | {'CWE-601'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-21291', 'https://github.com/oauth2-proxy/oauth2-proxy/releases/tag/v7.0.0', 'https://pkg.go.dev/github.com/oauth2-proxy/oauth2-proxy/v7', 'https://github.com/oauth2-proxy/oauth2-proxy/commit/780ae4f3c99b579cb2ea9845121caebb6192f725', 'https://github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-4mf2-f3wh-gvf2'} | null |
Go | GHSA-c8x3-rg72-fwwg | Privilege escalation in Hashicorp Nomad | HashiCorp Nomad and Nomad Enterprise Raft RPC layer allows non-server agents with a valid certificate signed by the same CA to access server-only functionality, enabling privilege escalation. Fixed in 1.0.10 and 1.1.4. | {'CVE-2021-37218'} | 2021-09-14T18:46:53Z | 2021-09-08T20:14:38Z | HIGH | null | {'CWE-295'} | {'https://github.com/hashicorp/nomad', 'https://www.hashicorp.com/blog/category/nomad', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37218', 'https://discuss.hashicorp.com/t/hcsec-2021-21-nomad-raft-rpc-privilege-escalation/29023'} | null |
Go | GHSA-fx5p-f64h-93xc | Opened exploitable ports in default docker-compose.yaml in go-ipfs | ### Impact
Allows admin API access to the IPFS node.
### Who ?
This affects people running the [docker-compose.yaml](https://github.com/ipfs/go-ipfs/blob/master/docker-compose.yaml) service in an environment where the docker host is directly attached to a public or untrusted IP. In the vulnerable version, the private API endpoint is publicly forwarded by exposing it as `0.0.0.0:5001` on the host machine.
If the host machine is hidden behind a firewall or NAT (and the LAN is trusted for NAT), this is not an immediate issue because of the protection from the firewall or NAT. That said, we still recommend users update to follow security best practices of not putting unnecessary dependency on a working firewall.
### Patches
This issue is in [docker-compose.yaml](https://github.com/ipfs/go-ipfs/blob/master/docker-compose.yaml). Users need to replace their current `docker-compose.yaml` file with a version `0.12.1` or later.
There is no need to update any of the binaries. Users running previous versions like `0.12.0` or earlier can download the `0.12.1` `docker-compose.yaml` file. You can replace a vulnerable `docker-compose.yaml` file with a the new one with:
```
curl https://raw.githubusercontent.com/ipfs/go-ipfs/v0.12.1/docker-compose.yaml > docker-compose.yaml
```
### How to test if you are vulnerable
#### Binding check on the host
On the host machine, while IPFS is running, run as root:
```bash
netstat -lnp | grep ":5001"
```
The output will be a list of listeners bound to `:5001`.
You then need to check that those listeners are private and preferably even localhost IPs.
⚠️ If this listener is on `0.0.0.0` or a public IP you are very likely vulnerable.
#### Remote hailing
While IPFS is running, you can try to contact the API from a remote machine. (Replace `1.2.3.4` with your node public IP. Or if you want to test in an untrusted NAT, then substitute the LAN IP instead.)
```bash
curl -X POST http://1.2.3.4:5001/api/v0/version
```
⚠️ If you see any json outputted (e.g., `{"Commit": "<string>","Golang": "<string>","Repo": "<string>","System": "<string>","Version": "<string>"}`), then you are vulnerable.
If it **fails**, then you are safe.
### For more information
If you have any questions or comments about this advisory:
* Please first read https://docs.ipfs.io/reference/http/api/ about best practices
* Ask in [IPFS Discord #ipfs-chatter](https://discord.gg/ipfs)
* Open an issue in [go-ipfs](https://github.com/ipfs/go-ipfs)
| null | 2022-04-04T21:23:55Z | 2022-04-04T21:23:55Z | MODERATE | null | null | {'https://github.com/ipfs/go-ipfs/pull/8773', 'https://github.com/ipfs/go-ipfs', 'https://github.com/ipfs/go-ipfs/commit/816a128aaf963d72c4930852ce32b9a4e31924a1', 'https://github.com/ipfs/go-ipfs/releases/tag/v0.12.1', 'https://github.com/ipfs/go-ipfs/security/advisories/GHSA-fx5p-f64h-93xc'} | null |
Go | GHSA-5796-p3m6-9qj4 | Denial of Service (DoS) in Cloud Foundry Routing | Cloud Foundry Routing, all versions before 0.193.0, does not properly validate nonce input. A remote unauthorized malicious user could forge a route service request using an invalid nonce that will cause the Gorouter to crash. | {'CVE-2019-11289'} | 2021-05-17T21:24:54Z | 2021-05-18T15:31:39Z | HIGH | null | {'CWE-20'} | {'https://www.cloudfoundry.org/blog/cve-2019-11289', 'https://nvd.nist.gov/vuln/detail/CVE-2019-11289'} | null |
Go | GHSA-xcf7-q56x-78gh | Connection descriptor exhaustion in proxyproto | The package `github.com/pires/go-proxyproto` before 0.6.0 are vulnerable to Denial of Service (DoS) via creating connections without the proxy protocol header. | {'CVE-2021-23409'} | 2021-07-26T17:31:53Z | 2021-07-26T21:23:49Z | HIGH | null | {'CWE-400'} | {'https://github.com/pires/go-proxyproto/pull/74/commits/cdc63867da24fc609b727231f682670d0d1cd346', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23409', 'https://github.com/pires/go-proxyproto/pull/74', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMPIRESGOPROXYPROTO-1316439', 'https://github.com/pires/go-proxyproto/issues/65', 'https://github.com/pires/go-proxyproto/releases/tag/v0.6.0'} | null |
Go | GHSA-2jhh-5xm2-j4gf | Improper Authentication in HashiCorp Nomad | HashiCorp Nomad and Nomad Enterprise up to 1.0.13, 1.1.7, and 1.2.0, with the QEMU task driver enabled, allowed authenticated users with job submission capabilities to bypass the configured allowed image paths. Fixed in 1.0.14, 1.1.8, and 1.2.1. | {'CVE-2021-43415'} | 2021-12-06T22:11:44Z | 2021-12-10T20:17:55Z | HIGH | null | {'CWE-287'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-43415', 'https://www.hashicorp.com/blog/category/nomad', 'https://discuss.hashicorp.com/t/hcsec-2021-31-nomad-qemu-task-driver-allowed-paths-bypass-with-job-args/32288', 'https://github.com/hashicorp/nomad'} | null |
Go | GHSA-x5m6-jh4r-34mv | Arbitrary File Overwrite in hub | The am function in lib/hub/commands.rb in hub before 1.12.1 allows local users to overwrite arbitrary files via a symlink attack on a temporary patch file. | {'CVE-2014-0177'} | 2021-05-20T20:32:04Z | 2022-02-15T01:07:53Z | MODERATE | null | {'CWE-377'} | {'https://secunia.com/advisories/58273', 'https://github.com/github/hub/commit/016ec99d25b1cb83cb4367e541177aa431beb600', 'https://nvd.nist.gov/vuln/detail/CVE-2014-0177'} | null |
Go | GHSA-xjqr-g762-pxwp | Improper limitation of path name | An improper limitation of path name flaw was found in containernetworking/cni in versions before 0.8.1. When specifying the plugin to load in the 'type' field in the network configuration, it is possible to use special elements such as "../" separators to reference binaries elsewhere on the system. This flaw allows an attacker to execute other existing binaries other than the cni plugins/types, such as 'reboot'. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability. | {'CVE-2021-20206'} | 2021-09-10T17:12:24Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-20', 'CWE-22'} | {'https://github.com/containernetworking/cni', 'https://bugzilla.redhat.com/show_bug.cgi?id=1919391', 'https://github.com/containernetworking/cni/pull/808', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMCONTAINERNETWORKINGCNIPKGINVOKE-1070549', 'https://nvd.nist.gov/vuln/detail/CVE-2021-20206'} | null |
Go | GHSA-7gfg-6934-mqq2 | Improper Authenication in Pion DTLS | handleIncomingPacket in conn.go in Pion DTLS before 1.5.2 lacks a check for application data with epoch 0, which allows remote attackers to inject arbitrary unencrypted data after handshake completion. | {'CVE-2019-20786'} | 2021-05-25T19:54:18Z | 2021-06-29T21:34:57Z | CRITICAL | null | {'CWE-287'} | {'https://www.usenix.org/conference/usenixsecurity20/presentation/fiterau-brostean', 'https://www.usenix.org/system/files/sec20fall_fiterau-brostean_prepub.pdf', 'https://github.com/pion/dtls/commit/fd73a5df2ff0e1fb6ae6a51e2777d7a16cc4f4e0', 'https://github.com/pion/dtls/compare/v1.5.1...v1.5.2', 'https://nvd.nist.gov/vuln/detail/CVE-2019-20786'} | null |
Go | GHSA-rrm8-32g4-w8m3 | Cross-site Request Forgery (CSRF) | CSRF in Bitly oauth2_proxy 2.1 during authentication flow | {'CVE-2017-1000069'} | 2021-05-12T18:30:22Z | 2021-12-20T18:04:46Z | HIGH | null | {'CWE-352'} | {'https://nvd.nist.gov/vuln/detail/CVE-2017-1000069', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-1000069', 'https://github.com/bitly/oauth2_proxy/commit/55085d9697962668fd4e43e8e4644144fe83cd93', 'https://github.com/bitly/oauth2_proxy/pull/360'} | null |
Go | GHSA-wmwp-pggc-h4mj | Cross-site Scripting in Documize | domain/section/markdown/markdown.go in Documize before 3.5.1 mishandles untrusted Markdown content. This was addressed by adding the bluemonday HTML sanitizer to defend against XSS. | {'CVE-2019-19619'} | 2021-05-17T21:29:00Z | 2021-05-18T15:30:30Z | MODERATE | null | {'CWE-79'} | {'https://github.com/documize/community/commit/a4384210d4d0d6b18e6fdb7e155de96d4a1cf9f3', 'https://github.com/documize/community/releases/tag/v3.5.1', 'https://github.com/documize/community/compare/v3.5.0...v3.5.1', 'https://nvd.nist.gov/vuln/detail/CVE-2019-19619'} | null |
Go | GO-2021-0067 | null | Using Reader.Open on an archive containing a file with a path
prefixed by "../" will cause a panic due to a stack overflow.
If parsing user supplied archives, this may be used as a
denial of service vector.
| {'CVE-2021-27919'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/golang/go/issues/44916', 'https://github.com/golang/go/commit/cd3b4ca9f20fd14187ed4cdfdee1a02ea87e5cd8', 'https://go-review.googlesource.com/c/go/+/300489'} | null |
Go | GHSA-3fx4-7f69-5mmg | Integer Overflow in go-jose | go-jose before 1.0.5 suffers from a CBC-HMAC integer overflow on 32-bit architectures. An integer overflow could lead to authentication bypass for CBC-HMAC encrypted ciphertexts on 32-bit architectures. | {'CVE-2016-9123'} | 2021-05-20T16:26:07Z | 2021-06-23T17:14:12Z | HIGH | null | {'CWE-190'} | {'https://nvd.nist.gov/vuln/detail/CVE-2016-9123', 'https://github.com/square/go-jose/commit/789a4c4bd4c118f7564954f441b29c153ccd6a96', 'https://hackerone.com/reports/165170', 'https://www.openwall.com/lists/oss-security/2016/11/03/1'} | null |
Go | GHSA-997c-fj8j-rq5h | Arbitrary Code Execution | Docker 1.3.2 allows remote attackers to execute arbitrary code with root privileges via a crafted (1) image or (2) build in a Dockerfile in an LZMA (.xz) archive, related to the chroot for archive extraction. | {'CVE-2014-9357'} | 2021-05-12T17:42:53Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-285'} | {'https://github.com/docker/docker/compare/aef842e7dfb534aba22c3c911de525ce9ac12b72...313a1b7620910e47d888f8b0a6a5eb06ad9c1ff2', 'https://github.com/moby/moby/blob/master/CHANGELOG.md#133-2014-12-11', 'https://groups.google.com/forum/#!msg/docker-user/nFAz-B-n4Bw/0wr3wvLsnUwJ', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-9357', 'http://www.securityfocus.com/archive/1/534215/100/0/threaded', 'https://nvd.nist.gov/vuln/detail/CVE-2014-9357', 'https://groups.google.com/forum/#%21msg/docker-user/nFAz-B-n4Bw/0wr3wvLsnUwJ'} | null |
Go | GHSA-m6gx-rhvj-fh52 | Denial of service in go-ethereum due to CVE-2020-28362 | ### Impact
Versions of Geth built with Go `<1.15.5` or `<1.14.12` are most likely affected by a critical DoS-related security vulnerability. The golang team has registered the underlying flaw as ‘CVE-2020-28362’.
We recommend all users to rebuild (ideally `v1.9.24`) with Go `1.15.5` or `1.14.12`, to avoid node crashes. Alternatively, if you are running binaries distributed via one of our official channels, we’re going to release `v1.9.24` ourselves built with Go `1.15.5`.
### Patches
This is not an issue in go-ethereum, rebuilding an older version with Go `1.15.5` or `1.14.12` will suffice to address the vulnerability.
### Workarounds
Rebuilding with Go `1.15.5` or `1.14.12` will suffice to address the vulnerability.
### References
- https://blog.ethereum.org/2020/11/12/geth_security_release/
- https://groups.google.com/g/golang-announce/c/NpBGTTmKzpM
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)
* Email us at [security@ethereum.org](mailto:security@ethereum.org)
| null | 2021-10-08T21:25:42Z | 2021-06-29T21:13:54Z | CRITICAL | null | null | {'https://github.com/ethereum/go-ethereum/security/advisories/GHSA-m6gx-rhvj-fh52', 'https://github.com/ethereum/go-ethereum'} | null |
Go | GO-2021-0088 | null | Skip ignores unknown fields, rather than failing. A malicious user can craft small
messages with unknown fields which can take significant resources to parse. If a
server accepts messages from an untrusted user, it may be used as a denial of service
vector.
| {'CVE-2019-3564'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://www.facebook.com/security/advisories/cve-2019-3564', 'https://github.com/facebook/fbthrift/commit/c461c1bd1a3e130b181aa9c854da3030cd4b5156'} | null |
Go | GHSA-gv2h-gf8m-r68j | Exposure of server configuration in github.com/go-vela/server | ### Impact
_What kind of vulnerability is it? Who is impacted?_
* The ability to expose configuration set in the [Vela server](https://github.com/go-vela/server) via [pipeline template functionality](https://go-vela.github.io/docs/templates/overview/).
* It impacts all users of Vela.
Sample of template exposing server configuration [using Sprig's `env` function](http://masterminds.github.io/sprig/os.html):
```yaml
metadata:
template: true
steps:
- name: sample
image: alpine:latest
commands:
# OAuth client ID for Vela <-> GitHub communication
- echo {{ env "VELA_SOURCE_CLIENT" }}
# secret used for server <-> worker communication
- echo {{ env "VELA_SECRET" }}
```
### Patches
_Has the problem been patched? What versions should users upgrade to?_
* Upgrade to `0.6.1`
#### Additional Recommended Action(s)
* Rotate all secrets
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
* No
### For more information
If you have any questions or comments about this advisory:
* Email us at [vela@target.com](mailto:vela@target.com) | {'CVE-2020-26294'} | 2022-02-15T00:19:57Z | 2022-02-15T00:19:57Z | HIGH | null | {'CWE-200', 'CWE-78'} | {'https://pkg.go.dev/github.com/go-vela/compiler/compiler', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26294', 'https://github.com/helm/helm/blob/6297c021cbda1483d8c08a8ec6f4a99e38be7302/pkg/engine/funcs.go#L46-L47', 'https://github.com/go-vela/compiler/commit/f1ace5f8a05c95c4d02264556e38a959ee2d9bda', 'https://github.com/go-vela/compiler/security/advisories/GHSA-gv2h-gf8m-r68j'} | null |
Go | GHSA-hx8w-ghh8-r4xf | Write access to the Catalog for any user when restricted-admin role is enabled in Rancher | ### Impact
This vulnerability only affects customers using the [`restricted-admin`](https://rancher.com/docs/rancher/v2.6/en/admin-settings/rbac/global-permissions/#restricted-admin) role in Rancher. For this role to be active, Rancher must be bootstrapped with the environment variable `CATTLE_RESTRICTED_DEFAULT_ADMIN=true` or the configuration flag `restrictedAdmin=true`.
A flaw was discovered in Rancher versions from 2.5.0 up to and including 2.5.12 and from 2.6.0 up to and including 2.6.3 where the `global-data` role in `cattle-global-data` namespace grants write access to the Catalogs. Since each user with any level of catalog access was bound to the `global-data` role, this grants write access to templates (`CatalogTemplates`) and template versions (`CatalogTemplateVersions`) for any user with any level of catalog access. New users created in Rancher are by default assigned to the `user` role (standard user), which is not designed to grant write catalog access. This vulnerability effectively elevates the privilege of any user to write access for the catalog template and catalog template version resources.
A malicious user could abuse this vulnerability to:
1. Make applications or individual versions of applications visible or hidden on the UI, by modifying `version` and `rancherMaxVersion` fields.
2. Change the logo (field `icon`) of an application or template to an arbitrary image.
3. Make a chart appear as a trusted or partner chart. This can be abused to make less trusted charts, such as customer defined charts, appear more legitimate than they are, by adding the label `io.rancher.certified: partner`.
4. Swap template versions between templates of charts inside the same catalog. This can be exploited to swap the files from one chart or version to another, by changing `versionDir` field. When a user on the target cluster deploys their chart, it will deploy the modified version.
This vulnerability does not allow to modify the base64 encoded `files` fields of the `templateVersions`, so one cannot inject arbitrary data to charts that have already been pulled from their respective catalog.
Without access to the Catalog, malicious users are limited to injecting apps which already exist in a registered catalog. They would need write access to the catalog or external write access to a source repo to inject arbitrary code.
### Patches
Patched versions include releases 2.5.13, 2.6.4 and later versions.
### Workarounds
Limit access in Rancher to trusted users. There is not a direct mitigation besides upgrading to the patched Rancher versions.
**Note:** If you use the `restricted-admin` as the default admin role in your environment, it's highly advised to review `CatalogTemplates` and `CatalogTemplateVersions` for possible malicious modifications.
### For more information
If you have any questions or comments about this advisory:
* Reach out to [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.
* Open an issue in [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository.
* Verify our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/). | {'CVE-2021-4200'} | 2022-05-02T19:26:55Z | 2022-05-02T19:26:55Z | HIGH | null | {'CWE-285', 'CWE-269'} | {'https://rancher.com/docs/rancher/v2.6/en/admin-settings/rbac/global-permissions/#restricted-admin', 'github.com/rancher/rancher', 'https://github.com/rancher/rancher/security/advisories/GHSA-hx8w-ghh8-r4xf'} | null |
Go | GHSA-q6gq-997w-f55g | Infinite loop in xz | Go before 1.13.15 and 14.x before 1.14.7 can have an infinite read loop in ReadUvarint and ReadVarint in encoding/binary via invalid inputs. | {'CVE-2020-16845'} | 2021-06-18T22:05:40Z | 2021-12-16T19:16:40Z | HIGH | null | {'CWE-835'} | {'https://security.netapp.com/advisory/ntap-20200924-0002/', 'http://lists.opensuse.org/opensuse-security-announce/2020-08/msg00021.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KWRBAH4UZJO3RROQ72SYCUPFCJFA22FO/', 'https://lists.debian.org/debian-lts-announce/2020/11/msg00037.html', 'https://github.com/ulikunitz/xz/commit/69c6093c7b2397b923acf82cb378f55ab2652b9b', 'https://lists.debian.org/debian-lts-announce/2020/11/msg00038.html', 'https://github.com/ulikunitz/xz/issues/35', 'https://groups.google.com/forum/#!topic/golang-announce/NyPIaucMgXo', 'https://groups.google.com/forum/#!topic/golang-announce/_ulYYcIWg3Q', 'https://nvd.nist.gov/vuln/detail/CVE-2020-16845', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TACQFZDPA7AUR6TRZBCX2RGRFSDYLI7O/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6RCFJTMKHY5ICGEM5BUFUEDDGSPJ25XU/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WV2VWKFTH4EJGZBZALVUJQJOAQB5MDQ4/', 'http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00029.html', 'http://lists.opensuse.org/opensuse-security-announce/2020-08/msg00028.html', 'https://www.debian.org/security/2021/dsa-4848', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00030.html'} | null |
Go | GHSA-gmq2-39ff-f5qg | A failed upgrade may lead to hung goroutines | ### Impact
Processes using tableflip may encounter hung goroutines in the parent process, after a failed upgrade.
The Go runtime has annoying behaviour around setting and clearing
O_NONBLOCK: exec.Cmd.Start() ends up calling os.File.Fd() for any
file in exec.Cmd.ExtraFiles. os.File.Fd() disables both the use
of the runtime poller for the file and clears O_NONBLOCK from
the underlying open file descriptor.
This can lead to goroutines hanging in a parent process, after at least
one failed upgrade. The bug manifests in goroutines which rely on
either a deadline or interruption via Close() to be unblocked being stuck
in read or accept like syscalls. As far as I can tell we've not experienced
this problem in production, so it's most likely quite rare.
### Patches
The problem has been fixed in v1.2.2.
### Workarounds
None.
### References
* https://github.com/cloudflare/tableflip/commit/cae714b289e199db5da5f08af861ea65be6232c0 | null | 2021-05-21T14:40:36Z | 2021-05-21T16:25:48Z | LOW | null | null | {'https://github.com/cloudflare/tableflip/security/advisories/GHSA-gmq2-39ff-f5qg', 'https://github.com/cloudflare/tableflip/commit/cae714b289e199db5da5f08af861ea65be6232c0'} | null |
Go | GO-2020-0003 | null | If the application accepts
[slice parameters](https://revel.github.io/manual/parameters.html#slices), an
attacker can cause the application to allocate large amounts of memory and
crash by manipulating the request query.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/revel/revel/commit/d160ecb72207824005b19778594cbdc272e8a605', 'https://github.com/revel/revel/pull/1427', 'https://github.com/revel/revel/issues/1424'} | null |
Go | GHSA-vfvf-6gx5-mqv6 | Incorrect Authorization in ORY Oathkeeper | ORY Oathkeeper is an Identity & Access Proxy (IAP) and Access Control Decision API that authorizes HTTP requests based on sets of Access Rules. When you make a request to an endpoint that requires the scope `foo` using an access token granted with that `foo` scope, introspection will be valid and that token will be cached. The problem comes when a second requests to an endpoint that requires the scope `bar` is made before the cache has expired. Whether the token is granted or not to the `bar` scope, introspection will be valid. A patch will be released with `v0.38.12-beta.1`. Per default, caching is disabled for the `oauth2_introspection` authenticator. When caching is disabled, this vulnerability does not exist. The cache is checked in [`func (a *AuthenticatorOAuth2Introspection) Authenticate(...)`](https://github.com/ory/oathkeeper/blob/6a31df1c3779425e05db1c2a381166b087cb29a4/pipeline/authn/authenticator_oauth2_introspection.go#L152). From [`tokenFromCache()`](https://github.com/ory/oathkeeper/blob/6a31df1c3779425e05db1c2a381166b087cb29a4/pipeline/authn/authenticator_oauth2_introspection.go#L97) it seems that it only validates the token expiration date, but ignores whether the token has or not the proper scopes. The vulnerability was introduced in PR #424. During review, we failed to require appropriate test coverage by the submitter which is the primary reason that the vulnerability passed the review process. | {'CVE-2021-32701'} | 2021-06-23T20:38:29Z | 2021-06-24T20:16:02Z | HIGH | null | {'CWE-863'} | {'https://github.com/ory/oathkeeper/pull/424', 'https://github.com/ory/oathkeeper/commit/1f9f625c1a49e134ae2299ee95b8cf158feec932', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32701', 'https://github.com/ory/oathkeeper/security/advisories/GHSA-qvp4-rpmr-xwrr'} | null |
Go | GHSA-f6px-w8rh-7r89 | Data race in Beego | The File Session Manager in Beego 1.10.0 allows local users to read session files because there is a race condition involving file creation within a directory with weak permissions. | {'CVE-2019-16354'} | 2021-07-22T21:51:41Z | 2021-08-02T17:15:05Z | MODERATE | null | {'CWE-732', 'CWE-362'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-16354', 'https://github.com/astaxie/beego/blob/develop/session/sess_file.go#L141', 'https://github.com/astaxie/beego/issues/3763', 'https://github.com/beego/beego/pull/3975/commits/f99cbe0fa40936f2f8dd28e70620c559b6e5e2fd', 'https://github.com/beego/beego/issues/3763'} | null |
Go | GHSA-r33q-22hv-j29q | Denial of service in github.com/ethereum/go-ethereum | ### Impact
A DoS vulnerability can make a LES server crash via malicious `GetProofsV2` request from a connected LES client.
### Patches
The vulnerability was patched in https://github.com/ethereum/go-ethereum/pull/21896.
### Workarounds
This vulnerability only concerns users explicitly enabling `les` server; disabling `les` prevents the exploit.
It can also be patched by manually applying the patch in https://github.com/ethereum/go-ethereum/pull/21896.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)
* Email us at [security@ethereum.org](mailto:security@ethereum.org) | {'CVE-2020-26264'} | 2021-05-21T21:45:23Z | 2021-06-29T21:14:07Z | MODERATE | null | {'CWE-400'} | {'https://github.com/ethereum/go-ethereum/commit/bddd103a9f0af27ef533f04e06ea429cf76b6d46', 'https://github.com/ethereum/go-ethereum/security/advisories/GHSA-r33q-22hv-j29q', 'https://github.com/ethereum/go-ethereum/releases/tag/v1.9.25', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26264', 'https://github.com/ethereum/go-ethereum/pull/21896'} | null |
Go | GHSA-7qw8-847f-pggm | Improper Locking in github.com/containers/storage | A deadlock vulnerability was found in 'github.com/containers/storage' in versions before 1.28.1. When a container image is processed, each layer is unpacked using `tar`. If one of those layers is not a valid `tar` archive this causes an error leading to an unexpected situation where the code indefinitely waits for the tar unpacked stream, which never finishes. An attacker could use this vulnerability to craft a malicious image, which when downloaded and stored by an application using containers/storage, would then cause a deadlock leading to a Denial of Service (DoS). | {'CVE-2021-20291'} | 2021-05-04T19:15:55Z | 2021-05-10T19:35:07Z | HIGH | null | {'CWE-400', 'CWE-667'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SPYOHNG2Q7DCAQZMGYLMENLKALGDLG3X/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZNMB7O2UIXE34PGSCSOULGHPX5LIJBMM/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/R5D7XL7FL24TWFMGQ3K2S72EOUSLZMKL/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WX24EITRXVHDM5M223BVTJA2ODF2FSHI/', 'https://github.com/containers/storage/commit/306fcabc964470e4b3b87a43a8f6b7d698209ee1', 'https://nvd.nist.gov/vuln/detail/CVE-2021-20291', 'https://unit42.paloaltonetworks.com/cve-2021-20291/', 'https://bugzilla.redhat.com/show_bug.cgi?id=1939485'} | null |
Go | GHSA-44gg-pmqr-4669 | Access Restriction Bypass in Docker | Docker 1.3.0 through 1.3.1 allows remote attackers to modify the default run profile of image containers and possibly bypass the container by applying unspecified security options to an image. | {'CVE-2014-6408'} | 2021-05-20T16:28:01Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-285'} | {'https://github.com/docker/docker/commit/c9379eb3fbbc484c056f5a5e49d8d0b755a29c45', 'https://secunia.com/advisories/60241', 'https://lists.opensuse.org/opensuse-security-announce/2014-12/msg00009.html', 'https://www.openwall.com/lists/oss-security/2014/11/24/5', 'https://nvd.nist.gov/vuln/detail/CVE-2014-6408', 'https://docs.docker.com/v1.3/release-notes/', 'https://lists.fedoraproject.org/pipermail/package-announce/2014-December/145154.html', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-6408', 'https://secunia.com/advisories/60171'} | null |
Go | GO-2020-0015 | null | An attacker could provide a single byte to a [`UTF16`] decoder instantiated with
[`UseBOM`] or [`ExpectBOM`] to trigger an infinite loop if the [`String`] function on
the [`Decoder`] is called, or the [`Decoder`] is passed to [`transform.String`].
If used to parse user supplied input, this may be used as a denial of service
vector.
| {'CVE-2020-14040'} | 2021-06-07T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/golang/text/commit/23ae387dee1f90d29a23c0e87ee0b46038fbed0e', 'https://github.com/golang/go/issues/39491', 'https://go-review.googlesource.com/c/text/+/238238', 'https://groups.google.com/g/golang-announce/c/bXVeAmGOqz0'} | null |
Go | GHSA-9cx9-x2gp-9qvh | CRLF vulnerability in Fiber | ### Impact
The filename that is given in [c.Attachment()](https://docs.gofiber.io/ctx#attachment) is not escaped, and therefore vulnerable for a CRLF injection attack. I.e. an attacker could upload a custom filename and then give the link to the victim. With this filename, the attacker can change the name of the downloaded file, redirect to another site, change the authorization header, etc.
### Steps to reproduce
```go
package main
import "github.com/gofiber/fiber"
const badFileName = "another secret document.pdf\"\r\nLocation: google.com\r\nAuthorization: \"example_of_session_fixation"
func splitTheResponse(c *fiber.Ctx) {
c.Attachment(badFileName)
}
func main() {
app := fiber.New()
app.Get("/attack", splitTheResponse)
app.Listen("127.0.0.1:8080")
}
```
```
HTTP/1.1 200 OK
Date: Fri, 10 Jul 2020 19:47:04 GMT
Content-Type: application/octet-stream
Content-Length: 0
Content-Disposition: attachment; filename="another secret document.pdf"
Location: google.com
Authorization: "example_of_session_fixation"
```
### Patches
This issue has been patched in `v1.12.6` with commit [579](https://github.com/gofiber/fiber/pull/579/commits/f698b5d5066cfe594102ae252cd58a1fe57cf56f) escaping the filename by default.
### Workarounds
You could of course serialize the input yourself before passing it to `ctx.Attachment()`, this is actually a good practice by default. But in case you forget, we got you covered 👍
### References
A CRLF injection attack is one of several types of injection attacks. It can be used to escalate to more malicious attacks such as Cross-site Scripting (XSS), page injection, web cache poisoning, cache-based defacement, and more. A CRLF injection vulnerability exists if an attacker can inject the CRLF characters into a web application, for example using a user input form or an HTTP request, [see acunetix](https://www.acunetix.com/websitesecurity/crlf-injection/)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [gofiber/fiber](https://github.com/gofiber/fiber)
* Join us on [Discord](https://gofiber.io/discord) | {'CVE-2020-15111'} | 2021-10-08T20:35:58Z | 2021-06-29T21:24:28Z | MODERATE | null | {'CWE-93', 'CWE-74'} | {'https://github.com/gofiber/fiber/security/advisories/GHSA-9cx9-x2gp-9qvh', 'https://github.com/gofiber/fiber/pull/579/commits/f698b5d5066cfe594102ae252cd58a1fe57cf56f', 'https://github.com/gofiber/fiber', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15111'} | null |
Go | GHSA-2575-pghm-6qqx | Incorrect Permission Assignment for Critical Resource and Use of Cache Containing Sensitive Information in Kubernetes | In Kubernetes v1.8.x-v1.14.x, schema info is cached by kubectl in the location specified by --cache-dir (defaulting to $HOME/.kube/http-cache), written with world-writeable permissions (rw-rw-rw-). If --cache-dir is specified and pointed at a different location accessible to other users/groups, the written files may be modified by other users/groups and disrupt the kubectl invocation. | {'CVE-2019-11244'} | 2021-05-07T17:22:21Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-732', 'CWE-524'} | {'http://www.securityfocus.com/bid/108064', 'https://github.com/kubernetes/client-go/commit/790a4f63632139cf6731014d00a9a8338f1fbd7d', 'https://access.redhat.com/errata/RHSA-2020:0074', 'https://access.redhat.com/errata/RHSA-2019:3942', 'https://github.com/kubernetes/kubernetes/issues/76676', 'https://github.com/kubernetes/kubernetes/pull/77874/commits/f228ae3364729caed59087e23c42868454bc3ff4', 'https://security.netapp.com/advisory/ntap-20190509-0002/', 'https://nvd.nist.gov/vuln/detail/CVE-2019-11244', 'https://github.com/kubernetes/kubernetes/pull/77874', 'https://access.redhat.com/errata/RHSA-2020:0020'} | null |
Go | GHSA-877x-32pm-p28x | Link Following in Kata Runtime | A malicious guest compromised before a container creation (e.g. a malicious guest image or a guest running multiple containers) can trick the kata runtime into mounting the untrusted container filesystem on any host path, potentially allowing for code execution on the host. This issue affects Kata Containers 1.11 versions earlier than 1.11.1; Kata Containers 1.10 versions earlier than 1.10.5; Kata Containers 1.9 and earlier versions. | {'CVE-2020-2026'} | 2021-05-13T19:28:33Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-59'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-2026', 'https://github.com/kata-containers/runtime/releases/tag/1.10.5', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QNJHSSPCKUGJDVXXIXK2JUWCRJDQX7CE/', 'https://github.com/kata-containers/runtime/issues/2712', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XWACJQSMY5BVDMVTF3FBN7HZSOSFOG3Q/', 'https://github.com/kata-containers/runtime/releases/tag/1.11.1', 'https://github.com/kata-containers/runtime/pull/2713', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2P7FHA4AF6Y6PAVJBTTQPUEHXZQUOF3P/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NJAMOVB7DSOGX7J26QH5HZKU7GSSX2VU/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6JPBKAQBF3OR72N55GWM2TDYQP2OHK6H/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6W5MKF7HSAIL2AX2BX6RV4WWVGUIKVLS/'} | null |
Go | GO-2020-0042 | null | Due to improper path santization, RPMs containing relative file
paths can cause files to be written (or overwritten) outside of the
target directory.
| {'CVE-2020-7667'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://snyk.io/research/zip-slip-vulnerability', 'https://github.com/sassoftware/go-rpmutils/commit/a64058cf21b8aada501bba923c9aab66fb6febf0'} | null |
Go | GHSA-f37q-q7p2-ccfc | Resource exhaustion in Mattermost | The image proxy component in Mattermost version 6.4.1 and earlier allocates memory for multiple copies of a proxied image, which allows an authenticated attacker to crash the server via links to very large image files. | {'CVE-2022-1337'} | 2022-04-26T13:05:37Z | 2022-04-14T00:00:17Z | MODERATE | null | {'CWE-400'} | {'https://github.com/mattermost/mattermost-server', 'https://mattermost.com/security-updates/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1337'} | null |
Go | GHSA-wc9w-wvq2-ffm9 | Server Side Request Forgery in Grafana | The avatar feature in Grafana 3.0.1 through 7.0.1 has an SSRF Incorrect Access Control issue that allows remote code execution. This vulnerability allows any unauthenticated user/client to make Grafana send HTTP requests to any URL and return its result to the user/client. This can be used to gain information about the network that Grafana is running on. | {'CVE-2020-13379'} | 2021-05-14T16:27:02Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-918'} | {'https://lists.apache.org/thread.html/r40f0a97b6765de6b8938bc212ee9dfb5101e9efa48bcbbdec02b2a60@%3Cissues.ambari.apache.org%3E', 'https://www.exploit-db.com/exploits/48638', 'https://mostwanted002.cf/post/grafanados/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/O2KSCCGKNEENZN3DW7TSPFBBUZH3YZXZ/', 'https://lists.apache.org/thread.html/rd0fd283e3844b9c54cd5ecc92d966f96d3f4318815bbf3ac41f9c820@%3Ccommits.ambari.apache.org%3E', 'https://rhynorater.github.io/CVE-2020-13379-Write-Up', 'https://lists.apache.org/thread.html/r093b405a49fd31efa0d949ac1a887101af1ca95652a66094194ed933@%3Cdev.ambari.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-13379', 'https://lists.apache.org/thread.html/rff71126fa7d9f572baafb9be44078ad409c85d2c0f3e26664f1ef5a2@%3Cdev.ambari.apache.org%3E', 'https://lists.apache.org/thread.html/r6bb57124a21bb638f552d81650c66684e70fc1ff9f40b6a8840171cd@%3Cissues.ambari.apache.org%3E', 'http://www.openwall.com/lists/oss-security/2020/06/03/4', 'https://lists.apache.org/thread.html/r6670a6c29044bcb77d4e5d165b5bd13fffe37b84caa5d6471b13b3a2@%3Cdev.ambari.apache.org%3E', 'https://lists.apache.org/thread.html/rba0247a27be78bd14046724098462d058a9969400a82344b3007cf90@%3Cdev.ambari.apache.org%3E', 'https://lists.apache.org/thread.html/r0928ee574281f8b6156e0a6d0291bfc27100a9dd3f9b0177ece24ae4@%3Cdev.ambari.apache.org%3E', 'https://lists.apache.org/thread.html/r984c3b42a500f5a6a89fbee436b9432fada5dc27ebab04910aafe4da@%3Cissues.ambari.apache.org%3E', 'http://lists.opensuse.org/opensuse-security-announce/2020-06/msg00060.html', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00017.html', 'http://packetstormsecurity.com/files/158320/Grafana-7.0.1-Denial-Of-Service.html', 'https://community.grafana.com/t/release-notes-v7-0-x/29381', 'https://lists.apache.org/thread.html/rad99b06d7360a5cf6e394afb313f8901dcd4cb777aee9c9197b3b23d@%3Cdev.ambari.apache.org%3E', 'https://community.grafana.com/t/grafana-7-0-2-and-6-7-4-security-update/31408', 'https://lists.apache.org/thread.html/re75f59639f3bc1d14c7ab362bc4485ade84f3c6a3c1a03200c20fe13@%3Cissues.ambari.apache.org%3E', 'http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00083.html', 'https://github.com/grafana/grafana/commit/ba953be95f0302c2ea80d23f1e5f2c1847365192', 'https://security.netapp.com/advisory/ntap-20200608-0006/', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00009.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EEKSZ6GE4EDOFZ23NGYWOCMD6O4JF5SO/', 'https://grafana.com/blog/2020/06/03/grafana-6.7.4-and-7.0.2-released-with-important-security-fix/', 'https://community.grafana.com/t/release-notes-v6-7-x/27119', 'https://lists.apache.org/thread.html/re7c4b251b52f49ba6ef752b829bca9565faaf93d03206b1db6644d31@%3Cdev.ambari.apache.org%3E', 'http://www.openwall.com/lists/oss-security/2020/06/09/2'} | null |
Go | GHSA-5mv9-q7fq-9394 | Action Commands (run/shell/exec) Against Library URIs Ignore Configured Remote Endpoint | ### Impact
Due to incorrect use of a default URL, `singularity` action commands (`run`/`shell`/`exec`) specifying a container using a `library://` URI will always attempt to retrieve the container from the default remote endpoint (`cloud.sylabs.io`) rather than the configured remote endpoint.
An attacker may be able to push a malicious container to the default remote endpoint with a URI that is identical to the URI used by a victim with a non-default remote endpoint, thus executing the malicious container.
Only action commands (`run`/`shell`/`exec`) against `library://` URIs are affected. Other commands such as `pull` / `push` respect the configured remote endpoint.
### Patches
All users should upgrade to Singularity 3.7.4 or later.
### Workarounds
Users who only interact with the default remote endpoint are not affected.
Installations with an execution control list configured to restrict execution to containers signed with specific secure keys are not affected.
### For more information
General questions about the impact of the advisory can be asked in the:
- [SingularityCE Slack Channel](https://singularityce.slack.com)
- [SingularityCE Mailing List](https://groups.google.com/g/singularity-ce)
Any sensitive security concerns should be directed to: security@sylabs.io
See our Security Policy here: https://sylabs.io/security-policy | {'CVE-2021-32635'} | 2022-04-25T23:42:19Z | 2021-06-01T21:21:01Z | MODERATE | null | {'CWE-20'} | {'https://github.com/sylabs/singularity', 'https://github.com/sylabs/singularity/releases/tag/v3.7.4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32635', 'https://security.gentoo.org/glsa/202107-50', 'https://github.com/sylabs/singularity/security/advisories/GHSA-5mv9-q7fq-9394', 'https://github.com/hpcng/singularity/security/advisories/GHSA-jq42-hfch-42f3'} | null |
Go | GHSA-4gh8-x3vv-phhg | Predictable SIF UUID Identifiers in github.com/sylabs/sif | ### Impact
The `siftool new` command and [func siftool.New()](https://pkg.go.dev/github.com/sylabs/sif/pkg/siftool#New) produce predictable UUID identifiers due to insecure randomness in the version of the `github.com/satori/go.uuid` module used as a dependency.
### Patches
A patch is available in versions 1.2.3 and newer of the module. Users are encouraged to upgrade.
### Workarounds
Users passing [CreateInfo struct](https://pkg.go.dev/github.com/sylabs/sif/pkg/sif#CreateInfo) should ensure the `ID` field is generated using a version of `github.com/satori/go.uuid` that is not vulnerable to this issue. Unfortunately, the latest tagged release is vulnerable to this issue. One way to obtain a non-vulnerable version is:
```
go get github.com/satori/go.uuid@75cca531ea763666bc46e531da3b4c3b95f64557
```
| {'CVE-2021-29499'} | 2021-05-07T21:39:49Z | 2021-05-18T18:30:38Z | HIGH | null | {'CWE-330', 'CWE-340'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29499', 'https://github.com/sylabs/sif/security/advisories/GHSA-4gh8-x3vv-phhg', 'https://github.com/satori/go.uuid/issues/73'} | null |
Go | GHSA-2x32-jm95-2cpx | Authentication Bypass in dex | A vulnerability exists in the SAML connector of the github.com/dexidp/dex library used to process SAML Signature Validation. This flaw allows an attacker to bypass SAML authentication. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability. This flaw affects dex versions before 2.27.0. | {'CVE-2020-27847'} | 2021-06-01T17:58:22Z | 2021-12-20T17:52:12Z | CRITICAL | null | {'CWE-290', 'CWE-228'} | {'https://github.com/dexidp/dex/security/advisories/GHSA-m9hp-7r99-94h5', 'https://nvd.nist.gov/vuln/detail/CVE-2020-27847', 'https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/', 'https://bugzilla.redhat.com/show_bug.cgi?id=1907732'} | null |
Go | GO-2020-0039 | null | Due to improper request santization, a specifically crafted URL
can cause the static file handler to redirect to an attacker chosen
URL, allowing for open redirect attacks.
| {'CVE-2020-12666'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/go-macaron/macaron/issues/198', 'https://github.com/go-macaron/macaron/commit/addc7461c3a90a040e79aa75bfd245107a210245', 'https://github.com/go-macaron/macaron/pull/199'} | null |
Go | GHSA-9wvh-ff5f-xjpj | Missing Authorization in Harbor | core/api/user.go in Harbor 1.7.0 through 1.8.2 allows non-admin users to create admin accounts via the POST /api/users API. This is fixed in 1.9.0-rc1. | {'CVE-2019-16097'} | 2021-05-17T16:40:42Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-862'} | {'https://github.com/goharbor/harbor/commit/b6db8a8a106259ec9a2c48be8a380cb3b37cf517', 'http://www.vmware.com/security/advisories/VMSA-2019-0015.html', 'https://github.com/goharbor/harbor/compare/v1.8.2...v1.9.0-rc1', 'https://github.com/goharbor/harbor/releases/tag/v1.8.3', 'https://github.com/goharbor/harbor/releases/tag/v1.7.6', 'https://unit42.paloaltonetworks.com/critical-vulnerability-in-harbor-enables-privilege-escalation-from-zero-to-admin-cve-2019-16097/', 'https://github.com/ianxtianxt/CVE-2019-16097', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16097'} | null |
Go | GHSA-g42g-737j-qx6j | Access Restriction Bypass in kube-apiserver | A vulnerability in Kubernetes `kube-apiserver` could allow node updates to bypass a _Validating Admission Webhook_ and allow unauthorized node updates. The information that is provided to the admission controller could contain old configurations that overwrite values used for validation. Since the overwriting takes place before the validation, this could lead the admission controller to accept requests that should be blocked. The vulnerability can be exploited when an update action on node resources is performed and an admission controller is in place and configured to validate the action.
Users are only affected by this vulnerability if they are running a _Validating Admission Webhook_ for Nodes that denies admission based partially on the old state of the Node object. It only impacts validating admission plugins that rely on old values in certain fields and does not impact calls from kubelets that go through the built-in NodeRestriction admission plugin. | {'CVE-2021-25735'} | 2022-03-22T18:43:41Z | 2021-05-28T19:49:59Z | MODERATE | null | {'CWE-863', 'CWE-284'} | {'https://sysdig.com/blog/cve-2021-25735-kubernetes-admission-bypass/', 'https://bugzilla.redhat.com/show_bug.cgi?id=1937562', 'https://github.com/kubernetes/kubernetes/issues/100096', 'https://github.com/kubernetes/kubernetes/pull/99946', 'https://pkg.go.dev/k8s.io/kubernetes@v1.23.5/cmd/kube-apiserver', 'https://groups.google.com/g/kubernetes-security-announce/c/FKAGqT4jx9Y', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25735', 'https://github.com/kubernetes/kubernetes', 'https://github.com/kubernetes/kubernetes/commit/00e81db174ef7aca497be5f42d87e46d14df2a90'} | null |
Go | GHSA-mfv7-gq43-w965 | Incomplete List of Disallowed Inputs in Kubernetes | A security issue was discovered in Kubernetes where a user may be able to redirect pod traffic to private networks on a Node. Kubernetes already prevents creation of Endpoint IPs in the localhost or link-local range, but the same validation was not performed on EndpointSlice IPs. | {'CVE-2021-25737'} | 2021-09-14T18:47:27Z | 2021-09-07T23:09:24Z | MODERATE | null | {'CWE-184', 'CWE-601'} | {'https://groups.google.com/g/kubernetes-security-announce/c/xAiN3924thY', 'https://security.netapp.com/advisory/ntap-20211004-0004/', 'https://github.com/kubernetes/kubernetes', 'https://github.com/kubernetes/kubernetes/issues/102106', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25737'} | null |
Go | GO-2021-0072 | null | Various storage methods do not impose limits on how much content is accepted
from user requests, allowing a malicious user to force the caller to allocate
an arbitary amount of memory.
| {'CVE-2017-11468'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/distribution/distribution/pull/2340', 'http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00047.html', 'https://github.com/distribution/distribution/commit/91c507a39abfce14b5c8541cf284330e22208c0f', 'https://access.redhat.com/errata/RHSA-2017:2603'} | null |
Go | GHSA-77cr-6gr8-7rr9 | Use After Free in HashiCorp Nomad | HashiCorp Nomad and Nomad Enterprise version 0.9.0 up to 0.12.5 client file sandbox feature can be subverted using either the template or artifact stanzas. Fixed in 0.12.6, 0.11.5, and 0.10.6 | {'CVE-2020-27195'} | 2021-05-12T21:58:02Z | 2022-02-15T01:57:18Z | CRITICAL | null | {'CWE-416'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-27195', 'https://github.com/hashicorp/nomad/blob/master/CHANGELOG.md#0126-october-21-2020', 'https://www.nomadproject.io/downloads', 'https://github.com/hashicorp/nomad/pull/9139', 'https://github.com/hashicorp/nomad/issues/9129'} | null |
Go | GHSA-75pc-qvwc-jf3g | Improper Input Validation in HashiCorp Vault | HashiCorp Vault and Vault Enterprise 1.4.x before 1.4.2 has Incorrect Access Control. | {'CVE-2020-12757'} | 2021-05-13T14:47:09Z | 2021-05-18T18:20:48Z | HIGH | null | {'CWE-20'} | {'https://www.hashicorp.com/blog/category/vault/', 'https://github.com/hashicorp/vault-plugin-secrets-gcp/commit/e43d20870c50f7428dead1411debcec075b35fb4', 'https://github.com/hashicorp/vault/blob/master/CHANGELOG.md', 'https://github.com/hashicorp/vault-plugin-secrets-gcp/pull/85', 'https://nvd.nist.gov/vuln/detail/CVE-2020-12757', 'https://github.com/hashicorp/vault/blob/master/CHANGELOG.md#142-may-21st-2020'} | null |
Go | GHSA-78hj-86cr-6j2v | Improper Access Control in Lightning Network Daemon | Lightning Network Daemon (lnd) before 0.7 allows attackers to trigger loss of funds because of Incorrect Access Control. | {'CVE-2019-12999'} | 2021-05-17T21:56:38Z | 2021-05-18T15:30:22Z | HIGH | null | {'CWE-284'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-12999', 'https://github.com/lightninglabs/chanleakcheck', 'https://github.com/lightningnetwork/lnd/releases/tag/v0.7.0-beta', 'https://lists.linuxfoundation.org/pipermail/lightning-dev/2019-September/002174.html', 'https://github.com/lightningnetwork/lnd/commits/master'} | null |
Go | GHSA-hpmr-prr2-cqc4 | Remote Code Execution | models/repo_mirror.go in Gitea before 1.7.6 and 1.8.x before 1.8-RC3 mishandles mirror repo URL settings, leading to remote code execution. | {'CVE-2019-11229'} | 2021-05-12T17:52:21Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-94'} | {'https://github.com/go-gitea/gitea/releases/tag/v1.8.0-rc3', 'https://www.exploit-db.com/exploits/49383', 'https://nvd.nist.gov/vuln/detail/CVE-2019-11229', 'https://github.com/go-gitea/gitea/releases/tag/v1.7.6', 'http://packetstormsecurity.com/files/160833/Gitea-1.7.5-Remote-Code-Execution.html', 'https://github.com/go-gitea/gitea/pull/6595', 'https://github.com/go-gitea/gitea/pull/6593'} | null |
Go | GHSA-m4jx-6526-vvhm | Denial of service in github.com/nats-io/nats-server/server | This affects all versions of package github.com/nats-io/nats-server/server. Untrusted accounts are able to crash the server using configs that represent a service export/import cycles. Disclaimer from the maintainers - Running a NATS service which is exposed to untrusted users presents a heightened risk. Any remote execution flaw or equivalent seriousness, or denial-of-service by unauthenticated users, will lead to prompt releases by the NATS maintainers. Fixes for denial of service issues with no threat of remote execution, when limited to account holders, are likely to just be committed to the main development branch with no special attention. Those who are running such services are encouraged to build regularly from git. | {'CVE-2020-28466'} | 2021-05-12T20:38:22Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-400'} | {'http://www.openwall.com/lists/oss-security/2021/03/16/1', 'https://github.com/nats-io/nats-server/pull/1731', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMNATSIONATSSERVERSERVER-1042967', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28466', 'https://github.com/nats-io/nats-server/pull/1731/commits/2e3c22672936f4980d343fb1d328b38919e74796', 'http://www.openwall.com/lists/oss-security/2021/03/16/2'} | null |
Go | GHSA-35vc-w93w-75c2 | JWT leak via Open Redirect in Programmatic access | ### Impact
Using programmatic access on protected sites, one can get a signed login URL with pomerium_redirect_uri set to an arbitrary URL. Then, if the user has already logged into Pomerium, they will be redirected to the specified pomerium_redirect_uri with a JWT attached. This allows an outside attacker to get a signed login URL that, upon visiting it, will redirect a victim to the attacker’s site. This creates an issue of Open Redirect and, more seriously, JWT leakage.
With a leaked JWT, the attacker will be able to unveil the victim’s identity (.e.g. email address) by supplying the JWT to the authenticate service or verify.pomerium.com. In addition, if an application integrating Pomerium only verifies the iss claim and others but not the aud claim, the attacker will be able to access it as the victim.
### Patches
Patched in Pomerium v0.13.4
### For more information
If you have any questions or comments about this advisory
* Open an issue in [pomerium](http://github.com/pomerium/pomerium)
* Email us at [security@pomerium.com](mailto:security@pomerium.com) | {'CVE-2021-29651'} | 2021-05-20T20:25:40Z | 2021-05-21T16:24:34Z | HIGH | null | {'CWE-601', 'CWE-200'} | {'https://github.com/pomerium/pomerium/pull/2049', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29651', 'https://github.com/pomerium/pomerium/security/advisories/GHSA-35vc-w93w-75c2'} | null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.