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-9h4h-8w5p-f28w | Denial of Service in geth | cmd/evm/runner.go in Go Ethereum (aka geth) allows attackers to cause a denial of service (SEGV) via crafted bytecode. | {'CVE-2018-19184'} | 2021-05-20T18:58:40Z | 2021-06-29T21:23:15Z | HIGH | null | {'CWE-476'} | {'https://github.com/ethereum/go-ethereum/issues/18069', 'https://github.com/ethereum/go-ethereum/commit/83e2761c3a13524bd5d6597ac08994488cf872ef', 'https://nvd.nist.gov/vuln/detail/CVE-2018-19184', 'https://github.com/ethereum/go-ethereum/commit/fb9f7261ec51e38eedb454594fc19f00de1a6834'} | null | {'https://github.com/ethereum/go-ethereum/commit/83e2761c3a13524bd5d6597ac08994488cf872ef', 'https://github.com/ethereum/go-ethereum/commit/fb9f7261ec51e38eedb454594fc19f00de1a6834'} | {'https://github.com/ethereum/go-ethereum/commit/83e2761c3a13524bd5d6597ac08994488cf872ef', 'https://github.com/ethereum/go-ethereum/commit/fb9f7261ec51e38eedb454594fc19f00de1a6834'} |
Go | GHSA-h563-xh25-x54q | Workflow re-write vulnerability using input parameter | ### Impact
* Allow end-users to set input parameters, but otherwise expect workflows to be secure.
### Patches
Not yet.
### Workarounds
* Set `EXPRESSION_TEMPLATES=false` for the workflow controller
### References
* https://github.com/argoproj/argo-workflows/issues/6441
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [example link to repo](http://example.com)
* Email us at [example email address](mailto:example@example.com)
| {'CVE-2021-37914'} | 2021-08-30T23:23:11Z | 2021-08-09T20:37:50Z | MODERATE | null | {'CWE-20'} | {'https://github.com/argoproj/argo-workflows/security/advisories/GHSA-h563-xh25-x54q', 'https://github.com/argoproj/argo-workflows/issues/6441', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37914', 'https://github.com/argoproj/argo-workflows/pull/6285', 'https://github.com/argoproj/argo-workflows/pull/6442', 'https://github.com/argoproj/argo-workflows/commit/2a2ecc916925642fd8cb1efd026588e6828f82e1', 'github.com/argoproj/argo-workflows/v3'} | null | {'https://github.com/argoproj/argo-workflows/commit/2a2ecc916925642fd8cb1efd026588e6828f82e1'} | {'https://github.com/argoproj/argo-workflows/commit/2a2ecc916925642fd8cb1efd026588e6828f82e1'} |
Go | GHSA-36xw-fx78-c5r4 | containerd-shim API Exposed to Host Network Containers | ## Impact
Access controls for the shim’s API socket verified that the connecting process had an effective UID of 0, but did not otherwise restrict access to the abstract Unix domain socket. This would allow malicious containers running in the same network namespace as the shim, with an effective UID of 0 but otherwise reduced privileges, to cause new processes to be run with elevated privileges.
## Patches
This vulnerability has been fixed in containerd 1.3.9 and 1.4.3. Users should update to these versions as soon as they are released. It should be noted that containers started with an old version of containerd-shim should be stopped and restarted, as running containers will continue to be vulnerable even after an upgrade.
## Workarounds
If you are not providing the ability for untrusted users to start containers in the same network namespace as the shim (typically the "host" network namespace, for example with `docker run --net=host` or `hostNetwork: true` in a Kubernetes pod) and run with an effective UID of 0, you are not vulnerable to this issue.
If you are running containers with a vulnerable configuration, you can deny access to all abstract sockets with AppArmor by adding a line similar to `deny unix addr=@**,` to your policy.
It is best practice to run containers with a reduced set of privileges, with a non-zero UID, and with isolated namespaces. The containerd maintainers strongly advise against sharing namespaces with the host. Reducing the set of isolation mechanisms used for a container necessarily increases that container's privilege, regardless of what container runtime is used for running that container.
## Credits
The containerd maintainers would like to thank Jeff Dileo of NCC Group for responsibly disclosing this issue in accordance with the [containerd security policy](https://github.com/containerd/project/blob/master/SECURITY.md) and for reviewing the patch.
## For more information
If you have any questions or comments about this advisory:
* [Open an issue](https://github.com/containerd/containerd/issues/new/choose)
* Email us at security@containerd.io if you think you’ve found a security bug. | {'CVE-2020-15257'} | 2021-05-27T19:46:55Z | 2021-05-24T17:00:22Z | MODERATE | null | {'CWE-669'} | {'https://github.com/containerd/containerd/releases/tag/v1.4.3', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LNKXLOLZWO5FMAPX63ZL7JNKTNNT5NQD/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15257', 'https://research.nccgroup.com/2020/12/10/abstract-shimmer-cve-2020-15257-host-networking-is-root-equivalent-again/', 'https://github.com/containerd/containerd/commit/4a4bb851f5da563ff6e68a83dc837c7699c469ad', 'https://www.debian.org/security/2021/dsa-4865', 'https://github.com/containerd/containerd/security/advisories/GHSA-36xw-fx78-c5r4', 'https://security.gentoo.org/glsa/202105-33'} | null | {'https://github.com/containerd/containerd/commit/4a4bb851f5da563ff6e68a83dc837c7699c469ad'} | {'https://github.com/containerd/containerd/commit/4a4bb851f5da563ff6e68a83dc837c7699c469ad'} |
Go | GHSA-68wm-pfjf-wqp6 | Authentication bypassed with malformed request URI on nginx | ### Impact
This affects uses who are using nginx ngx_http_auth_request_module with Authelia, it allows a malicious individual who crafts a malformed HTTP request to bypass the authentication mechanism. It additionally could theoretically affect other proxy servers, but all of the ones we officially support except nginx do not allow malformed URI paths.
### Patches
The problem is rectified entirely in v4.29.3. As this patch is relatively straightforward we can back port this to any version upon request. Alternatively we are supplying a git patch to 4.25.1 which should be relatively straightforward to apply to any version, the git patches for specific versions can be found below.
<details><summary>Patch for 4.25.1:</summary><p>
```patch
From ca22f3d2c44ca7bef043ffbeeb06d6659c1d550f Mon Sep 17 00:00:00 2001
From: James Elliott <james-d-elliott@users.noreply.github.com>
Date: Wed, 19 May 2021 12:10:13 +1000
Subject: [PATCH] fix(handlers): verify returns 200 on malformed request
This is a git patch for commit at tag v4.25.1 to address a potential method to bypass authentication in proxies that forward malformed information to Authelia in the forward auth process. Instead of returning a 200 this ensures that Authelia returns a 401 when this occurs.
---
internal/handlers/handler_verify.go | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/internal/handlers/handler_verify.go b/internal/handlers/handler_verify.go
index 65c064ce..4dd9702d 100644
--- a/internal/handlers/handler_verify.go
+++ b/internal/handlers/handler_verify.go
@@ -396,7 +396,9 @@ func VerifyGet(cfg schema.AuthenticationBackendConfiguration) middlewares.Reques
targetURL, err := getOriginalURL(ctx)
if err != nil {
- ctx.Error(fmt.Errorf("Unable to parse target URL: %s", err), operationFailedMessage)
+ ctx.Logger.Error(fmt.Errorf("Unable to parse target URL: %s", err))
+ ctx.ReplyUnauthorized()
+
return
}
--
2.31.1
```
</p></details>
### Workarounds
The most relevant workaround is upgrading. **If you need assistance with an upgrade please contact us on [Matrix](https://riot.im/app/#/room/#authelia:matrix.org) or [Discord](https://discord.authelia.com).** Please just let us know you're needing help upgrading to above 4.29.2.
You can add an block which fails requests that contains a malformed URI in the internal location block. We have crafted one that should work in most instances, it basically checks no chars that are required to be URL-encoded for either the path or the query are in the URI. Basically this regex checks that the characters between the square braces are the only characters in the $request_uri header, if they exist, it returns a HTTP 401 status code. The characters in the regex match are tested to not cause a parsing error that would result in a failure, however they are not exhaustive since query strings seem to not always conform to the RFC.
<details><summary>authelia.conf:</summary><p>
```nginx
location /authelia {
internal;
# **IMPORTANT**
# This block rejects requests with a 401 which contain characters that are unable to be parsed.
# It is necessary for security prior to v4.29.3 due to the fact we returned an invalid code in the event of a parser error.
# You may comment this section if you're using Authelia v4.29.3 or above. We strongly recommend upgrading.
# RFC3986: http://tools.ietf.org/html/rfc3986
# Commentary on RFC regarding Query Strings: https://www.456bereastreet.com/archive/201008/what_characters_are_allowed_unencoded_in_query_strings/
if ($request_uri ~ [^a-zA-Z0-9_+-=\!@$%&*?~.:#'\;\(\)\[\]]) {
return 401;
}
# Include the remainder of the block here.
}
````
</p></details>
### Discovery
This issue was discovered by:
Siemens Energy
Cybersecurity Red Team
- Silas Francisco
- Ricardo Pesqueira
### Identifying active exploitation of the vulnerability
The following regex should match log entries that are an indication of the vulnerability being exploited:
```regex
level=error msg="Unable to parse target URL: Unable to parse URL (extracted from X-Original-URL header)?.*?: parse.*?net/url:.*github\.com/authelia/authelia/internal/handlers/handler_verify\.go
```
Example log entry ***with*** X-Original-URL configured:
```log
time="2021-05-21T16:31:15+10:00" level=error msg="Unable to parse target URL: Unable to parse URL extracted from X-Original-URL header: parse \"https://example.com/": net/url: invalid control character in URL" method=GET path=/api/verify remote_ip=192.168.1.10 stack="github.com/authelia/authelia/internal/middlewares/authelia_context.go:65 (*AutheliaCtx).Error\ngithub.com/authelia/authelia/internal/handlers/handler_verify.go:431 VerifyGet.func1\ngithub.com/authelia/authelia/internal/middlewares/authelia_context.go:50 AutheliaMiddleware.func1.1\ngithub.com/fasthttp/router@v1.3.12/router.go:414 (*Router).Handler\ngithub.com/authelia/authelia/internal/middlewares/log_request.go:14 LogRequestMiddleware.func1\ngithub.com/valyala/fasthttp@v1.24.0/server.go:2219 (*Server).serveConn\ngithub.com/valyala/fasthttp@v1.24.0/workerpool.go:223 (*workerPool).workerFunc\ngithub.com/valyala/fasthttp@v1.24.0/workerpool.go:195 (*workerPool).getCh.func1\nruntime/asm_amd64.s:1371 goexit"
```
Example log entry ***without*** X-Original-URL configured:
```log
time="2021-05-21T16:30:17+10:00" level=error msg="Unable to parse target URL: Unable to parse URL https://example.com/: parse \"https://example.com/": net/url: invalid control character in URL" method=GET path=/api/verify remote_ip=192.168.1.10 stack="github.com/authelia/authelia/internal/middlewares/authelia_context.go:65 (*AutheliaCtx).Error\ngithub.com/authelia/authelia/internal/handlers/handler_verify.go:431 VerifyGet.func1\ngithub.com/authelia/authelia/internal/middlewares/authelia_context.go:50 AutheliaMiddleware.func1.1\ngithub.com/fasthttp/router@v1.3.12/router.go:414 (*Router).Handler\ngithub.com/authelia/authelia/internal/middlewares/log_request.go:14 LogRequestMiddleware.func1\ngithub.com/valyala/fasthttp@v1.24.0/server.go:2219 (*Server).serveConn\ngithub.com/valyala/fasthttp@v1.24.0/workerpool.go:223 (*workerPool).workerFunc\ngithub.com/valyala/fasthttp@v1.24.0/workerpool.go:195 (*workerPool).getCh.func1\nruntime/asm_amd64.s:1371 goexit"
```
### For more information
If you have any questions or comments about this advisory:
* Open an issue at [authelia](https://github.com/authelia/authelia/issues)
* Email us at [security@authelia.com](mailto:security@authelia.com)
| {'CVE-2021-32637'} | 2021-05-28T18:08:47Z | 2021-12-20T16:57:16Z | CRITICAL | null | {'CWE-287'} | {'https://github.com/authelia/authelia/commit/c62dbd43d6e69ae81530e7c4f8763857f8ff1dda', 'https://github.com/authelia/authelia/security/advisories/GHSA-68wm-pfjf-wqp6', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32637'} | null | {'https://github.com/authelia/authelia/commit/c62dbd43d6e69ae81530e7c4f8763857f8ff1dda'} | {'https://github.com/authelia/authelia/commit/c62dbd43d6e69ae81530e7c4f8763857f8ff1dda'} |
Go | GHSA-m6wg-2mwg-4rfq | Use After Free | The proglottis Go wrapper before 0.1.1 for the GPGME library has a use-after-free, as demonstrated by use for container image pulls by Docker or CRI-O. This leads to a crash or potential code execution during GPG signature verification. | {'CVE-2020-8945'} | 2021-05-17T22:00:21Z | 2021-05-18T15:29:42Z | HIGH | null | {'CWE-416'} | {'https://access.redhat.com/errata/RHSA-2020:0689', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WXV7NZELYWRRCXATXU3FYD3G3WJT3WYM/', 'https://github.com/proglottis/gpgme/commit/92153bcb59bd2f511e502262c46c7bd660e21733', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8945', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3SOCLOPTSYABTE4CLTSPDIFE6ZZZR4LX/', 'https://github.com/containers/image/commit/4c7a23f82ef09127b0ff28366d1cf31316dd6cc1', 'https://access.redhat.com/errata/RHSA-2020:0679', 'https://access.redhat.com/errata/RHSA-2020:0697', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KDBT77KV3U7BESJX3P4S4MPVDGRTAQA2/', 'https://bugzilla.redhat.com/show_bug.cgi?id=1795838', 'https://github.com/proglottis/gpgme/pull/23', 'https://github.com/proglottis/gpgme/compare/v0.1.0...v0.1.1', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/H6P6SSNKN4H6GSEVROHBDXA64PX7EOED/'} | null | {'https://github.com/proglottis/gpgme/commit/92153bcb59bd2f511e502262c46c7bd660e21733', 'https://github.com/containers/image/commit/4c7a23f82ef09127b0ff28366d1cf31316dd6cc1'} | {'https://github.com/containers/image/commit/4c7a23f82ef09127b0ff28366d1cf31316dd6cc1', 'https://github.com/proglottis/gpgme/commit/92153bcb59bd2f511e502262c46c7bd660e21733'} |
Go | GHSA-9c4x-5hgq-q3wh | Instance config inline secret exposure in Grafana | ### Impact
Some inline secrets are exposed in plaintext over the Grafana Agent HTTP server:
* Inline secrets for metrics instance configs in the base YAML file are exposed at `/-/config`
* Inline secrets for integrations are exposed at `/-/config`
* Inline secrets for Consul ACL tokens and ETCD basic auth when configured for the scraping service at `/-/config`.
* Inline secrets for the Kafka receiver for OpenTelemetry-Collector tracing at `/-/config`.
* Inline secrets for metrics instance configs loaded from the scraping service are exposed at `/agent/api/v1/configs/{name}`.
Inline secrets will be exposed to anyone being able to reach these endpoints.
Secrets found in these sections are used for:
* Delivering metrics to a Prometheus Remote Write system
* Authenticating against a system for discovering Prometheus targets
* Authenticating against a system for collecting metrics (scrape_configs and integrations)
* Authenticating against a Consul or ETCD for storing configurations to distribute in scraping service mode
* Authenticating against Kafka for receiving traces
Non-inlined secrets, such as `*_file`-based secrets, are not impacted by this vulnerability.
### Patches
Download [v0.20.1](https://github.com/grafana/agent/releases/tag/v0.20.1) or any version past [v0.21.2](https://github.com/grafana/agent/releases/tag/v0.21.2) to patch Grafana Agent. These patches obfuscate the listed impacted secrets from the vulnerable endpoints.
The patches also disable the endpoints by default. Pass the command-line flag `--config.enable-read-api` to opt-in and re-enable the endpoints.
### Workarounds
If for some reason you cannot upgrade, use non-inline secrets where possible. Not all configuration options may have a non-inline equivalent.
You also may desire to restrict API access to Grafana Agent, with some combination of:
* Restrict network interfaces Grafana Agent listens on through `http_listen_address` in the `server` block. `127.0.0.1` is the most restrictive, `0.0.0.0` is the default.
* Configure Grafana Agent to use HTTPS with client authentication.
* Use firewall rules to restrict external access to Grafana Agent's API. | {'CVE-2021-41090'} | 2021-12-14T15:32:21Z | 2021-12-08T19:52:40Z | MODERATE | null | {'CWE-312', 'CWE-200'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-41090', 'https://github.com/grafana/agent/releases/tag/v0.21.2', 'https://github.com/grafana/agent/commit/af7fb01e31fe2d389e5f1c36b399ddc46b412b21', 'https://github.com/grafana/agent/pull/1152', 'https://security.netapp.com/advisory/ntap-20211229-0004/', 'https://github.com/grafana/agent/releases/tag/v0.20.1', 'https://github.com/grafana/agent', 'https://github.com/grafana/agent/security/advisories/GHSA-9c4x-5hgq-q3wh', 'https://github.com/grafana/agent/commit/a5479755e946e5c7cddb793ee9adda8f5692ba11'} | null | {'https://github.com/grafana/agent/commit/af7fb01e31fe2d389e5f1c36b399ddc46b412b21', 'https://github.com/grafana/agent/commit/a5479755e946e5c7cddb793ee9adda8f5692ba11'} | {'https://github.com/grafana/agent/commit/af7fb01e31fe2d389e5f1c36b399ddc46b412b21', 'https://github.com/grafana/agent/commit/a5479755e946e5c7cddb793ee9adda8f5692ba11'} |
Go | GHSA-7mqr-2v3q-v2wm | Ignored errors on token revokation in github.com/ory/fosite | ### Impact
The `TokenRevocationHandler` ignores errors coming from the storage. This can lead to unexpected 200 status codes indicating successful revocation while the token is still valid. Whether an attacker can use this for her advantage depends on the ability to trigger errors in the store.
### References
[RFC 7009](https://tools.ietf.org/html/rfc7009#section-2.2.1) states that a 503 HTTP code must be returned when the server has a problem. | {'CVE-2020-15223'} | 2021-05-24T12:53:07Z | 2021-05-24T16:57:39Z | HIGH | null | {'CWE-755'} | {'https://github.com/ory/fosite/security/advisories/GHSA-7mqr-2v3q-v2wm', 'https://tools.ietf.org/html/rfc7009#section-2.2.1', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15223', 'https://github.com/ory/fosite/commit/03dd55813f5521985f7dd64277b7ba0cf1441319'} | null | {'https://github.com/ory/fosite/commit/03dd55813f5521985f7dd64277b7ba0cf1441319'} | {'https://github.com/ory/fosite/commit/03dd55813f5521985f7dd64277b7ba0cf1441319'} |
Go | GO-2021-0081 | null | The HTTP client used to connect to the container registry authorization
service explicitly disables TLS verification, allowing an attacker that
is able to MITM the connection to steal credentials.
| {'CVE-2019-10214'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/containers/image/pull/669', 'https://github.com/containers/image/issues/654', 'https://github.com/containers/image/commit/634605d06e738aec8332bcfd69162e7509ac7aaf', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10214'} | null | {'https://github.com/containers/image/commit/634605d06e738aec8332bcfd69162e7509ac7aaf'} | {'https://github.com/containers/image/commit/634605d06e738aec8332bcfd69162e7509ac7aaf'} |
Go | GHSA-wpfr-6297-9v57 | User object created with invalid provider data in GoTrue | ### Impact
_What kind of vulnerability is it? Who is impacted?_
Under certain circumstances a valid user object would have been created with invalid provider metadata.
This vulnerability affects everyone running an instance of GoTrue as a service. We advise you to update especially if you are using the provider metadata from the user object to secure other resources.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
A patch is available with the release of version [1.0.1 on Github](https://github.com/netlify/gotrue/releases/tag/v1.0.1).
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
If you don't rely on the provider metadata in the user object, you might not be affected. We still strongly recommend upgrading.
### References
_Are there any links users can visit to find out more?_
This problem was initially found and reported by the team at Supabase: https://github.com/supabase/gotrue/security/advisories/GHSA-5hvv-9cqv-894r. We want to thank them for the cooperation around this report.
In contrast to their advisory, we decided to set the severity to "Moderate" since the provider metadata is not an inherent security feature of this GoTrue codebase or the Netlify ecosystem.
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@netlify.com](mailto:security@netlify.com)
| null | 2022-02-09T22:29:01Z | 2022-02-09T22:29:01Z | MODERATE | null | null | {'https://github.com/netlify/gotrue/releases/tag/v1.0.1', 'https://github.com/netlify/gotrue/commit/4d8a3b39fe485a5f83c70617d594be01130c5b83', 'https://github.com/netlify/gotrue/pull/313', 'https://github.com/netlify/gotrue', 'https://github.com/netlify/gotrue/security/advisories/GHSA-wpfr-6297-9v57'} | null | {'https://github.com/netlify/gotrue/commit/4d8a3b39fe485a5f83c70617d594be01130c5b83'} | {'https://github.com/netlify/gotrue/commit/4d8a3b39fe485a5f83c70617d594be01130c5b83'} |
Go | GO-2020-0025 | null | Due to improper path santization, archives containing relative file
paths can cause files to be written (or overwritten) outside of the
target directory.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/cloudfoundry/archiver/commit/09b5706aa9367972c09144a450bb4523049ee840', 'https://snyk.io/research/zip-slip-vulnerability'} | null | {'https://github.com/cloudfoundry/archiver/commit/09b5706aa9367972c09144a450bb4523049ee840'} | {'https://github.com/cloudfoundry/archiver/commit/09b5706aa9367972c09144a450bb4523049ee840'} |
Go | GHSA-wxc4-f4m6-wwqv | Excessive Platform Resource Consumption within a Loop in Kubernetes | The Kubernetes API Server component in versions 1.1-1.14, and versions prior to 1.15.10, 1.16.7 and 1.17.3 allows an authorized user who sends malicious YAML payloads to cause the kube-apiserver to consume excessive CPU cycles while parsing YAML. | {'CVE-2019-11254'} | 2021-05-07T17:24:04Z | 2021-12-20T16:55:06Z | MODERATE | null | {'CWE-1050'} | {'https://security.netapp.com/advisory/ntap-20200413-0003/', 'https://github.com/kubernetes/kubernetes/issues/89535', 'https://github.com/go-yaml/yaml/commit/53403b58ad1b561927d19068c655246f2db79d48', 'https://nvd.nist.gov/vuln/detail/CVE-2019-11254', 'https://groups.google.com/d/msg/kubernetes-announce/ALL9s73E5ck/4yHe8J-PBAAJ', 'https://github.com/kubernetes/kubernetes/pull/87467/commits/b86df2bec4f377afc0ca03482ffad2f0a49a83b8'} | null | {'https://github.com/kubernetes/kubernetes/pull/87467/commits/b86df2bec4f377afc0ca03482ffad2f0a49a83b8', 'https://github.com/go-yaml/yaml/commit/53403b58ad1b561927d19068c655246f2db79d48'} | {'https://github.com/kubernetes/kubernetes/pull/87467/commits/b86df2bec4f377afc0ca03482ffad2f0a49a83b8', 'https://github.com/go-yaml/yaml/commit/53403b58ad1b561927d19068c655246f2db79d48'} |
Go | GHSA-6c7m-qwxj-mvhp | Broken encryption in EdgeX Foundry | ### Summary
Broken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors.
### Detailed Description
The app-functions-sdk exports an “aes” transform that user scripts can optionally call to encrypt data in the processing pipeline. No decrypt function is provided. Encryption is not enabled by default, but if used, the level of protection may be less than the user may expects due to a broken implementation in https://github.com/edgexfoundry/app-functions-sdk-go/blob/v1.0.0/pkg/transforms/encryption.go
Version v2.1.0 (EdgeX Foundry Jakarta release and later) of app-functions-sdk-go/v2 deprecates the “aes” transform and provides an improved “aes256” transform in its place. The broken implementation will remain in a deprecated state until it is removed in the next EdgeX major release to avoid breakage of existing software that depends on the broken implementation.
### Impact
As the broken transform is a library function that is not invoked by default, users who do not use the AES transform in their processing pipelines are unaffected. Those that are affected are urged to upgrade to the Jakarta EdgeX release and modify processing pipelines to use the new "aes256" transform.
#### Vulnerable go modules
- github.com/edgexfoundry/app-functions-sdk-go < v2.1.0
- github.com/edgexfoundry/app-functions-sdk-go/v2 < v2.1.0
- github.com/edgexfoundry/app-service-configurable < v2.1.0
#### Vulnerable containers
- https://hub.docker.com/r/edgexfoundry/app-service-configurable >= 2.0.0 < v2.1.0
- https://hub.docker.com/r/edgexfoundry/app-service-configurable-arm64 >= 2.0.0 < 2.1.0
- https://hub.docker.com/r/edgexfoundry/docker-app-service-configurable < 2.0.0
- https://hub.docker.com/r/edgexfoundry/docker-app-service-configurable-arm64 < 2.0.0
#### Vulnerable Snaps
- https://snapcraft.io/edgex-app-service-configurable >= 2.0.0 < 2.1.0
### Patches
Upgrade to 2.1.0 version of app-functions-sdk-go/v2, app-service-configurable, and related docker containers shown below and modify user scripts to use the new "aes256" transform in place of the existing "aes" transform.
#### Patched go modules
- github.com/edgexfoundry/app-functions-sdk-go/v2 v2.1.0
- github.com/edgexfoundry/app-service-configurable v2.1.0
Modification of user scripts is necessary for full remediation.
#### Patched containers
- https://hub.docker.com/r/edgexfoundry/app-service-configurable:>=2.1.0
- https://hub.docker.com/r/edgexfoundry/app-service-configurable-arm64:>=2.1.0
Modification of user scripts is necessary for full remediation.
#### Patched Snaps
- https://snapcraft.io/edgex-app-service-configurable >= 2.1.0
Modification of user scripts is necessary for full remediation.
### Workarounds
If unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption.
### References
* [2.0 documentation](https://docs.edgexfoundry.org/2.0/microservices/application/BuiltIn/#aes)
* [2.1 documentation](https://docs.edgexfoundry.org/2.1/microservices/application/BuiltIn/#encryption-deprecated)
* [GitHub issue](https://github.com/edgexfoundry/app-functions-sdk-go/issues/968)
### For more information
If you have any questions or comments about this advisory:
* Contact us in the [Slack #security channel](https://slack.edgexfoundry.org/)
* Open an issue in [edgex-go](https://github.com/edgexfoundry/edgex-go)
* Email us at [EdgeX-TSC-Security@lists.edgexfoundry.org](mailto:EdgeX-TSC-Security@lists.edgexfoundry.org) | {'CVE-2021-41278'} | 2021-11-24T19:01:48Z | 2021-11-19T20:55:16Z | MODERATE | null | {'CWE-327'} | {'https://github.com/edgexfoundry/app-functions-sdk-go', 'https://github.com/edgexfoundry/app-functions-sdk-go/commit/8fa13c6388ce76a6b878b54490eac61aa7d81165', 'https://github.com/edgexfoundry/app-functions-sdk-go/security/advisories/GHSA-6c7m-qwxj-mvhp', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41278'} | null | {'https://github.com/edgexfoundry/app-functions-sdk-go/commit/8fa13c6388ce76a6b878b54490eac61aa7d81165'} | {'https://github.com/edgexfoundry/app-functions-sdk-go/commit/8fa13c6388ce76a6b878b54490eac61aa7d81165'} |
Go | GO-2020-0005 | null | Malformed WALs can be constructed such that [`WAL.ReadAll`][] can cause attempted
out of bounds reads, or creation of arbitarily sized slices, which may be used as
a DoS vector.
| {'CVE-2020-15106'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/etcd-io/etcd/commit/f4b650b51dc4a53a8700700dc12e1242ac56ba07', 'https://github.com/etcd-io/etcd/blob/master/security/SECURITY_AUDIT.pdf', 'https://github.com/etcd-io/etcd/pull/11793'} | null | {'https://github.com/etcd-io/etcd/commit/f4b650b51dc4a53a8700700dc12e1242ac56ba07'} | {'https://github.com/etcd-io/etcd/commit/f4b650b51dc4a53a8700700dc12e1242ac56ba07'} |
Go | GHSA-jcxc-rh6w-wf49 | Link Following in Iris | This affects all versions of package github.com/kataras/iris; all versions of package github.com/kataras/iris/v12. The unsafe handling of file names during upload using UploadFormFiles method may enable attackers to write to arbitrary locations outside the designated target folder. | {'CVE-2021-23772'} | 2022-01-05T18:09:47Z | 2022-01-06T21:36:19Z | HIGH | null | {'CWE-59'} | {'https://github.com/kataras/iris', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMKATARASIRIS-2325169', 'https://github.com/kataras/iris/commit/e213dba0d32ff66653e0ef124bc5088817264b08', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMKATARASIRISV12-2325170', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23772'} | null | {'https://github.com/kataras/iris/commit/e213dba0d32ff66653e0ef124bc5088817264b08'} | {'https://github.com/kataras/iris/commit/e213dba0d32ff66653e0ef124bc5088817264b08'} |
Go | GHSA-7v5r-r995-q2x2 | SSRF in repository migration | Gogs is a self-hosted Git service. The malicious user is able to discover services in the internal network through repository migration functionality. All installations accepting public traffic are affected. Internal network CIDRs are prohibited to be used as repository migration targets. Users should upgrade to 0.12.5 or the latest 0.13.0+dev. Gogs should be ran in its own private network until users can update. | {'CVE-2022-0870'} | 2022-03-24T23:23:21Z | 2022-03-12T00:00:34Z | MODERATE | null | {'CWE-918'} | {'https://huntr.dev/bounties/327797d7-ae41-498f-9bff-cc0bf98cf531', 'https://github.com/gogs/gogs', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0870', 'https://github.com/gogs/gogs/commit/91f2cde5e95f146bfe4765e837e7282df6c7cabb'} | null | {'https://github.com/gogs/gogs/commit/91f2cde5e95f146bfe4765e837e7282df6c7cabb'} | {'https://github.com/gogs/gogs/commit/91f2cde5e95f146bfe4765e837e7282df6c7cabb'} |
Go | GO-2020-0013 | null | By default host key verification is disabled which allows for
man-in-the-middle attacks against SSH clients if
[`ClientConfig.HostKeyCallback`] is not set.
| {'CVE-2017-3204'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://go-review.googlesource.com/38701', 'https://bridge.grumpy-troll.org/2017/04/golang-ssh-security/', 'https://github.com/golang/crypto/commit/e4e2799dd7aab89f583e1d898300d96367750991', 'https://github.com/golang/go/issues/19767'} | null | {'https://github.com/golang/crypto/commit/e4e2799dd7aab89f583e1d898300d96367750991'} | {'https://github.com/golang/crypto/commit/e4e2799dd7aab89f583e1d898300d96367750991'} |
Go | GHSA-jq7p-26h5-w78r | Out-of-bounds read in Apache Thrift | In Apache Thrift 0.9.3 to 0.12.0, a server implemented in Go using TJSONProtocol or TSimpleJSONProtocol may panic when feed with invalid input data. | {'CVE-2019-0210'} | 2021-05-17T21:09:18Z | 2021-05-18T15:32:04Z | HIGH | null | {'CWE-125'} | {'https://lists.apache.org/thread.html/r2832722c31d78bef7526e2c701ba4b046736e4c851473194a247392f@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/rab740e5c70424ef79fd095a4b076e752109aeee41c4256c2e5e5e142@%3Ccommits.pulsar.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2020:0806', 'https://security.gentoo.org/glsa/202107-32', 'https://github.com/apache/thrift/blob/master/CHANGES.md#0130', 'https://lists.apache.org/thread.html/r36581cc7047f007dd6aadbdd34e18545ec2c1eb7ccdae6dd47a877a9@%3Ccommits.pulsar.apache.org%3E', 'https://github.com/apache/thrift/commit/264a3f318ed3e9e51573f67f963c8509786bcec2', 'https://access.redhat.com/errata/RHSA-2020:0804', 'https://access.redhat.com/errata/RHSA-2020:0811', 'http://mail-archives.apache.org/mod_mbox/thrift-dev/201910.mbox/%3C277A46CA87494176B1BBCF5D72624A2A%40HAGGIS%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2019-0210', 'https://access.redhat.com/errata/RHSA-2020:0805', 'https://lists.apache.org/thread.html/r55609613abab203a1f2c1f3de050b63ae8f5c4a024df0d848d6915ff@%3Ccommits.pulsar.apache.org%3E'} | null | {'https://github.com/apache/thrift/commit/264a3f318ed3e9e51573f67f963c8509786bcec2'} | {'https://github.com/apache/thrift/commit/264a3f318ed3e9e51573f67f963c8509786bcec2'} |
Go | GO-2021-0058 | null | Due to the behavior of encoding/xml, a crafted XML document may cause
XML Digital Signature validation to be entirely bypassed, causing an
unsigned document to appear signed.
| {'CVE-2020-27846'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/crewjam/saml/security/advisories/GHSA-4hq8-gmxx-h6w9', 'https://github.com/crewjam/saml/commit/da4f1a0612c0a8dd0452cf8b3c7a6518f6b4d053'} | null | {'https://github.com/crewjam/saml/commit/da4f1a0612c0a8dd0452cf8b3c7a6518f6b4d053'} | {'https://github.com/crewjam/saml/commit/da4f1a0612c0a8dd0452cf8b3c7a6518f6b4d053'} |
Go | GHSA-xg75-q3q5-cqmv | Denial of Service in http-swagger | ### Impact
Allows an attacker to perform a DOS attack consisting of memory exhaustion on the host system.
### Patches
Yes. Please upgrade to v1.2.6.
### Workarounds
A workaround is to restrict the path prefix to the "GET" method. As shown below
```
func main() {
r := mux.NewRouter()
r.PathPrefix("/swagger/").Handler(httpSwagger.Handler(
httpSwagger.URL("http://localhost:1323/swagger/doc.json"), //The url pointing to API definition
httpSwagger.DeepLinking(true),
httpSwagger.DocExpansion("none"),
httpSwagger.DomID("#swagger-ui"),
)).Methods(http.MethodGet)
```
### References
Reporter dongguangli from https://www.huoxian.cn/ company
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [http-swagger](https://github.com/swaggo/http-swagger/issues)
| {'CVE-2022-24863'} | 2022-04-22T20:55:52Z | 2022-04-22T20:55:52Z | HIGH | null | {'CWE-400', 'CWE-755'} | {'https://github.com/swaggo/http-swagger', 'https://github.com/swaggo/http-swagger/pull/62', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24863', 'https://github.com/swaggo/http-swagger/releases/tag/v1.2.6', 'https://github.com/swaggo/http-swagger/security/advisories/GHSA-xg75-q3q5-cqmv', 'https://github.com/swaggo/http-swagger/commit/b7d83e8fba85a7a51aa7e45e8244b4173f15049e'} | null | {'https://github.com/swaggo/http-swagger/commit/b7d83e8fba85a7a51aa7e45e8244b4173f15049e'} | {'https://github.com/swaggo/http-swagger/commit/b7d83e8fba85a7a51aa7e45e8244b4173f15049e'} |
Go | GHSA-jp4j-47f9-2vc3 | Integer Overflow or Wraparound in NATS Server | An integer overflow in NATS Server 2.0.0 allows a remote attacker to crash the server by sending a crafted request. | {'CVE-2019-13126'} | 2021-05-17T16:35:04Z | 2021-05-18T18:14:55Z | HIGH | null | {'CWE-190'} | {'https://github.com/nats-io/nats-server/commits/master', 'https://github.com/nats-io/nats-server/commit/07ef71ff98f45f8c2711be4aeaf484610d891dda', 'https://github.com/nats-io/nats-server/pull/1053', 'https://github.com/nats-io/nats-server/pull/1441', 'https://nvd.nist.gov/vuln/detail/CVE-2019-13126', 'https://www.twistlock.com/labs-blog/finding-dos-vulnerability-nats-go-fuzz-cve-2019-13126/'} | null | {'https://github.com/nats-io/nats-server/commit/07ef71ff98f45f8c2711be4aeaf484610d891dda'} | {'https://github.com/nats-io/nats-server/commit/07ef71ff98f45f8c2711be4aeaf484610d891dda'} |
Go | GHSA-f5fj-7265-jxhj | Information Exposure | Gitea version prior to version 1.5.1 contains a CWE-200 vulnerability that can result in Exposure of users private email addresses. This attack appear to be exploitable via Watch a repository to receive email notifications. Emails received contain the other recipients even if they have the email set as private. This vulnerability appears to have been fixed in 1.5.1. | {'CVE-2018-1000803'} | 2021-05-12T18:09:38Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-200'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-1000803', 'https://github.com/go-gitea/gitea/pull/4664/files#diff-146e0c2b5bb1ea96c9fb73d509456e57', 'https://github.com/go-gitea/gitea/commit/194a11eb110cd98fc2ba52861abf7770db6885a3', 'https://github.com/go-gitea/gitea/pull/4664'} | null | {'https://github.com/go-gitea/gitea/commit/194a11eb110cd98fc2ba52861abf7770db6885a3'} | {'https://github.com/go-gitea/gitea/commit/194a11eb110cd98fc2ba52861abf7770db6885a3'} |
Go | GHSA-jj6m-r8jc-2gp7 | Asymmetric Resource Consumption (Amplification) in Docker containers created by Wings | ### Impact
All versions of Pterodactyl Wings preior to `1.4.4` are vulnerable to system resource exhaustion due to improper container process limits being defined. A malicious user can consume more resources than intended and cause downstream impacts to other clients on the same hardware, eventually causing the physical server to stop responding.
### Patches
Users should upgrade to `1.4.4`.
### Workarounds
There is no non-code based workaround for impacted versions of the software. Users running customized versions of this software can manually set a PID limit for containers created.
### For more information
If you have any questions or comments about this advisory:
* Contact us on [Discord](https://discord.gg/pterodactyl)
* Email us at `dane ät pterodactyl dot io` | {'CVE-2021-32699'} | 2021-10-21T13:26:03Z | 2021-06-23T18:03:18Z | MODERATE | null | {'CWE-405'} | {'https://github.com/pterodactyl/wings', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32699', 'https://github.com/pterodactyl/wings/commit/e0078eee0a71d61573a94c75e6efcad069d78de3', 'https://github.com/pterodactyl/wings/security/advisories/GHSA-jj6m-r8jc-2gp7'} | null | {'https://github.com/pterodactyl/wings/commit/e0078eee0a71d61573a94c75e6efcad069d78de3'} | {'https://github.com/pterodactyl/wings/commit/e0078eee0a71d61573a94c75e6efcad069d78de3'} |
Go | GHSA-mr6h-chqp-p9g2 | SQL Injection in gogs.io/gogs | SQL injection vulnerability in the GetIssues function in models/issue.go in Gogs (aka Go Git Service) 0.3.1-9 through 0.5.6.x before 0.5.6.1025 Beta allows remote attackers to execute arbitrary SQL commands via the label parameter to user/repos/issues. | {'CVE-2014-8681'} | 2021-05-19T21:48:08Z | 2021-06-29T18:32:44Z | MODERATE | null | {'CWE-89'} | {'http://seclists.org/fulldisclosure/2014/Nov/31', 'http://gogs.io/docs/intro/change_log.html', 'http://packetstormsecurity.com/files/129116/Gogs-Label-Search-Blind-SQL-Injection.html', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/98695', 'https://www.exploit-db.com/exploits/35237', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-8681', 'https://nvd.nist.gov/vuln/detail/CVE-2014-8681', 'https://github.com/gogits/gogs/commit/83283bca4cb4e0f4ec48a28af680f0d88db3d2c8', 'https://github.com/gogits/gogs/releases/tag/v0.5.8'} | null | {'https://github.com/gogits/gogs/commit/83283bca4cb4e0f4ec48a28af680f0d88db3d2c8'} | {'https://github.com/gogits/gogs/commit/83283bca4cb4e0f4ec48a28af680f0d88db3d2c8'} |
Go | GHSA-4fqx-74rv-638w | SQL Injection | Pivotal Concourse version 5.0.0, contains an API that is vulnerable to SQL injection. An Concourse resource can craft a version identifier that can carry a SQL injection payload to the Concourse server, allowing the attacker to read privileged data. | {'CVE-2019-3792'} | 2021-05-12T18:21:05Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-89'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-3792', 'https://github.com/concourse/concourse/blob/master/release-notes/v5.0.1.md#v501-note-1', 'https://pivotal.io/security/cve-2019-3792', 'https://github.com/concourse/concourse/commit/dc3d15ab6c3a69890c9985f9c875d4c2949be727'} | null | {'https://github.com/concourse/concourse/commit/dc3d15ab6c3a69890c9985f9c875d4c2949be727'} | {'https://github.com/concourse/concourse/commit/dc3d15ab6c3a69890c9985f9c875d4c2949be727'} |
Go | GHSA-fx95-883v-4q4h | Path traversal in github.com/valyala/fasthttp | The package github.com/valyala/fasthttp before 1.34.0 is vulnerable to Directory Traversal via the ServeFile function, due to improper sanitization. It is possible to be exploited by using a backslash %5c character in the path. **Note:** This security issue impacts Windows users only. | {'CVE-2022-21221'} | 2022-03-29T22:03:08Z | 2022-03-18T00:01:11Z | HIGH | null | {'CWE-22'} | {'https://github.com/valyala/fasthttp/commit/15262ecf3c602364639d465daba1e7f3604d00e8', 'https://github.com/valyala/fasthttp/commit/6b5bc7bb304975147b4af68df54ac214ed2554c1', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMVALYALAFASTHTTP-2407866', 'https://github.com/valyala/fasthttp', 'https://github.com/valyala/fasthttp/issues/1226', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21221', 'https://github.com/valyala/fasthttp/releases/tag/v1.34.0'} | null | {'https://github.com/valyala/fasthttp/commit/15262ecf3c602364639d465daba1e7f3604d00e8', 'https://github.com/valyala/fasthttp/commit/6b5bc7bb304975147b4af68df54ac214ed2554c1'} | {'https://github.com/valyala/fasthttp/commit/15262ecf3c602364639d465daba1e7f3604d00e8', 'https://github.com/valyala/fasthttp/commit/6b5bc7bb304975147b4af68df54ac214ed2554c1'} |
Go | GO-2020-0029 | 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.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/gin-gonic/gin/commit/0099840c98ae1473c5ff0f18bc93a8e13ceed829', 'https://github.com/gin-gonic/gin/pull/182'} | null | {'https://github.com/gin-gonic/gin/commit/0099840c98ae1473c5ff0f18bc93a8e13ceed829'} | {'https://github.com/gin-gonic/gin/commit/0099840c98ae1473c5ff0f18bc93a8e13ceed829'} |
Go | GHSA-4cxw-hq44-r344 | Off-by-one Error in v2fly/v2ray-core | v2fly/v2ray-core prior to 4.44.0 is vulnerable to an off-by-one error. Indexing operations on arrays, slices, or strings should use an index at most one less than the length. If the index is checked for being less than or equal to the length (`<=`), instead of less than the length (`<`), the index could be out of bounds. | {'CVE-2021-4070'} | 2022-03-03T19:17:50Z | 2022-02-24T00:00:52Z | CRITICAL | null | {'CWE-193'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-4070', 'https://github.com/v2fly/v2ray-core', 'https://huntr.dev/bounties/8da19456-4d89-41ef-9781-a41efd6a1877', 'https://github.com/v2fly/v2ray-core/commit/c1af2bfd7aa59a4482aa7f6ec4b9208c1d350b5c'} | null | {'https://github.com/v2fly/v2ray-core/commit/c1af2bfd7aa59a4482aa7f6ec4b9208c1d350b5c'} | {'https://github.com/v2fly/v2ray-core/commit/c1af2bfd7aa59a4482aa7f6ec4b9208c1d350b5c'} |
Go | GHSA-465w-gg5p-85c9 | Insufficient Session Expiration in Kiali | An insufficient JWT validation vulnerability was found in Kiali versions 0.4.0 to 1.15.0 and was fixed in Kiali version 1.15.1, wherein a remote attacker could abuse this flaw by stealing a valid JWT cookie and using that to spoof a user session, possibly gaining privileges to view and alter the Istio configuration. | {'CVE-2020-1762'} | 2021-05-18T20:45:55Z | 2021-05-18T21:09:01Z | HIGH | null | {'CWE-613', 'CWE-384', 'CWE-295'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1762', 'https://github.com/kiali/kiali/commit/c91a0949683976f621cca213c1193831d63b381c', 'https://nvd.nist.gov/vuln/detail/CVE-2020-1762', 'https://bugzilla.redhat.com/show_bug.cgi?id=1810387', 'https://kiali.io/news/security-bulletins/kiali-security-001/', 'https://github.com/kiali/kiali/commit/93f5cd0b6698e8fe8772afb8f35816f6c086aef1'} | null | {'https://github.com/kiali/kiali/commit/c91a0949683976f621cca213c1193831d63b381c', 'https://github.com/kiali/kiali/commit/93f5cd0b6698e8fe8772afb8f35816f6c086aef1'} | {'https://github.com/kiali/kiali/commit/93f5cd0b6698e8fe8772afb8f35816f6c086aef1', 'https://github.com/kiali/kiali/commit/c91a0949683976f621cca213c1193831d63b381c'} |
Go | GHSA-63qx-x74g-jcr7 | Path traversal and dereference of symlinks in Argo CD | ### Impact
All versions of Argo CD are vulnerable to a path traversal bug that allows to pass arbitrary values files to be consumed by Helm charts.
Additionally, it is possible to craft special Helm chart packages containing value files that are actually symbolic links, pointing to arbitrary files outside the repository's root directory.
If an attacker with permissions to create or update Applications knows or can guess the full path to a file containing valid YAML, they can create a malicious Helm chart to consume that YAML as values files, thereby gaining access to data they would otherwise have no access to.
The impact can especially become critical in environments that make use of encrypted value files (e.g. using plugins with git-crypt or SOPS) containing sensitive or confidential data, and decrypt these secrets to disk before rendering the Helm chart.
Also, because any error message from `helm template` is passed back to the user, and these error messages are quite verbose, enumeration of files on the repository server's file system is possible.
### Patches
A patch for this vulnerability has been released in the following Argo CD versions:
* v2.3.0
* v2.2.4
* v2.1.9
We urge users of Argo CD to update their installation to one of the fixed versions as listed above.
### Workarounds
No workaround for this issue.
### References
* https://apiiro.com/blog/malicious-kubernetes-helm-charts-can-be-used-to-steal-sensitive-information-from-argo-cd-deployments
* https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24348
### 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`
### Credits
The path traversal vulnerability was discovered and reported by Moshe Zioni, VP Security Research, [Apiiro](https://www.apiiro.com).
During the development of a fix for the path traversal vulnerability, the Argo CD team discovered the related issue with symbolic links.
The Argo CD team would like to thank Moshe Zioni for the responsible disclosure, and the constructive discussions during handling this issue!
| {'CVE-2022-24348'} | 2022-02-07T19:06:18Z | 2022-02-07T19:06:18Z | HIGH | null | {'CWE-200', 'CWE-22'} | {'https://github.com/argoproj/argo-cd', 'https://apiiro.com/blog/malicious-kubernetes-helm-charts-can-be-used-to-steal-sensitive-information-from-argo-cd-deployments/', 'https://github.com/argoproj/argo-cd/releases/tag/v2.1.9', 'https://github.com/argoproj/argo-cd/releases/tag/v2.2.4', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24348', 'https://github.com/argoproj/argo-cd/commit/78c2084f0febd159039ff785ddc2bd4ba1cecf88', 'https://github.com/argoproj/argo-cd/security/advisories/GHSA-63qx-x74g-jcr7'} | null | {'https://github.com/argoproj/argo-cd/commit/78c2084f0febd159039ff785ddc2bd4ba1cecf88'} | {'https://github.com/argoproj/argo-cd/commit/78c2084f0febd159039ff785ddc2bd4ba1cecf88'} |
Go | GHSA-c52f-pq47-2r9j | plugin.yaml file allows for duplicate entries in helm | ### Impact
During a security audit of Helm's code base, Helm maintainers identified a bug in which a Helm plugin can contain duplicates of the same entry, with the last one always used. If a plugin is compromised, this lowers the level of access that an attacker needs to modify a plugin's install hooks, causing a local execution attack.
To perform this attack, an attacker must have write access to the git repository or plugin archive (.tgz) while being downloaded (which can occur during a MITM attack on a non-SSL connection).
### Patches
This issue has been patched in Helm 2.16.11 and Helm 3.3.2.
### Workarounds
Make sure to install plugins using a secure connection protocol like SSL. | {'CVE-2020-15187'} | 2021-11-19T15:21:02Z | 2021-05-24T16:57:21Z | LOW | null | {'CWE-694', 'CWE-74'} | {'https://github.com/helm/helm/security/advisories/GHSA-c52f-pq47-2r9j', 'https://github.com/helm/helm/commit/6aab63765f99050b115f0aec3d6350c85e8da946', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15187', 'https://github.com/helm/helm/commit/d9ef5ce8bad512e325390c0011be1244b8380e4b', 'https://github.com/helm/helm'} | null | {'https://github.com/helm/helm/commit/d9ef5ce8bad512e325390c0011be1244b8380e4b', 'https://github.com/helm/helm/commit/6aab63765f99050b115f0aec3d6350c85e8da946'} | {'https://github.com/helm/helm/commit/6aab63765f99050b115f0aec3d6350c85e8da946', 'https://github.com/helm/helm/commit/d9ef5ce8bad512e325390c0011be1244b8380e4b'} |
Go | GHSA-gfh2-7jg5-653p | Denial of Service in docker2aci | docker2aci <= 0.12.3 has an infinite loop when handling local images with cyclic dependency chain. | {'CVE-2016-8579'} | 2021-05-20T16:29:42Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-835'} | {'https://nvd.nist.gov/vuln/detail/CVE-2016-8579', 'https://www.securityfocus.com/bid/93560', 'https://github.com/appc/docker2aci/issues/203', 'https://github.com/appc/docker2aci/pull/204/commits/54331ec7020e102935c31096f336d31f6400064f', 'https://github.com/appc/docker2aci/releases/tag/v0.13.0', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-8579'} | null | {'https://github.com/appc/docker2aci/pull/204/commits/54331ec7020e102935c31096f336d31f6400064f'} | {'https://github.com/appc/docker2aci/pull/204/commits/54331ec7020e102935c31096f336d31f6400064f'} |
Go | GHSA-q9vw-wr57-xjv3 | Information Exposure in Heketi | An access flaw was found in Heketi 5, where the heketi.json configuration file was world readable. An attacker having local access to the Heketi server could read plain-text passwords from the heketi.json file. | {'CVE-2017-15104'} | 2021-05-19T22:48:28Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-200', 'CWE-552'} | {'https://nvd.nist.gov/vuln/detail/CVE-2017-15104', 'https://github.com/heketi/heketi/commit/787bae461b23003a4daa4d1d639016a754cf6b00', 'https://access.redhat.com/security/cve/CVE-2017-15104', 'https://github.com/heketi/heketi/releases/tag/v5.0.1', 'https://access.redhat.com/errata/RHSA-2017:3481', 'https://bugzilla.redhat.com/show_bug.cgi?id=1510149'} | null | {'https://github.com/heketi/heketi/commit/787bae461b23003a4daa4d1d639016a754cf6b00'} | {'https://github.com/heketi/heketi/commit/787bae461b23003a4daa4d1d639016a754cf6b00'} |
Go | GO-2021-0063 | null | Due to a nil pointer dereference, a malicously crafted RPC message
can cause a panic. If handling RPC messages from untrusted clients,
this may be used as a denial of service vector.
| {'CVE-2020-26264'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/ethereum/go-ethereum/pull/21896', 'https://github.com/ethereum/go-ethereum/commit/bddd103a9f0af27ef533f04e06ea429cf76b6d46'} | null | {'https://github.com/ethereum/go-ethereum/commit/bddd103a9f0af27ef533f04e06ea429cf76b6d46'} | {'https://github.com/ethereum/go-ethereum/commit/bddd103a9f0af27ef533f04e06ea429cf76b6d46'} |
Go | GO-2020-0028 | null | Due to a nil pointer dereference, parsing a malformed zone file
containing TA records may cause a panic. If parsing user supplied
input, this may be used as a denial of service vector.
| {'CVE-2018-17419'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/miekg/dns/commit/501e858f679edecd4a38a86317ce50271014a80d', 'https://github.com/miekg/dns/issues/742'} | null | {'https://github.com/miekg/dns/commit/501e858f679edecd4a38a86317ce50271014a80d'} | {'https://github.com/miekg/dns/commit/501e858f679edecd4a38a86317ce50271014a80d'} |
Go | GHSA-h395-qcrw-5vmq | Inconsistent Interpretation of HTTP Requests in github.com/gin-gonic/gin | This affects all versions of package github.com/gin-gonic/gin under 1.7.0. When gin is exposed directly to the internet, a client's IP can be spoofed by setting the X-Forwarded-For header. | {'CVE-2020-28483'} | 2021-05-12T21:46:50Z | 2021-06-23T17:53:21Z | HIGH | null | {'CWE-113', 'CWE-444'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-28483', 'https://github.com/gin-gonic/gin/commit/bfc8ca285eb46dad60e037d57c545cd260636711', 'https://github.com/gin-gonic/gin/pull/2632', 'https://github.com/gin-gonic/gin/pull/2474%23issuecomment-729696437', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMGINGONICGIN-1041736', 'https://github.com/gin-gonic/gin/releases/tag/v1.7.0'} | null | {'https://github.com/gin-gonic/gin/commit/bfc8ca285eb46dad60e037d57c545cd260636711'} | {'https://github.com/gin-gonic/gin/commit/bfc8ca285eb46dad60e037d57c545cd260636711'} |
Go | GHSA-v592-xf75-856p | Erroneous Proof of Work calculation in geth | ### Impact
An ethash mining DAG generation flaw in Geth could cause miners to erroneously calculate PoW in an upcoming epoch (estimated early January, 2021). This happened on the ETC chain on 2020-11-06. This issue is relevant only for miners, non-mining nodes are unaffected.
### Patches
This issue is also fixed as of 1.9.24. Thanks to @slavikus for bringing the issue to our attention and writing the fix.
### 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-26240'} | 2021-05-21T21:52:58Z | 2021-06-29T21:12:56Z | MODERATE | null | {'CWE-682'} | {'https://github.com/ethereum/go-ethereum/commit/d990df909d7839640143344e79356754384dcdd0', 'https://github.com/ethereum/go-ethereum/security/advisories/GHSA-v592-xf75-856p', 'https://blog.ethereum.org/2020/11/12/geth_security_release/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26240', 'https://github.com/ethereum/go-ethereum/pull/21793'} | null | {'https://github.com/ethereum/go-ethereum/commit/d990df909d7839640143344e79356754384dcdd0'} | {'https://github.com/ethereum/go-ethereum/commit/d990df909d7839640143344e79356754384dcdd0'} |
Go | GHSA-4cx6-fj7j-pjx9 | Code injection in Stripe CLI on windows | ### Impact
A vulnerability in Stripe CLI exists on Windows when certain commands are run in a directory where an attacker has planted files. The commands are `stripe login`, `stripe config -e`, `stripe community`, and `stripe open`. MacOS and Linux are unaffected.
An attacker who successfully exploits the vulnerability can run arbitrary code in the context of the current user. The update addresses the vulnerability by throwing an error in these situations before the code can run.
There has been no evidence of exploitation of this vulnerability.
### Recommendation
Upgrade to Stripe CLI v1.7.13.
### Acknowledgments
Thanks to [trungpabc](https://hackerone.com/trungpabc) for reporting the issue.
### For more information
Email us at [security@stripe.com](mailto:security@stripe.com).
| {'CVE-2022-24753'} | 2022-03-18T21:10:48Z | 2022-03-10T18:17:50Z | HIGH | null | {'CWE-78'} | {'https://github.com/stripe/stripe-cli/commit/be38da5c0191adb77f661f769ffff2fbc7ddf6cd', 'https://github.com/stripe/stripe-cli', 'https://github.com/stripe/stripe-cli/security/advisories/GHSA-4cx6-fj7j-pjx9', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24753'} | null | {'https://github.com/stripe/stripe-cli/commit/be38da5c0191adb77f661f769ffff2fbc7ddf6cd'} | {'https://github.com/stripe/stripe-cli/commit/be38da5c0191adb77f661f769ffff2fbc7ddf6cd'} |
Go | GHSA-mh3m-8c74-74xh | Denial of Service in graphql-go | ### Impact
This is a DoS vulnerability that is possible due to a bug in the library that would allow an attacker with specifically designed queries to cause stack overflow panics. Any user with access to the GraphQL handler can send these queries and cause stack overflows. This in turn could potentially compromise the ability of the server to serve data to its users. To make things worse the only mitigation in affected versions creates opportunities for other attacks. This issue is only available if you are using `graphql.MaxDepth` option in your schema (which is highly recommended in most cases).
### Patches
The issue has been patched in version `v1.3.0`. We have been trying to maintain backwards compatibility and avoid breaking changes so upgrading should not be problematic.
### Workarounds
The best workaround is to patch to a version greater than or equal to `v1.3.0`.
Otherwise, the only workaround in versions prior to `v1.3.0` is to disable the `graphql.MaxDepth` option from your schema. Unfortunately, this could potentially create opportunities for other attacks.
### References
There are no references or links. This issue was reported privately and was fixed before creating this Security Advisory.
### For more information
If you have any questions or comments feel free to reach out to @pavelnikolov or @tony on the Gopher Slack. | {'CVE-2022-21708'} | 2022-01-31T21:59:33Z | 2022-01-27T15:28:06Z | MODERATE | null | {'CWE-400'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-21708', 'https://github.com/graph-gophers/graphql-go', 'https://github.com/graph-gophers/graphql-go/commit/eae31ca73eb3473c544710955d1dbebc22605bfe', 'https://github.com/graph-gophers/graphql-go/security/advisories/GHSA-mh3m-8c74-74xh'} | null | {'https://github.com/graph-gophers/graphql-go/commit/eae31ca73eb3473c544710955d1dbebc22605bfe'} | {'https://github.com/graph-gophers/graphql-go/commit/eae31ca73eb3473c544710955d1dbebc22605bfe'} |
Go | GHSA-557g-r22w-9wvx | Incorrect Permission Assignment for Critical Resource in Singularity | An issue was discovered in Singularity 3.1.0 to 3.2.0-rc2, a malicious user with local/network access to the host system (e.g. ssh) could exploit this vulnerability due to insecure permissions allowing a user to edit files within `/run/singularity/instances/sing/<user>/<instance>`. The manipulation of those files can change the behavior of the starter-suid program when instances are joined resulting in potential privilege escalation on the host. | {'CVE-2019-11328'} | 2021-05-17T15:50:05Z | 2021-12-20T18:25:33Z | HIGH | null | {'CWE-269'} | {'http://www.openwall.com/lists/oss-security/2019/05/16/1', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LNU5BUHFOTYUZVHFUSX2VG4S3RCPUEMA/', 'https://github.com/sylabs/singularity/commit/618c9d56802399adb329c23ea2b70598eaff4a31', 'http://lists.opensuse.org/opensuse-security-announce/2019-10/msg00028.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LIHV7DSEVTB5SUPEZ2UXGS3Q6WMEQSO2/', 'https://github.com/sylabs/singularity/releases/tag/v3.2.0', 'http://www.securityfocus.com/bid/108360', 'http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00059.html', 'https://nvd.nist.gov/vuln/detail/CVE-2019-11328', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5O3TPL5OOTIZEI4H6IQBCCISBARJ6WL3/'} | null | {'https://github.com/sylabs/singularity/commit/618c9d56802399adb329c23ea2b70598eaff4a31'} | {'https://github.com/sylabs/singularity/commit/618c9d56802399adb329c23ea2b70598eaff4a31'} |
Go | GHSA-vrxp-mg9f-hwf3 | Improperly Implemented path matching for in-toto-golang | ### Impact
Authenticated attackers posing as functionaries (i.e., within a trusted set of users for a layout) are able to create attestations that may bypass DISALLOW rules in the same layout. An attacker with access to trusted private keys, may issue an attestation that contains a disallowed artifact by including path traversal semantics (e.g., foo vs dir/../foo).
### Patches
The problem has been fixed in version 0.3.0.
### Workarounds
Exploiting this vulnerability is dependent on the specific policy applied.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [in-toto-golang](http://github.com/in-toto/in-toto-golang)
* Email us at [in-toto-public](mailto:in-toto-public@googlegroups.com)
* If this is a sensitive security-relevant disclosure, please send a PGP encrypted email to santiagotorres@purdue.edu or jcappos@nyu.edu
| {'CVE-2021-41087'} | 2021-09-21T21:51:18Z | 2021-09-22T20:37:09Z | MODERATE | null | {'CWE-345', 'CWE-22'} | {'https://github.com/in-toto/in-toto-golang', 'https://github.com/in-toto/in-toto-golang/security/advisories/GHSA-vrxp-mg9f-hwf3', 'https://github.com/in-toto/in-toto-golang/commit/f2c57d1e0f15e3ffbeac531829c696b72ecc4290', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41087'} | null | {'https://github.com/in-toto/in-toto-golang/commit/f2c57d1e0f15e3ffbeac531829c696b72ecc4290'} | {'https://github.com/in-toto/in-toto-golang/commit/f2c57d1e0f15e3ffbeac531829c696b72ecc4290'} |
Go | GHSA-q9mp-79cp-9g8j | Improper Authentication | Traefik 2.x, in certain configurations, allows HTTPS sessions to proceed without mutual TLS verification in a situation where ERR_BAD_SSL_CLIENT_AUTH_CERT should have occurred. | {'CVE-2019-20894'} | 2021-08-02T22:18:22Z | 2021-09-02T22:00:09Z | HIGH | null | {'CWE-287', 'CWE-295'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-20894', 'https://github.com/containous/traefik/issues/5312', 'https://github.com/containous/traefik/pull/7008', 'https://github.com/containous/traefik/commit/2b353971696717e980521b0e4baa1eba66c8d2bf'} | null | {'https://github.com/containous/traefik/commit/2b353971696717e980521b0e4baa1eba66c8d2bf'} | {'https://github.com/containous/traefik/commit/2b353971696717e980521b0e4baa1eba66c8d2bf'} |
Go | GHSA-8wrg-m8vm-5fvj | Authentication Bypass by Primary Weakness in github.com/kongchuanhujiao/server | ### Impact
Authentication Bypass by Primary Weakness (CWE-305)
Commit:
https://github.com/kongchuanhujiao/server/commit/9a125624f219e496bdf4b07b404816d5a309bdc1
ALL Users is impacted.
### Patches
Yes, PLEASE UPGRADE TO v1.3.21-beta.d0ffc0a6 | {'CVE-2021-21403'} | 2021-05-20T22:25:09Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-305'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-21403', 'https://github.com/kongchuanhujiao/server/security/advisories/GHSA-8wrg-m8vm-5fvj', 'https://github.com/kongchuanhujiao/server/commit/9a125624f219e496bdf4b07b404816d5a309bdc1'} | null | {'https://github.com/kongchuanhujiao/server/commit/9a125624f219e496bdf4b07b404816d5a309bdc1'} | {'https://github.com/kongchuanhujiao/server/commit/9a125624f219e496bdf4b07b404816d5a309bdc1'} |
Go | GHSA-mqf3-28j7-3mj6 | Information Exposure in Kubernetes | Kubernetes before 1.2.0-alpha.5 allows remote attackers to read arbitrary pod logs via a container name. | {'CVE-2015-7528'} | 2022-04-12T22:40:14Z | 2022-04-12T22:40:14Z | MODERATE | null | {'CWE-200'} | {'https://github.com/kubernetes/kubernetes/pull/17886', 'https://nvd.nist.gov/vuln/detail/CVE-2015-7528', 'https://github.com/kubernetes/kubernetes/releases/tag/v1.2.0-alpha.5', 'https://github.com/kubernetes/kubernetes', 'https://github.com/kubernetes/kubernetes/commit/afd56495a1052a3387b81df1786a8d0f51bc8671', 'http://rhn.redhat.com/errata/RHSA-2015-2615.html', 'https://github.com/openshift/origin/pull/6113', 'https://access.redhat.com/errata/RHSA-2015:2544'} | null | {'https://github.com/kubernetes/kubernetes/commit/afd56495a1052a3387b81df1786a8d0f51bc8671'} | {'https://github.com/kubernetes/kubernetes/commit/afd56495a1052a3387b81df1786a8d0f51bc8671'} |
Go | GO-2021-0075 | null | Due to improper argument validation in RPC messages, a maliciously crafted
message can cause a panic, leading to denial of service.
| {'CVE-2018-12018'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://peckshield.com/2018/06/27/EPoD/', 'https://github.com/ethereum/go-ethereum/commit/a5237a27eaf81946a3edb4fafe13ed6359d119e4', 'https://github.com/ethereum/go-ethereum/pull/16891'} | null | {'https://github.com/ethereum/go-ethereum/commit/a5237a27eaf81946a3edb4fafe13ed6359d119e4'} | {'https://github.com/ethereum/go-ethereum/commit/a5237a27eaf81946a3edb4fafe13ed6359d119e4'} |
Go | GHSA-pf59-j7c2-rh6x | Exposure of Sensitive Information to an Unauthorized Actor and Insertion of Sensitive Information Into Sent Data in Calico | Clusters using Calico (version 3.14.0 and below), Calico Enterprise (version 2.8.2 and below), may be vulnerable to information disclosure if IPv6 is enabled but unused. A compromised pod with sufficient privilege is able to reconfigure the node’s IPv6 interface due to the node accepting route advertisement by default, allowing the attacker to redirect full or partial network traffic from the node to the compromised pod. | {'CVE-2020-13597'} | 2021-05-14T16:27:14Z | 2022-02-15T01:57:18Z | LOW | null | {'CWE-200', 'CWE-201'} | {'https://github.com/kubernetes/kubernetes/issues/91507', 'https://nvd.nist.gov/vuln/detail/CVE-2020-13597', 'https://groups.google.com/forum/#!topic/kubernetes-security-announce/BMb_6ICCfp8', 'https://github.com/containernetworking/plugins/pull/484/', 'https://github.com/containernetworking/plugins/commit/ad10b6fa91aacd720f1f9ab94341a97a82a24965', 'https://www.projectcalico.org/security-bulletins/'} | null | {'https://github.com/containernetworking/plugins/commit/ad10b6fa91aacd720f1f9ab94341a97a82a24965'} | {'https://github.com/containernetworking/plugins/commit/ad10b6fa91aacd720f1f9ab94341a97a82a24965'} |
Go | GO-2020-0045 | null | CSRF tokens are generated using math/rand, which is not a cryptographically secure
rander number generation, making predicting their values relatively trivial and
allowing an attacker to bypass CSRF protections which relatively few requests.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/dinever/golf/issues/20', 'https://github.com/dinever/golf/commit/3776f338be48b5bc5e8cf9faff7851fc52a3f1fe', 'https://github.com/dinever/golf/pull/24'} | null | {'https://github.com/dinever/golf/commit/3776f338be48b5bc5e8cf9faff7851fc52a3f1fe'} | {'https://github.com/dinever/golf/commit/3776f338be48b5bc5e8cf9faff7851fc52a3f1fe'} |
Go | GO-2021-0059 | 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-35380'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/tidwall/gjson/issues/192', 'https://github.com/tidwall/gjson/commit/f0ee9ebde4b619767ae4ac03e8e42addb530f6bc'} | null | {'https://github.com/tidwall/gjson/commit/f0ee9ebde4b619767ae4ac03e8e42addb530f6bc'} | {'https://github.com/tidwall/gjson/commit/f0ee9ebde4b619767ae4ac03e8e42addb530f6bc'} |
Go | GHSA-rfq3-w54c-f9q5 | OAuth2 Redirect URL validity does not respect query parameters and character casing for loopback addresses | ### Impact
[fosite#400](https://github.com/ory/fosite/pull/400) (released as v0.30.2) introduced a new feature for handling redirect URLs pointing to loopback interfaces ([rfc8252#section-7.3](https://tools.ietf.org/html/rfc8252#section-7.3)). As part of that change new behavior was introduced which failed to respect the redirect URL's (only for loopback interfaces!) query parameters
1. Registering a client with allowed redirect URL `http://127.0.0.1/callback`
2. Performing OAuth2 flow and requesting redirect URL `http://127.0.0.1/callback?bar=foo`
3. Instead of an error, the browser is redirected to `http://127.0.0.1/callback?bar=foo` with a potentially successful OAuth2 response.
as well as the host parameter (as long as the host is a loopback interface):
1. Registering a client with allowed redirect URL `https://example.com/callback`
2. Performing OAuth2 flow and requesting redirect URL `http://127.0.0.1/callback`
3. Instead of an error, the browser is redirected to `http://127.0.0.1/callback` with a potentially successful OAuth2 response.
These bugs are only applicable in scenarios where the attacker has control over the loopback interface (`localhost`, `127.0.0.1`, `[::1]`) where the browser performing the OAuth2 flow is running. | {'CVE-2020-15233'} | 2021-11-19T14:42:56Z | 2021-05-24T17:00:12Z | MODERATE | null | {'CWE-601', 'CWE-20'} | {'https://github.com/ory/fosite/pull/400', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15233', 'https://github.com/ory/fosite', 'https://github.com/ory/fosite/commit/cdee51ebe721bfc8acca0fd0b86b030ca70867bf', 'https://github.com/ory/fosite/security/advisories/GHSA-rfq3-w54c-f9q5'} | null | {'https://github.com/ory/fosite/commit/cdee51ebe721bfc8acca0fd0b86b030ca70867bf'} | {'https://github.com/ory/fosite/commit/cdee51ebe721bfc8acca0fd0b86b030ca70867bf'} |
Go | GHSA-rqjq-mrgx-85hp | Allocation of Resources Without Limits or Throttling in Hashicorp Consul | HashiCorp Consul and Consul Enterprise include an HTTP API (introduced in 1.2.0) and DNS (introduced in 1.4.3) caching feature that was vulnerable to denial of service. Fixed in 1.6.6 and 1.7.4. | {'CVE-2020-13250'} | 2021-07-29T18:19:34Z | 2021-05-18T18:21:35Z | HIGH | null | {'CWE-770'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-13250', 'https://github.com/hashicorp/consul/blob/v1.7.4/CHANGELOG.md', 'https://github.com/hashicorp/consul/pull/8023', 'https://github.com/hashicorp/consul/commit/72f92ae7ca4cabc1dc3069362a9b64ef46941432', 'https://github.com/hashicorp/consul/blob/v1.6.6/CHANGELOG.md'} | null | {'https://github.com/hashicorp/consul/commit/72f92ae7ca4cabc1dc3069362a9b64ef46941432'} | {'https://github.com/hashicorp/consul/commit/72f92ae7ca4cabc1dc3069362a9b64ef46941432'} |
Go | GO-2020-0012 | null | An attacker can craft an ssh-ed25519 or sk-ssh-ed25519@openssh.com public
key, such that the library will panic when trying to verify a signature
with it. If verifying signatures using user supplied public keys, this
may be used as a denial of service vector.
| {'CVE-2020-9283'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://go-review.googlesource.com/c/crypto/+/220357', 'https://groups.google.com/g/golang-announce/c/3L45YRc91SY', 'https://github.com/golang/crypto/commit/bac4c82f69751a6dd76e702d54b3ceb88adab236'} | null | {'https://github.com/golang/crypto/commit/bac4c82f69751a6dd76e702d54b3ceb88adab236'} | {'https://github.com/golang/crypto/commit/bac4c82f69751a6dd76e702d54b3ceb88adab236'} |
Go | GHSA-ch68-7cf4-35vr | Limited ability to spoof SAML authentication with missing audience verification in Fleet | ### Impact
This impacts deployments using SAML SSO in two specific cases:
1. A malicious or compromised Service Provider (SP) could reuse the SAML response to log into Fleet as a user -- only if the user has an account with the same email in Fleet, _and_ the user signs into the malicious SP via SAML SSO from the same Identity Provider (IdP) configured with Fleet.
2. A user with an account in Fleet could reuse a SAML response intended for another SP to log into Fleet. This is only a concern if the user is blocked from Fleet in the IdP, but continues to have an account in Fleet. If the user is blocked from the IdP entirely, this cannot be exploited.
### Patches
Fleet 4.9.1 resolves this issue.
### Workarounds and good practices
* Reduce the length of sessions on your IdP to reduce the window for malicious re-use.
* Limit the amount of SAML Service Providers/Applications used by user accounts with access to Fleet.
* When removing access to Fleet in the IdP, delete the Fleet user from Fleet as well.
### For more information
If you have any questions or comments about this advisory:
* Join us in the #fleet channel of [osquery Slack](https://join.slack.com/t/osquery/shared_invite/zt-h29zm0gk-s2DBtGUTW4CFel0f0IjTEw).
* Email us at [security@fleetdm.com](mailto:security@fleetdm.com). | {'CVE-2022-23600'} | 2022-02-07T21:57:38Z | 2022-02-07T21:57:38Z | MODERATE | null | {'CWE-287', 'CWE-284'} | {'https://github.com/fleetdm/fleet', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23600', 'https://github.com/fleetdm/fleet/security/advisories/GHSA-ch68-7cf4-35vr', 'https://github.com/fleetdm/fleet/commit/35d5a7b285f15ddd47486fa656e8b1acf3d48374'} | null | {'https://github.com/fleetdm/fleet/commit/35d5a7b285f15ddd47486fa656e8b1acf3d48374'} | {'https://github.com/fleetdm/fleet/commit/35d5a7b285f15ddd47486fa656e8b1acf3d48374'} |
Go | GHSA-2v6x-frw8-7r7f | Exposure of Sensitive Information to an Unauthorized Actor in kube-state-metrics | A security issue was discovered in kube-state-metrics 1.7.x before 1.7.2. An experimental feature was added to v1.7.0 and v1.7.1 that enabled annotations to be exposed as metrics. By default, kube-state-metrics metrics only expose metadata about Secrets. However, a combination of the default kubectl behavior and this new feature can cause the entire secret content to end up in metric labels, thus inadvertently exposing the secret content in metrics. | {'CVE-2019-17110'} | 2021-05-17T21:04:15Z | 2021-05-18T15:38:54Z | MODERATE | null | {'CWE-200'} | {'https://github.com/kubernetes/kube-state-metrics/commit/2a9ab3a9a0f1c4dbecb6a5577185b33bfac86a96', 'https://github.com/kubernetes/kube-state-metrics/commit/03122fe3e2df49a9a7298b8af921d3c37c430f7f', 'https://nvd.nist.gov/vuln/detail/CVE-2019-17110', 'https://github.com/kubernetes/kube-state-metrics/releases/tag/v1.7.2'} | null | {'https://github.com/kubernetes/kube-state-metrics/commit/2a9ab3a9a0f1c4dbecb6a5577185b33bfac86a96', 'https://github.com/kubernetes/kube-state-metrics/commit/03122fe3e2df49a9a7298b8af921d3c37c430f7f'} | {'https://github.com/kubernetes/kube-state-metrics/commit/2a9ab3a9a0f1c4dbecb6a5577185b33bfac86a96', 'https://github.com/kubernetes/kube-state-metrics/commit/03122fe3e2df49a9a7298b8af921d3c37c430f7f'} |
Go | GO-2020-0004 | null | If any of the `ListenAndServe` functions are called with an empty token,
token authentication is disabled globally for all listeners.
Also, a minor timing side channel was present allowing attackers with
very low latency and able to make a lot of requests to potentially
recover the token.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/nanobox-io/golang-nanoauth/commit/063a3fb69896acf985759f0fe3851f15973993f3', 'https://github.com/nanobox-io/golang-nanoauth/pull/5'} | null | {'https://github.com/nanobox-io/golang-nanoauth/commit/063a3fb69896acf985759f0fe3851f15973993f3'} | {'https://github.com/nanobox-io/golang-nanoauth/commit/063a3fb69896acf985759f0fe3851f15973993f3'} |
Go | GHSA-q8q8-93cv-v6h8 | Lookup function information discolosure in helm | The Helm core maintainers have identified an information disclosure vulnerability in Helm 3.0.0-3.1.2.
### Impact
`lookup` is a Helm template function introduced in Helm v3. It is able to lookup resources in the cluster to check for the existence of specific resources and get details about them. This can be used as part of the process to render templates.
The documented behavior of `helm template` states that it does not attach to a remote cluster. However, as the recently added `lookup` template function circumvents this restriction and connects to the cluster even during `helm template` and `helm install|update|delete|rollback --dry-run`. The user is not notified of this behavior.
Running `helm template` should not make calls to a cluster. This is different from `install`, which is presumed to have access to a cluster in order to load resources into Kubernetes. Helm 2 is unaffected by this vulnerability.
A malicious chart author could inject a `lookup` into a chart that, when rendered through `helm template`, performs unannounced lookups against the cluster a user's `KUBECONFIG` file points to. This information can then be disclosed via the output of `helm template`.
### Patches
This issue has been fixed in Helm 3.2.0
### Workarounds
Due to another bug (also fixed in Helm 3.2.0), the command `helm lint` will fail with an error if the `lookup` function is used in a chart. Therefore, run `helm lint` on an untrusted chart before running `helm template`.
Alternately, setting the `KUBECONFIG` environment variable to point to an empty Kubernetes configuration file will prevent unintended network connections.
Finally, a chart may be manually analyzed for the presence of a `lookup` function in any file in the `templates/` directory.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the Helm repository](https://github.com/helm/helm/issues)
* For security-specific issues, email us at [cncf-helm-security@lists.cncf.io](mailto:cncf-helm-security@lists.cncf.io) | {'CVE-2020-11013'} | 2021-05-24T21:15:16Z | 2021-05-27T18:44:56Z | HIGH | null | {'CWE-200'} | {'https://github.com/helm/helm/releases/tag/v3.2.0', 'https://github.com/helm/helm/pull/7969', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11013', 'https://github.com/helm/helm/pull/7969/commits/c67b644a791a8fa61c760a3a0474533e63e74008', 'https://github.com/helm/helm/security/advisories/GHSA-q8q8-93cv-v6h8'} | null | {'https://github.com/helm/helm/pull/7969/commits/c67b644a791a8fa61c760a3a0474533e63e74008'} | {'https://github.com/helm/helm/pull/7969/commits/c67b644a791a8fa61c760a3a0474533e63e74008'} |
Go | GHSA-c8xp-8mf3-62h9 | OctoRPKI lacks contextual out-of-bounds check when validating RPKI ROA maxLength values | Any CA issuer in the RPKI can trick OctoRPKI prior to https://github.com/cloudflare/cfrpki/commit/a8db4e009ef217484598ba1fd1c595b54e0f6422 into emitting an invalid VRP "MaxLength" value, causing RTR sessions to terminate.
### Impact
An attacker can use this to disable RPKI Origin Validation in a victim network (for example AS 13335 - Cloudflare) prior to launching a BGP hijack which during normal operations would be rejected as "RPKI invalid". Additionally, in certain deployments RTR session flapping in and of itself also could cause BGP routing churn, causing availability issues.
### Patches
https://github.com/cloudflare/cfrpki/commit/a8db4e009ef217484598ba1fd1c595b54e0f6422
https://github.com/cloudflare/cfrpki/releases/tag/v1.3.0
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@cloudflare.com](security@cloudflare.com)
| {'CVE-2021-3761'} | 2021-09-03T21:40:39Z | 2021-09-07T23:02:18Z | HIGH | null | {'CWE-787', 'CWE-295'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-3761', 'https://github.com/cloudflare/cfrpki/releases/tag/v1.3.0', 'https://www.debian.org/security/2022/dsa-5041', 'https://github.com/cloudflare/cfrpki/security/advisories/GHSA-c8xp-8mf3-62h9', 'https://github.com/cloudflare/cfrpki/commit/a8db4e009ef217484598ba1fd1c595b54e0f6422', 'github.com/cloudflare/cfrpki'} | null | {'https://github.com/cloudflare/cfrpki/commit/a8db4e009ef217484598ba1fd1c595b54e0f6422'} | {'https://github.com/cloudflare/cfrpki/commit/a8db4e009ef217484598ba1fd1c595b54e0f6422'} |
Go | GHSA-86f3-hf24-76q4 | Use of Hard-coded Cryptographic Key in Netmaker | ### Impact
There is a hard-coded cryptographic key in the code base which can be exploited to run admin commands on a remote server, if you know the address and username of the admin. This effects the server (netmaker) component, and not clients.
### Patches
This has been patched in Netmaker v0.8.5, v0.9.4, and v0.10.0. If you are running these versions, the fix is to perform the following:
1. docker-compose down
2. docker pull gravitl/netmaker:( version )
3. docker-compose up -d
#### Additional Information
If you are running **any other version**, you will need to upgrade to one of these three versions. If you have a special circumstance that requires running a different version, let us know and we may be able to build a custom patch.
### For more information
If you have any questions or comments about this advisory:
* Email us at [info@gravitl.com](mailto:info@gravitl.com)
| {'CVE-2022-23650'} | 2022-02-22T19:40:23Z | 2022-02-22T19:40:23Z | HIGH | null | {'CWE-321', 'CWE-798'} | {'https://github.com/gravitl/netmaker/commit/3d4f44ecfe8be4ca38920556ba3b90502ffb4fee', 'https://github.com/gravitl/netmaker/commit/e9bce264719f88c30e252ecc754d08f422f4c080', 'https://github.com/gravitl/netmaker', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23650', 'https://github.com/gravitl/netmaker/security/advisories/GHSA-86f3-hf24-76q4', 'https://github.com/gravitl/netmaker/pull/781/commits/1bec97c662670dfdab804343fc42ae4b1d050a87'} | null | {'https://github.com/gravitl/netmaker/commit/3d4f44ecfe8be4ca38920556ba3b90502ffb4fee', 'https://github.com/gravitl/netmaker/pull/781/commits/1bec97c662670dfdab804343fc42ae4b1d050a87', 'https://github.com/gravitl/netmaker/commit/e9bce264719f88c30e252ecc754d08f422f4c080'} | {'https://github.com/gravitl/netmaker/pull/781/commits/1bec97c662670dfdab804343fc42ae4b1d050a87', 'https://github.com/gravitl/netmaker/commit/3d4f44ecfe8be4ca38920556ba3b90502ffb4fee', 'https://github.com/gravitl/netmaker/commit/e9bce264719f88c30e252ecc754d08f422f4c080'} |
Go | GHSA-99cg-575x-774p | Improper Input Validation in AKPublic.Verify with attacker-controlled TPM Quote | ### Impact
An improper input validation vulnerability in go-attestation before 0.4.0 allows local users to provide a maliciously-formed Quote over no/some PCRs, causing `AKPublic.Verify` to succeed despite the inconsistency. Subsequent use of the same set of PCR values in `Eventlog.Verify` lacks the authentication performed by quote verification, meaning a local attacker could couple this vulnerability with a maliciously-crafted TCG log in `Eventlog.Verify` to spoof events in the TCG log, hence defeating remotely-attested measured-boot.
### Patches
This issue is resolved in version 0.4.0. If your usage of this library verifies PCRs using multiple quotes, make sure to use the new method `AKPublic.VerifyAll()` instead of `AKPublic.Verify`. | {'CVE-2022-0317'} | 2022-02-11T15:06:33Z | 2022-02-01T00:43:17Z | MODERATE | null | {'CWE-20'} | {'https://github.com/google/go-attestation/commit/82f2c9c2c76e1d3691d17ee78116d1d93a123788', 'https://github.com/google/go-attestation/', 'https://github.com/google/go-attestation/security/advisories/GHSA-99cg-575x-774p', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0317'} | null | {'https://github.com/google/go-attestation/commit/82f2c9c2c76e1d3691d17ee78116d1d93a123788'} | {'https://github.com/google/go-attestation/commit/82f2c9c2c76e1d3691d17ee78116d1d93a123788'} |
Go | GHSA-pw59-4qgf-jxr8 | Cache Manipulation Attack in Apache Traffic Control | When ORT (now via atstccfg) generates ip_allow.config files in Apache Traffic Control 3.0.0 to 3.1.0 and 4.0.0 to 4.1.0, those files include permissions that allow bad actors to push arbitrary content into and remove arbitrary content from CDN cache servers. Additionally, these permissions are potentially extended to IP addresses outside the desired range, resulting in them being granted to clients possibly outside the CDN arcitechture. | {'CVE-2020-17522'} | 2022-04-04T21:27:42Z | 2021-06-18T22:04:32Z | MODERATE | null | {'CWE-525', 'CWE-732'} | {'https://github.com/apache/trafficcontrol/commit/492290d810e9608afb5d265b98cd3f3e153e776b', 'https://lists.apache.org/thread.html/r3de212a3da73bcf98fa2db7eafb75b2eb8e131ff466e6efc4284df09%40%3Cdev.trafficcontrol.apache.org%3E', 'https://github.com/apache/trafficcontrol', 'https://lists.apache.org/thread.html/rc8bfd7d4f71d61e9193efcd4699eccbab3c202ec1d75ed9d502f08bf@%3Ccommits.trafficcontrol.apache.org%3E', 'https://lists.apache.org/thread.html/r3c675031ac220b5eae64a9c84a03ee60045c6045738607dca4a96cb8@%3Ccommits.trafficcontrol.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-17522'} | null | {'https://github.com/apache/trafficcontrol/commit/492290d810e9608afb5d265b98cd3f3e153e776b'} | {'https://github.com/apache/trafficcontrol/commit/492290d810e9608afb5d265b98cd3f3e153e776b'} |
Go | GHSA-82mm-ffjr-h86c | Authorization bypass in Istio | "In Istio 1.5.0 though 1.5.8 and Istio 1.6.0 through 1.6.7, when users specify an AuthorizationPolicy resource with DENY actions using wildcard suffixes (e.g. *-some-suffix) for source principals or namespace fields, callers will never be denied access, bypassing the intended policy." | {'CVE-2020-16844'} | 2021-05-12T21:59:07Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-284'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-16844', 'https://istio.io/latest/news/security/istio-security-2020-009/', 'https://istio.io/latest/news/releases/1.5.x/announcing-1.5.9/', 'https://github.com/istio/istio/commit/4c73414556b83f0e75c1b3a0a89a23103a71573c', 'https://istio.io/latest/news/releases/1.6.x/announcing-1.6.8/', 'https://github.com/istio/istio/releases/tag/1.6.8', 'https://github.com/istio/istio/releases/tag/1.5.9', 'https://github.com/istio/istio/commit/72d2e135374f421b656d6f1a21f474db46134ace', 'https://github.com/istio/istio/releases'} | null | {'https://github.com/istio/istio/commit/72d2e135374f421b656d6f1a21f474db46134ace', 'https://github.com/istio/istio/commit/4c73414556b83f0e75c1b3a0a89a23103a71573c'} | {'https://github.com/istio/istio/commit/4c73414556b83f0e75c1b3a0a89a23103a71573c', 'https://github.com/istio/istio/commit/72d2e135374f421b656d6f1a21f474db46134ace'} |
Go | GO-2020-0024 | null | The RemoteAddr and LocalAddr methods on the returned net.Conn may
call themselves, leading to an infinite loop which will crash the
program due to a stack overflow.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/btcsuite/go-socks/commit/233bccbb1abe02f05750f7ace66f5bffdb13defc'} | null | {'https://github.com/btcsuite/go-socks/commit/233bccbb1abe02f05750f7ace66f5bffdb13defc'} | {'https://github.com/btcsuite/go-socks/commit/233bccbb1abe02f05750f7ace66f5bffdb13defc'} |
Go | GHSA-93p5-8fqw-wjx3 | Authentication bypass by capture-replay in github.com/cosmos/ethermint | Cosmos Network Ethermint <= v0.4.0 is affected by a transaction replay vulnerability in the EVM module. If the victim sends a very large nonce transaction, the attacker can replay the transaction through the application. | {'CVE-2021-25834'} | 2021-05-12T21:17:36Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-294', 'CWE-287'} | {'https://github.com/cosmos/ethermint/commit/d7bdbd7488644f0aaeee5cdcdc119c863f199f72', 'https://github.com/cosmos/ethermint/releases/tag/v0.4.1', 'https://github.com/cosmos/ethermint/issues/686', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25834'} | null | {'https://github.com/cosmos/ethermint/commit/d7bdbd7488644f0aaeee5cdcdc119c863f199f72'} | {'https://github.com/cosmos/ethermint/commit/d7bdbd7488644f0aaeee5cdcdc119c863f199f72'} |
Go | GHSA-6rrw-4fm9-rghv | Use of Hard-coded Cryptographic Key in Netmaker | Netmaker prior to versions 0.8.5, 0.9.4, 0.10.0, and 0.10.1 uses a hard-coded cryptographic key. | {'CVE-2022-0664'} | 2022-02-23T15:45:21Z | 2022-02-19T00:01:36Z | HIGH | null | {'CWE-321'} | {'https://github.com/gravitl/netmaker', 'https://huntr.dev/bounties/29898a42-fd4f-4b5b-a8e3-ab573cb87eac', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0664', 'https://github.com/gravitl/netmaker/commit/9bee12642986cb9534e268447b70e6f0f03c59cf'} | null | {'https://github.com/gravitl/netmaker/commit/9bee12642986cb9534e268447b70e6f0f03c59cf'} | {'https://github.com/gravitl/netmaker/commit/9bee12642986cb9534e268447b70e6f0f03c59cf'} |
Go | GHSA-rrp4-2xx3-mv29 | Command injection in gh-ost | Gh-ost version <= 1.1.2 allows users to inject DSN strings via the `-database` parameter.
This is a low severity vulnerability as the attacker must have access to the target host or trick an administrator into executing a malicious `gh-ost` command on a host running `gh-ost`, plus network access from host running `gh-ost` to the attack's malicious MySQL server.
### Impact
This issue may lead to arbitrary local file read.
### Patches
Fixed in 1.1.3+.
### Workarounds
None
### References
- https://advisory.dw1.io/51
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [github/gh-ost](http://github.com/github/gh-ost) | {'CVE-2022-21687'} | 2022-02-07T21:07:25Z | 2022-02-01T00:47:33Z | MODERATE | null | {'CWE-20', 'CWE-74'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-21687', 'https://github.com/github/gh-ost/commit/a91ab042de013cfd8fbb633763438932d9080d8f', 'https://github.com/github/gh-ost/security/advisories/GHSA-rrp4-2xx3-mv29', 'https://github.com/github/gh-ost'} | null | {'https://github.com/github/gh-ost/commit/a91ab042de013cfd8fbb633763438932d9080d8f'} | {'https://github.com/github/gh-ost/commit/a91ab042de013cfd8fbb633763438932d9080d8f'} |
Go | GHSA-5wmg-j84w-4jj4 | Arbitrary File Write via Archive Extraction in mholt/archiver | mholt/archiver golang package before e4ef56d48eb029648b0e895bb0b6a393ef0829c3 is vulnerable to directory traversal, allowing attackers to write to arbitrary files via a ../ (dot dot slash) in an archive entry that is mishandled during extraction. This vulnerability is also known as 'Zip-Slip'. | {'CVE-2018-1002207'} | 2021-05-20T16:56:29Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-1002207', 'https://github.com/mholt/archiver/commit/e4ef56d48eb029648b0e895bb0b6a393ef0829c3', 'https://github.com/snyk/zip-slip-vulnerability', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMMHOLTARCHIVERCMDARCHIVER-50071', 'https://snyk.io/research/zip-slip-vulnerability', 'https://github.com/mholt/archiver/pull/65'} | null | {'https://github.com/mholt/archiver/commit/e4ef56d48eb029648b0e895bb0b6a393ef0829c3'} | {'https://github.com/mholt/archiver/commit/e4ef56d48eb029648b0e895bb0b6a393ef0829c3'} |
Go | GHSA-579h-mv94-g4gp | Privilege Escalation in Kubernetes | In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied upgrade requests in the kube-apiserver allowed specially crafted requests to establish a connection through the Kubernetes API server to backend servers, then send arbitrary requests over the same connection directly to the backend, authenticated with the Kubernetes API server's TLS credentials used to establish the backend connection. | {'CVE-2018-1002105'} | 2021-05-20T20:40:04Z | 2022-02-15T01:57:18Z | CRITICAL | null | {'CWE-269'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-1002105', 'https://access.redhat.com/errata/RHSA-2018:3624', 'https://www.openwall.com/lists/oss-security/2019/06/28/2', 'https://github.com/kubernetes/kubernetes/commit/2257c1ecbe3c0cf71dd50b82752ae189c94ec905', 'https://access.redhat.com/errata/RHSA-2018:3752', 'https://access.redhat.com/errata/RHSA-2018:3754', 'https://security.netapp.com/advisory/ntap-20190416-0001/', 'https://github.com/kubernetes/kubernetes/issues/71411', 'https://access.redhat.com/errata/RHSA-2018:3549', 'https://github.com/evict/poc_CVE-2018-1002105', 'https://access.redhat.com/errata/RHSA-2018:3537', 'https://access.redhat.com/errata/RHSA-2018:3551', 'https://www.exploit-db.com/exploits/46053', 'https://www.exploit-db.com/exploits/46053/', 'https://access.redhat.com/errata/RHSA-2018:3598', 'https://access.redhat.com/errata/RHSA-2018:3742', 'https://groups.google.com/forum/#!topic/kubernetes-announce/GVllWCg6L88', 'https://www.openwall.com/lists/oss-security/2019/07/06/3', 'https://www.openwall.com/lists/oss-security/2019/07/06/4', 'https://www.exploit-db.com/exploits/46052/', 'https://lists.opensuse.org/opensuse-security-announce/2020-04/msg00041.html', 'https://www.coalfire.com/The-Coalfire-Blog/December-2018/Kubernetes-Vulnerability-What-You-Can-Should-Do', 'https://www.securityfocus.com/bid/106068'} | null | {'https://github.com/kubernetes/kubernetes/commit/2257c1ecbe3c0cf71dd50b82752ae189c94ec905'} | {'https://github.com/kubernetes/kubernetes/commit/2257c1ecbe3c0cf71dd50b82752ae189c94ec905'} |
Go | GO-2020-0032 | null | Due to improper santization of user input, Controller.FileHandler 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/goadesign/goa/pull/2388', 'https://github.com/goadesign/goa/commit/70b5a199d0f813d74423993832c424e1fc73fb39'} | null | {'https://github.com/goadesign/goa/commit/70b5a199d0f813d74423993832c424e1fc73fb39'} | {'https://github.com/goadesign/goa/commit/70b5a199d0f813d74423993832c424e1fc73fb39'} |
Go | GO-2021-0096 | null | Due to improper setting of finalizers, memory passed to C may be freed before it is used,
leading to crashes due to memory corruption or possible code execution.
| {'CVE-2020-8945'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://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-vc3x-gx6c-g99f | Denial of Service in Bytom | In the client in Bytom before 1.0.6, checkTopicRegister in p2p/discover/net.go does not prevent negative idx values, leading to a crash. | {'CVE-2018-18206'} | 2021-05-20T18:55:02Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-190'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-18206', 'https://github.com/Bytom/bytom/pull/1307', 'https://github.com/Bytom/bytom/commit/1ac3c8ac4f2b1e1df9675228290bda6b9586ba42'} | null | {'https://github.com/Bytom/bytom/commit/1ac3c8ac4f2b1e1df9675228290bda6b9586ba42'} | {'https://github.com/Bytom/bytom/commit/1ac3c8ac4f2b1e1df9675228290bda6b9586ba42'} |
Go | GO-2021-0079 | null | A malformed query can cause an out-of-bounds panic due to improper
validation of arguments. If processing queries from untrusted
parties, this may be used as a vector for denial of service
attacks.
| {'CVE-2018-18206'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/Bytom/bytom/commit/1ac3c8ac4f2b1e1df9675228290bda6b9586ba42', 'https://github.com/Bytom/bytom/pull/1307'} | null | {'https://github.com/Bytom/bytom/commit/1ac3c8ac4f2b1e1df9675228290bda6b9586ba42'} | {'https://github.com/Bytom/bytom/commit/1ac3c8ac4f2b1e1df9675228290bda6b9586ba42'} |
Go | GHSA-qj26-7grj-whg3 | Privilege Escalation in fscrypt | The pam_fscrypt module in fscrypt before 0.2.4 may incorrectly restore primary and supplementary group IDs to the values associated with the root user, which allows attackers to gain privileges via a successful login through certain applications that use Linux-PAM (aka pam). | {'CVE-2018-6558'} | 2021-05-20T21:04:58Z | 2021-06-23T17:18:49Z | MODERATE | null | null | {'https://launchpad.net/bugs/1787548', 'https://github.com/google/fscrypt/commit/3022c1603d968c22f147b4a2c49c4637dd1be91b', 'https://github.com/google/fscrypt/commit/315f9b042237200174a1fb99427f74027e191d66', 'https://github.com/google/fscrypt/issues/77', 'https://nvd.nist.gov/vuln/detail/CVE-2018-6558'} | null | {'https://github.com/google/fscrypt/commit/3022c1603d968c22f147b4a2c49c4637dd1be91b', 'https://github.com/google/fscrypt/commit/315f9b042237200174a1fb99427f74027e191d66'} | {'https://github.com/google/fscrypt/commit/315f9b042237200174a1fb99427f74027e191d66', 'https://github.com/google/fscrypt/commit/3022c1603d968c22f147b4a2c49c4637dd1be91b'} |
Go | GO-2020-0049 | null | Due to improper validation of caller input, validation is silently disabled
if the provided expected token is malformed, causing any user supplied token
to be considered valid.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/justinas/nosurf/pull/60', 'https://github.com/justinas/nosurf/commit/4d86df7a4affa1fa50ab39fb09aac56c3ce9c314'} | null | {'https://github.com/justinas/nosurf/commit/4d86df7a4affa1fa50ab39fb09aac56c3ce9c314'} | {'https://github.com/justinas/nosurf/commit/4d86df7a4affa1fa50ab39fb09aac56c3ce9c314'} |
Go | GHSA-599h-8wpj-75xj | Authentication Bypass in tyk-identity-broker | The package github.com/tyktechnologies/tyk-identity-broker before 1.1.1 are vulnerable to Authentication Bypass via the Go XML parser which can cause SAML authentication bypass. This is because the XML parser doesn’t guarantee integrity in the XML round-trip (encoding/decoding XML data). | {'CVE-2021-23365'} | 2021-05-20T21:24:49Z | 2021-06-23T17:23:30Z | CRITICAL | null | {'CWE-287'} | {'https://github.com/TykTechnologies/tyk-identity-broker/pull/147', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMTYKTECHNOLOGIESTYKIDENTITYBROKER-1089720', 'https://github.com/TykTechnologies/tyk-identity-broker/releases/tag/v1.1.1', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23365', 'https://github.com/TykTechnologies/tyk-identity-broker/commit/46f70420e0911e4e8b638575e29d394c227c75d0', 'https://github.com/TykTechnologies/tyk-identity-broker/commit/243092965b0f93a95a14cb882b5b9a3df61dd5c0'} | null | {'https://github.com/TykTechnologies/tyk-identity-broker/commit/46f70420e0911e4e8b638575e29d394c227c75d0', 'https://github.com/TykTechnologies/tyk-identity-broker/commit/243092965b0f93a95a14cb882b5b9a3df61dd5c0'} | {'https://github.com/TykTechnologies/tyk-identity-broker/commit/243092965b0f93a95a14cb882b5b9a3df61dd5c0', 'https://github.com/TykTechnologies/tyk-identity-broker/commit/46f70420e0911e4e8b638575e29d394c227c75d0'} |
Go | GHSA-vj54-cjrx-x696 | Observable Discrepancy in Argo | Fixed in v1.5.1, Argo version v1.5.0 was vulnerable to a user-enumeration vulnerability which allowed attackers to determine the usernames of valid (non-SSO) accounts within Argo. | {'CVE-2020-11576'} | 2021-07-29T16:07:15Z | 2021-12-09T19:59:24Z | MODERATE | null | {'CWE-203'} | {'https://github.com/argoproj/argo-cd/commit/35a7350b7444bcaf53ee0bb11b9d8e3ae4b717a1', 'https://www.soluble.ai/blog/argo-cves-2020', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11576', 'https://github.com/argoproj/argo-cd/pull/3215'} | null | {'https://github.com/argoproj/argo-cd/commit/35a7350b7444bcaf53ee0bb11b9d8e3ae4b717a1'} | {'https://github.com/argoproj/argo-cd/commit/35a7350b7444bcaf53ee0bb11b9d8e3ae4b717a1'} |
Go | GO-2021-0110 | null | Uniqueness of JWT IDs (jti) are not checked, allowing the JWT to be
replayed.
| {'CVE-2020-15222'} | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/ory/fosite/commit/0c9e0f6d654913ad57c507dd9a36631e1858a3e9', 'https://github.com/ory/fosite/security/advisories/GHSA-v3q9-2p3m-7g43'} | null | {'https://github.com/ory/fosite/commit/0c9e0f6d654913ad57c507dd9a36631e1858a3e9'} | {'https://github.com/ory/fosite/commit/0c9e0f6d654913ad57c507dd9a36631e1858a3e9'} |
Go | GHSA-q3j5-32m5-58c2 | Privilege Elevation in runc | libcontainer/user/user.go in runC before 0.1.0, as used in Docker before 1.11.2, improperly treats a numeric UID as a potential username, which allows local users to gain privileges via a numeric username in the password file in a container. | {'CVE-2016-3697'} | 2021-10-05T16:34:17Z | 2021-12-20T18:21:34Z | HIGH | null | null | {'https://github.com/opencontainers/runc/releases/tag/v0.1.0', 'https://github.com/opencontainers/runc', 'https://lists.opensuse.org/opensuse-updates/2016-05/msg00111.html', 'https://rhn.redhat.com/errata/RHSA-2016-2634.html', 'https://security.gentoo.org/glsa/201612-28', 'https://nvd.nist.gov/vuln/detail/CVE-2016-3697', 'https://rhn.redhat.com/errata/RHSA-2016-1034.html', 'https://github.com/docker/docker/issues/21436', 'https://github.com/opencontainers/runc/commit/69af385de62ea68e2e608335cffbb0f4aa3db091', 'https://github.com/opencontainers/runc/pull/708'} | null | {'https://github.com/opencontainers/runc/commit/69af385de62ea68e2e608335cffbb0f4aa3db091'} | {'https://github.com/opencontainers/runc/commit/69af385de62ea68e2e608335cffbb0f4aa3db091'} |
Go | GHSA-h3p9-wrgx-82cm | Use of a Broken or Risky Cryptographic Algorithm in Terraform | When using the Azure backend with a shared access signature (SAS), Terraform versions prior to 0.12.17 may transmit the token and state snapshot using cleartext HTTP. | {'CVE-2019-19316'} | 2021-05-13T15:15:38Z | 2021-05-18T18:18:50Z | HIGH | null | {'CWE-327', 'CWE-20'} | {'https://github.com/hashicorp/terraform/commit/6db3cf8e5b4cfb2a3cd1d99a813b50b2d5d363bb', 'https://nvd.nist.gov/vuln/detail/CVE-2019-19316', 'https://github.com/hashicorp/terraform/issues/23493', 'https://github.com/hashicorp/terraform/security/advisories/GHSA-4rvg-555h-r626'} | null | {'https://github.com/hashicorp/terraform/commit/6db3cf8e5b4cfb2a3cd1d99a813b50b2d5d363bb'} | {'https://github.com/hashicorp/terraform/commit/6db3cf8e5b4cfb2a3cd1d99a813b50b2d5d363bb'} |
Go | GO-2020-0008 | null | DNS message transaction IDs are generated using [`math/rand`] which
makes them relatively predictable. This reduces the complexity
of response spoofing attacks against DNS clients.
| {'CVE-2019-19794'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/miekg/dns/pull/1044', 'https://github.com/miekg/dns/issues/1037', 'https://github.com/miekg/dns/commit/8ebf2e419df7857ac8919baa05248789a8ffbf33', 'https://github.com/miekg/dns/issues/1043'} | null | {'https://github.com/miekg/dns/commit/8ebf2e419df7857ac8919baa05248789a8ffbf33'} | {'https://github.com/miekg/dns/commit/8ebf2e419df7857ac8919baa05248789a8ffbf33'} |
Go | GHSA-5jgq-x857-p8xw | Account compromise in Evmos | ## Impact
_What kind of vulnerability is it? Who is impacted?_
### Classification
The vulnerability has been classified as `critical` with a score of `9.0` (highest). It has the potential to affect and drain unclaimed airdrop funds from Cosmos and Osmosis eligible user addresses.
### Disclosure
The attack requires advanced knowledge of the internals of the core and application packages of IBC, IBC relayers, the Cosmos SDK `AnteHandler`, and the Evmos `x/claims` module. The step-by-step attack is described below:
1. An actor creates a malicious chain with a custom `AnteHandler` that skips signature verification for transactions, specifically IBC `MsgTransfer`. This allows the attacker to impersonate any account by setting a custom `sender` address field of the IBC transfer message.
2. The malicious actor then connects this newly created chain via IBC to Evmos and fills the `recipient` address from the transfer message with an address they control.
3. Once the IBC packet containing the Transfer data is relayed to Evmos, it is processed by the claims module IBC middleware. Which migrates the claim records to the recipient address, which is owned by the attacker.
4. The attacker then performs two airdrop Actions, claiming up to 75% of the total initial claimable amount.
5. The Actor repeats steps 1., 2., and 3. for every address that has unclaimed funds from the airdrop. This automatically claims 75% of the unclaimable amount.
6. The malicious actor performs the final Action, claiming 100% of all the user funds.
7. Then, the attacker transfers the funds to another chain with a DEX (Osmosis, Cosmos Hub) via IBC.
8. Finally, the attacker withdraws the total amount in fiat through a centralized exchange.
### Users impacted
No users have suffered the loss of funds as no malicious chains have been connected to Evmos.
## Patches
_Has the problem been patched? What versions should users upgrade to?_
The patch involves defining a list of authorized channels for chains that are connected to Evmos via IBC. This restricts the chains that have the capability of migrating users' claims records as per the specification. By default, the authorized destination channels are `"channel-0"` (Osmosis) and `"channel-3"` (Cosmos Hub).
Please upgrade your mainnet node and validator to [`v2.0.1`](https://github.com/tharsis/evmos/releases/tag/v2.0.1) **ASAP**.
## Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
No, the fix for the critical vulnerability is state machine breaking. An upgrade procedure must be coordinated with the nodes running the network.
## References
_Are there any links users can visit to find out more?_
* Claims module spec: [evmos.dev/modules/claims](https://evmos.dev/modules/claims)
* Cosmos SDK documentation: [docs.cosmos.network](https://docs.cosmos.network/)
* IBC documentation: [ibc.cosmos.network](https://ibc.cosmos.network/)
## For more information
If you have any questions or comments about this advisory:
* Reach out to the Core Team in [Discord](https://discord.gg/evmos)
* Open an issue in [tharsis/evmos](http://github.com/tharsis/evmos/issues)
* Email us at [security@thars.is](security@thars.is)
Thanks to the Core IBC team at Interchain GmbH for the secure disclosure of this vulnerability | {'CVE-2022-24738'} | 2022-03-18T20:07:34Z | 2022-03-07T21:45:59Z | HIGH | null | {'CWE-287'} | {'https://github.com/tharsis/evmos/security/advisories/GHSA-5jgq-x857-p8xw', 'https://github.com/tharsis/evmos/commit/28870258d4ee9f1b8aeef5eba891681f89348f71', 'https://github.com/tharsis/evmos', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24738', 'https://github.com/tharsis/evmos/releases/tag/v2.0.1'} | null | {'https://github.com/tharsis/evmos/commit/28870258d4ee9f1b8aeef5eba891681f89348f71'} | {'https://github.com/tharsis/evmos/commit/28870258d4ee9f1b8aeef5eba891681f89348f71'} |
Go | GHSA-69j6-29vr-p3j9 | Authentication bypass for viewing and deletions of snapshots | Today we are releasing Grafana 7.5.11, and 8.1.6. These patch releases include an important security fix for an issue that affects all Grafana versions from 2.0.1.
[Grafana Cloud](https://grafana.com/cloud) instances have already been patched and an audit did not find any usage of this attack vector. [Grafana Enterprise](https://grafana.com/products/enterprise) customers were provided with updated binaries under embargo.
8.1.5 contained a single fix for bar chart panels. We believe that users can expedite deployment by moving from 8.1.4 to 8.1.6 directly.
## CVE-2021-39226 Snapshot authentication bypass
### Summary
CVSS Score: 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
We received a security report to [security@grafana.com](mailto:security@grafana.com) on 2021-09-15 about a vulnerability in Grafana regarding the snapshot feature. It was later identified as affecting Grafana versions from 2.0.1 to 8.1.6. [CVE-2021-39226](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39226) has been assigned to this vulnerability.
### Impact
Unauthenticated and authenticated users are able to view the snapshot with the lowest database key by accessing the literal paths:
* `/dashboard/snapshot/:key`, or
* `/api/snapshots/:key`
If the snapshot "public_mode" configuration setting is set to true (vs default of false), unauthenticated users are able to delete the snapshot with the lowest database key by accessing the literal path:
* `/api/snapshots-delete/:deleteKey`
Regardless of the snapshot "public_mode" setting, authenticated users are able to delete the snapshot with the lowest database key by accessing the literal paths:
* `/api/snapshots/:key`, or
* `/api/snapshots-delete/:deleteKey`
The combination of deletion and viewing enables a complete walk through all snapshot data while resulting in complete snapshot data loss.
### Attack audit
While we can not guarantee that the below will identify all attacks, if you do find something with the below, you should consider doing a full assessment.
#### Through reverse proxy/load balancer logs
To determine if your Grafana installation has been exploited for this vulnerability, search through your reverse proxy/load balancer access logs for instances where the path is `/dashboard/snapshot/:key`, `/api/snapshots/:key` or `/api/snapshots-delete/:deleteKey`, and the response status code was 200 (OK).
For example, if you’re using the Kubernetes ingress-nginx controller and sending logs to Loki, use a LogQL query like `{job="nginx-ingress-controller"} |= "\"status\": 200" |= "\"uri\": \"/api/snapshots/:key\""`.
#### Through the Grafana Enterprise audit feature
If you enabled “Log web requests” in your configuration with `router_logging = true`, look for
`"requestUri":"/api/snapshots-delete/”`,`“requestUri":"/api/snapshots/:key"`, or `"type":"snapshot"` in combination with `"action":"delete"`.
### Patched versions
Release 8.1.6:
- [Download Grafana 8.1.6](https://grafana.com/grafana/download/8.1.6)
- [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-8-1-6/)
Release 7.5.11:
- [Download Grafana 7.5.11](https://grafana.com/grafana/download/7.5.11)
- [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-7-5-11/)
### Solutions and mitigations
Download and install the appropriate patch for your version of Grafana.
[Grafana Cloud](https://grafana.com/cloud) instances have already been patched, and [Grafana Enterprise](https://grafana.com/products/enterprise) customers were provided with updated binaries under embargo.
### Workaround
If for some reason you cannot upgrade:
You can use a reverse proxy or similar to block access to the literal paths
* `/api/snapshots/:key`
* `/api/snapshots-delete/:deleteKey`
* `/dashboard/snapshot/:key`
* `/api/snapshots/:key`
They have no normal function and can be disabled without side effects.
### Timeline and postmortem
Here is a detailed timeline starting from when we originally learned of the issue. All times in UTC.
* 2021-09-15 14:49: Tuan Tran theblackturtle0901@gmail.com sends initial report about viewing snapshots without authentication
* 2021-09-15 15:56: Initial reproduction
* 2021-09-15 17:10: MEDIUM severity declared
* 2021-09-15 18:58: Workaround deployed on Grafana Cloud
* 2021-09-15 19:15: `/api/snapshots/:key` found to be vulnerable as well
* 2021-09-15 19:30: `/api/snapshots/:key` blocked on Grafana Cloud
* 2021-09-16 09:31: `/api/snapshots-delete/:deleteKey` found to be vulnerable as well, blocked on Grafana Cloud. From this point forward, Cloud is not affected any more.
* 2021-09-16 09:35: HIGH severity declared
* 2021-09-16 11:19: Realization that combination of deletion and viewing allows enumeration and permanent DoS
* 2021-09-16 11:19: CRITICAL declared
* 2021-09-17 10:53: Determination that no weekend work is needed. While issue is CRITICAL, scope is very limited
* 2021-09-17 14:26: Audit of Grafana Cloud concluded, no evidence of exploitation
* 2021-09-23: Grafana Cloud instances updated
* 2021-09-28 12:00: Grafana Enterprise images released to customers under embargo
* 2021-10-05 17:00: Public release
## Reporting security issues
If you think you have found a security vulnerability, please send a report to [security@grafana.com](mailto:security@grafana.com). This address can be used for all of
Grafana Labs's open source and commercial products (including but not limited to Grafana, Tempo, Loki, Amixr, k6, Tanka, and Grafana Cloud, Grafana Enterprise, and grafana.com). We only accept vulnerability reports at this address. We would prefer that you encrypt your message to us using our PGP key. The key fingerprint is:
F988 7BEA 027A 049F AE8E 5CAA D125 8932 BE24 C5CA
The key is available from [keys.gnupg.net](http://keys.gnupg.net/pks/lookup?op=get&fingerprint=on&search=0xD1258932BE24C5CA) by searching for [security@grafana](http://keys.gnupg.net/pks/lookup?search=security@grafana&fingerprint=on&op=index.
## Security announcements
We maintain a category on the community site named [Security Announcements](https://community.grafana.com/c/security-announcements),
where we will post a summary, remediation, and mitigation details for any patch containing security fixes. You can also subscribe to email updates to this category if you have a grafana.com account and sign in to the community site, or via updates from our [Security Announcements RSS feed](https://community.grafana.com/c/security-announcements.rss).
## Acknowledgement
We would like to thank [Tran Viet Tuan](https://github.com/theblackturtle) for responsibly disclosing the initially discovered vulnerability to us. | {'CVE-2021-39226'} | 2021-11-18T15:13:27Z | 2021-10-05T20:24:02Z | HIGH | null | {'CWE-287'} | {'https://grafana.com/docs/grafana/latest/release-notes/release-notes-8-1-6/', 'https://github.com/grafana/grafana/commit/2d456a6375855364d098ede379438bf7f0667269', 'http://www.openwall.com/lists/oss-security/2021/10/05/4', 'https://github.com/grafana/grafana', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/E6ANHRDBXQT6TURLP2THM26ZPDINFBEG/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DCKBFUSY6V4VU5AQUYWKISREZX5NLQJT/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39226', 'https://security.netapp.com/advisory/ntap-20211029-0008/', 'https://github.com/grafana/grafana/security/advisories/GHSA-69j6-29vr-p3j9', 'https://grafana.com/docs/grafana/latest/release-notes/release-notes-7-5-11/'} | null | {'https://github.com/grafana/grafana/commit/2d456a6375855364d098ede379438bf7f0667269'} | {'https://github.com/grafana/grafana/commit/2d456a6375855364d098ede379438bf7f0667269'} |
Go | GO-2021-0106 | 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-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/whyrusleeping/tar-utils/commit/20a61371de5b51380bbdb0c7935b30b0625ac227', 'https://snyk.io/research/zip-slip-vulnerability'} | null | {'https://github.com/whyrusleeping/tar-utils/commit/20a61371de5b51380bbdb0c7935b30b0625ac227'} | {'https://github.com/whyrusleeping/tar-utils/commit/20a61371de5b51380bbdb0c7935b30b0625ac227'} |
Maven | GHSA-cf2j-vf36-c6w8 | Communities and collections administrators can escalate their privilege up to system administrator | ### Impact
Any community or collection administrator can escalate their permission up to become system administrator.
This vulnerability only existed in 7.0 and does not impact 6.x or below.
### Patches
Fix is included in [7.1](https://github.com/DSpace/DSpace/releases/tag/dspace-7.1). Please upgrade to 7.1 at your earliest convenience.
### Workarounds
In 7.0, temporarily disable the ability for community or collection administrators to manage permissions or workflows settings, i.e. set the following properties in your local.cfg / dspace.cfg file
```
core.authorization.collection-admin.policies = false
core.authorization.community-admin.policies = false
core.authorization.community-admin.collection.workflows = false
```
Once upgraded to 7.1, these settings can be safely reverted to the default values of `true`.
### References
Discovered during investigation of https://github.com/DSpace/DSpace/issues/7928
### For more information
If you have any questions or comments about this advisory:
* Email us at security@dspace.org
| {'CVE-2021-41189'} | 2022-03-03T05:13:25.172783Z | 2021-11-01T19:18:16Z | HIGH | null | {'CWE-863'} | {'https://github.com/DSpace/DSpace/commit/277b499a5cd3a4f5eb2370513a1b7e4ec2a6e041', 'https://github.com/DSpace/DSpace/commit/c3bea16ab911606e15ae96c97a1575e1ffb14f8a', 'https://github.com/DSpace/DSpace/security/advisories/GHSA-cf2j-vf36-c6w8', 'https://github.com/DSpace/DSpace', 'https://github.com/DSpace/DSpace/issues/7928', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41189'} | null | {'https://github.com/DSpace/DSpace/commit/c3bea16ab911606e15ae96c97a1575e1ffb14f8a', 'https://github.com/DSpace/DSpace/commit/277b499a5cd3a4f5eb2370513a1b7e4ec2a6e041'} | {'https://github.com/DSpace/DSpace/commit/c3bea16ab911606e15ae96c97a1575e1ffb14f8a', 'https://github.com/DSpace/DSpace/commit/277b499a5cd3a4f5eb2370513a1b7e4ec2a6e041'} |
Maven | GHSA-gwp4-hfv6-p7hw | Deserialization of untrusted data in FasterXML jackson-databind | A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.x before 2.9.9.2. This occurs when Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the logback jar in the classpath. | {'CVE-2019-14439'} | 2022-03-03T05:13:30.808736Z | 2019-08-01T19:18:06Z | HIGH | null | {'CWE-502'} | {'https://lists.apache.org/thread.html/ee0a051428d2c719acfa297d0854a189ea5e284ef3ed491fa672f4be@%3Cdev.tomee.apache.org%3E', 'https://www.debian.org/security/2019/dsa-4542', 'https://lists.apache.org/thread.html/940b4c3fef002461b89a050935337056d4a036a65ef68e0bbd4621ef@%3Cdev.struts.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2019/08/msg00011.html', 'https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html', 'https://lists.apache.org/thread.html/2d2a76440becb610b9a9cb49b15eac3934b02c2dbcaacde1000353e4@%3Cdev.tomee.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2019:3200', 'https://security.netapp.com/advisory/ntap-20190814-0001/', 'https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442@%3Cdev.drill.apache.org%3E', 'https://lists.apache.org/thread.html/34717424b4d08b74f65c09a083d6dd1cb0763f37a15d6de135998c1d@%3Cdev.tomee.apache.org%3E', 'https://lists.apache.org/thread.html/5fc0e16b7af2590bf1e97c76c136291c4fdb244ee63c65c485c9a7a1@%3Cdev.tomee.apache.org%3E', 'https://lists.apache.org/thread.html/bcce5a9c532b386c68dab2f6b3ce8b0cc9b950ec551766e76391caa3@%3Ccommits.nifi.apache.org%3E', 'https://seclists.org/bugtraq/2019/Oct/6', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'https://lists.apache.org/thread.html/5ecc333113b139429f4f05000d4aa2886974d4df3269c1dd990bb319@%3Cdev.tomee.apache.org%3E', 'https://lists.apache.org/thread.html/56c8042873595b8c863054c7bfccab4bf2c01c6f5abedae249d914b9@%3Cdev.tomee.apache.org%3E', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OVRZDN2T6AZ6DJCZJ3VSIQIVHBVMVWBL/', 'https://github.com/FasterXML/jackson-databind/compare/jackson-databind-2.9.9.1...jackson-databind-2.9.9.2', 'https://nvd.nist.gov/vuln/detail/CVE-2019-14439', 'https://lists.apache.org/thread.html/87e46591de8925f719664a845572d184027258c5a7af0a471b53c77b@%3Cdev.tomee.apache.org%3E', 'https://lists.apache.org/thread.html/rca37935d661f4689cb4119f1b3b224413b22be161b678e6e6ce0c69b@%3Ccommits.nifi.apache.org%3E', 'https://github.com/FasterXML/jackson-databind/commit/ad418eeb974e357f2797aef64aa0e3ffaaa6125b', 'https://www.oracle.com/security-alerts/cpuapr2020.html', 'https://lists.apache.org/thread.html/0d4b630d9ee724aee50703397d9d1afa2b2befc9395ba7797d0ccea9@%3Cdev.tomee.apache.org%3E', 'https://www.oracle.com/security-alerts/cpujul2020.html', 'https://lists.apache.org/thread.html/3f99ae8dcdbd69438cb733d745ee3ad5e852068490719a66509b4592@%3Ccommits.cassandra.apache.org%3E', 'https://github.com/FasterXML/jackson-databind/issues/2389', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E', 'https://www.oracle.com/security-alerts/cpujan2020.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TXRVXNRFHJSQWFHPRJQRI5UPMZ63B544/'} | null | {'https://github.com/FasterXML/jackson-databind/commit/ad418eeb974e357f2797aef64aa0e3ffaaa6125b'} | {'https://github.com/FasterXML/jackson-databind/commit/ad418eeb974e357f2797aef64aa0e3ffaaa6125b'} |
Maven | GHSA-g5vf-v6wf-7w2r | Ciphertext Malleability Issue in Tink Java | ### Impact
Tink's Java version before 1.5 under some circumstances allowed attackers to change the key ID part of the ciphertext, resulting in the attacker creating a second ciphertext that will decrypt to the same plaintext. This can be a problem in particular in the case of encrypting with a deterministic AEAD with a single key, and relying on the fact that there is only a single valid ciphertext per plaintext.
No loss of confidentiality or loss of plaintext integrity occurs due to this problem, only ciphertext integrity is compromised.
### Patches
The issue was fixed in this [pull request](https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899).
### Workarounds
The only workaround is to backport the fixing [pull request](https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899).
### Details
Tink uses the first five bytes of a ciphertext for a version byte and a four byte key ID. Since each key has a well defined prefix, this extends non-malleability properties (but technically not indistinguishability). However, in the Java version this prefix lookup used a hash map indexed by unicode strings instead of the byte array, which means that invalid Unicode characters would be [replaced by U+FFFD](https://en.wikipedia.org/wiki/UTF-8#Invalid_sequences_and_error_handling) by the [Java API's default behavior](https://docs.oracle.com/javase/7/docs/api/java/lang/String.html#String(byte[],%20java.nio.charset.Charset)). This means several different values for the five bytes would result in the same hash table key, which allows an attacker to exchange one invalid byte sequence for another, creating a mutated ciphertext that still decrypts (to the same plaintext).
### Acknowledgements
We'd like to thank Peter Esbensen for finding this issue and raising it internally.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Tink](https://github.com/google/tink/issues) | {'CVE-2020-8929'} | 2022-03-03T05:14:16.042047Z | 2020-10-16T00:51:24Z | LOW | null | {'CWE-327', 'CWE-176'} | {'https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899', 'https://github.com/google/tink/security/advisories/GHSA-g5vf-v6wf-7w2r', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8929'} | null | {'https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899'} | {'https://github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899'} |
Maven | GHSA-vmqm-g3vh-847m | Denial of service in Apache Xerces2 | Apache Xerces2 Java Parser before 2.12.0 allows remote attackers to cause a denial of service (CPU consumption) via a crafted message to an XML service, which triggers hash table collisions. | {'CVE-2012-0881'} | 2022-03-03T05:13:08.829332Z | 2020-06-15T18:51:38Z | HIGH | null | {'CWE-400'} | {'https://github.com/apache/xerces2-j/commit/992b5d9c24102ad20330d36c0a71162753a37449', 'https://lists.apache.org/thread.html/708d94141126eac03011144a971a6411fcac16d9c248d1d535a39451@%3Csolr-user.lucene.apache.org%3E', 'https://bugzilla.redhat.com/show_bug.cgi?id=787104', 'http://www.openwall.com/lists/oss-security/2014/07/08/11', 'https://lists.apache.org/thread.html/rea7b831dceeb2a2fa817be6f63b08722042e3647fb2d47c144370a56@%3Ccommon-issues.hadoop.apache.org%3E', 'https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442@%3Cdev.drill.apache.org%3E', 'https://issues.apache.org/jira/browse/XERCESJ-1685', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2012-0881', 'https://lists.apache.org/thread.html/r204ba2a9ea750f38d789d2bb429cc0925ad6133deea7cbc3001d96b5@%3Csolr-user.lucene.apache.org%3E', 'https://lists.apache.org/thread.html/49dc6702104a86ecbb40292dcd329ce9ae4c32b74733199ecab14a73@%3Cj-users.xerces.apache.org%3E', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/apache/xerces2-j/commit/992b5d9c24102ad20330d36c0a71162753a37449'} | {'https://github.com/apache/xerces2-j/commit/992b5d9c24102ad20330d36c0a71162753a37449'} |
Maven | GHSA-w3f4-3q6j-rh82 | Deserialization of Untrusted Data in jackson-databind | FasterXML jackson-databind through 2.8.11 and 2.9.x through 2.9.3 allows unauthenticated remote code execution because of an incomplete fix for the CVE-2017-7525 and CVE-2017-17485 deserialization flaws. This is exploitable via two different gadgets that bypass a blacklist. | {'CVE-2018-5968'} | 2022-03-03T05:13:07.865218Z | 2020-06-30T20:40:50Z | HIGH | null | {'CWE-502', 'CWE-184'} | {'https://github.com/FasterXML/jackson-databind/issues/1899', 'https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbhf03902en_us', 'https://access.redhat.com/errata/RHSA-2018:0481', 'https://access.redhat.com/errata/RHSA-2019:3149', 'https://access.redhat.com/errata/RHSA-2018:0478', 'https://access.redhat.com/errata/RHSA-2018:0479', 'https://nvd.nist.gov/vuln/detail/CVE-2018-5968', 'https://github.com/FasterXML/jackson-databind', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://access.redhat.com/errata/RHSA-2019:2858', 'https://github.com/GulajavaMinistudio/jackson-databind/pull/92/commits/038b471e2efde2e8f96b4e0be958d3e5a1ff1d05', 'https://www.debian.org/security/2018/dsa-4114', 'https://access.redhat.com/errata/RHSA-2018:1525', 'https://security.netapp.com/advisory/ntap-20180423-0002/', 'https://access.redhat.com/errata/RHSA-2018:0480'} | null | {'https://github.com/GulajavaMinistudio/jackson-databind/pull/92/commits/038b471e2efde2e8f96b4e0be958d3e5a1ff1d05'} | {'https://github.com/GulajavaMinistudio/jackson-databind/pull/92/commits/038b471e2efde2e8f96b4e0be958d3e5a1ff1d05'} |
Maven | GHSA-73xv-w5gp-frxh | Logic error in Legion of the Bouncy Castle BC Java | An issue was discovered in Legion of the Bouncy Castle BC Java 1.65 and 1.66. The OpenBSDBCrypt.checkPassword utility method compared incorrect data when checking the password, allowing incorrect passwords to indicate they were matching with previously hashed ones that were different. | {'CVE-2020-28052'} | 2022-04-22T17:31:09.893912Z | 2021-04-30T16:14:15Z | HIGH | null | {'CWE-670'} | {'https://www.bouncycastle.org/releasenotes.html', 'https://lists.apache.org/thread.html/rf9abfc0223747a56694825c050cc6b66627a293a32ea926b3de22402@%3Cissues.karaf.apache.org%3E', 'https://lists.apache.org/thread.html/rdfd2901b8b697a3f6e2c9c6ecc688fd90d7f881937affb5144d61d6e@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/rfc0db1f3c375087e69a239f9284ded72d04fbb55849eadde58fa9dc2@%3Cissues.karaf.apache.org%3E', 'https://lists.apache.org/thread.html/rdcbad6d8ce72c79827ed8c635f9a62dd919bb21c94a0b64cab2efc31@%3Cissues.karaf.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://lists.apache.org/thread.html/r77af3ac7c3bfbd5454546e13faf7aec21d627bdcf36c9ca240436b94@%3Cissues.karaf.apache.org%3E', 'https://github.com/bcgit/bc-java/wiki/CVE-2020-28052', 'https://lists.apache.org/thread.html/r25d53acd06f29244b8a103781b0339c5e7efee9099a4d52f0c230e4a@%3Ccommits.druid.apache.org%3E', 'https://github.com/bcgit/bc-java/commit/97578f9b7ed277e6ecb58834e85e3d18385a4219', 'https://lists.apache.org/thread.html/rc9e441c1576bdc4375d32526d5cf457226928e9c87b9f54ded26271c@%3Cissues.karaf.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://lists.apache.org/thread.html/rcd37d9214b08067a2e8f2b5b4fd123a1f8cb6008698d11ef44028c21@%3Cissues.karaf.apache.org%3E', 'https://lists.apache.org/thread.html/r954d80fd18e9dafef6e813963eb7e08c228151c2b6268ecd63b35d1f@%3Ccommits.druid.apache.org%3E', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://lists.apache.org/thread.html/r167dbc42ef7c59802c2ca1ac14735ef9cf687c25208229993d6206fe@%3Cissues.karaf.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28052', 'https://lists.apache.org/thread.html/r8c36ba34e80e05eecb1f80071cc834d705616f315b634ec0c7d8f42e@%3Cissues.solr.apache.org%3E', 'https://github.com/bcgit/bc-java', 'https://lists.apache.org/thread.html/r175f5a25d100dbe2b1bd3459b3ce882a84c3ff91b120ed4ff2d57b53@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/rddd2237b8636a48d573869006ee809262525efb2b6ffa6eff50d2a2d@%3Cjira.kafka.apache.org%3E', 'https://lists.apache.org/thread.html/r37d332c0bf772f4982d1fdeeb2f88dd71dab6451213e69e43734eadc@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/r2ddabd06d94b60cfb0141e4abb23201c628ab925e30742f61a04d013@%3Cissues.karaf.apache.org%3E', 'https://www.synopsys.com/blogs/software-security/cve-2020-28052-bouncy-castle/', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://lists.apache.org/thread.html/r30a139c165b3da6e0d5536434ab1550534011b1fdfcd2f5d95892c5b@%3Cissues.karaf.apache.org%3E', 'https://lists.apache.org/thread.html/r4e1619cfefcd031fac62064a3858f5c9229eef907bd5d8ef14c594fc@%3Cissues.karaf.apache.org%3E', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/bcgit/bc-java/commit/97578f9b7ed277e6ecb58834e85e3d18385a4219'} | {'https://github.com/bcgit/bc-java/commit/97578f9b7ed277e6ecb58834e85e3d18385a4219'} |
Maven | GHSA-959q-32g8-vvp7 | Moderate severity vulnerability that affects org.keycloak:keycloak-core | It was found that keycloak before 3.4.2 final would permit misuse of a client-side /etc/hosts entry to spoof a URL in a password reset request. An attacker could use this flaw to craft a malicious password reset request and gain a valid reset token, leading to information disclosure or further attacks. | {'CVE-2017-12161'} | 2022-03-03T05:13:30.784473Z | 2018-10-18T16:50:05Z | MODERATE | null | {'CWE-602'} | {'https://github.com/advisories/GHSA-959q-32g8-vvp7', 'https://github.com/keycloak/keycloak-documentation/pull/268/commits/a2b58aadee42af2c375b72e86dffc2cf23cc3770', 'https://bugzilla.redhat.com/show_bug.cgi?id=1484564', 'https://nvd.nist.gov/vuln/detail/CVE-2017-12161'} | null | {'https://github.com/keycloak/keycloak-documentation/pull/268/commits/a2b58aadee42af2c375b72e86dffc2cf23cc3770'} | {'https://github.com/keycloak/keycloak-documentation/pull/268/commits/a2b58aadee42af2c375b72e86dffc2cf23cc3770'} |
Maven | GHSA-7ph6-5cmq-xgjq | Path traversal in xwiki-platform-skin-skinx | ### Impact
AbstractSxExportURLFactoryActionHandler#processSx does not escape anything from SSX document reference when serializing it on filesystem, so it's easy to mess up the HTML export process with reference elements containing filesystem syntax like "../", "./". or "/" in general (the last two not causing any security threat, but can cause conflicts with others serialized files).
### Patches
Fixed in 13.6-rc-1
### Workarounds
* giving script or subwiki admin right only to trusted people
* disabling HTML/PDF export
### References
https://jira.xwiki.org/browse/XWIKI-18819
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [JIRA](https://jira.xwiki.org)
* Email us at [XWiki Security Mailing list](mailto:security@xwiki.org) | {'CVE-2022-23620'} | 2022-02-09T21:53:29Z | 2022-02-09T21:53:29Z | MODERATE | null | {'CWE-22'} | {'https://jira.xwiki.org/browse/XWIKI-18819', 'https://github.com/xwiki/xwiki-platform', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23620', 'https://github.com/xwiki/xwiki-platform/commit/ab778254fb8f71c774e1c1239368c44fe3b6bba5', 'https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-7ph6-5cmq-xgjq'} | null | {'https://github.com/xwiki/xwiki-platform/commit/ab778254fb8f71c774e1c1239368c44fe3b6bba5'} | {'https://github.com/xwiki/xwiki-platform/commit/ab778254fb8f71c774e1c1239368c44fe3b6bba5'} |
Maven | GHSA-4fcw-pq4r-f4q7 | Server-Side Request Forgery in Spinnaker Orca | The Spinnaker template resolution functionality is vulnerable to Server-Side Request Forgery (SSRF), which allows an attacker to send requests on behalf of Spinnaker potentially leading to sensitive data disclosure. | {'CVE-2020-9298'} | 2021-05-05T19:53:13Z | 2021-05-07T15:54:31Z | HIGH | null | {'CWE-918'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-9298', 'https://github.com/spinnaker/orca/releases/tag/v8.7.0', 'https://github.com/Netflix/security-bulletins/blob/master/advisories/nflx-2020-003.md', 'https://github.com/spinnaker/orca/pull/3706/commits/4f3c07da8fcacd67bb1984aef11b2066f2c0d11c'} | null | {'https://github.com/spinnaker/orca/pull/3706/commits/4f3c07da8fcacd67bb1984aef11b2066f2c0d11c'} | {'https://github.com/spinnaker/orca/pull/3706/commits/4f3c07da8fcacd67bb1984aef11b2066f2c0d11c'} |
Maven | GHSA-c7fh-chf7-jr5x | ReDOS in Vfsjfilechooser2 | A Regular Expression Denial of Service (ReDOS) vulnerability was discovered in Vfsjfilechooser2 which occurs when the application attempts to validate crafted URIs. | {'CVE-2021-29061'} | 2022-03-03T05:13:58.202139Z | 2022-01-06T18:44:27Z | HIGH | null | {'CWE-770'} | {'https://github.com/fracpete/vfsjfilechooser2/issues/7', 'https://github.com/fracpete/vfsjfilechooser2/commit/9c9f2c317f3de5ece60a3ae28c371e9796e3909b', 'https://github.com/fracpete/vfsjfilechooser2/releases/tag/vfsjfilechooser2-0.2.9', 'https://github.com/yetingli/PoCs/blob/main/CVE-2021-29061/Vfsjfilechooser2.md', 'https://github.com/yetingli/SaveResults/blob/main/md/vfsjfilechooser2.md', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29061'} | null | {'https://github.com/fracpete/vfsjfilechooser2/commit/9c9f2c317f3de5ece60a3ae28c371e9796e3909b'} | {'https://github.com/fracpete/vfsjfilechooser2/commit/9c9f2c317f3de5ece60a3ae28c371e9796e3909b'} |
Maven | GHSA-7cj4-gj8m-m2f7 | Authentication bypass in Apache Shiro | Apache Shiro before 1.7.0, when using Apache Shiro with Spring, a specially crafted HTTP request may cause an authentication bypass. | {'CVE-2020-17510'} | 2022-03-03T05:13:46.136754Z | 2021-04-22T16:13:23Z | CRITICAL | null | {'CWE-287'} | {'https://lists.apache.org/thread.html/r575301804bfac87a064359cf4b4ae9d514f2d10db7d44120765f4129@%3Cdev.shiro.apache.org%3E', 'https://lists.apache.org/thread.html/rb47d88af224e396ee34ffb88ee99fb6d04510de5722cf14b7137e6bc@%3Cdev.shiro.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2021/08/msg00002.html', 'https://github.com/apache/shiro/commit/dc194fc977ab6cfbf3c1ecb085e2bac5db14af6d', 'https://lists.apache.org/thread.html/rc2cff2538b683d480426393eecf1ce8dd80e052fbef49303b4f47171%40%3Cdev.shiro.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-17510', 'https://lists.apache.org/thread.html/r70098e336d02047ce4d4e69293fe8d558cd68cde06f6430398959bc4@%3Cdev.shiro.apache.org%3E', 'https://github.com/apache/shiro', 'https://lists.apache.org/thread.html/re25b8317b00a50272a7252c4552cf1a81a97984cc2111ef7728e48e0@%3Cdev.shiro.apache.org%3E', 'https://lists.apache.org/thread.html/r852971e28f54cafa7d325bd7033115c67d613b112a2a1076817390ac@%3Cdev.shiro.apache.org%3E', 'https://lists.apache.org/thread.html/r9d93dfb5df016b1a71a808486bc8f9fbafebbdbc8533625f91253f1d@%3Cdev.shiro.apache.org%3E', 'https://lists.apache.org/thread.html/r95bdf3703858b5f958b5e190d747421771b430d97095880db91980d6@%3Cannounce.apache.org%3E', 'https://lists.apache.org/thread.html/r70b907ccb306e9391145e2b10f56cc6914a245f91720a17a486c020a@%3Cdev.shiro.apache.org%3E'} | null | {'https://github.com/apache/shiro/commit/dc194fc977ab6cfbf3c1ecb085e2bac5db14af6d'} | {'https://github.com/apache/shiro/commit/dc194fc977ab6cfbf3c1ecb085e2bac5db14af6d'} |
Maven | GHSA-54fx-gm74-q676 | Permissions bypass in SmallRye | A flaw was found in SmallRye's API through version 1.6.1. The API can allow other code running within the application server to potentially obtain the ClassLoader, bypassing any permissions checks that should have been applied. The largest threat from this vulnerability is a threat to data confidentiality. This is fixed in SmallRye 1.6.2 | {'CVE-2020-1729'} | 2022-03-18T18:03:03.686621Z | 2022-03-18T17:55:47Z | MODERATE | null | {'CWE-863'} | {'https://github.com/smallrye/smallrye-config/commit/fb0def6f61c09a2a80c9145e4ec6521225cd0b99', 'https://bugzilla.redhat.com/show_bug.cgi?id=1802444', 'https://nvd.nist.gov/vuln/detail/CVE-2020-1729'} | null | {'https://github.com/smallrye/smallrye-config/commit/fb0def6f61c09a2a80c9145e4ec6521225cd0b99'} | {'https://github.com/smallrye/smallrye-config/commit/fb0def6f61c09a2a80c9145e4ec6521225cd0b99'} |
Maven | GHSA-xxgp-pcfc-3vgc | Privilege Escalation in Hibernate Validator | In Hibernate Validator 5.2.x before 5.2.5 final, 5.3.x, and 5.4.x, it was found that when the security manager's reflective permissions, which allows it to access the private members of the class, are granted to Hibernate Validator, a potential privilege escalation can occur. By allowing the calling code to access those private members without the permission an attacker may be able to validate an invalid instance and access the private member value via ConstraintViolation#getInvalidValue(). | {'CVE-2017-7536'} | 2022-03-31T22:19:43.235684Z | 2020-06-15T19:57:48Z | HIGH | null | {'CWE-470'} | {'https://github.com/hibernate/hibernate-validator/commit/0886e89900d343ea20fde5137c9a3086e6da9ac', 'https://access.redhat.com/errata/RHSA-2018:2742', 'https://access.redhat.com/errata/RHSA-2017:2810', 'https://access.redhat.com/errata/RHSA-2018:2741', 'https://access.redhat.com/errata/RHSA-2017:2809', 'http://www.securitytracker.com/id/1039744', 'https://lists.apache.org/thread.html/9317fd092b257a0815434b116a8af8daea6e920b6673f4fd5583d5fe@%3Ccommits.druid.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2017-7536', 'https://access.redhat.com/errata/RHSA-2018:3817', 'https://access.redhat.com/errata/RHSA-2017:3455', 'https://access.redhat.com/errata/RHSA-2017:3141', 'https://bugzilla.redhat.com/show_bug.cgi?id=1465573', 'https://access.redhat.com/errata/RHSA-2017:2811', 'https://access.redhat.com/errata/RHSA-2018:2927', 'https://access.redhat.com/errata/RHSA-2017:2808', 'http://www.securityfocus.com/bid/101048', 'https://access.redhat.com/errata/RHSA-2017:3458', 'https://github.com/hibernate/hibernate-validator/commit/0778a5c98b817771a645c6f4ba0b28dd8b5437b', 'https://access.redhat.com/errata/RHSA-2018:2740', 'https://access.redhat.com/errata/RHSA-2018:2743', 'https://access.redhat.com/errata/RHSA-2017:3454', 'https://github.com/hibernate/hibernate-validator', 'https://access.redhat.com/errata/RHSA-2017:3456'} | null | {'https://github.com/hibernate/hibernate-validator/commit/0886e89900d343ea20fde5137c9a3086e6da9ac', 'https://github.com/hibernate/hibernate-validator/commit/0778a5c98b817771a645c6f4ba0b28dd8b5437b'} | {'https://github.com/hibernate/hibernate-validator/commit/0778a5c98b817771a645c6f4ba0b28dd8b5437b', 'https://github.com/hibernate/hibernate-validator/commit/0886e89900d343ea20fde5137c9a3086e6da9ac'} |
Maven | GHSA-7hwc-46rm-65jh | Denial of service in XStream | XStream through 1.4.9, when a certain denyTypes workaround is not used, mishandles attempts to create an instance of the primitive type 'void' during unmarshalling, leading to a remote application crash, as demonstrated by an xstream.fromXML("<void/>") call. | {'CVE-2017-7957'} | 2022-03-03T05:13:52.552340Z | 2020-06-30T22:48:24Z | HIGH | null | {'CWE-20'} | {'https://exchange.xforce.ibmcloud.com/vulnerabilities/125800', 'https://access.redhat.com/errata/RHSA-2017:2889', 'https://github.com/x-stream/xstream/commit/6e546ec366419158b1e393211be6d78ab9604ab', 'http://www.securitytracker.com/id/1039499', 'https://www-prd-trops.events.ibm.com/node/715749', 'https://github.com/x-stream/xstream/commit/b3570be2f39234e61f99f9a20640756ea71b1b4', 'https://github.com/x-stream/xstream', 'http://x-stream.github.io/CVE-2017-7957.html', 'https://access.redhat.com/errata/RHSA-2017:2888', 'http://www.debian.org/security/2017/dsa-3841', 'https://access.redhat.com/errata/RHSA-2017:1832', 'https://nvd.nist.gov/vuln/detail/CVE-2017-7957', 'http://www.securityfocus.com/bid/100687', 'https://github.com/x-stream/xstream/commit/8542d02d9ac5d384c85f4b33d6c1888c53bd55d'} | null | {'https://github.com/x-stream/xstream/commit/b3570be2f39234e61f99f9a20640756ea71b1b4', 'https://github.com/x-stream/xstream/commit/8542d02d9ac5d384c85f4b33d6c1888c53bd55d', 'https://github.com/x-stream/xstream/commit/6e546ec366419158b1e393211be6d78ab9604ab'} | {'https://github.com/x-stream/xstream/commit/6e546ec366419158b1e393211be6d78ab9604ab', 'https://github.com/x-stream/xstream/commit/b3570be2f39234e61f99f9a20640756ea71b1b4', 'https://github.com/x-stream/xstream/commit/8542d02d9ac5d384c85f4b33d6c1888c53bd55d'} |
Maven | GHSA-g644-pr5v-vppf | Insertion of Sensitive Information into Log File in Apache NiFi | In Apache NiFi 1.10.0 to 1.11.4, the NiFi stateless execution engine produced log output which included sensitive property values. When a flow was triggered, the flow definition configuration JSON was printed, potentially containing sensitive values in plaintext. | {'CVE-2020-9486'} | 2022-03-03T05:14:10.953929Z | 2022-01-06T20:41:02Z | HIGH | null | {'CWE-532'} | {'https://nifi.apache.org/security#CVE-2020-9486', 'https://github.com/apache/nifi/commit/148537d64a017b73160b0d49943183c18f883ab0', 'https://nvd.nist.gov/vuln/detail/CVE-2020-9486'} | null | {'https://github.com/apache/nifi/commit/148537d64a017b73160b0d49943183c18f883ab0'} | {'https://github.com/apache/nifi/commit/148537d64a017b73160b0d49943183c18f883ab0'} |
Maven | GHSA-cvx5-m8vg-vxgc | Arbitrary filesystem write access from velocity. | ### Impact
The velocity scripts is not properly sandboxed against using the Java File API to perform read or write operations on the filesystem. Now writing an attacking script in velocity requires the Script rights in XWiki so not all users can use it, and it also requires finding an XWiki API which returns a File.
### Patches
The problem has been patched on versions 12.6.7, 12.10.3 and 13.0RC1.
### Workarounds
There's no easy workaround for fixing this vulnerability other than upgrading and being careful when giving Script rights.
### References
https://jira.xwiki.org/browse/XWIKI-5168
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Jira XWiki](https://jira.xwiki.org)
* Email us at [XWiki Security mailing-list](mailto:security@xwiki.org)
| {'CVE-2022-24897'} | 2022-05-03T18:01:48.701710Z | 2022-04-28T21:16:40Z | HIGH | null | {'CWE-22'} | {'https://github.com/xwiki/xwiki-commons/commit/215951cfb0f808d0bf5b1097c9e7d1e503449ab8', 'https://jira.xwiki.org/browse/XWIKI-5168', 'https://github.com/xwiki/xwiki-commons', 'https://github.com/xwiki/xwiki-commons/security/advisories/GHSA-cvx5-m8vg-vxgc'} | null | {'https://github.com/xwiki/xwiki-commons/commit/215951cfb0f808d0bf5b1097c9e7d1e503449ab8'} | {'https://github.com/xwiki/xwiki-commons/commit/215951cfb0f808d0bf5b1097c9e7d1e503449ab8'} |
Maven | GHSA-w3gh-g32m-cvhr | High severity vulnerability that affects org.apache.cxf.fediz:fediz-jetty8, org.apache.cxf.fediz:fediz-jetty9, org.apache.cxf.fediz:fediz-spring, org.apache.cxf.fediz:fediz-spring2, and org.apache.cxf.fediz:fediz-spring3 | Versions of Apache CXF Fediz prior to 1.4.4 do not fully disable Document Type Declarations (DTDs) when either parsing the Identity Provider response in the application plugins, or in the Identity Provider itself when parsing certain XML-based parameters. | {'CVE-2018-8038'} | 2022-03-03T05:13:46.576561Z | 2018-10-18T16:56:47Z | HIGH | null | {'CWE-20'} | {'http://cxf.apache.org/security-advisories.data/CVE-2018-8038.txt.asc', 'https://nvd.nist.gov/vuln/detail/CVE-2018-8038', 'https://lists.apache.org/thread.html/rc774278135816e7afc943dc9fc78eb0764f2c84a2b96470a0187315c@%3Ccommits.cxf.apache.org%3E', 'https://lists.apache.org/thread.html/rff42cfa5e7d75b7c1af0e37589140a8f1999e578a75738740b244bd4@%3Ccommits.cxf.apache.org%3E', 'https://lists.apache.org/thread.html/rd49aabd984ed540c8ff7916d4d79405f3fa311d2fdbcf9ed307839a6@%3Ccommits.cxf.apache.org%3E', 'https://lists.apache.org/thread.html/r36e44ffc1a9b365327df62cdfaabe85b9a5637de102cea07d79b2dbf@%3Ccommits.cxf.apache.org%3E', 'https://github.com/apache/cxf-fediz/commit/b6ed9865d0614332fa419fe4b6d0fe81bc2e660d', 'https://lists.apache.org/thread.html/rfb87e0bf3995e7d560afeed750fac9329ff5f1ad49da365129b7f89e@%3Ccommits.cxf.apache.org%3E', 'https://lists.apache.org/thread.html/f0a6a05ec3b3a00458da43712b0ff3a2f573175d9bfb39fb0de21424@%3Cdev.cxf.apache.org%3E', 'https://lists.apache.org/thread.html/rec7160382badd3ef4ad017a22f64a266c7188b9ba71394f0d321e2d4@%3Ccommits.cxf.apache.org%3E', 'http://www.securitytracker.com/id/1041220', 'https://github.com/advisories/GHSA-w3gh-g32m-cvhr'} | null | {'https://github.com/apache/cxf-fediz/commit/b6ed9865d0614332fa419fe4b6d0fe81bc2e660d'} | {'https://github.com/apache/cxf-fediz/commit/b6ed9865d0614332fa419fe4b6d0fe81bc2e660d'} |
Maven | GHSA-jgwr-3qm3-26f3 | Potential remote code execution in Apache Tomcat | The fix for CVE-2020-9484 was incomplete. When using Apache Tomcat 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41, 8.5.0 to 8.5.61 or 7.0.0. to 7.0.107 with a configuration edge case that was highly unlikely to be used, the Tomcat instance was still vulnerable to CVE-2020-9494. Note that both the previously published prerequisites for CVE-2020-9484 and the previously published mitigations for CVE-2020-9484 also apply to this issue. | {'CVE-2021-25329'} | 2022-03-03T05:13:17.256982Z | 2021-03-19T20:11:13Z | CRITICAL | null | {'CWE-502'} | {'https://security.netapp.com/advisory/ntap-20210409-0002/', 'https://lists.apache.org/thread.html/rfe62fbf9d4c314f166fe8c668e50e5d9dd882a99447f26f0367474bf@%3Cannounce.tomcat.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2021/03/msg00018.html', 'https://lists.apache.org/thread.html/rb51ccd58b2152fc75125b2406fc93e04ca9d34e737263faa6ff0f41f@%3Cusers.tomcat.apache.org%3E', 'https://lists.apache.org/thread.html/r732b2ca289dc02df2de820e8775559abd6c207f159e39f559547a085@%3Cusers.tomcat.apache.org%3E', 'https://lists.apache.org/thread.html/r11ce01e8a4c7269b88f88212f21830edf73558997ac7744f37769b77@%3Cusers.tomcat.apache.org%3E', 'https://lists.apache.org/thread.html/rf6d5d57b114678d8898005faef31e9fd6d7c981fcc4ccfc3bc272fc9@%3Cdev.tomcat.apache.org%3E', 'https://lists.apache.org/thread.html/rfe62fbf9d4c314f166fe8c668e50e5d9dd882a99447f26f0367474bf%40%3Cannounce.tomcat.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25329', 'https://lists.apache.org/thread.html/rfe62fbf9d4c314f166fe8c668e50e5d9dd882a99447f26f0367474bf@%3Cdev.tomcat.apache.org%3E', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://github.com/apache/tomcat/commit/6d66e99ef85da93e4d2c2a536ca51aa3418bfaf4', 'https://lists.apache.org/thread.html/rfe62fbf9d4c314f166fe8c668e50e5d9dd882a99447f26f0367474bf@%3Cannounce.apache.org%3E', 'http://www.openwall.com/lists/oss-security/2021/03/01/2', 'https://lists.apache.org/thread.html/r8a2ac0e476dbfc1e6440b09dcc782d444ad635d6da26f0284725a5dc@%3Cusers.tomcat.apache.org%3E', 'https://github.com/apache/tomcat', 'https://lists.apache.org/thread.html/rfe62fbf9d4c314f166fe8c668e50e5d9dd882a99447f26f0367474bf@%3Cusers.tomcat.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://www.debian.org/security/2021/dsa-4891', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/apache/tomcat/commit/6d66e99ef85da93e4d2c2a536ca51aa3418bfaf4'} | {'https://github.com/apache/tomcat/commit/6d66e99ef85da93e4d2c2a536ca51aa3418bfaf4'} |
Maven | GHSA-6w39-qhmq-g8cp | CSRF vulnerability in Jenkins Publish Over FTP Plugin | A cross-site request forgery (CSRF) vulnerability in Jenkins Publish Over FTP Plugin 1.16 and earlier allows attackers to connect to an FTP server using attacker-specified credentials. | {'CVE-2022-29050'} | 2022-05-04T21:03:09.782938Z | 2022-04-13T00:00:16Z | HIGH | null | {'CWE-352'} | {'https://github.com/jenkinsci/publish-over-ftp-plugin', 'https://github.com/jenkinsci/publish-over-ftp-plugin/commit/b265201428557ab91304e06199ad38221efc23e7', 'https://www.jenkins.io/security/advisory/2022-04-12/#SECURITY-2321', 'https://nvd.nist.gov/vuln/detail/CVE-2022-29050'} | null | {'https://github.com/jenkinsci/publish-over-ftp-plugin/commit/b265201428557ab91304e06199ad38221efc23e7'} | {'https://github.com/jenkinsci/publish-over-ftp-plugin/commit/b265201428557ab91304e06199ad38221efc23e7'} |
Maven | GHSA-f9hv-mg5h-xcw9 | High severity vulnerability that affects com.fasterxml.jackson.core:jackson-databind | FasterXML jackson-databind 2.x before 2.9.8 might allow attackers to have unspecified impact by leveraging failure to block the axis2-transport-jms class from polymorphic deserialization. | {'CVE-2018-19360'} | 2022-03-03T05:12:35.261196Z | 2019-01-04T19:06:57Z | CRITICAL | null | {'CWE-502'} | {'http://www.securityfocus.com/bid/107985', 'https://access.redhat.com/errata/RHSA-2019:3140', 'https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html', 'https://nvd.nist.gov/vuln/detail/CVE-2018-19360', 'https://lists.apache.org/thread.html/ff8dcfe29377088ab655fda9d585dccd5b1f07fabd94ae84fd60a7f8@%3Ccommits.pulsar.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2019:2804', 'https://lists.apache.org/thread.html/rf1bbc0ea4a9f014cf94df9a12a6477d24a27f52741dbc87f2fd52ff2@%3Cissues.geode.apache.org%3E', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2019/03/msg00005.html', 'https://access.redhat.com/errata/RHBA-2019:0959', 'https://access.redhat.com/errata/RHSA-2019:1797', 'https://seclists.org/bugtraq/2019/May/68', 'https://access.redhat.com/errata/RHSA-2019:4037', 'https://github.com/FasterXML/jackson-databind/commit/42912cac4753f3f718ece875e4d486f8264c2f2b', 'https://lists.apache.org/thread.html/c70da3cb6e3f03e0ad8013e38b6959419d866c4a7c80fdd34b73f25c@%3Ccommits.pulsar.apache.org%3E', 'https://security.netapp.com/advisory/ntap-20190530-0003/', 'https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.9.8', 'https://www.debian.org/security/2019/dsa-4452', 'https://access.redhat.com/errata/RHSA-2019:2858', 'https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2019:1822', 'https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html', 'https://github.com/FasterXML/jackson-databind/issues/2186', 'https://access.redhat.com/errata/RHSA-2019:3149', 'https://access.redhat.com/errata/RHSA-2019:0782', 'https://access.redhat.com/errata/RHSA-2019:0877', 'https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442@%3Cdev.drill.apache.org%3E', 'https://lists.apache.org/thread.html/r1b103833cb5bc8466e24ff0ecc5e75b45a705334ab6a444e64e840a0@%3Cissues.bookkeeper.apache.org%3E', 'https://lists.apache.org/thread.html/37e1ed724a1b0e5d191d98c822c426670bdfde83804567131847d2a3@%3Cdevnull.infra.apache.org%3E', 'https://lists.apache.org/thread.html/bcce5a9c532b386c68dab2f6b3ce8b0cc9b950ec551766e76391caa3@%3Ccommits.nifi.apache.org%3E', 'https://github.com/advisories/GHSA-f9hv-mg5h-xcw9', 'https://access.redhat.com/errata/RHSA-2019:3002', 'https://issues.apache.org/jira/browse/TINKERPOP-2121', 'https://access.redhat.com/errata/RHSA-2019:1782', 'https://lists.apache.org/thread.html/rca37935d661f4689cb4119f1b3b224413b22be161b678e6e6ce0c69b@%3Ccommits.nifi.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuapr2020.html', 'https://access.redhat.com/errata/RHSA-2019:3892', 'https://access.redhat.com/errata/RHSA-2019:1823'} | null | {'https://github.com/FasterXML/jackson-databind/commit/42912cac4753f3f718ece875e4d486f8264c2f2b'} | {'https://github.com/FasterXML/jackson-databind/commit/42912cac4753f3f718ece875e4d486f8264c2f2b'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.