ecosystem stringclasses 14 values | vuln_id stringlengths 10 19 | summary stringlengths 4 267 ⌀ | details stringlengths 9 13.5k | aliases stringlengths 17 144 ⌀ | modified_date stringdate 2010-05-27 05:47:00 2022-05-10 08:46:52 | published_date stringdate 2005-12-31 05:00:00 2022-05-10 08:46:50 | severity stringclasses 5 values | score float64 0 10 ⌀ | cwe_id stringclasses 988 values | refs stringlengths 30 17.7k ⌀ | introduced stringlengths 75 4.26k ⌀ |
|---|---|---|---|---|---|---|---|---|---|---|---|
Go | GHSA-cjjc-xp8v-855w | Panic in malformed cerftificate | The Helm core maintainers have identified a high severity security vulnerability in Go's `crypto` package affecting all versions prior to Helm 2.16.8 and Helm 3.1.0.
Thanks to @ravin9249 for identifying the vulnerability.
### Impact
Go before 1.12.16 and 1.13.x before 1.13.7 (and the `crypto/cryptobyte` package before 0.0.0-20200124225646-8b5121be2f68 for Go) allows attacks on clients resulting in a panic via a malformed X.509 certificate. This may allow a remote attacker to cause a denial of service.
### Patches
A patch to compile Helm against Go 1.14.4 has been provided for Helm 2 and is available in Helm 2.16.8. Helm 3.1.0 and newer are compiled against Go 1.13.7+.
### Workarounds
No workaround is available. Users are urged to upgrade.
### References
- https://nvd.nist.gov/vuln/detail/CVE-2020-7919
- https://github.com/helm/helm/pull/8288
### 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> | {'CVE-2020-7919'} | 2021-10-06T21:23:32Z | 2021-06-23T18:02:39Z | HIGH | null | {'CWE-295'} | {'https://security.netapp.com/advisory/ntap-20200327-0001/', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://github.com/helm/helm/security/advisories/GHSA-cjjc-xp8v-855w', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7919', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S43VLYRURELDWX4D5RFOYBNFGO6CGBBC/', 'https://github.com/helm/helm', 'https://groups.google.com/forum/#!topic/golang-announce/-sdUB4VEQkA', 'https://www.debian.org/security/2021/dsa-4848', 'https://groups.google.com/forum/#!topic/golang-announce/Hsw4mHYc470', 'https://groups.google.com/forum/#!forum/golang-announce'} | null |
Go | GHSA-x95h-979x-cf3j | Policies not properly enforced in bluemonday | The bluemonday sanitizer before 1.0.16 for Go, and before 0.0.8 for Python (in pybluemonday), does not properly enforce policies associated with the SELECT, STYLE, and OPTION elements. | {'CVE-2021-42576'} | 2022-03-03T05:14:13.158012Z | 2021-10-19T20:15:30Z | MODERATE | null | {'CWE-20'} | {'https://github.com/microcosm-cc/bluemonday', 'https://nvd.nist.gov/vuln/detail/CVE-2021-42576', 'https://docs.google.com/document/d/11SoX296sMS0XoQiQbpxc5pNxSdbJKDJkm5BDv0zrX50/'} | null |
Go | GO-2021-0104 | null | Due to improper error handling, DTLS connections were not killed when certificate verification
failed, causing users who did not check the connection state to continue to use the connection.
This could allow allow an attacker which holds the ICE password, but not a valid certificate,
to bypass this restriction.
| {'CVE-2021-28681'} | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/pion/webrtc/commit/545613dcdeb5dedb01cce94175f40bcbe045df2e', 'https://github.com/advisories/GHSA-74xm-qj29-cq8p', 'https://github.com/pion/webrtc/pull/1709', 'https://github.com/pion/webrtc/issues/1708'} | null |
Go | GHSA-g9mp-8g3h-3c5c | Improper nonce handling: potential overflow, potential state DoS | The Go package `github.com/flynn/noise`, a [Noise Protocol](https://noiseprotocol.org/) implementation, has two bugs in nonce handling in versions prior to v1.0.0.
### Issue 1: Potential nonce overflow
If 2^64 (~18.4 quintillion) or more messages are encrypted with `Encrypt` after handshaking, the nonce counter will wrap around, causing multiple messages to be encrypted with the same key and nonce, resulting in a potentially catastrophic weakening of the security properties of the symmetric cipher.
This has been resolved in the patched version by returning `ErrMaxNonce` from the `CipherState` `Encrypt` and `Decrypt` methods before the reserved maximum nonce is reached. If this error is encountered, the program should handshake again to start with a fresh `CipherState`.
### Issue 2: Potential denial of service via invalid ciphertext
If an attacker sends an invalid ciphertext into one peer's `Decrypt`, the nonce is incremented unconditionally. This causes a desync of the `CipherState` due to a nonce mismatch between the peers, resulting in a failure to decrypt all subsequent messages. A new handshake will be required to establish a new `CipherState`.
This has been resolved in the patched version by returning authentication errors from `Decrypt` before incrementing the nonce.
### Patches
Fixed in https://github.com/flynn/noise/pull/44, tagged as v1.0.0.
### Acknowledgements
These issues were discovered during [an audit](https://www.bamsoftware.com/software/dnstt/cure53-turbotunnel-2021.pdf) of a user of this package ([dnstt](https://www.bamsoftware.com/software/dnstt/)). Thanks to UC Berkley for commissioning the audit, and to David Fifield and Nathan Brown for their collaboration on the fixes. The fixed issues are noted in the audit as:
* UCB-02-003 Potential nonce overflow in Noise protocol
* UCB-02-006 DoS due to unconditional nonce increment | null | 2021-05-18T21:46:19Z | 2022-02-15T01:57:18Z | MODERATE | null | null | {'https://github.com/flynn/noise/security/advisories/GHSA-g9mp-8g3h-3c5c'} | null |
Go | GHSA-g6w6-r76c-28j7 | Incorrect Authorization in NATS nats-server | (This advisory is canonically <https://advisories.nats.io/CVE/CVE-2022-24450.txt>)
## Problem Description
NATS nats-server through 2022-02-04 has Incorrect Access Control, with unchecked ability for clients to authorize into any account, because of a coding error in a long-extant experimental feature.
A client crafting the initial protocol-level handshake could, with valid credentials for any account, specify a target account and switch into it immediately. This includes any other tenant, and includes the System account which controls nats-server core operations.
For deployments not using multi-tenancy through NATS Accounts, there is still a vulnerability: normal users are able to choose to be in the System account.
An experimental feature to provide dynamically provisioned sandbox accounts was designed to allow a server administrator to turn on an option to allow clients to dynamically request a brand new account inline at connection time. This feature went nowhere, but lived on in the code and was used by a number of tests; support was never added to any client libraries or to the documentation.
A bug in handling the feature meant that if someone did in fact have valid account credentials, then they could specify any other existing account and they would be assigned into that account.
Release 2.7.2 of nats-server removes the feature.
Because of the lack of client support and absence from protocol documentation, we feel this is safe operationally as well as the safest fix for the code.
## Affected versions
#### NATS Server
* All 2.x versions up to and including 2.7.1.
* Fixed with nats-io/nats-server: 2.7.2
* NATS Server 1.x did not have accounts.
* Docker image: nats <https://hub.docker.com/_/nats>
#### NATS Streaming Server
* All versions embedding affected NATS Server:
+ Affected: v0.15.0 up to and including v0.24.0
+ Fixed with nats-io/nats-streaming-server: 0.24.1
* Docker image: nats-streaming <https://hub.docker.com/_/nats-streaming>
## Impact
Existing users could act in any account, including the System account.
## Workaround
None.
## Solution
Upgrade the NATS server. | {'CVE-2022-24450'} | 2022-02-08T17:23:16Z | 2022-02-08T17:23:16Z | CRITICAL | null | {'CWE-863'} | {'https://github.com/nats-io/nats-server/security/advisories/GHSA-g6w6-r76c-28j7', 'https://github.com/nats-io/nats-server', 'https://advisories.nats.io/CVE/CVE-2022-24450.txt', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24450', 'https://github.com/nats-io/nats-server/releases/tag/v2.7.2'} | null |
Go | GHSA-44r7-7p62-q3fr | Insecure generation of random numbers | The miekg Go DNS package before 1.1.25, as used in CoreDNS before 1.6.6 and other products, improperly generates random numbers because math/rand is used. The TXID becomes predictable, leading to response forgeries. | {'CVE-2019-19794'} | 2021-05-18T20:42:52Z | 2021-05-18T21:09:13Z | MODERATE | null | {'CWE-338', 'CWE-330'} | {'https://github.com/coredns/coredns/issues/3547', 'https://nvd.nist.gov/vuln/detail/CVE-2019-19794', 'https://github.com/miekg/dns/pull/1044', 'https://github.com/miekg/dns/issues/1043', 'https://github.com/miekg/dns/commit/8ebf2e419df7857ac8919baa05248789a8ffbf33', 'https://github.com/coredns/coredns/issues/3519', 'https://github.com/miekg/dns/compare/v1.1.24...v1.1.25'} | null |
Go | GO-2021-0112 | null | Due to improper input sanitization when marshalling Go objects into BSON, a maliciously constructed
Go structure could allow an attacker to inject additional fields into a MongoDB document. Users are
affected if they use this package to handle untrusted user input.
| {'CVE-2021-20329'} | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/mongodb/mongo-go-driver/commit/2aca31d5986a9e1c65a92264736de9fdc3b9b4ca', 'https://jira.mongodb.org/browse/GODRIVER-1923', 'https://github.com/mongodb/mongo-go-driver/pull/622', 'https://github.com/advisories/GHSA-f6mq-5m25-4r72'} | null |
Go | GO-2021-0057 | 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-35381'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/buger/jsonparser/pull/221', 'https://github.com/buger/jsonparser/commit/df3ea76ece10095374fd1c9a22a4fb85a44efc42', 'https://github.com/buger/jsonparser/issues/219'} | null |
Go | GHSA-wf43-55jj-vwq8 | DNS Rebinding in etcd | DNS rebinding vulnerability found in etcd 3.3.1 and earlier. An attacker can control his DNS records to direct to localhost, and trick the browser into sending requests to localhost (or any other address). | {'CVE-2018-1099'} | 2021-05-19T22:09:57Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-350', 'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-1099', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UPGYHMSKDPW5GAMI7BEP3XQRVRLLBJKS/', 'https://github.com/coreos/etcd/issues/9353', 'https://bugzilla.redhat.com/show_bug.cgi?id=1552717', 'https://github.com/coreos/etcd/commit/a7e5790c82039945639798ae9a3289fe787f5e56', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JX7QTIT465BQGRGNCE74RATRQLKT2QE4/'} | null |
Go | GHSA-3p3g-vpw6-4w66 | Authentication Bypass in hydra | ### Impact
"When using client authentication method "private_key_jwt" [1], OpenId specification says the following about assertion `jti`:"
> A unique identifier for the token, which can be used to prevent reuse of the token. These tokens MUST only be used once, unless conditions for reuse were negotiated between the parties
"Hydra does not seem to check the uniqueness of this `jti` value. Here is me sending the same token request twice, hence with the same `jti` assertion, and getting two access tokens:"
```
$ curl --insecure --location --request POST 'https://localhost/_/oauth2/token' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'grant_type=client_credentials' \
--data-urlencode 'client_id=c001d00d-5ecc-beef-ca4e-b00b1e54a111' \
--data-urlencode 'scope=application openid' \
--data-urlencode 'client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer' \
--data-urlencode 'client_assertion=eyJhb [...] jTw'
{"access_token":"zeG0NoqOtlACl8q5J6A-TIsNegQRRUzqLZaYrQtoBZQ.VR6iUcJQYp3u_j7pwvL7YtPqGhtyQe5OhnBE2KCp5pM","expires_in":3599,"scope":"application openid","token_type":"bearer"}⏎ ~$ curl --insecure --location --request POST 'https://localhost/_/oauth2/token' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'grant_type=client_credentials' \
--data-urlencode 'client_id=c001d00d-5ecc-beef-ca4e-b00b1e54a111' \
--data-urlencode 'scope=application openid' \
--data-urlencode 'client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer' \
--data-urlencode 'client_assertion=eyJhb [...] jTw'
{"access_token":"wOYtgCLxLXlELORrwZlmeiqqMQ4kRzV-STU2_Sollas.mwlQGCZWXN7G2IoegUe1P0Vw5iGoKrkOzOaplhMSjm4","expires_in":3599,"scope":"application openid","token_type":"bearer"}
```
### Severity
"We rate the severity as medium because the following reasons make it hard to replay tokens without the patch:"
- TLS protects against MITM which makes it difficult to intercept valid tokens for replay attacks
- The expiry time of the JWT gives only a short window of opportunity where it could be replayed
### Patches
This will be patched with v1.4.0+oryOS.17
### Workarounds
Two workarounds have been identified:
- Do not allow clients to use `private_key_jwt`
- Use short expiry times for the JWTs
### Upstream
This issue will be resolved in the upstream repository https://github.com/ory/fosite | {'CVE-2020-5300'} | 2021-05-24T21:19:26Z | 2021-05-27T18:43:22Z | MODERATE | null | {'CWE-294'} | {'https://github.com/ory/hydra/commit/700d17d3b7d507de1b1d459a7261d6fb2571ebe3', 'https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5300', 'https://github.com/ory/hydra/releases/tag/v1.4.0', 'https://github.com/ory/hydra/security/advisories/GHSA-3p3g-vpw6-4w66'} | null |
Go | GHSA-c3xm-pvg7-gh7r | mount destinations can be swapped via symlink-exchange to cause mounts outside the rootfs | ### Summary
runc 1.0.0-rc94 and earlier are vulnerable to a symlink exchange attack whereby
an attacker can request a seemingly-innocuous container configuration that
actually results in the host filesystem being bind-mounted into the container
(allowing for a container escape). CVE-2021-30465 has been assigned for this
issue.
An attacker must have the ability to start containers using some kind of custom
volume configuration, and while recommended container hardening mechanisms such
as LSMs (AppArmor/SELinux) and user namespaces will restrict the amount of
damage an attacker could do, they do not block this attack outright. We have a
reproducer using Kubernetes (and the below description mentions
Kubernetes-specific paths), but this is not a Kubernetes-specific issue.
The now-released [runc v1.0.0-rc95][release] contains a fix for this issue, we
recommend users update as soon as possible.
[release]: https://github.com/opencontainers/runc/releases/tag/v1.0.0-rc95
### Details
In circumstances where a container is being started, and runc is mounting
inside a volume shared with another container (which is conducting a
symlink-exchange attack), runc can be tricked into mounting outside of the
container rootfs by swapping the target of a mount with a symlink due to a
time-of-check-to-time-of-use (TOCTTOU) flaw. This is fairly similar in style to
previous TOCTTOU attacks (and is a problem we are working on solving with
libpathrs).
However, this alone is not useful because this happens inside a mount namespace
with `MS_SLAVE` propagation applied to `/` (meaning that the mount doesn't
appear on the host -- it's only a "host-side mount" inside the container's
namespace). To exploit this, you must have additional mount entries in the
configuration that use some subpath of the mounted-over host path as a source
for a subsequent mount.
However, it turns out with some container orchestrators (such as Kubernetes --
though it is very likely that other downstream users of runc could have similar
behaviour be accessible to untrusted users), the existence of additional volume
management infrastructure allows this attack to be applied to gain access to
the host filesystem without requiring the attacker to have completely arbitrary
control over container configuration.
In the case of Kubernetes, this is exploitable by creating a symlink in a
volume to the top-level (well-known) directory where volumes are sourced from
(for instance,
`/var/lib/kubelet/pods/$MY_POD_UID/volumes/kubernetes.io~empty-dir`), and then
using that symlink as the target of a mount. The source of the mount is an
attacker controlled directory, and thus the source directory from which
subsequent mounts will occur is an attacker-controlled directory. Thus the
attacker can first place a symlink to `/` in their malicious source directory
with the name of a volume, and a subsequent mount in the container will
bind-mount `/` into the container.
Applying this attack requires the attacker to start containers with a slightly
peculiar volume configuration (though not explicitly malicious-looking such as
bind-mounting `/` into the container explicitly), and be able to run malicious
code in a container that shares volumes with said volume configuration. It
helps the attacker if the host paths used for volume management are well known,
though this is not a hard requirement.
### Patches
This has been patched in runc 1.0.0-rc95, and users should upgrade as soon as
possible. The patch itself can be found [here](https://github.com/opencontainers/runc/commit/0ca91f44f1664da834bc61115a849b56d22f595f).
### Workarounds
There are no known workarounds for this issue.
However, users who enforce running containers with more confined security
profiles (such as reduced capabilities, not running code as root in the
container, user namespaces, AppArmor/SELinux, and seccomp) will restrict what
an attacker can do in the case of a container breakout -- we recommend users
make use of strict security profiles if possible (most notably user namespaces
-- which can massively restrict the impact a container breakout can have on the
host system).
### References
* [commit](https://github.com/opencontainers/runc/commit/0ca91f44f1664da834bc61115a849b56d22f595f)
* [seclists public disclosure](https://www.openwall.com/lists/oss-security/2021/05/19/2)
### Credit
Thanks to Etienne Champetier for discovering and disclosing this vulnerability,
to Noah Meyerhans for writing the first draft of this patch, and to Samuel Karp
for testing it.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [our issue tracker](https://github.com/opencontainers/runc/issues).
* Email us at <security@opencontainers.org>. | {'CVE-2021-30465'} | 2021-05-21T19:34:43Z | 2021-05-25T18:44:42Z | HIGH | null | {'CWE-367', 'CWE-22'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4HOARVIT47RULTTFWAU7XBG4WY6TDDHV/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-30465', 'https://bugzilla.opensuse.org/show_bug.cgi?id=1185405', 'https://security.netapp.com/advisory/ntap-20210708-0003/', 'https://github.com/opencontainers/runc/commit/0ca91f44f1664da834bc61115a849b56d22f595f', 'https://github.com/opencontainers/runc/security/advisories/GHSA-c3xm-pvg7-gh7r', 'https://github.com/opencontainers/runc/releases', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/35ZW6NBZSBH5PWIT7JU4HXOXGFVDCOHH/', 'http://www.openwall.com/lists/oss-security/2021/05/19/2'} | null |
Go | GHSA-hwrr-rhmm-vcvf | NULL Pointer Dereference in Kubernetes CSI snapshot-controller | Kubernetes CSI snapshot-controller prior to v2.1.3 and v3.0.2 could panic when processing a VolumeSnapshot custom resource when:
- The VolumeSnapshot referenced a non-existing PersistentVolumeClaim and the VolumeSnapshot did not reference any VolumeSnapshotClass.
- The snapshot-controller crashes, is automatically restarted by Kubernetes, and processes the same VolumeSnapshot custom resource after the restart, entering an endless crashloop.
Only the volume snapshot feature is affected by this vulnerability. When exploited, users can’t take snapshots of their volumes or delete the snapshots. All other Kubernetes functionality is not affected. | {'CVE-2020-8569'} | 2021-05-12T21:41:14Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-476'} | {'https://groups.google.com/g/kubernetes-security-announce/c/1EzCr1qUxxU', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8569', 'https://github.com/kubernetes-csi/external-snapshotter/issues/380'} | null |
Go | GHSA-cg3q-j54f-5p7p | Uncontrolled Resource Consumption in promhttp | This is the Go client library for Prometheus. It has two separate parts, one for instrumenting application code, and one for creating clients that talk to the Prometheus HTTP API. client_golang is the instrumentation library for Go applications in Prometheus, and the promhttp package in client_golang provides tooling around HTTP servers and clients.
### Impact
HTTP server susceptible to a Denial of Service through unbounded cardinality, and potential memory exhaustion, when handling requests with non-standard HTTP methods.
### Affected Configuration
In order to be affected, an instrumented software must
* Use any of `promhttp.InstrumentHandler*` middleware except `RequestsInFlight`.
* Do not filter any specific methods (e.g GET) before middleware.
* Pass metric with `method` label name to our middleware.
* Not have any firewall/LB/proxy that filters away requests with unknown `method`.
### Patches
* https://github.com/prometheus/client_golang/pull/962
* https://github.com/prometheus/client_golang/pull/987
### Workarounds
If you cannot upgrade to [v1.11.1 or above](https://github.com/prometheus/client_golang/releases/tag/v1.11.1), in order to stop being affected you can:
* Remove `method` label name from counter/gauge you use in the InstrumentHandler.
* Turn off affected promhttp handlers.
* Add custom middleware before promhttp handler that will sanitize the request method given by Go http.Request.
* Use a reverse proxy or web application firewall, configured to only allow a limited set of methods.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/prometheus/client_golang
* Email us at `prometheus-team@googlegroups.com`
| {'CVE-2022-21698'} | 2022-02-25T15:41:10Z | 2022-02-16T22:26:35Z | HIGH | null | {'CWE-772', 'CWE-400'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7V7I72LSQ3IET3QJR6QPAVGJZ4CBDLN5/', 'https://github.com/prometheus/client_golang/security/advisories/GHSA-cg3q-j54f-5p7p', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AK7CJBCGERCRXYUR2EWDSSDVAQMTAZGX/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZKORFJTRRDJCWBTJPISKKCVMMMJBIRLG/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KBMVIQFKQDSSTHVVJWJ4QH6TW3JVB7XZ/', 'https://github.com/prometheus/client_golang/pull/962', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/J5WPM42UR6XIBQNQPNQHM32X7S4LJTRX/', 'https://github.com/prometheus/client_golang', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FY3N7H6VSDZM37B4SKM2PFFCUWU7QYWN/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HLAQRRGNSO5MYCPAXGPH2OCSHOGHSQMQ/', 'https://github.com/prometheus/client_golang/releases/tag/v1.11.1', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2PFW6Q2LXXWTFRTMTRN4ZGADFRQPKJ3D/', 'https://github.com/prometheus/client_golang/pull/987', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21698', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SASRKYHT5ZFSVMJUQUG3UAEQRJYGJKAR/'} | null |
Go | GHSA-4c7m-vv47-7c69 | Insecure Permissions in Gogs | In Gogs 0.11.91, MakeEmailPrimary in models/user_mail.go lacks a "not the owner of the email" check. | {'CVE-2020-14958'} | 2021-05-12T14:55:34Z | 2021-05-18T20:33:05Z | MODERATE | null | {'CWE-281'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-14958', 'https://github.com/gogs/gogs/pull/5988', 'https://github.com/gogs/gogs/commit/82ff0c5852f29daa5f95d965fd50665581e7ea3c'} | null |
Go | GHSA-gp4j-w3vj-7299 | Information Exposure in RunC | RunC allowed additional container processes via 'runc exec' to be ptraced by the pid 1 of the container. This allows the main processes of the container, if running as root, to gain access to file-descriptors of these new processes during the initialization and can lead to container escapes or modification of runC state before the process is fully placed inside the container. | {'CVE-2016-9962'} | 2021-05-20T16:22:33Z | 2021-12-20T18:21:43Z | MODERATE | null | {'CWE-200'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WUQ3MQNEL5IBZZLMLR72Q4YDCL2SCKRK/', 'http://seclists.org/fulldisclosure/2017/Jan/21', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FINGBFMIXBG6B6ZWYH3TMRP5V3PDBNXR/', 'http://rhn.redhat.com/errata/RHSA-2017-0127.html', 'https://security.gentoo.org/glsa/201701-34', 'http://www.securityfocus.com/bid/95361', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UVM7FCOQMPKOFLDTUYSS4ES76DDM56VP/', 'https://github.com/opencontainers/runc/commit/50a19c6ff828c58e5dab13830bd3dacde268afe5', 'https://github.com/opencontainers/runc/commit/5d93fed3d27f1e2bab58bad13b180a7a81d0b378', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BQAXJMMLRU7DD2IMG47SR2K4BOFFG7FZ/', 'http://rhn.redhat.com/errata/RHSA-2017-0123.html', 'https://access.redhat.com/security/vulnerabilities/cve-2016-9962', 'http://seclists.org/fulldisclosure/2017/Jan/29', 'http://www.securityfocus.com/archive/1/540001/100/0/threaded', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-9962', 'https://github.com/docker/docker/releases/tag/v1.12.6', 'https://nvd.nist.gov/vuln/detail/CVE-2016-9962', 'https://bugzilla.suse.com/show_bug.cgi?id=1012568#c6', 'http://rhn.redhat.com/errata/RHSA-2017-0116.html'} | null |
Go | GHSA-v24h-pjjv-mcp6 | Denial of service in Tendermint | ### Description
**Denial of Service 1**
Tendermint 0.33.2 and earlier does not limit the number of P2P connection requests. For each p2p connection, Tendermint allocates XXX bytes. Even though this memory is garbage collected once the connection is terminated (due to duplicate IP or reaching a maximum number of inbound peers), temporary memory spikes can lead to OOM (Out-Of-Memory) exceptions.
Tendermint 0.33.3 (and 0.32.10) limits the total number of P2P incoming connection requests to to `p2p.max_num_inbound_peers + len(p2p.unconditional_peer_ids)`.
Notes:
- Tendermint does not rate limit P2P connection requests per IP (an attacker can saturate all the inbound slots);
- Tendermint does not rate limit HTTP(S) requests. If you expose any RPC endpoints to the public, please make sure to put in place some protection (https://www.nginx.com/blog/rate-limiting-nginx/). We may implement this in the future (https://github.com/tendermint/tendermint/issues/1696).
**Denial of Service 2**
Tendermint 0.33.2 and earlier does not reclaim `activeID` of a peer after it's removed in `Mempool` reactor. This does not happen all the time. It only happens when a connection fails (for any reason) before the `Peer` is created and added to all reactors. `RemovePeer` is therefore called before `AddPeer`, which leads to always growing memory (`activeIDs` map). The `activeIDs` map has a maximum size of 65535 and the node will panic if this map reaches the maximum. An attacker can create a lot of connection attempts (exploiting Denial of Service 1), which ultimately will lead to the node panicking.
Tendermint 0.33.3 (and 0.32.10) claims `activeID` for a peer in `InitPeer`, which is executed before `MConnection` is started.
Notes:
- `InitPeer` function was added to all reactors to combat a similar issue - https://github.com/tendermint/tendermint/issues/3338;
- Denial of Service 2 is independent of Denial of Service 1 and can be executed without it.
### Impact
- All full nodes (except for validators who are behind closed networks)
- Node's memory usage increases, then it panics either in the mempool or due to OOM.
### Patches
- v0.33.3
- v0.32.10
- v0.31.12
### Workarounds
No workarounds.
### References
- https://hackerone.com/reports/820317 (not disclosed yet)
- https://github.com/tendermint/tendermint/issues/3338
- https://github.com/tendermint/tendermint/issues/1696
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [tendermint/tendermint](https://github.com/tendermint/tendermint)
* Email us at [security@tendermint.com](mailto:security@tendermint.com)
More information can be found [here](https://tendermint.com/security/).
### Credits
- [fudongbai](https://hackerone.com/fudongbai) for discovering and reporting Denial of Service 2
- Ethan Buchman (@ebuchman) for writing a test case for Denial of Service 2 and Tess Rinearson (@tessr) for fixing it
- Anton Kaliaev (@melekes) for fixing Denial of Service 1 | {'CVE-2020-5303'} | 2021-05-24T21:16:50Z | 2021-05-27T18:44:09Z | LOW | null | {'CWE-789', 'CWE-787'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-5303', 'https://github.com/tendermint/tendermint/blob/master/CHANGELOG.md#denial-of-service-1', 'https://github.com/tendermint/tendermint/commit/e2d6859afd7dba4cf97c7f7d412e7d8fc908d1cd', 'https://github.com/tendermint/tendermint/issues/1696', 'https://github.com/tendermint/tendermint/issues/3338', 'https://github.com/tendermint/tendermint/security/advisories/GHSA-v24h-pjjv-mcp6', 'https://hackerone.com/reports/820317'} | null |
Go | GHSA-qq3j-xp49-j73f | Plugin archive directory traversal in Helm | The Helm core maintainers have identified an information disclosure
vulnerability in Helm 3.0.0-3.2.3.
### Impact
A traversal attack is possible when installing Helm plugins from a tar
archive over HTTP. It is possible for a malicious plugin author to inject a relative
path into a plugin archive, and copy a file outside of the intended directory.
Traversal Attacks are a form of a Directory Traversal that can be exploited by
extracting files from an archive. The premise of the Directory Traversal
vulnerability is that an attacker can gain access to parts of the file system
outside of the target folder in which they should reside. The attacker can
then overwrite executable files and either invoke them remotely or wait for
the system or user to call them, thus achieving Remote Command Execution on
the victim's machine. The vulnerability can also cause damage by overwriting
configuration files or other sensitive resources, and can be exploited on both
client (user) machines and servers.
https://snyk.io/research/zip-slip-vulnerability
### Patches
This issue has been fixed in Helm 3.2.4
### 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-4053'} | 2021-05-24T20:57:17Z | 2021-06-23T18:14:36Z | LOW | null | {'CWE-22'} | {'https://github.com/helm/helm/releases/tag/v3.2.4', 'https://github.com/helm/helm/pull/8317', 'https://github.com/helm/helm/commit/0ad800ef43d3b826f31a5ad8dfbb4fe05d143688', 'https://github.com/helm/helm/security/advisories/GHSA-qq3j-xp49-j73f', 'https://github.com/helm/helm/commit/b6bbe4f08bbb98eadd6c9cd726b08a5c639908b3', 'https://nvd.nist.gov/vuln/detail/CVE-2020-4053'} | null |
Go | GO-2021-0094 | null | Protections against directory traversal during archive extraction can be
bypassed by chaining multiple symbolic links within the archive. This allows
a malicious attacker to cause files to be created outside of the target
directory. Additionally if the attacker is able to read extracted files
they may create symbolic links to arbitary files on the system which the
unpacker has permissions to read.
| {'CVE-2020-29529'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/hashicorp/go-slug/pull/12', 'https://securitylab.github.com/advisories/GHSL-2020-262-zipslip-go-slug', 'https://github.com/hashicorp/go-slug/commit/28cafc59c8da6126a3ae94dfa84181df4073454f'} | null |
Go | GHSA-vf6q-9f2f-mwhv | Improper network isolation in Hashicorp Nomad | HashiCorp Nomad and Nomad Enterprise up to version 1.0.4 bridge networking mode allows ARP spoofing from other bridged tasks on the same node. Fixed in 0.12.12, 1.0.5, and 1.1.0 RC1. | {'CVE-2021-32575'} | 2021-06-23T18:01:24Z | 2021-06-24T20:28:21Z | MODERATE | null | {'CWE-1100'} | {'https://discuss.hashicorp.com/t/hcsec-2021-14-nomad-bridge-networking-mode-allows-arp-spoofing-from-other-bridged-tasks-on-same-node/24296', 'https://www.hashicorp.com/blog/category/nomad', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32575'} | null |
Go | GHSA-3xh2-74w9-5vxm | Integer overflow in github.com/gorilla/websocket | An integer overflow vulnerability exists with the length of websocket frames received via a websocket connection. An attacker would use this flaw to cause a denial of service attack on an HTTP Server allowing websocket connections. | {'CVE-2020-27813'} | 2021-05-18T20:56:17Z | 2021-05-18T21:08:02Z | HIGH | null | {'CWE-400', 'CWE-190'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=1902111', 'https://lists.debian.org/debian-lts-announce/2021/01/msg00008.html', 'https://github.com/gorilla/websocket/security/advisories/GHSA-jf24-p9p9-4rjh', 'https://nvd.nist.gov/vuln/detail/CVE-2020-27813', 'https://github.com/gorilla/websocket/pull/537', 'https://github.com/gorilla/websocket/commit/5b740c29263eb386f33f265561c8262522f19d37'} | null |
Go | GHSA-gcj7-j438-hjj2 | Smokescreen SSRF via deny list bypass | The primary use case for Smokescreen is to prevent server-side request forgery (SSRF) attacks in which external attackers leverage the behavior of applications to connect to or scan internal infrastructure.
Smokescreen also offers an option to deny access to additional (e.g., external) URLs by way of a deny list. There was an issue in Smokescreen that made it possible to bypass the deny list feature by appending a dot to the end of user-supplied URLs, or by providing input in a different letter case.
### Recommendation
Upgrade Smokescreen to version 0.0.3 or later.
### Acknowledgements
Thanks to [Grzegorz Niedziela](https://twitter.com/gregxsunday) for reporting the issue.
### For more information
Email us at security@stripe.com | {'CVE-2022-24825'} | 2022-04-07T22:10:22Z | 2022-04-07T22:10:22Z | MODERATE | null | {'CWE-918'} | {'https://github.com/stripe/smokescreen/security/advisories/GHSA-gcj7-j438-hjj2', 'https://github.com/stripe/smokescreen/commit/fafb6ae48c6c40aa011d87b61306abc48db8797b', 'github.com/stripe/smokescreen', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24825'} | null |
Go | GHSA-7638-r9r3-rmjj | chroot isolation: environment value leakage to intermediate processes | ### Impact
When running processes using "chroot" isolation, the process being run can examine the environment variables of its immediate parent and grandparent processes (CVE-2021-3602). This isolation type is often used when running `buildah` in unprivileged containers, and it is often used to do so in CI/CD environments. If sensitive information is exposed to the original `buildah` process through its environment, that information will unintentionally be shared with child processes which it starts as part of handling RUN instructions or during `buildah run`. The commands that `buildah` is instructed to run can read that information if they choose to.
### Patches
Users should upgrade packages, or images which contain packages, to include version 1.21.3 or later.
### Workarounds
As a workaround, invoking `buildah` in a container under `env -i` to have it started with a reinitialized environment should prevent the leakage.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [buildah](https://github.com/containers/buildah/issues)
* Email us at [the buildah general mailing list](mailto:buildah@lists.buildah.io), or [the podman security mailing list](mailto:security@lists.podman.io) if it's sensitive. | {'CVE-2021-3602'} | 2022-03-18T21:03:34Z | 2021-07-19T15:19:09Z | MODERATE | null | {'CWE-200'} | {'https://github.com/containers/buildah/security/advisories/GHSA-7638-r9r3-rmjj', 'https://ubuntu.com/security/CVE-2021-3602', 'https://bugzilla.redhat.com/show_bug.cgi?id=1969264', 'https://github.com/containers/buildah', 'https://github.com/containers/buildah/commit/a468ce0ffd347035d53ee0e26c205ef604097fb0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3602'} | null |
Go | GHSA-pmcr-2rhp-36hr | SQL injection in github.com/navidrome/navidrome | model/criteria/criteria.go in Navidrome before 0.47.5 is vulnerable to SQL injection attacks when processing crafted Smart Playlists. An authenticated user could abuse this to extract arbitrary data from the database, including the user table (which contains sensitive information such as the users' encrypted passwords). | {'CVE-2022-23857'} | 2022-01-25T21:03:46Z | 2022-01-27T16:23:02Z | MODERATE | null | {'CWE-89'} | {'https://github.com/navidrome/navidrome', 'https://github.com/navidrome/navidrome/commit/9e79b5cbf2a48c1e4344df00fea4ed3844ea965d', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23857', 'https://github.com/navidrome/navidrome/releases/tag/v0.47.5'} | null |
Go | GHSA-8fvr-5rqf-3wwh | Information Exposure in Docker Engine | Docker Engine before 1.6.1 uses weak permissions for (1) /proc/asound, (2) /proc/timer_stats, (3) /proc/latency_stats, and (4) /proc/fs, which allows local users to modify the host, obtain sensitive information, and perform protocol downgrade attacks via a crafted image. | {'CVE-2015-3630'} | 2021-05-19T22:47:32Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-285'} | {'https://seclists.org/fulldisclosure/2015/May/28', 'https://groups.google.com/forum/#!searchin/docker-user/1.6.1/docker-user/47GZrihtr-4/nwgeOOFLexIJ', 'https://lists.opensuse.org/opensuse-updates/2015-05/msg00023.html', 'https://www.securityfocus.com/bid/74566', 'https://nvd.nist.gov/vuln/detail/CVE-2015-3630', 'https://groups.google.com/forum/#%21searchin/docker-user/1.6.1/docker-user/47GZrihtr-4/nwgeOOFLexIJ', 'https://packetstormsecurity.com/files/131835/Docker-Privilege-Escalation-Information-Disclosure.html', 'https://github.com/moby/moby/commit/545b440a80f676a506e5837678dd4c4f65e78660', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-3630'} | null |
Go | GHSA-5j5w-g665-5m35 | Ambiguous OCI manifest parsing | ### Impact
In the OCI Distribution Specification version 1.0.0 and prior and in the OCI Image Specification version 1.0.1 and prior, manifest and index documents are ambiguous without an accompanying Content-Type HTTP header. Versions of containerd prior to 1.4.12 and 1.5.8 treat the Content-Type header as trusted and deserialize the document according to that header. If the Content-Type header changed between pulls of the same ambiguous document (with the same digest), the document may be interpreted differently, meaning that the digest alone is insufficient to unambiguously identify the content of the image.
### Patches
This issue has been fixed in containerd 1.4.12 and 1.5.8. Image pulls for manifests that contain a “manifests” field or indices which contain a “layers” field are rejected.
### Workarounds
Ensure you only pull images from trusted sources.
### References
https://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m
https://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [containerd](https://github.com/containerd/containerd/issues/new/choose)
* Email us at [security@containerd.io](mailto:security@containerd.io) | null | 2021-11-18T14:43:45Z | 2021-11-18T16:08:58Z | LOW | null | {'CWE-843'} | {'https://github.com/containerd/containerd/releases/tag/v1.4.12', 'https://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh', 'https://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m', 'https://github.com/containerd/containerd/releases/tag/v1.5.8', 'https://github.com/containerd/containerd/security/advisories/GHSA-5j5w-g665-5m35', 'https://github.com/containerd/containerd'} | null |
Go | GHSA-56hp-xqp3-w2jf | Repository credentials passed to alternate domain | While working on the Helm source, a Helm core maintainer discovered a situation where the username and password credentials associated with a Helm repository could be passed on to another domain referenced by that Helm repository.
### Impact
The `index.yaml` within a Helm chart repository contains a reference where to get the chart archive for each version of a chart. The reference can be relative to the `index.yaml` file or a URL to location. The URL can point to any domain and this is a feature leveraged by Helm users. For example, an `index.yaml` file can be hosted on GitHub pages while the chart archives are hosted as GitHub releases. These are on different domain names and the `index.yaml` file points to the other domain.
When a username and password were associated with a Helm repository the username and password were also passed on to other domains referenced in the `index.yaml` file. This occurred when Helm went to retrieve a specific chart archive on the other domain.
### Patches
This issue has been resolved in 3.6.1.
There is a slight behavior change to credential handling with regard to repositories. Usernames and passwords are only passed to the URL location of the Helm repository by default. The username and password are scoped to the scheme, host, and port of the Helm repository. To pass the username and password to other domains Helm may encounter when it goes to retrieve a chart, the new `--pass-credentials` flag can be used. This flag restores the old behavior for a single repository as an opt-in behavior.
### Workarounds
If you use a username and password for a Helm repository you can audit the Helm repository in order to check for another domain being used that could have received the credentials. In the `index.yaml` file for that repository, look for another domain in the `urls` list for the chart versions. If there is another domain found and that chart version was pulled or installed the credentials would have been passed on.
### For more information
Helm's security policy is spelled out in detail in our [SECURITY](https://github.com/helm/community/blob/master/SECURITY.md) document.
| null | 2021-06-16T19:43:50Z | 2021-06-23T18:14:15Z | MODERATE | null | {'CWE-200'} | {'https://github.com/helm/helm/security/advisories/GHSA-56hp-xqp3-w2jf'} | null |
Go | GHSA-j34v-3552-5r7j | Multiple security issues in Pomerium's embedded envoy | Envoy, which Pomerium is based on, has issued multiple CVEs impacting stability and security.
Though Pomerium may not be vulnerable to all of the issues, it is recommended that all users upgrade to Pomerium v0.16.4 as soon as possible to minimize risk.
### Impact
- Possible DoS or crash
- Resources available to unauthorized users
- Pomerium may trust upstream certificates that should not be trusted
### Patches
Patched in v0.16.4
### Workarounds
No
### References
[Envoy Security Announcement](https://groups.google.com/g/envoy-security-announce/c/QBGxoqZdTR4)
* [CVE-2021-43824](https://github.com/envoyproxy/envoy/security/advisories/GHSA-vj5m-rch8-5r2p) (CVSS Score 6.5, Medium): Envoy 1.21.0 and earlier - Potential null pointer dereference when using JWT filter safe_regex match
* [CVE-2021-43825](https://github.com/envoyproxy/envoy/security/advisories/GHSA-h69p-g6xg-mhhh) (CVSS Score 6.1, Medium): Envoy 1.21.0 and earlier - Use-after-free when response filters increase response data, and increased data exceeds downstream buffer limits.
* [CVE-2021-43826](https://github.com/envoyproxy/envoy/security/advisories/GHSA-cmx3-fvgf-83mf) (CVSS Score 6.1, Medium): Envoy 1.21.0 and earlier - Use-after-free when tunneling TCP over HTTP, if downstream disconnects during upstream connection establishment
* [CVE-2022-21654](https://github.com/envoyproxy/envoy/security/advisories/GHSA-5j4x-g36v-m283) (CVSS Score 7.3, High): Envoy 1.7.0 and later - Incorrect configuration handling allows mTLS session re-use without re-validation after validation settings have changed.
* [CVE-2022-21655](https://github.com/envoyproxy/envoy/security/advisories/GHSA-7r5p-7fmh-jxpg) (CVSS Score 7.5, High): Envoy 1.21 and earlier - Incorrect handling of internal redirects to routes with a direct response entry
* [CVE-2022-21657](https://github.com/envoyproxy/envoy/security/advisories/GHSA-837m-wjrv-vm5g) (CVSS Score 3.1, Low): Envoy 1.20.1 and earlier - X.509 Extended Key Usage and Trust Purposes bypass
### For more information
If you have any questions or comments about this advisory:
Open an issue in [pomerium/pomerium](https://github.com/pomerium/pomerium/issues)
Email us at [security@pomerium.com](mailto:security@pomerium.com)
| null | 2022-03-01T22:04:17Z | 2022-03-01T22:04:17Z | MODERATE | null | null | {'https://github.com/pomerium/pomerium/security/advisories/GHSA-j34v-3552-5r7j', 'https://github.com/pomerium/pomerium'} | null |
Go | GHSA-7p8f-8hjm-wm92 | Lookup operations do not take into account wildcards in SpiceDB | ### Impact
Any user making use of a wildcard relationship under the right hand branch of an `exclusion` or within an `intersection` operation will see `Lookup`/`LookupResources` return a resource as "accessible" if it is *not* accessible by virtue of the inclusion of the wildcard in the intersection or the right side of the exclusion.
For example, given schema:
```zed
definition user {}
definition resource {
relation viewer: user
relation banned: user | user:*
permission view = viewer - banned
}
```
If `user:*` is placed into the `banned` relation for a particular resource, `view` should return false for *all* resources. in `v1.3.0`, the wildcard is ignored entirely in lookup's dispatch, resulting in the `banned` wildcard being ignored in the exclusion.
### Workarounds
Don't make use of wildcards on the right side of intersections or within exclusions.
### References
https://github.com/authzed/spicedb/issues/358
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [SpiceDB](https://github.com/authzed/spicedb)
* Ask a question in the [SpiceDB Discord](https://authzed.com/discord)
| {'CVE-2022-21646'} | 2022-01-13T15:02:31Z | 2022-01-13T15:05:41Z | HIGH | null | {'CWE-155', 'CWE-20'} | {'https://github.com/authzed/spicedb/security/advisories/GHSA-7p8f-8hjm-wm92', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21646', 'https://github.com/authzed/spicedb/issues/358', 'https://github.com/authzed/spicedb/releases/tag/v1.4.0', 'https://github.com/authzed/spicedb', 'https://github.com/authzed/spicedb/commit/15bba2e2d2a4bda336a37a7fe8ef8a35028cd970'} | null |
Go | GHSA-4hq8-gmxx-h6w9 | XML Processing error in github.com/crewjam/saml | ### Impact
There are three vulnerabilities in the go `encoding/xml` package that can allow an attacker to forge part of a signed XML document. For details on this vulnerability see [xml-roundtrip-validator](https://github.com/mattermost/xml-roundtrip-validator)
### Patches
In version 0.4.3, all XML input is validated prior to being parsed. | {'CVE-2020-27846'} | 2021-05-21T20:54:26Z | 2021-06-23T17:29:42Z | HIGH | null | {'CWE-115', 'CWE-287'} | {'https://grafana.com/blog/2020/12/17/grafana-6.7.5-7.2.3-and-7.3.6-released-with-important-security-fix-for-grafana-enterprise/', 'https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/', 'https://bugzilla.redhat.com/show_bug.cgi?id=1907670', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3YUTKIRWT6TWU7DS6GF3EOANVQBFQZYI/', 'https://github.com/crewjam/saml/commit/da4f1a0612c0a8dd0452cf8b3c7a6518f6b4d053', 'https://github.com/crewjam/saml/security/advisories/GHSA-4hq8-gmxx-h6w9', 'https://nvd.nist.gov/vuln/detail/CVE-2020-27846', 'https://security.netapp.com/advisory/ntap-20210205-0002/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ICP3YRY2VUCNCF2VFUSK77ZMRIC77FEM/'} | null |
Go | GHSA-6x2m-w449-qwx7 | Code Injection in CRI-O | ### Impact
A flaw introduced in CRI-O version 1.19 which an attacker can use to bypass the safeguards and set arbitrary kernel parameters on the host. As a result, anyone with rights to deploy a pod on a Kubernetes cluster that uses the CRI-O runtime can abuse the `kernel.core_pattern` kernel parameter to achieve container escape and arbitrary code execution as root on any node in the cluster.
### Patches
The patches will be present in 1.19.6, 1.20.7, 1.21.6, 1.22.3, 1.23.2, 1.24.0
### Workarounds
- Users can set manage_ns_lifecycle to false, which causes the sysctls to be configured by the OCI runtime, which typically filter these cases. This option is available in 1.20 and 1.19. Newer versions don't have this option.
- An admission webhook could be created to deny pods that specify a `+` in the sysctl value of a pod.
- A [PodSecurityPolicy](https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/#podsecuritypolicy) [deprecated] could be created, specifying all sysctls as forbidden like so:
```
apiVersion: policy/v1beta1
kind: PodSecurityPolicy
metadata:
name: sysctl-psp
spec:
forbiddenSysctls:
- "*"
```
However, this option will not work if any sysctls are required by any pods in the cluster.
### Credits
Credit for finding this vulnerability goes to John Walker and Manoj Ahuje of Crowdstrike. The CRI-O community deeply thanks them for the report.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the CRI-O repo](http://github.com/cri-o/cri-o/issues)
* To make a report, email your vulnerability to the private
[cncf-crio-security@lists.cncf.io](mailto:cncf-crio-security@lists.cncf.io) list
with the security details and the details expected for [all CRI-O bug
reports](https://github.com/cri-o/cri-o/blob/main/.github/ISSUE_TEMPLATE/bug-report.yml).
| {'CVE-2022-0811'} | 2022-03-18T17:47:49Z | 2022-03-15T20:13:38Z | HIGH | null | {'CWE-94'} | {'https://www.crowdstrike.com/blog/cr8escape-zero-day-vulnerability-discovered-in-cri-o-container-engine-cve-2022-0811/', 'https://github.com/cri-o/cri-o/security/advisories/GHSA-6x2m-w449-qwx7', 'https://access.redhat.com/security/cve/CVE-2022-0811', 'https://bugzilla.redhat.com/show_bug.cgi?id=2059475', 'https://bugs.gentoo.org/835336', 'https://github.com/cri-o/cri-o', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0811'} | null |
Go | GHSA-q6cj-6jvq-jwmh | Privilege Escalation in Cloud Native Computing Foundation Harbor | Cloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 has a Privilege Escalation Vulnerability in the VMware Harbor Container Registry for the Pivotal Platform. | {'CVE-2019-19023'} | 2021-05-04T21:59:38Z | 2021-05-18T18:27:28Z | MODERATE | null | {'CWE-269'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-19023', 'https://github.com/goharbor/harbor/security/advisories/GHSA-3868-7c5x-4827', 'https://github.com/goharbor/harbor/security/advisories', 'https://tanzu.vmware.com/security/cve-2019-19023'} | null |
Go | GHSA-w4f8-fxq2-j35v | Possible privilege escalation via bash completion script | The bash completion script for `fscrypt` through v0.3.2 allows injection of commands via crafted mountpoint paths, allowing privilege escalation under a specific set of circumstances. A local user who has control over mountpoint paths could potentially escalate their privileges if they create a malicious mountpoint path and if the system administrator happens to be using the `fscrypt` bash completion script to complete mountpoint paths. We recommend upgrading to v0.3.3 or above.
For more details, see [CVE-2022-25328](https://www.cve.org/CVERecord?id=CVE-2022-25328). | null | 2022-03-01T21:04:57Z | 2022-03-01T21:04:57Z | MODERATE | null | null | {'github.com/google/fscrypt', 'https://github.com/google/fscrypt/security/advisories/GHSA-w4f8-fxq2-j35v'} | null |
Go | GHSA-742w-89gc-8m9c | containerd v1.2.x can be coerced into leaking credentials during image pull | ## Impact
If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format includes a URL for the location of a specific image layer (otherwise known as a “foreign layer”), the default containerd resolver will follow that URL to attempt to download it. In v1.2.x but not 1.3.0 or later, the default containerd resolver will provide its authentication credentials if the server where the URL is located presents an HTTP 401 status code along with registry-specific HTTP headers.
If an attacker publishes a public image with a manifest that directs one of the layers to be fetched from a web server they control and they trick a user or system into pulling the image, they can obtain the credentials used for pulling that image. In some cases, this may be the user's username and password for the registry. In other cases, this may be the credentials attached to the cloud virtual instance which can grant access to other cloud resources in the account.
The default containerd resolver is used by the cri-containerd plugin (which can be used by Kubernetes), the ctr development tool, and other client programs that have explicitly linked against it.
This vulnerability has been rated by the containerd maintainers as medium, with a CVSS score of 6.1 and a vector string of CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N.
## Patches
This vulnerability has been fixed in containerd 1.2.14. containerd 1.3 and later are not affected.
## Workarounds
If you are using containerd 1.3 or later, you are not affected. If you are using cri-containerd in the 1.2 series or prior, you should ensure you only pull images from trusted sources. Other container runtimes built on top of containerd but not using the default resolver (such as Docker) are not affected.
## Credits
The containerd maintainers would like to thank Brad Geesaman, Josh Larsen, Ian Coldwater, Duffie Cooley, and Rory McCune for responsibly disclosing this issue in accordance with the [containerd security policy](https://github.com/containerd/project/blob/master/SECURITY.md). | {'CVE-2020-15157'} | 2022-02-11T23:27:39Z | 2022-02-11T23:27:39Z | MODERATE | null | {'CWE-522'} | {'https://www.debian.org/security/2021/dsa-4865', 'https://github.com/containerd/containerd/releases/tag/v1.2.14', 'https://github.com/containerd/containerd/security/advisories/GHSA-742w-89gc-8m9c', 'https://usn.ubuntu.com/4589-2/', 'https://github.com/containerd/containerd/commit/1ead8d9deb3b175bf40413b8c47b3d19c2262726', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15157', 'https://github.com/containerd/containerd', 'https://darkbit.io/blog/cve-2020-15157-containerdrip', 'https://usn.ubuntu.com/4589-1/'} | null |
Go | GO-2021-0082 | null | Thirft Servers preallocate memory for the declared size of messages before
checking the actual size of the message. This allows a malicious user to
send messages that declare that they are significantly larger than they
actually are, allowing them to force the server to allocate significant
amounts of memory. This can be used as a denial of service vector.
| {'CVE-2019-11939'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/facebook/fbthrift/commit/483ed864d69f307e9e3b9dadec048216100c0757', 'https://www.facebook.com/security/advisories/cve-2019-11939'} | null |
Go | GO-2020-0026 | null | Due to improper path santization, archives containing relative file
paths can cause files to be written (or overwritten) outside of the
target directory.
| {'CVE-2018-1103'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/openshift/source-to-image/commit/f5cbcbc5cc6f8cc2f479a7302443bea407a700cb', 'https://snyk.io/research/zip-slip-vulnerability'} | null |
Go | GHSA-j77r-2fxf-5jrw | Improper path handling in kustomization files allows path traversal | The kustomize-controller enables the use of Kustomize’s functionality when applying Kubernetes declarative state onto a cluster. A malicious user can use built-in features and a specially crafted `kustomization.yaml` to expose sensitive data from the controller’s pod filesystem. In multi-tenancy deployments this can lead to privilege escalation if the controller's service account has elevated permissions.
Within the affected versions, users with write access to a Flux source are able to use built-in features to expose sensitive data from the controller’s pod filesystem using a malicious `kustomization.yaml` file.
This vulnerability was fixed in kustomize-controller v0.24.0 and included in flux2 v0.29.0 released on 2022-04-20. The changes introduce a new Kustomize file system implementation which ensures that all files being handled are contained within the Kustomization working directory, blocking references to any files that do not meet that requirement.
Automated tooling (e.g. conftest) could be employed as a workaround, as part of a user's CI/CD pipeline to ensure that their `kustomization.yaml` files conform with specific policies, blocking access to sensitive path locations. | {'CVE-2022-24877'} | 2022-05-05T21:49:51Z | 2022-05-04T18:04:07Z | CRITICAL | null | {'CWE-22'} | {'https://github.com/fluxcd/flux2/security/advisories/GHSA-j77r-2fxf-5jrw', 'https://github.com/fluxcd/kustomize-controller/commit/f4528fb25d611da94e491346bea056d5c5c3611f', 'https://github.com/fluxcd/pkg/commit/0ec014baf417fd3879d366a45503a548b9267d2a', 'github.com/fluxcd/kustomize-controller'} | null |
Go | GHSA-mv55-23xp-3wp8 | Access control flaw in Kiali | An incorrect access control flaw was found in the kiali-operator in versions before 1.33.0. This flaw allows an attacker with a basic level of access to the cluster (to deploy a kiali operand) to use this vulnerability and deploy a given image to anywhere in the cluster, potentially gaining access to privileged service account tokens. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. | {'CVE-2021-3495'} | 2021-06-15T19:56:20Z | 2021-06-08T20:09:36Z | HIGH | null | {'CWE-281'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=1947361', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3495', 'https://kiali.io/news/security-bulletins/kiali-security-003/', 'https://github.com/kiali/kiali-operator/pull/278'} | null |
Go | GO-2021-0066 | null | Attempting to read a malformed .dockercfg may cause secrets to be
inappropriately logged.
| {'CVE-2020-8564'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/kubernetes/kubernetes/issues/95622', 'https://github.com/kubernetes/kubernetes/commit/11793434dac97a49bfed0150b56ac63e5dc34634', 'https://github.com/kubernetes/kubernetes/pull/94712'} | null |
Go | GHSA-crp2-qrr5-8pq7 | containerd CRI plugin: Insecure handling of image volumes | ### Impact
A bug was found in containerd where containers launched through containerd’s CRI implementation with a specially-crafted image configuration could gain access to read-only copies of arbitrary files and directories on the host. This may bypass any policy-based enforcement on container setup (including a Kubernetes Pod Security Policy) and expose potentially sensitive information. Kubernetes and crictl can both be configured to use containerd’s CRI implementation.
### Patches
This bug has been fixed in containerd 1.6.1, 1.5.10 and 1.4.13. Users should update to these versions to resolve the issue.
### Workarounds
Ensure that only trusted images are used.
### Credits
The containerd project would like to thank Felix Wilhelm of Google Project Zero for responsibly disclosing this issue in accordance with the [containerd security policy](https://github.com/containerd/project/blob/main/SECURITY.md).
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [containerd](https://github.com/containerd/containerd/issues/new/choose)
* Email us at [security@containerd.io](mailto:security@containerd.io) | {'CVE-2022-23648'} | 2022-03-29T19:11:08Z | 2022-03-02T21:33:17Z | HIGH | null | {'CWE-200'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-23648', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OCCARJ6FU4MWBTXHZNMS7NELPDBIX2VO/', 'https://github.com/containerd/containerd/commit/10f428dac7cec44c864e1b830a4623af27a9fc70', 'http://packetstormsecurity.com/files/166421/containerd-Image-Volume-Insecure-Handling.html', 'https://github.com/containerd/containerd/releases/tag/v1.5.10', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HFTS2EF3S7HNYSNZSEJZIJHPRU7OPUV3/', 'https://www.debian.org/security/2022/dsa-5091', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AUDQUQBZJGBWJPMRVB6QCCCRF7O3O4PA/', 'https://github.com/containerd/containerd/releases/tag/v1.6.1', 'https://github.com/containerd/containerd', 'https://github.com/containerd/containerd/releases/tag/v1.4.13', 'https://github.com/containerd/containerd/security/advisories/GHSA-crp2-qrr5-8pq7'} | null |
Go | GO-2021-0089 | null | Parsing malformed JSON which contain opening brackets, but not closing brackes,
leads to an infinite loop. If operating on untrusted user input this can be
used as a denial of service vector.
| {'CVE-2020-10675'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/buger/jsonparser/pull/192', 'https://github.com/buger/jsonparser/issues/188', 'https://github.com/buger/jsonparser/commit/91ac96899e492584984ded0c8f9a08f10b473717'} | null |
Go | GHSA-5qgp-p5jc-w2rm | Arbitrary Code Execution in Docker | Docker before 1.3.2 allows remote attackers to write to arbitrary files and execute arbitrary code via a (1) symlink or (2) hard link attack in an image archive in a (a) pull or (b) load operation. | {'CVE-2014-6407'} | 2021-05-20T21:03:55Z | 2022-02-15T00:41:12Z | HIGH | null | {'CWE-59'} | {'https://secunia.com/advisories/60241', 'https://lists.opensuse.org/opensuse-security-announce/2014-12/msg00009.html', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-6407', 'https://www.openwall.com/lists/oss-security/2014/11/24/5', 'https://github.com/docker/docker/commit/3ac6394b8082d4700483d52fbfe54914be537d9e', 'https://nvd.nist.gov/vuln/detail/CVE-2014-6407', 'https://docs.docker.com/v1.3/release-notes/', 'https://lists.fedoraproject.org/pipermail/package-announce/2014-December/145154.html', 'https://secunia.com/advisories/60171'} | null |
Go | GHSA-72wf-hwcq-65h9 | Cross-Site Request Forgery in Filebrowser | A Cross-Site Request Forgery (CSRF) vulnerability exists in Filebrowser < 2.18.0 that allows attackers to create a backdoor user with admin privilege and get access to the filesystem via a malicious HTML webpage that is sent to the victim. | {'CVE-2021-46398'} | 2022-02-11T16:20:19Z | 2022-02-05T00:00:31Z | HIGH | null | {'CWE-352'} | {'https://systemweakness.com/critical-csrf-to-rce-in-filebrowser-865a3c34b8e7', 'https://nvd.nist.gov/vuln/detail/CVE-2021-46398', 'https://github.com/filebrowser/filebrowser/commit/74b7cd8e81840537a8206317344f118093153e8d', 'https://febin0x4e4a.blogspot.com/2022/01/critical-csrf-in-filebrowser.html', 'http://packetstormsecurity.com/files/165885/FileBrowser-2.17.2-Code-Execution-Cross-Site-Request-Forgery.html', 'https://febinj.medium.com/critical-csrf-to-rce-in-filebrowser-865a3c34b8e7', 'https://github.com/filebrowser/filebrowser/', 'https://febin0x4e4a.wordpress.com/2022/01/19/critical-csrf-in-filebrowser/'} | null |
Go | GHSA-gq5r-cc4w-g8xf | Denial of Service (DoS) | This affects all versions up to and including 0.6.0 of package github.com/russellhaering/gosaml2. There is a crash on nil-pointer dereference caused by sending malformed XML signatures. | {'CVE-2020-7731'} | 2021-05-20T21:39:22Z | 2021-06-23T17:25:08Z | HIGH | null | {'CWE-476'} | {'https://github.com/russellhaering/gosaml2/issues/59', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7731', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMRUSSELLHAERINGGOSAML2-608302'} | null |
Go | GHSA-25xm-hr59-7c27 | Release v0.5.8 of github.com/ulikunitz/xz fixes readUvarint denial of service | ### Impact
The function readUvarint used to read the xz container format may not terminate a loop provide malicous input.
### Patches
The problem has been fixed in release v0.5.8.
### Workarounds
Limit the size of the compressed file input to a reasonable size for your use case.
### References
The standard library had recently the same issue and got the [CVE-2020-16845](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16845) allocated.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [xz](https://github.com/ulikunitz/xz/issues). | {'CVE-2021-29482'} | 2021-05-24T17:52:22Z | 2021-05-25T18:39:37Z | HIGH | null | {'CWE-835'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29482', 'https://github.com/ulikunitz/xz/commit/69c6093c7b2397b923acf82cb378f55ab2652b9b', 'https://github.com/ulikunitz/xz/security/advisories/GHSA-25xm-hr59-7c27'} | null |
Go | GHSA-25xj-89g5-fm6h | Information Disclosure in HashiCorp Vault | HashiCorp Vault and Vault Enterprise before 1.3.6, and 1.4.2 before 1.4.2, insert Sensitive Information into a Log File. | {'CVE-2020-13223'} | 2022-02-24T13:07:50Z | 2021-05-18T18:21:09Z | HIGH | null | {'CWE-532', 'CWE-200'} | {'https://www.hashicorp.com/blog/category/vault/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-13223', 'https://github.com/hashicorp/vault/commit/e52f34772affb69f3239b2cdf6523cb7cfd67a92', 'https://github.com/hashicorp/vault', 'https://github.com/hashicorp/vault/commit/87f47c216cf1a28f4054b80cff40de8c9e00e36c', 'https://github.com/hashicorp/vault/blob/master/CHANGELOG.md#142-may-21st-2020'} | null |
Go | GHSA-rc7p-gmvh-xfx2 | Attack on Kubernetes via Misconfigured Argo Workflows | ### Impact
Users running using the Argo Server with `--auth-mode=server` (which is the default < v3.0.0) AND have exposed their UI to the Internet may allow remote users to execute arbitrary code on their cluster, e.g. crypto-mining.
### Resolution
* Do not expose your user interface to the Internet.
* Change configuration. `--auth-mode=client`.
For users using an older 2.x version of Argo Server, consider upgrading to Argo Server version 3.x or later.
| null | 2021-08-02T17:18:32Z | 2021-08-02T17:19:52Z | MODERATE | null | null | {'https://www.intezer.com/blog/container-security/new-attacks-on-kubernetes-via-misconfigured-argo-workflows/', 'https://github.com/argoproj/argo-workflows/security/advisories/GHSA-rc7p-gmvh-xfx2'} | null |
Go | GHSA-59hh-656j-3p7v | DoS via maliciously crafted p2p message | ### Impact
A vulnerable node is susceptible to crash when processing a maliciously crafted message from a peer, via the `snap/1` protocol. The crash can be triggered by sending a malicious `snap/1` `GetTrieNodes` package.
### Details
On September 21, 2021, geth-team member Gary Rong (@rjl493456442) found a way to crash the snap request handler .
By using this vulnerability, a peer connected on the `snap/1` protocol could cause a vulnerable node to crash with a `panic`.
In the `trie.TryGetNode` implementation, if the requested path is reached, the associated node will be returned. However the nilness is
not checked there.
```golang
func (t *Trie) tryGetNode(origNode node, path []byte, pos int) (item []byte, newnode node, resolved int, err error) {
// If we reached the requested path, return the current node
if pos >= len(path) {
// Although we most probably have the original node expanded, encoding
// that into consensus form can be nasty (needs to cascade down) and
// time consuming. Instead, just pull the hash up from disk directly.
var hash hashNode
if node, ok := origNode.(hashNode); ok {
hash = node
} else {
hash, _ = origNode.cache()
}
```
More specifically the `origNode` can be nil(e.g. the child of fullnode) and system can panic at line `hash, _ = origNode.cache()`.
When investigating this, @holiman tried to find it via fuzzing, which uncovered a second crasher, also related to the snap `GetTrieNodes` package. If the caller requests a storage trie:
```golang
// Storage slots requested, open the storage trie and retrieve from there
account, err := snap.Account(common.BytesToHash(pathset[0]))
loads++ // always account database reads, even for failures
if account == nil {
break
}
stTrie, err := trie.NewSecure(common.BytesToHash(account.Root), triedb)
```
The code assumes that `snap.Account` returns _either_ a non-nil response unless `error` is also provided. This is however not the case, since `snap.Account` can return `nil, nil`.
### Patches
```diff
--- a/eth/protocols/snap/handler.go
+++ b/eth/protocols/snap/handler.go
@@ -469,7 +469,7 @@ func handleMessage(backend Backend, peer *Peer) error {
// Storage slots requested, open the storage trie and retrieve from there
account, err := snap.Account(common.BytesToHash(pathset[0]))
loads++ // always account database reads, even for failures
- if err != nil {
+ if err != nil || account == nil {
break
}
stTrie, err := trie.NewSecure(common.BytesToHash(account.Root), triedb)
diff --git a/trie/trie.go b/trie/trie.go
index 7ea7efa835..d0f0d4e2bc 100644
--- a/trie/trie.go
+++ b/trie/trie.go
@@ -174,6 +174,10 @@ func (t *Trie) TryGetNode(path []byte) ([]byte, int, error) {
}
func (t *Trie) tryGetNode(origNode node, path []byte, pos int) (item []byte, newnode node, resolved int, err error) {
+ // If non-existent path requested, abort
+ if origNode == nil {
+ return nil, nil, 0, nil
+ }
// If we reached the requested path, return the current node
if pos >= len(path) {
// Although we most probably have the original node expanded, encoding
@@ -193,10 +197,6 @@ func (t *Trie) tryGetNode(origNode node, path []byte, pos int) (item []byte, new
}
// Path still needs to be traversed, descend into children
switch n := (origNode).(type) {
- case nil:
- // Non-existent path requested, abort
- return nil, nil, 0, nil
-
case valueNode:
// Path prematurely ended, abort
return nil, nil, 0, nil
```
The fixes were merged into [#23657](https://github.com/ethereum/go-ethereum/pull/23657), with commit [f1fd963](https://github.com/ethereum/go-ethereum/pull/23657/commits/f1fd963a5a965e643e52fcf805a2a02a323c32b8), and released as part of Geth [v1.10.9](https://github.com/ethereum/go-ethereum/tree/v1.10.9) on Sept 29, 2021.
### Workarounds
Apply the patch above or upgrade to a version which is not vulnerable.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum/)
* Email us at [security@ethereum.org](mailto:security@ethereum.org)
| {'CVE-2021-41173'} | 2021-11-23T19:17:38Z | 2021-10-25T19:42:57Z | MODERATE | null | {'CWE-20'} | {'https://github.com/ethereum/go-ethereum/commit/e40b37718326b8b4873b3b00a0db2e6c6d9ea738', 'https://github.com/ethereum/go-ethereum/security/advisories/GHSA-59hh-656j-3p7v', 'https://github.com/ethereum/go-ethereum/releases/tag/v1.10.9', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41173', 'https://github.com/ethereum/go-ethereum', 'https://github.com/ethereum/go-ethereum/pull/23801'} | null |
Go | GHSA-jqmc-79gx-7g8p | Incorrect Permission Assignment for Critical Resource in CRI-O | An incorrect sysctls validation vulnerability was found in CRI-O 1.18 and earlier. The sysctls from the list of "safe" sysctls specified for the cluster will be applied to the host if an attacker is able to create a pod with a hostIPC and hostNetwork kernel namespace. | {'CVE-2022-0532'} | 2022-02-23T22:00:51Z | 2022-02-11T00:00:54Z | MODERATE | null | {'CWE-732'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=2051730', 'https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/#enabling-unsafe-sysctls', 'https://github.com/cri-o/cri-o/releases/tag/v1.23.1', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0532', 'https://github.com/cri-o/cri-o/pull/5610', 'https://github.com/cri-o/cri-o'} | null |
Go | GO-2021-0070 | null | GetExecUser in the github.com/opencontainers/runc/libcontainer/user package will
improperly interpred numeric UIDs as usernames. If the method is used without
verify usernames are formatted as expected, it may allow a user to gain unexpected
privileges.
| {'CVE-2016-3697'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://security.gentoo.org/glsa/201612-28', 'http://rhn.redhat.com/errata/RHSA-2016-1034.html', 'https://github.com/docker/docker/issues/21436', 'http://rhn.redhat.com/errata/RHSA-2016-2634.html', 'https://github.com/opencontainers/runc/commit/69af385de62ea68e2e608335cffbb0f4aa3db091', 'https://github.com/opencontainers/runc/pull/708'} | null |
Go | GHSA-x6mj-w4jf-jmgw | Server Side Request Forgery (SSRF) in Kubernetes | The Kubernetes kube-controller-manager in versions v1.0-1.14, versions prior to v1.15.12, v1.16.9, v1.17.5, and version v1.18.0 are vulnerable to a Server Side Request Forgery (SSRF) that allows certain authorized users to leak up to 500 bytes of arbitrary information from unprotected endpoints within the master's host network (such as link-local or loopback services). | {'CVE-2020-8555'} | 2021-05-13T20:13:43Z | 2022-02-15T01:57:18Z | LOW | null | {'CWE-918'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-8555', 'https://github.com/kubernetes/kubernetes/pull/89794', 'https://groups.google.com/d/topic/kubernetes-security-announce/kEK27tqqs30/discussion', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3SOCLOPTSYABTE4CLTSPDIFE6ZZZR4LX/', 'https://security.netapp.com/advisory/ntap-20200724-0005/', 'http://www.openwall.com/lists/oss-security/2021/05/04/8', 'https://github.com/kubernetes/kubernetes/issues/91542', 'http://www.openwall.com/lists/oss-security/2020/06/01/4'} | null |
Go | GHSA-m9hp-7r99-94h5 | Critical security issues in XML encoding in github.com/dexidp/dex | ### Impact
The following vulnerabilities have been disclosed, which impact users leveraging the SAML connector:
Signature Validation Bypass (CVE-2020-15216): https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7
`encoding/xml` instabilities:
- [Element namespace prefix instability (CVE-2020-29511)](https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-elements.md)
- [Attribute namespace prefix instability (CVE-2020-29509)](https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-attributes.md)
- [Directive comment instability (CVE-2020-29510)](https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-directives.md)
### Patches
Immediately update to [Dex v2.27.0](https://github.com/dexidp/dex/releases/tag/v2.27.0).
### Workarounds
There are no known workarounds. | {'CVE-2020-26290'} | 2021-05-21T20:49:36Z | 2021-12-20T17:53:53Z | CRITICAL | null | {'CWE-347'} | {'https://github.com/dexidp/dex/commit/324b1c886b407594196113a3dbddebe38eecd4e8', 'https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/', 'https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-attributes.md', 'https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-directives.md', 'https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-elements.md', 'https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7', 'https://github.com/dexidp/dex/security/advisories/GHSA-m9hp-7r99-94h5', 'https://github.com/dexidp/dex/releases/tag/v2.27.0', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26290'} | null |
Go | GHSA-mj9r-wwm8-7q52 | Open Redirect in github.com/AndrewBurian/powermux | ### Impact
Attackers may be able to craft phishing links and other open redirects by exploiting the trailing slash redirection feature. This may lead to users being redirected to untrusted sites after following an attacker crafted link.
### Patches
The issue is resolved in v1.1.1
### Workarounds
There are no existing workarounds.
You may detect attempts to craft urls that exploit this feature by looking for request paths containing pairs of forward slashes in sequence combined with a trailing slash e.g. `https://example.com//foo/`
| {'CVE-2021-32721'} | 2021-06-30T17:43:53Z | 2021-07-01T17:00:32Z | MODERATE | null | {'CWE-601'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-32721', 'https://github.com/AndrewBurian/powermux/commit/5e60a8a0372b35a898796c2697c40e8daabed8e9', 'https://github.com/AndrewBurian/powermux/security/advisories/GHSA-mj9r-wwm8-7q52'} | null |
Go | GHSA-r9cr-hvjj-496v | Path traversal and improper access control allows leaking out-of-bound files from Argo CD repo-server | ### Impact
All unpatched versions of Argo CD starting with v1.3.0 are vulnerable to a path traversal bug, compounded by an improper access control bug, allowing a malicious user with read-only repository access to leak sensitive files from Argo CD's repo-server.
A malicious Argo CD user who has been granted [`get` access for a repository](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#rbac-resources-and-actions) containing a Helm chart can craft an API request to the `/api/v1/repositories/{repo_url}/appdetails` endpoint to leak the contents of out-of-bounds files from the repo-server.
The malicious payload would reference an out-of-bounds file, and the contents of that file would be returned as part of the response. Contents from a non-YAML file may be returned as part of an error message. The attacker would have to know or guess the location of the target file.
Sensitive files which could be leaked include files from other Applications' source repositories (potentially decrypted files, if you are using a decryption plugin) or any secrets which have been mounted as files on the repo-server.
### Patches
A patch for this vulnerability has been released in the following Argo CD versions:
* v2.3.0
* v2.2.6
* v2.1.11
The patches do two things:
1) prevent path traversal
2) limit `/api/v1/repositories/{repo_url}/appdetails` access to users who either A) have been granted Application `create` privileges or B) have been granted Application `get` privileges _and_ are requesting details for a `repo_url` that has already been used for the given Application
### Workarounds
The only certain way to avoid the vulnerability is to upgrade.
To mitigate the problem, you can
* avoid storing secrets in git
* avoid mounting secrets as files on the repo-server
* avoid decrypting secrets into files on the repo-server
* carefully [limit who has `get` access for repositories](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#rbac-resources-and-actions)
### References
* [Security documentation for the repo-server component](https://argo-cd.readthedocs.io/en/stable/operator-manual/security/#git-helm-repositories)
* [Argo CD RBAC configuration documentation](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#)
### For more information
Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions)
Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel #argo-cd
| {'CVE-2022-24730'} | 2022-03-24T00:04:03Z | 2022-03-24T00:04:03Z | HIGH | null | {'CWE-22', 'CWE-284'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-24730', 'https://github.com/argoproj/argo-cd/security/advisories/GHSA-r9cr-hvjj-496v', 'https://github.com/argoproj/argo-cd'} | null |
Go | GHSA-qrrc-ww9x-r43g | Improper Input Validation in Docker Engine | An issue was discovered in Docker Engine before 19.03.11. An attacker in a container, with the CAP_NET_RAW capability, can craft IPv6 router advertisements, and consequently spoof external IPv6 hosts, obtain sensitive information, or cause a denial of service. | {'CVE-2020-13401'} | 2021-05-14T16:27:26Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-13401', 'https://github.com/docker/docker-ce/releases/tag/v19.03.11', 'https://docs.docker.com/engine/release-notes/', 'https://www.debian.org/security/2020/dsa-4716', 'http://www.openwall.com/lists/oss-security/2020/06/01/5', 'https://security.netapp.com/advisory/ntap-20200717-0002/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KJZLKRCOJMOGUIJI2AS27BOZS3RBEF3K/', 'http://lists.opensuse.org/opensuse-security-announce/2020-06/msg00040.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DN4JQAOXBE3XUNK3FD423LHE3K74EMJT/', 'https://security.gentoo.org/glsa/202008-15'} | null |
Go | GHSA-w3jx-wv97-67ph | Cross-site scripting in Dutchcoders transfer.sh | Dutchcoders transfer.sh before 1.2.4 allows XSS via an inline view. | {'CVE-2021-33496'} | 2021-05-28T18:03:43Z | 2021-06-29T21:25:27Z | MODERATE | null | {'CWE-79'} | {'https://github.com/dutchcoders/transfer.sh/releases/tag/v1.2.4', 'https://github.com/dutchcoders/transfer.sh/pull/373', 'https://github.com/dutchcoders/transfer.sh/commit/9df18fdc69de2e71f30d8c1e6bfab2fda2e52eb4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-33496', 'https://vuln.ryotak.me/advisories/43'} | null |
Go | GO-2020-0040 | null | Due to unchecked type assertions, maliciously crafted messages can
cause panics, which may be used as a denial of service vector.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/shiyanhui/dht/issues/57'} | null |
Go | GHSA-jpj5-hg26-6jgc | Cross-site Scripting in Alist | Alist versions 2.0.10 through 2.1.0 were discovered to contain a cross-site scripting (XSS) vulnerability via /i/:data/ipa.plist. This issue was fixed in version 2.1.1. | {'CVE-2022-26533'} | 2022-03-23T15:47:27Z | 2022-03-13T00:00:54Z | MODERATE | null | {'CWE-79'} | {'https://github.com/Xhofe/alist/issues/645', 'https://nvd.nist.gov/vuln/detail/CVE-2022-26533', 'https://github.com/Xhofe/alist', 'https://github.com/Xhofe/alist/commit/6af17e2509a400979420f613fd7f2f9721fdcd6e'} | null |
Go | GHSA-5r5w-h76p-m726 | Use of a Broken or Risky Cryptographic Algorithm in Max Mazurov Maddy | A Broken or Risky Cryptographic Algorithm exists in Max Mazurov Maddy before 0.5.2, which is an unnecessary risk that may result in the exposure of sensitive information. | {'CVE-2021-42583'} | 2022-01-13T18:32:43Z | 2022-01-06T22:20:53Z | HIGH | null | {'CWE-327'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-42583', 'https://github.com/foxcpp/maddy', 'https://github.com/foxcpp/maddy/releases/tag/v0.5.2', 'https://github.com/foxcpp/maddy/blob/df40dce1284cd0fd0a9e8e7894029553d653d0a5/internal/auth/shadow/verify.go'} | null |
Go | GO-2020-0017 | null | If a JWT contains an audience claim with an array of strings, rather
than a single string, and `MapClaims.VerifyAudience` is called with
`req` set to `false`, then audience verification will be bypassed,
allowing an invalid set of audiences to be provided.
| {'CVE-2020-26160'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/dgrijalva/jwt-go/commit/ec0a89a131e3e8567adcb21254a5cd20a70ea4ab', 'https://github.com/dgrijalva/jwt-go/issues/422'} | null |
Go | GHSA-5cgx-vhfp-6cf9 | Directory traversal in Kubernetes Secrets Store CSI Driver | Kubernetes Secrets Store CSI Driver versions v0.0.15 and v0.0.16 allow an attacker who can modify a SecretProviderClassPodStatus/Status resource the ability to write content to the host filesystem and sync file contents to Kubernetes Secrets. This includes paths under var/lib/kubelet/pods that contain other Kubernetes Secrets. | {'CVE-2020-8568'} | 2021-05-12T21:44:15Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-20', 'CWE-22', 'CWE-24'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-8568', 'https://github.com/kubernetes-sigs/secrets-store-csi-driver/pull/371', 'https://github.com/kubernetes-sigs/secrets-store-csi-driver/issues/378', 'https://groups.google.com/g/kubernetes-secrets-store-csi-driver/c/Cb9cvymTzl4'} | null |
Go | GHSA-gwmc-6795-qghj | HashiCorp Nomad Artifact Download Race Condition | HashiCorp Nomad and Nomad Enterprise 0.3.0 through 1.0.17, 1.1.11, and 1.2.5 artifact download functionality has a race condition such that the Nomad client agent could download the wrong artifact into the wrong destination. This issue is fixed in 1.0.18, 1.1.12, and 1.2.6. | {'CVE-2022-24686'} | 2022-03-18T18:21:52Z | 2022-02-15T00:02:46Z | MODERATE | null | {'CWE-362'} | {'https://security.netapp.com/advisory/ntap-20220318-0008/', 'https://github.com/hashicorp/nomad/issues/12036', 'https://github.com/hashicorp/nomad', 'https://discuss.hashicorp.com/t/hcsec-2022-01-nomad-artifact-download-race-condition/35559', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24686', 'https://discuss.hashicorp.com', 'https://github.com/hashicorp/nomad/releases/tag/v1.2.6'} | null |
Go | GHSA-g5v4-5x39-vwhx | Zip slip directory exploit in github.com/deislabs/oras | ### Impact
The directory support (#55) allows the downloaded gzipped tarballs to be automatically extracted to the user-specified directory where the tarball can have symbolic links and hard links.
A well-crafted tarball or tarballs allow malicious artifact providers linking, writing, or overwriting specific files on the host filesystem outside of the user-specified directory unexpectedly with the same permissions as the user who runs `oras pull`.
Precisely, the following users of the affected versions are impacted
- `oras` CLI users who runs `oras pull`.
- Go programs, which invokes `github.com/deislabs/oras/pkg/content.FileStore`.
### Patches
The problem has been patched by the PR linked with this advisory. Users should upgrade their `oras` CLI and packages to `0.9.0`.
### Workarounds
For `oras` CLI users, there is no workarounds other than pulling from a trusted artifact provider.
For `oras` package users, the workaround is to not use `github.com/deislabs/oras/pkg/content.FileStore`, and use other content stores instead, or pull from a trusted artifact provider.
### References
- [Zip Slip](https://github.com/snyk/zip-slip-vulnerability)
### For more information
If you have any questions or comments about this advisory:
* Open an issue on the [GitHub repo](https://github.com/deislabs/oras)
* Email the [list of maintainers](https://github.com/deislabs/oras/blob/main/MAINTAINERS) | {'CVE-2021-21272'} | 2022-02-15T00:32:04Z | 2022-02-15T00:32:04Z | HIGH | null | {'CWE-29', 'CWE-22'} | {'https://pkg.go.dev/github.com/deislabs/oras/pkg/oras', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21272', 'https://github.com/deislabs/oras/security/advisories/GHSA-g5v4-5x39-vwhx', 'https://github.com/deislabs/oras/commit/96cd90423303f1bb42bd043cb4c36085e6e91e8e', 'https://github.com/deislabs/oras/releases/tag/v0.9.0'} | null |
Go | GO-2020-0001 | null | The default [`Formatter`][LoggerConfig.Formatter] for the [`Logger`][] middleware
(included in the [`Default`][] engine) allows attackers to inject arbitrary log
entries by manipulating the request path.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/gin-gonic/gin/commit/a71af9c144f9579f6dbe945341c1df37aaf09c0d', 'https://github.com/gin-gonic/gin/pull/2237'} | null |
Go | GHSA-433w-mm6h-rv9p | Auth bypass in SAML provider | ### Impact
The following vulnerabilities have been disclosed, which impact users leveraging the SAML auth provider:
- [`goxmldsig` - Signature Validation Bypass](https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7)
- [`gosaml2` - Authentication Bypass](https://github.com/russellhaering/gosaml2/security/advisories/GHSA-xhqq-x44f-9fgg)
### Patches
[Patch available](https://github.com/netlify/gotrue/pull/274)
Please upgrade to v1.0.0 or commit hash `a2b4dd6bc4ef7562d1df044098b303f564eefa90`
### Workarounds
No known workarounds.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [gotrue](https://github.com/netlify/gotrue/issues)
* Email us at [security@netlify.com](mailto:security@netlify.com) | null | 2021-05-21T20:47:30Z | 2021-06-23T17:29:06Z | CRITICAL | null | null | {'https://github.com/netlify/gotrue/security/advisories/GHSA-433w-mm6h-rv9p'} | null |
Go | GHSA-2hfj-cxw7-g45p | Unsafe inline XSS in pasting DOM element into chat | ### Impact
Inline scripts are executed when Javascript is parsed via a paste action.
1. Open https://watch.owncast.online/
2. Copy and then paste `<img src=null onerror=alert('hello')>` into the
chat field.
3. An alert should pop up.
### Patches
```
⋮ 13 │ // Content security policy
⋮ 14 │ csp := []string{
⋮ 15 │ "script-src 'self' 'sha256-2HPCfJIJHnY0NrRDPTOdC7AOSJIcQyNxzUuut3TsYRY='",
⋮ 16 │ "worker-src 'self' blob:", // No single quotes around blob:
⋮ 17 │ }
```
Will be patched in 0.0.9 by blocking `unsafe-inline` Content Security Policy and specifying the `script-src`. The `worker-src` is required to be set to `blob` for the video player.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [owncast/owncast](https://github.com/owncast/owncast/issues)
* Email us at [gabek@real-ity.com](mailto:gabek@real-ity.com)
| {'CVE-2021-39183'} | 2022-01-04T18:54:05Z | 2021-12-14T21:48:16Z | HIGH | null | {'CWE-79'} | {'https://github.com/owncast/owncast', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39183', 'https://github.com/owncast/owncast/security/advisories/GHSA-2hfj-cxw7-g45p'} | null |
Go | GHSA-grh6-q6m2-rh72 | Origin Validation Error | Rootless containers run with Podman, receive all traffic with a source IP address of 127.0.0.1 (including from remote hosts). This impacts containerized applications that trust localhost (127.0.01) connections by default and do not require authentication. This issue affects Podman versions from 1.8.0 to 3.0.0. | {'CVE-2021-20199'} | 2021-05-18T21:02:35Z | 2021-05-18T21:07:49Z | MODERATE | null | {'CWE-200', 'CWE-346'} | {'https://github.com/containers/podman/pull/9052', 'https://github.com/containers/podman/pull/9225', 'https://github.com/containers/podman/releases/tag/v3.0.0-rc3', 'https://github.com/containers/podman/issues/5138', 'https://github.com/rootless-containers/rootlesskit/pull/206', 'https://bugzilla.redhat.com/show_bug.cgi?id=1919050', 'https://nvd.nist.gov/vuln/detail/CVE-2021-20199'} | null |
Go | GHSA-9vh5-r4qw-v3vv | Improper Resource Shutdown or Release in HashiCorp Vault | HashiCorp Vault Enterprise 0.11.0 through 1.3.1 fails, in certain circumstances, to revoke dynamic secrets for a mount in a deleted namespace. Fixed in 1.3.2. | {'CVE-2020-7220'} | 2021-07-27T15:15:57Z | 2021-07-28T17:57:46Z | HIGH | null | {'CWE-404'} | {'https://github.com/hashicorp/vault/blob/master/CHANGELOG.md#132-january-22nd-2020', 'https://www.hashicorp.com/blog/category/vault/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7220'} | null |
Go | GO-2020-0021 | null | Due to improper santization of user input, a number of methods are
vulnerable to SQL injection if used with user input that has not
been santized by the caller.
| {'CVE-2014-8681'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/gogs/gogs/commit/83283bca4cb4e0f4ec48a28af680f0d88db3d2c8', 'https://seclists.org/fulldisclosure/2014/Nov/31'} | null |
Go | GHSA-c3g4-w6cv-6v7h | Non-empty default inheritable capabilities for linux container in Buildah | A bug was found in Buildah where containers were created with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2).
This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set.
| {'CVE-2022-27651'} | 2022-04-19T18:02:46Z | 2022-04-01T13:56:42Z | MODERATE | null | {'CWE-276'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7NETC7I6RTMMBRJJQVJOJUPDK4W4PQSJ/', 'https://github.com/containers/buildah/commit/e7e55c988c05dd74005184ceb64f097a0cfe645b', 'https://github.com/containers/buildah/pull/3855', 'https://github.com/containers/buildah', 'https://github.com/containers/buildah/commit/90b3254c7404039c1c786999ac189654228f6e0e', 'https://github.com/containers/buildah/security/advisories/GHSA-c3g4-w6cv-6v7h', 'https://bugzilla.redhat.com/show_bug.cgi?id=2066840', 'https://nvd.nist.gov/vuln/detail/CVE-2022-27651', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2VWH6X6HOFPO6HTESF42HIJZEPXSWVIO/'} | null |
Go | GHSA-chxf-fjcf-7fwp | Possible filesystem space exhaustion by local users | `fscrypt` through v0.3.2 creates a world-writable directory by default when setting up a filesystem, allowing unprivileged users to exhaust filesystem space. We recommend upgrading to `fscrypt` v0.3.3 or above and adjusting the permissions on existing `fscrypt` metadata directories where applicable.
For more details, see [CVE-2022-25326](https://www.cve.org/CVERecord?id=CVE-2022-25326) and https://github.com/google/fscrypt#setting-up-fscrypt-on-a-filesystem.
| null | 2022-03-01T21:04:07Z | 2022-03-01T21:04:07Z | MODERATE | null | null | {'https://github.com/google/fscrypt/security/advisories/GHSA-chxf-fjcf-7fwp', 'https://github.com/google/fscrypt'} | null |
Go | GHSA-ffjp-66mx-3qpj | Privilege escalation in beego | An issue was discovered in file profile.go. The MemProf and GetCPUProfile functions do not correctly check whether the created file exists. As a result attackers can launch attacks symlink attacks locally. Attackers can use this vulnerability to escalate privileges. | {'CVE-2021-27116'} | 2022-04-07T18:31:32Z | 2022-04-06T00:01:30Z | HIGH | null | {'CWE-59'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-27116', 'https://github.com/beego/beego/issues/4484', 'https://github.com/beego/beego'} | null |
Go | GO-2021-0085 | null | AppArmor restrictions may be bypassed due to improper validation of mount
targets, allowing a malicious image to mount volumes over e.g. /proc.
| {'CVE-2019-16884'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/opencontainers/runc/issues/2128', 'https://github.com/opencontainers/runc/commit/cad42f6e0932db0ce08c3a3d9e89e6063ec283e4', 'https://github.com/opencontainers/runc/pull/2130'} | null |
Go | GHSA-9689-rx4v-cqgc | Open Redirect | Pivotal Concourse Release, versions 4.x prior to 4.2.2, login flow allows redirects to untrusted websites. A remote unauthenticated attacker could convince a user to click on a link using the oAuth redirect link with an untrusted website and gain access to that user's access token in Concourse. | {'CVE-2018-15798'} | 2021-05-12T18:15:16Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-601'} | {'https://pivotal.io/security/cve-2018-15798', 'https://github.com/concourse/concourse/blob/release/5.2.x/release-notes/v5.2.8.md', 'https://nvd.nist.gov/vuln/detail/CVE-2018-15798', 'https://github.com/concourse/concourse/pull/5350/commits/38cb4cc025e5ed28764b4adc363a0bbf41f3c7cb'} | null |
Go | GHSA-5mxh-2qfv-4g7j | NUL character in ROA causes OctoRPKI to crash | OctoRPKI crashes when encountering a repository that returns an invalid ROA (just an encoded `NUL` (`\0`) character).
## Patches
## For more information
If you have any questions or comments about this advisory email us at security@cloudflare.com | {'CVE-2021-3910'} | 2022-04-05T19:29:23Z | 2021-11-10T20:15:06Z | HIGH | null | {'CWE-20'} | {'https://github.com/cloudflare/cfrpki', 'https://www.debian.org/security/2022/dsa-5041', 'https://github.com/cloudflare/cfrpki/releases/tag/v1.4.0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3910', 'https://github.com/cloudflare/cfrpki/security/advisories/GHSA-5mxh-2qfv-4g7j'} | null |
Go | GHSA-5gjh-5j4f-cpwv | Unrestricted Upload of File with Dangerous Type in Gogs | ### Impact
The malicious user is able to upload a crafted `config` file into repository's `.git` directory with to gain SSH access to the server. All installations with [repository upload enabled (default)](https://github.com/gogs/gogs/blob/f36eeedbf89328ee70cc3a2e239f6314f9021f58/conf/app.ini#L127-L129) are affected.
### Patches
Repository file uploads are prohibited to its `.git` directory. Users should upgrade to 0.12.6 or the latest 0.13.0+dev.
### Workarounds
[Disable repository files upload](https://github.com/gogs/gogs/blob/f36eeedbf89328ee70cc3a2e239f6314f9021f58/conf/app.ini#L128-L129).
### References
https://huntr.dev/bounties/b4928cfe-4110-462f-a180-6d5673797902/
### For more information
If you have any questions or comments about this advisory, please post on #6833.
| {'CVE-2022-0415'} | 2022-03-28T16:46:41Z | 2022-03-28T16:46:41Z | HIGH | null | {'CWE-434', 'CWE-20'} | {'https://github.com/gogs/gogs/commit/0fef3c9082269e9a4e817274942a5d7c50617284', 'https://huntr.dev/bounties/b4928cfe-4110-462f-a180-6d5673797902', 'https://github.com/gogs/gogs/pull/6838', 'https://github.com/gogs/gogs/issues/6833', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0415', 'https://github.com/gogs/gogs', 'https://github.com/gogs/gogs/security/advisories/GHSA-5gjh-5j4f-cpwv'} | null |
Go | GHSA-62mh-w5cv-p88c | Import token permissions checking not enforced | (This advisory is canonically <https://advisories.nats.io/CVE/CVE-2021-3127.txt>)
## Problem Description
The NATS server provides for Subjects which are namespaced by Account; all Subjects are supposed to be private to an account, with an Export/Import system used to grant cross-account access to some Subjects. Some Exports are public, such that anyone can import the
relevant subjects, and some Exports are private, such that the Import requires a token JWT to prove permission.
The JWT library's validation of the bindings in the Import Token incorrectly warned on mismatches, instead of outright rejecting the token.
As a result, any account can take an Import token used by any other account and re-use it for themselves because the binding to the
importing account is not rejected, and use it to import *any* Subject from the Exporting account, not just the Subject referenced in the Import Token.
The NATS account-server system treats account JWTs as semi-public information, such that an attacker can easily enumerate all account JWTs and retrieve all Import Tokens from those account JWTs.
The CVE identifier should cover the JWT library repair and the nats-server containing the fixed JWT library, and any other application depending upon the fixed JWT library.
## Affected versions
#### JWT library
* all versions prior to 2.0.1
* fixed after nats-io/jwt#149 landed (2021-03-14)
#### NATS Server
* Version 2 prior to 2.2.0
+ 2.0.0 through and including 2.1.9 are vulnerable
* fixed with nats-io/nats-server@423b79440c (2021-03-14)
## Impact
In deployments with untrusted accounts able to update the Account Server with imports, a malicious account can access any Subject from an account which provides Exported Subjects.
Abuse of this facility requires the malicious actor to upload their tampered Account JWT to the Account Server, providing the service operator with a data-store which can be scanned for signs of abuse.
## Workaround
Deny access to clients to update their account JWT in the account server.
## Solution
Upgrade the JWT dependency in any application using it.
Upgrade the NATS server if using NATS Accounts (with private Exports; Account owners can create those at any time though).
Audit all accounts JWTs to scan for exploit attempts; a Python script to audit the accounts can be found at <https://gist.github.com/philpennock/09d49524ad98043ff11d8a40c2bb0d5a>. | null | 2022-02-15T00:42:28Z | 2022-02-15T00:42:28Z | CRITICAL | null | {'CWE-863'} | {'https://github.com/nats-io/jwt', 'https://github.com/nats-io/jwt/security/advisories/GHSA-62mh-w5cv-p88c'} | null |
Go | GHSA-fgv8-vj5c-2ppq | Incorrect Authorization in runc | runc through 1.0.0-rc8, as used in Docker through 19.03.2-ce and other products, allows AppArmor restriction bypass because libcontainer/rootfs_linux.go incorrectly checks mount targets, and thus a malicious Docker image can mount over a /proc directory. | {'CVE-2019-16884'} | 2022-02-22T15:38:08Z | 2022-02-22T15:38:08Z | HIGH | null | {'CWE-863'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-16884', 'https://security.netapp.com/advisory/ntap-20220221-0004/', 'https://access.redhat.com/errata/RHSA-2019:4269', 'https://github.com/opencontainers/runc/issues/2128', 'https://access.redhat.com/errata/RHSA-2019:4074', 'http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00009.html', 'http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00010.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DGK6IV5JGVDXHOXEKJOJWKOVNZLT6MYR/', 'https://usn.ubuntu.com/4297-1/', 'https://github.com/opencontainers/runc/pull/2129', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SPK4JWP32BUIVDJ3YODZSOEVEW6BHQCF/', 'https://security.gentoo.org/glsa/202003-21', 'http://lists.opensuse.org/opensuse-security-announce/2019-10/msg00073.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/62OQ2P7K5YDZ5BRCH2Q6DHUJIHQD3QCD/', 'https://access.redhat.com/errata/RHSA-2019:3940', 'https://github.com/crosbymichael/runc/commit/78dce1cf1ec36bbe7fe6767bdb81f7cbf6d34d70'} | null |
Go | GHSA-qvf8-p83w-v58j | Podman's default inheritable capabilities for linux container not empty | A bug was found in Podman where containers were created with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2).
This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set. | {'CVE-2022-27649'} | 2022-04-19T18:03:15Z | 2022-04-01T20:52:29Z | HIGH | null | {'CWE-276'} | {'https://github.com/containers/podman', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/J5WPM42UR6XIBQNQPNQHM32X7S4LJTRX/', 'https://github.com/containers/podman/releases/tag/v4.0.3', 'https://nvd.nist.gov/vuln/detail/CVE-2022-27649', 'https://github.com/containers/podman/security/advisories/GHSA-qvf8-p83w-v58j', 'https://github.com/containers/podman/commit/aafa80918a245edcbdaceb1191d749570f1872d0', 'https://bugzilla.redhat.com/show_bug.cgi?id=2066568'} | null |
Go | GHSA-hrhx-6h34-j5hc | Skip the router TLS configuration when the host header is an FQDN | ### Impact
People that configure mTLS between Traefik and clients.
For a request, the TLS configuration choice can be different than the router choice, which implies the use of a wrong TLS configuration.
- When sending a request using FQDN handled by a router configured with a dedicated TLS configuration, the TLS configuration falls back to the default configuration that might not correspond to the configured one.
- If the CNAME flattening is enabled, the selected TLS configuration is the SNI one and the routing uses the CNAME value, so this can skip the expected TLS configuration.
### Patches
Traefik v2.6.x: https://github.com/traefik/traefik/releases/tag/v2.6.1
### Workarounds
Add the FDQN to the host rule:
Example:
```yml
whoami:
image: traefik/whoami:v1.7.1
labels:
traefik.http.routers.whoami.rule: Host(`whoami.example.com`, `whoami.example.com.`)
traefik.http.routers.whoami.tls: true
traefik.http.routers.whoami.tls.options: mtls@file
```
There is no workaround if the CNAME flattening is enabled.
### For more information
If you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).
| {'CVE-2022-23632'} | 2022-02-16T22:30:57Z | 2022-02-16T22:30:57Z | HIGH | null | {'CWE-295'} | {'https://github.com/traefik/traefik/security/advisories/GHSA-hrhx-6h34-j5hc', 'https://github.com/traefik/traefik/releases/tag/v2.6.1', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23632', 'https://github.com/traefik/traefik/pull/8764', 'https://github.com/traefik/traefik'} | null |
Go | GHSA-5m8f-chrv-7rw5 | Denial of Service in Go-Ethereum | Go-Ethereum 1.10.9 nodes crash (denial of service) after receiving a serial of messages and cannot be recovered. They will crash with "runtime error: invalid memory address or nil pointer dereference" and arise a SEGV signal. | {'CVE-2021-43668'} | 2021-11-19T13:19:43Z | 2021-11-23T18:04:47Z | MODERATE | null | {'CWE-476'} | {'https://github.com/ethereum/go-ethereum/issues/23866', 'https://github.com/ethereum/go-ethereum', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43668', 'https://github.com/syndtr/goleveldb/issues/373'} | null |
Go | GHSA-pmqp-h87c-mr78 | XML Entity Expansion and Improper Input Validation in Kubernetes API server | Improper input validation in the Kubernetes API server in versions v1.0-1.12 and versions prior to v1.13.12, v1.14.8, v1.15.5, and v1.16.2 allows authorized users to send malicious YAML or JSON payloads, causing the API server to consume excessive CPU or memory, potentially crashing and becoming unavailable. Prior to v1.14.0, default RBAC policy authorized anonymous users to submit requests that could trigger this vulnerability. Clusters upgraded from a version prior to v1.14.0 keep the more permissive policy by default for backwards compatibility. | {'CVE-2019-11253'} | 2021-05-17T21:06:33Z | 2021-05-18T15:38:48Z | HIGH | null | {'CWE-776', 'CWE-20'} | {'https://groups.google.com/forum/#!topic/kubernetes-security-announce/jk8polzSUxs', 'https://security.netapp.com/advisory/ntap-20191031-0006/', 'https://access.redhat.com/errata/RHSA-2019:3811', 'https://gist.github.com/bgeesaman/0e0349e94cd22c48bf14d8a9b7d6b8f2', 'https://nvd.nist.gov/vuln/detail/CVE-2019-11253', 'https://access.redhat.com/errata/RHSA-2019:3239', 'https://github.com/kubernetes/kubernetes/issues/83253', 'https://github.com/kubernetes/kubernetes/pull/83261', 'https://access.redhat.com/errata/RHSA-2019:3905'} | null |
Go | GHSA-74xm-qj29-cq8p | Failed DTLS certificate verification doesn't stop data channel communication | ### Impact
Data channel communication was incorrectly allowed with users who have failed DTLS certificate verification.
This attack requires
* Attacker knows the ICE password.
* Only take place during PeerConnection handshake.
This attack can be detected by monitoring `PeerConnectionState` in all versions of Pion WebRTC.
### Patches
Users should upgrade to v3.0.15.
The exact patch is https://github.com/pion/webrtc/commit/545613dcdeb5dedb01cce94175f40bcbe045df2e
### Workarounds
Users should listen for when `PeerConnectionState` changes to `PeerConnectionStateFailed`. When it enters this state users should not continue using the PeerConnection.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/pion/webrtc
* Email us at [team@pion.ly](mailto:team@pion.ly)
Thank you to https://github.com/Gaukas for discovering this. | {'CVE-2021-28681'} | 2021-05-21T21:29:41Z | 2021-05-25T18:42:42Z | MODERATE | null | {'CWE-863'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-28681', 'https://github.com/pion/webrtc/security/advisories/GHSA-74xm-qj29-cq8p', 'https://github.com/pion/webrtc/issues/1708', 'https://github.com/pion/webrtc/pull/1709'} | null |
Go | GHSA-fxwj-v664-wv5g | Improper Control of a Resource Through its Lifetime in Mattermost | Mattermost 6.4.x and earlier fails to properly invalidate pending email invitations when the action is performed from the system console, which allows accidentally invited users to join the workspace and access information from the public teams and channels. | {'CVE-2022-1385'} | 2022-04-28T19:49:33Z | 2022-04-20T00:00:30Z | MODERATE | null | {'CWE-664', 'CWE-668'} | {'https://github.com/mattermost/mattermost-server', 'https://mattermost.com/security-updates/', 'https://hackerone.com/reports/1486820', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1385'} | null |
Go | GHSA-v4h8-794j-g8mm | Arbitrary File Override in Docker Engine | Docker Engine before 1.6.1 allows local users to set arbitrary Linux Security Modules (LSM) and docker_t policies via an image that allows volumes to override files in /proc. | {'CVE-2015-3631'} | 2021-05-19T22:04:37Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-285'} | {'http://packetstormsecurity.com/files/131835/Docker-Privilege-Escalation-Information-Disclosure.html', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-3631', 'https://github.com/moby/moby/compare/769acfec2928c47a35da5357d854145b1036448d...b6a9dc399be31c531e3753104e10d74760ed75a2', 'https://groups.google.com/forum/#!searchin/docker-user/1.6.1/docker-user/47GZrihtr-4/nwgeOOFLexIJ', 'https://groups.google.com/forum/#%21searchin/docker-user/1.6.1/docker-user/47GZrihtr-4/nwgeOOFLexIJ', 'http://lists.opensuse.org/opensuse-updates/2015-05/msg00023.html', 'https://nvd.nist.gov/vuln/detail/CVE-2015-3631', 'http://seclists.org/fulldisclosure/2015/May/28'} | null |
Go | GO-2020-0037 | null | Due to support of Gzip compression in request bodies, as well
as a lack of limiting response body sizes, a malicious server
can cause a client to consume a significant amount of system
resources, which may be used as a denial of service vector.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/tendermint/tendermint/commit/03085c2da23b179c4a51f59a03cb40aa4e85a613', 'https://github.com/tendermint/tendermint/pull/3430'} | null |
Go | GHSA-m7vp-hqwv-7m5x | Unbounded memory usage on exposed HTTP/2 (non-gRPC) endpoints | ### Impact
The net/http Go package has a reported vulnerability tracked under CVE-2021-44716 which allows attacker controlled HTTP/2 requests to trigger unbounded memory usage in HTTP/2 endpoints. gRPC endpoints are not vulnerable as they rely on their own HTTP/2 implementation instead of the net/http package. HTTP/2 endpoints consuming the net/http package within SPIRE server and agent (or other components in this repository) that are _on by default_ include the following:
- OIDC Discovery Provider
- K8s Workload Registrar in webhook mode
The following endpoints are vulnerable _when enabled_:
- SPIRE server bundle endpoint (i.e. Federation API)
The following endpoints are _NOT_ vulnerable, since HTTP/2 support in go is not enabled on non-TLS protected endpoints:
- SPIRE server/agent metrics endpoint when configured for Prometheus
- SPIRE server/agent health endpoints
- SPIRE server/agent profiling endpoints
### Patches
SPIRE 1.0.3 and 1.1.3 have been released with an upgraded Go toolchain which patches the vulnerability
### Workarounds
The vulnerability can be worked around entirely by including the `http2server=0` value in the `GODEBUG` environment variable (see https://github.com/golang/go/issues/50058). This turns off HTTP/2 support on all non-gRPC endpoints. They will still function with HTTP/1.1.
The risk associated with this vulnerability can be somewhat mitigated by limiting the exposure of the endpoints in question. If necessary, vulnerable components or endpoints that are optionally configured can be disabled temporarily.
### References
- https://github.com/golang/go/issues/50058
- https://go-review.googlesource.com/c/go/+/370574/
- https://nvd.nist.gov/vuln/detail/CVE-2021-44716
| null | 2022-01-11T16:45:39Z | 2022-01-12T22:33:04Z | HIGH | null | null | {'https://github.com/spiffe/spire/security/advisories/GHSA-m7vp-hqwv-7m5x'} | null |
Go | GHSA-r3gq-wxqf-q4gh | Cross-site Scripting in Gitea | Cross Site Scripting (XSS) vulnerability exists in Gitea before 1.5.1 via the repository settings inside the external wiki/issue tracker URL field. | {'CVE-2021-45329'} | 2022-02-14T23:01:49Z | 2022-02-10T00:00:32Z | MODERATE | null | {'CWE-79'} | {'https://github.com/go-gitea/gitea/pull/4710', 'https://blog.gitea.io/2018/09/gitea-1.5.1-is-released/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-45329', 'https://github.com/go-gitea/gitea'} | null |
Go | GHSA-26cm-qrc6-mfgj | Improper Neutralization of Special Elements used in an LDAP Query in stevenweathers/thunderdome-planning-poker | ### Impact
LDAP injection vulnerability, only affects instances with LDAP authentication enabled.
### Patches
Patch for vulnerability released with v1.16.3.
### Workarounds
Disable LDAP feature if in use
### References
[OWASP LDAP Injection Prevention Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/LDAP_Injection_Prevention_Cheat_Sheet.html
)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Thunderdome Github Repository](https://github.com/StevenWeathers/thunderdome-planning-poker)
* Email us at [steven@weathers.me](mailto:steven@weathers.me)
| {'CVE-2021-41232'} | 2021-11-02T18:40:07Z | 2021-11-08T18:16:21Z | HIGH | null | {'CWE-90', 'CWE-74'} | {'https://github.com/StevenWeathers/thunderdome-planning-poker', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41232', 'https://github.com/StevenWeathers/thunderdome-planning-poker/security/advisories/GHSA-26cm-qrc6-mfgj', 'https://github.com/github/securitylab/issues/464#issuecomment-957094994', 'https://github.com/StevenWeathers/thunderdome-planning-poker/commit/f1524d01e8a0f2d6c3db5461c742456c692dd8c1'} | null |
Go | GHSA-q2qr-3c2p-9235 | Denial of Service (DoS) in HashiCorp Consul | HashiCorp Consul and Consul Enterprise could crash when configured with an abnormally-formed service-router entry. Introduced in 1.6.0, fixed in 1.6.6 and 1.7.4. | {'CVE-2020-12758'} | 2021-05-13T14:26:25Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-400'} | {'https://github.com/hashicorp/consul/blob/v1.6.6/CHANGELOG.md', 'https://github.com/hashicorp/consul/pull/7783', 'https://github.com/hashicorp/consul/commit/69b44fb9424cfdc05f1b7243876ab10d236ef1fc', 'https://nvd.nist.gov/vuln/detail/CVE-2020-12758', 'https://github.com/hashicorp/consul/blob/v1.7.4/CHANGELOG.md'} | null |
Go | GHSA-7774-7vr3-cc8j | Authorization Policy Bypass Due to Case Insensitive Host Comparison | ### Impact
According to [RFC 4343](https://datatracker.ietf.org/doc/html/rfc4343), Istio authorization policy should compare the hostname in the HTTP Host header in a case insensitive way, but currently the comparison is case sensitive. The Envoy proxy will route the request hostname in a case-insensitive way which means the authorization policy could be bypassed.
As an example, the user may have an authorization policy that rejects request with hostname "httpbin.foo" for some source IPs, but the attacker can bypass this by sending the request with hostname "Httpbin.Foo".
### Patches
* Istio 1.11.1 and above
* Istio 1.10.4 and above
* Istio 1.9.8 and above
### Workarounds
A Lua filter may be written to normalize Host header before the authorization check. This is similar to the Path normalization presented in the [Security Best Practices](https://istio.io/latest/docs/ops/best-practices/security/#case-normalization) guide.
### References
More details can be found in the [Istio Security Bulletin](https://istio.io/latest/news/security/istio-security-2021-008).
### For more information
If you have any questions or comments about this advisory, please email us at istio-security-vulnerability-reports@googlegroups.com
| {'CVE-2021-39155'} | 2021-12-13T13:09:54Z | 2021-08-30T16:15:56Z | HIGH | null | {'CWE-178'} | {'https://github.com/istio/istio/security/advisories/GHSA-7774-7vr3-cc8j', 'https://datatracker.ietf.org/doc/html/rfc4343', 'https://github.com/istio/istio', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39155'} | null |
Go | GHSA-jm5c-rv3w-w83m | Denial of service in geth | ### Impact
Denial-of-service (crash) during block processing
### Details
Affected versions suffer from a vulnerability which can be exploited through the `MULMOD` operation, by specifying a modulo of `0`: `mulmod(a,b,0)`, causing a `panic` in the underlying library.
The crash was in the `uint256` library, where a buffer [underflowed](https://github.com/holiman/uint256/blob/4ce82e695c10ddad57215bdbeafb68b8c5df2c30/uint256.go#L442).
if `d == 0`, `dLen` remains `0`
and https://github.com/holiman/uint256/blob/4ce82e695c10ddad57215bdbeafb68b8c5df2c30/uint256.go#L451 will try to access index `[-1]`.
The `uint256` library was first merged in this [commit](https://github.com/ethereum/go-ethereum/commit/cf6674539c589f80031f3371a71c6a80addbe454), on 2020-06-08.
Exploiting this vulnerabilty would cause all vulnerable nodes to drop off the network.
The issue was brought to our attention through a [bug report](https://github.com/ethereum/go-ethereum/issues/21367), showing a `panic` occurring on sync from genesis on the Ropsten network.
It was estimated that the least obvious way to fix this would be to merge the fix into `uint256`, make a new release of that library and then update the geth-dependency.
- https://github.com/holiman/uint256/releases/tag/v1.1.1 was made the same day,
- PR to address the issue: https://github.com/holiman/uint256/pull/80
- PR to update geth deps: https://github.com/ethereum/go-ethereum/pull/21368
### Patches
Upgrade to v1.9.18 or higher
### 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-26242'} | 2021-05-21T21:50:44Z | 2021-06-29T21:13:20Z | MODERATE | null | {'CWE-125', 'CWE-400', 'CWE-191'} | {'https://github.com/ethereum/go-ethereum/security/advisories/GHSA-jm5c-rv3w-w83m', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26242', 'https://github.com/ethereum/go-ethereum/commit/7163a6664ee664df81b9028ab3ba13b9d65a7196', 'https://blog.ethereum.org/2020/11/12/geth_security_release/'} | null |
Go | GHSA-34jx-wx69-9x8v | Symlink Attack in kubectl cp | The kubectl cp command allows copying files between containers and the user machine. To copy files from a container, Kubernetes creates a tar inside the container, copies it over the network, and kubectl unpacks it on the user’s machine. If the tar binary in the container is malicious, it could run any code and output unexpected, malicious results. An attacker could use this to write files to any path on the user’s machine when kubectl cp is called, limited only by the system permissions of the local user. The untar function can both create and follow symbolic links. The issue is resolved in kubectl v1.11.9, v1.12.7, v1.13.5, and v1.14.0. | {'CVE-2019-1002101'} | 2021-05-19T21:58:27Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-59'} | {'https://access.redhat.com/errata/RHBA-2019:0636', 'https://access.redhat.com/errata/RHBA-2019:0620', 'https://www.twistlock.com/labs-blog/disclosing-directory-traversal-vulnerability-kubernetes-copy-cve-2019-1002101/', 'https://nvd.nist.gov/vuln/detail/CVE-2019-1002101', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QZB7E3DOZ5WDG46XAIU6K32CXHXPXB2F/', 'http://www.openwall.com/lists/oss-security/2019/06/21/1', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BPV2RE5RMOGUVP5WJMXKQJZUBBLAFZPZ/', 'https://github.com/kubernetes/kubernetes/pull/75037', 'https://access.redhat.com/errata/RHBA-2019:0619', 'http://www.securityfocus.com/bid/107652', 'http://www.openwall.com/lists/oss-security/2019/08/05/5', 'https://github.com/kubernetes/kubernetes/commit/47063891dd782835170f500a83f37cc98c3c1013'} | null |
Go | GHSA-qh54-9vc5-m9fg | MD5 hash support in github.com/foxcpp/maddy | ### Impact
This vulnerability affects maddy 0.5.1, 0.5.0 users using auth.shadow module
and an extremely outdated system that still allows MD5 hashes in
/etc/shadows.
### Patches
Patch is available as part of the 0.5.2 release.
### Workarounds
Ensure MD5 hashes are not present in /etc/shadow.
| null | 2021-10-11T21:16:02Z | 2021-10-12T16:06:30Z | LOW | null | {'CWE-261'} | {'https://github.com/foxcpp/maddy/security/advisories/GHSA-qh54-9vc5-m9fg', 'https://github.com/foxcpp/maddy'} | null |
Go | GO-2021-0103 | null | Due to improper bounds checking, certain mathmatical operations can cause a panic, due to an
out of bounds read. If this package is used to process untrusted user inputs, this may be used
as a vector for a denial of service attack.
| {'CVE-2020-26242'} | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/holiman/uint256/pull/80', 'https://github.com/holiman/uint256/commit/6785da6e3eea403260a5760029e722aa4ff1716d', 'https://github.com/ethereum/go-ethereum/security/advisories/GHSA-jm5c-rv3w-w83m'} | null |
Go | GHSA-rgjg-66cx-5x9m | Authentication Bypass | Grafana before 4.6.4 and 5.x before 5.2.3 allows authentication bypass because an attacker can generate a valid "remember me" cookie knowing only a username of an LDAP or OAuth user. | {'CVE-2018-15727'} | 2021-05-20T21:09:16Z | 2022-02-15T01:57:18Z | CRITICAL | null | {'CWE-287'} | {'https://access.redhat.com/errata/RHSA-2019:0019', 'https://github.com/grafana/grafana/commit/df83bf10a225811927644bdf6265fa80bdea9137', 'https://grafana.com/blog/2018/08/29/grafana-5.2.3-and-4.6.4-released-with-important-security-fix/', 'https://access.redhat.com/errata/RHSA-2018:3829', 'https://www.securityfocus.com/bid/105184', 'https://nvd.nist.gov/vuln/detail/CVE-2018-15727', 'https://github.com/grafana/grafana/commit/7baecf0d0deae0d865e45cf03e082bc0db3f28c3'} | null |
Go | GHSA-6rw3-3whw-jvjj | Git LFS can execute a binary from the current directory on Windows | ### Impact
On Windows, if Git LFS operates on a malicious repository with a `..exe` file as well as a file named `git.exe`, and `git.exe` is not found in `PATH`, the `..exe` program will be executed, permitting the attacker to execute arbitrary code. This does not affect Unix systems.
Similarly, if the malicious repository contains files named `..exe` and `cygpath.exe`, and `cygpath.exe` is not found in `PATH`, the `..exe` program will be executed when certain Git LFS commands are run.
More generally, if the current working directory contains any file with a base name of `.` and a file extension from `PATHEXT` (except `.bat` and `.cmd`), and also contains another file with the same base name as a program Git LFS intends to execute (such as `git`, `cygpath`, or `uname`) and any file extension from `PATHEXT` (including `.bat` and `.cmd`), then, on Windows, when Git LFS attempts to execute the intended program the `..exe`, `..com`, etc., file will be executed instead, but only if the intended program is not found in any directory listed in `PATH`.
The vulnerability occurs because when Git LFS detects that the program it intends to run does not exist in any directory listed in `PATH` then Git LFS passes an empty string as the executable file path to the Go `os/exec` package, which contains a bug such that, on Windows, it prepends the name of the current working directory (i.e., `.`) to the empty string without adding a path separator, and as a result searches in that directory for a file with the base name `.` combined with any file extension from `PATHEXT`, executing the first one it finds.
(The reason `..bat` and `..cmd` files are not executed in the same manner is that, although the Go `os/exec` package tries to execute them just as it does a `..exe` file, the Microsoft Win32 API `CreateProcess()` family of functions have an undocumented feature in that they apparently recognize when a caller is attempting to execute a batch script file and instead run the `cmd.exe` command interpreter, passing the full set of command line arguments as parameters. These are unchanged from the command line arguments set by Git LFS, and as such, the intended program's name is the first, resulting in a command line like `cmd.exe /c git`, which then fails.)
Git LFS has resolved this vulnerability by always reporting an error when a program is not found in any directory listed in `PATH` rather than passing an empty string to the Go `os/exec` package in this case.
The bug in the Go `os/exec` package has been reported to the Go project and is expected to be patched after this security advisory is published.
### Patches
The problem was introduced in v2.12.1 and is patched in v3.1.3 and v3.1.4. Users of affected versions should upgrade to v3.1.4.
### Workarounds
There are no known workarounds at this time.
### References
* https://github.com/git-lfs/git-lfs/security/advisories/GHSA-6rw3-3whw-jvjj
* https://nvd.nist.gov/vuln/detail/CVE-2022-24826
* https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24826
* https://github.com/git-lfs/git-lfs/releases/tag/v3.1.4
* [git-lfs/git-lfs@762ccd4a49](https://github.com/git-lfs/git-lfs/commit/762ccd4a498f5c17723b91d56b9304434ada5540)
### For more information
If you have any questions or comments about this advisory:
* For general questions, start a discussion in the Git LFS [discussion forum](https://github.com/git-lfs/git-lfs/discussions).
* For reports of additional vulnerabilities, please follow the Git LFS [security reporting policy](https://github.com/git-lfs/git-lfs/blob/main/SECURITY.md). | {'CVE-2022-24826'} | 2022-04-22T20:13:21Z | 2022-04-22T20:13:21Z | CRITICAL | null | {'CWE-426'} | {'https://github.com/git-lfs/git-lfs/security/advisories/GHSA-6rw3-3whw-jvjj', 'https://github.com/git-lfs/git-lfs', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24826'} | null |
Go | GHSA-j7px-6hwj-hpjg | Open Redirect in OAuth2 Proxy | ### Impact
As users can provide a redirect address for the proxy to send the authenticated user to at the end of the authentication flow. This is expected to be the original URL that the user was trying to access.
This redirect URL is checked within the proxy and validated before redirecting the user to prevent malicious actors providing redirects to potentially harmful sites.
However, by crafting a redirect URL with HTML encoded whitespace characters (eg. `%0a`, `%0b`,`%09`,`%0d`) the validation could be bypassed and allow a redirect to any URL provided.
### Patches
@rootxharsh and @iamnoooob provided this patch as potential solution:
```
From 4b941f56eda310b5c4dc8080b7635a6bfabccad4 Mon Sep 17 00:00:00 2001
From: Harsh Jaiswal <harsh@pop-os.localdomain>
Date: Fri, 1 May 2020 20:38:31 +0530
Subject: [PATCH] Fixes redirect issue
---
oauthproxy.go | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/oauthproxy.go b/oauthproxy.go
index 1e9bb7c..f8beb4d 100644
--- a/oauthproxy.go
+++ b/oauthproxy.go
@@ -577,8 +577,9 @@ func validOptionalPort(port string) bool {
// IsValidRedirect checks whether the redirect URL is whitelisted
func (p *OAuthProxy) IsValidRedirect(redirect string) bool {
+ matched, _ := regexp.MatchString(`^/\s+/|\\`, redirect)
switch {
- case strings.HasPrefix(redirect, "/") && !strings.HasPrefix(redirect, "//") && !strings.HasPrefix(redirect, "/\\"):
+ case strings.HasPrefix(redirect, "/") && !strings.HasPrefix(redirect, "//") && !matched:
return true
case strings.HasPrefix(redirect, "http://") || strings.HasPrefix(redirect, "https://"):
redirectURL, err := url.Parse(redirect)
--
2.17.1
```
This issue was also reported to us separately by @mik317 several hours later
The fix was implemented in [#xxx]() and released as version 5.1.1 | {'CVE-2020-11053'} | 2021-05-24T21:05:58Z | 2021-12-20T17:59:10Z | HIGH | null | {'CWE-601'} | {'https://github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-j7px-6hwj-hpjg', 'https://github.com/oauth2-proxy/oauth2-proxy/commit/0d5fa211df8ef2449347a56b22c779eb8d894c43', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11053'} | null |
Go | GHSA-jr34-mff8-pc6f | SQL Injection in Cloud Native Computing Foundation Harbor | Cloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 allows SQL Injection via user-groups in the VMware Harbor Container Registry for the Pivotal Platform. | {'CVE-2019-19029'} | 2021-05-04T22:00:21Z | 2021-05-18T18:27:36Z | MODERATE | null | {'CWE-89'} | {'https://github.com/goharbor/harbor/security/advisories/GHSA-qcfv-8v29-469w', 'https://tanzu.vmware.com/security/cve-2019-19029', 'https://nvd.nist.gov/vuln/detail/CVE-2019-19029', 'https://github.com/goharbor/harbor/security/advisories'} | null |
Go | GHSA-h289-x5wc-xcv8 | Improper Validation of Certificate with Host Mismatch in mellium.im/xmpp/websocket | ### Impact
If no TLS configuration is provided by the user, the websocket package constructs its own TLS configuration using recommended defaults. When looking up a WSS endpoint using the DNS TXT record method described in [XEP-0156: Discovering Alternative XMPP Connection Methods](https://xmpp.org/extensions/xep-0156.html) the ServerName field was incorrectly being set to the name of the server returned by the TXT record request, not the name of the initial server we were attempting to connect to. This means that any attacker that can spoof a DNS record (ie. in the absence of DNSSEC, DNS-over-TLS, DNS-over-HTTPS, or similar technologies) could redirect the user to a server of their choosing and as long as it had a valid TLS certificate for itself the connection would succeed, resulting in a MITM situation.
### Patches
All users should upgrade to v0.21.1.
### Workarounds
To work around the issue, manually specify a TLS configuration with the correct hostname.
### References
- https://mellium.im/cve/cve-2022-24968/
- https://nvd.nist.gov/vuln/detail/CVE-2022-24968
### For more information
If you have any questions or comments about this advisory:
* Reach out on XMPP to [sam@samwhited.com](xmpp:sam@samwhited.com?msg)
* Email us at [sam@samwhited.com](mailto:sam@samwhited.com)
| null | 2022-02-16T22:56:21Z | 2022-02-16T22:56:21Z | MODERATE | null | {'CWE-295'} | {'https://github.com/mellium/xmpp/security/advisories/GHSA-h289-x5wc-xcv8'} | null |
Go | GO-2021-0102 | null | Due to improper input validation, a maliciously crafted input can cause a panic, due to incorrect
nonce size. If this package is used to decrypt user supplied messages without checking the size of
supplied nonces, this may be used as a vector for a denial of service attack.
| {'CVE-2019-11289'} | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/cloudfoundry/gorouter/commit/b1b5c44e050f73b399b379ca63a42a2c5780a83f', 'https://www.cloudfoundry.org/blog/cve-2019-11289/', 'https://github.com/advisories/GHSA-5796-p3m6-9qj4'} | null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.