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-8m9g-647g-5pxw | Infinite loop in Yubico yubihsm-connector | An issue was discovered in the /api/connector endpoint handler in Yubico yubihsm-connector before 3.0.1 (in YubiHSM SDK before 2021.04). The handler did not validate the length of the request, which can lead to a state where yubihsm-connector becomes stuck in a loop waiting for the YubiHSM to send it data, preventing any further operations until the yubihsm-connector is restarted. An attacker can send 0, 1, or 2 bytes to trigger this. | {'CVE-2021-28484'} | 2021-05-07T16:04:45Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-835'} | {'https://github.com/Yubico/yubihsm-connector/commit/82bdf202c53460bac9106cc9b4b34a0a16cae0ed', 'https://github.com/Yubico/yubihsm-connector/releases', 'https://nvd.nist.gov/vuln/detail/CVE-2021-28484', 'https://www.yubico.com/support/security-advisories/ysa-2021-02/'} | null |
Go | GHSA-m3fm-h5jp-q79p | Authorization bypass in Openshift | Openshift allows remote attackers to gain privileges by updating a build configuration that was created with an allowed type to a type that is not allowed. | {'CVE-2016-1906'} | 2021-05-19T22:01:34Z | 2021-12-20T16:58:14Z | CRITICAL | null | {'CWE-285'} | {'https://nvd.nist.gov/vuln/detail/CVE-2016-1906', 'https://access.redhat.com/errata/RHSA-2016:0351', 'https://github.com/openshift/origin/commit/d95ec085f03ecf10e8c424a4f0340ddb38891406', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-1906', 'https://github.com/openshift/origin/issues/6556', 'https://access.redhat.com/errata/RHSA-2016:0070', 'https://github.com/openshift/origin/pull/6576'} | null |
Go | GO-2020-0043 | null | Due to improper TLS verification when serving traffic for multiple
SNIs, an attacker may bypass TLS client authentication by indicating
an SNI during the TLS handshake that is different from the name in
the HTTP Host header.
| {'CVE-2018-21246'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/caddyserver/caddy/pull/2099', 'https://bugs.gentoo.org/715214', 'https://github.com/caddyserver/caddy/commit/4d9ee000c8d2cbcdd8284007c1e0f2da7bc3c7c3'} | null |
Go | GHSA-cx3w-xqmc-84g5 | Git LFS can execute a Git binary from the current directory on Windows | ### Impact
On Windows, if Git LFS operates on a malicious repository with a git.bat or git.exe file in the current directory, that program would be executed, permitting the attacker to execute arbitrary code. This does not affect Unix systems.
This is the result of an incomplete fix for CVE-2020-27955.
This issue occurs because on Windows, [Go includes (and prefers) the current directory when the name of a command run does not contain a directory separator](https://github.com/golang/go/issues/38736).
### Patches
This version should be patched in v2.13.2, which will be released in coordination with this security advisory.
### Workarounds
Other than avoiding untrusted repositories or using a different operating system, there is no workaround.
### References
_Are there any links users can visit to find out more?_
### For more information
If you have any questions or comments about this advisory:
- Start a discussion in [the Git LFS discussion page](https://github.com/git-lfs/git-lfs/discussions).
- If you cannot open a discussion, please email the core team using their usernames at `github.com`. | {'CVE-2021-21237'} | 2022-04-20T16:24:41Z | 2022-02-15T00:30:37Z | HIGH | null | {'CWE-94', 'CWE-426'} | {'https://github.com/git-lfs/git-lfs', 'https://github.com/git-lfs/git-lfs/releases/tag/v2.13.2', 'https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27955', 'https://github.com/git-lfs/git-lfs/commit/fc664697ed2c2081ee9633010de0a7f9debea72a', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21237', 'https://github.com/git-lfs/git-lfs/security/advisories/GHSA-cx3w-xqmc-84g5'} | null |
Go | GHSA-4g52-pqcj-phvh | BLS Signature "Malleability" | ### Impact
1. BLS signature validation in lotus uses blst library method VerifyCompressed. This method accepts signatures in 2 forms - "serialized", and "compressed", meaning that BLS signatures can be provided as either of 2 unique byte arrays.
2. Lotus block validation functions perform a uniqueness check on provided blocks. Two blocks are considered distinct if the CIDs of their blockheader do not match. The CID method for blockheader includes the BlockSig of the block.
The result of these issues is that it would be possible to punish miners for valid blocks, as there are two different valid block CIDs available for each block, even though this must be unique.
### Patches
By switching from the go based `blst` bindings over to the bindings in `filecoin-ffi`, the code paths now ensure that all signatures are compressed by size and the way they are deserialized.
This happened in https://github.com/filecoin-project/lotus/pull/5393
### References
- Original POC: https://gist.github.com/wadeAlexC/2490d522e81a796af9efcad1686e6754 | {'CVE-2021-21405'} | 2021-05-20T20:51:00Z | 2021-05-21T16:23:43Z | MODERATE | null | {'CWE-347'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-21405', 'https://github.com/filecoin-project/lotus/security/advisories/GHSA-4g52-pqcj-phvh', 'https://gist.github.com/wadeAlexC/2490d522e81a796af9efcad1686e6754', 'https://github.com/filecoin-project/lotus/pull/5393'} | null |
Go | GHSA-rf3m-mhv7-x39f | Denial of Service in OpenShift Origin | The API server in OpenShift Origin 1.0.5 allows remote attackers to cause a denial of service (master process crash) via crafted JSON data. | {'CVE-2015-5250'} | 2021-05-19T22:21:13Z | 2021-12-20T16:58:22Z | MODERATE | null | {'CWE-20'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=1259867', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-5250', 'https://access.redhat.com/errata/RHSA-2015:1736', 'https://github.com/openshift/origin/issues/4374', 'https://github.com/openshift/origin/commit/dace5075e31b74703e944b6b3ebe8836be8d1b9a', 'https://nvd.nist.gov/vuln/detail/CVE-2015-5250'} | null |
Go | GO-2020-0014 | null | [`html.Parse`] does not properly handle "select" tags, which can lead
to an infinite loop. If parsing user supplied input, this may be used
as a denial of service vector.
| {'CVE-2018-17846'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/golang/go/issues/27842', 'https://github.com/golang/net/commit/d26f9f9a57f3fab6a695bec0d84433c2c50f8bbf', 'https://go-review.googlesource.com/c/137275'} | null |
Go | GHSA-g622-r636-qfqh | SQL Injection in Couchbase Sync Gateway | The Couchbase Sync Gateway 2.1.2 in combination with a Couchbase Server is affected by a previously undisclosed N1QL-injection vulnerability in the REST API. An attacker with access to the public REST API can insert additional N1QL statements through the parameters ?startkey? and ?endkey? of the ?_all_docs? endpoint. | {'CVE-2019-9039'} | 2021-05-17T16:33:43Z | 2022-02-15T01:57:18Z | CRITICAL | null | {'CWE-89'} | {'https://github.com/couchbase/sync_gateway/commit/97adb5b496aa96aa70398018ea96da913ffd8d8c', 'https://docs.couchbase.com/sync-gateway/2.5/release-notes.html', 'https://research.hisolutions.com/2019/06/n1ql-injection-in-couchbase-sync-gateway-cve-2019-9039/', 'https://www.couchbase.com/resources/security#SecurityAlerts', 'https://nvd.nist.gov/vuln/detail/CVE-2019-9039'} | null |
Go | GO-2020-0002 | null | The [`Data`][], [`Context`][], or [`Key`][] finalizers might run during or
before GPGME operations, releasing the C structures as they are still in use,
leading to crashes and potentially code execution through a use-after-free.
| {'CVE-2020-8945'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/proglottis/gpgme/pull/23', 'https://github.com/proglottis/gpgme/commit/92153bcb59bd2f511e502262c46c7bd660e21733'} | null |
Go | GHSA-2c64-vj8g-vwrq | Incorrect handling of credential expiry by NATS Server | (This advisory is canonically https://advisories.nats.io/CVE/CVE-2020-26892.txt )
## Problem Description
NATS nats-server through 2020-10-07 has Incorrect Access Control because of how expired credentials are handled.
The NATS accounts system has expiration timestamps on credentials; the <https://github.com/nats-io/jwt> library had an API which encouraged misuse and an `IsRevoked()` method which misused its own API.
A new `IsClaimRevoked()` method has correct handling and the nats-server has been updated to use this. The old `IsRevoked()` method now always returns true and other client code will have to be updated to avoid calling it.
The CVE identifier should cover any application using the old JWT API, where the nats-server is one of those applications.
## Affected versions
#### JWT library
* all versions prior to 1.1.0
* fixed after nats-io/jwt PR 103 landed (2020-10-06)
#### NATS Server
* Version 2 prior to 2.1.9
+ 2.0.0 through and including 2.1.8 are vulnerable.
* fixed with nats-io/nats-server PRs 1632, 1635, 1645
## Impact
Time-based credential expiry did not work.
## Workaround
Have credentials which only expire after fixes can be deployed.
## Solution
Upgrade the JWT dependency in any application using it.
Upgrade the NATS server if using NATS Accounts. | null | 2021-05-20T22:19:22Z | 2021-05-21T16:11:49Z | HIGH | null | {'CWE-284'} | {'https://github.com/nats-io/nats-server/security/advisories/GHSA-2c64-vj8g-vwrq'} | null |
Go | GHSA-23jv-v6qj-3fhh | Denial of Service (DoS) in HashiCorp Consul | HashiCorp Consul and Consul Enterprise up to 1.6.2 HTTP/RPC services allowed unbounded resource usage, and were susceptible to unauthenticated denial of service. Fixed in 1.6.3. | {'CVE-2020-7219'} | 2021-07-28T18:12:48Z | 2021-05-18T18:19:21Z | HIGH | null | {'CWE-400', 'CWE-770'} | {'https://www.hashicorp.com/blog/category/consul/', 'https://github.com/hashicorp/consul/issues/7159', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7219'} | null |
Go | GHSA-qq97-vm5h-rrhg | OCI Manifest Type Confusion Issue | ### Impact
Systems that rely on digest equivalence for image attestations may be vulnerable to type confusion.
### Patches
Upgrade to at least `v2.8.0-beta.1` if you are running `v2.x` release. If you use the code from the `main` branch, update at least to the commit after [b59a6f827947f9e0e67df0cfb571046de4733586](https://github.com/distribution/distribution/commit/b59a6f827947f9e0e67df0cfb571046de4733586).
### Workarounds
There is no way to work around this issue without patching.
### References
Due to [an oversight in the OCI Image Specification](https://github.com/opencontainers/image-spec/pull/411) that removed the embedded `mediaType` field from manifests, a maliciously crafted OCI Container Image can cause registry clients to parse the same image in two different ways without modifying the image’s digest by modifying the `Content-Type` header returned by a registry. This can invalidate a common pattern of relying on container image digests for equivalence.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [distribution](https://github.com/distribution/distribution)
* Open an issue in [distribution-spec](https://github.com/opencontainers/distribution-spec)
* Email us at [cncf-distribution-security@lists.cncf.io](mailto:cncf-distribution-security@lists.cncf.io)
| null | 2022-02-11T22:31:47Z | 2022-02-08T18:53:56Z | LOW | null | {'CWE-843'} | {'https://github.com/distribution/distribution/commit/b59a6f827947f9e0e67df0cfb571046de4733586', 'https://github.com/distribution/distribution/security/advisories/GHSA-qq97-vm5h-rrhg', 'https://github.com/distribution/distribution/', 'https://github.com/opencontainers/image-spec/pull/411'} | null |
Go | GHSA-4hj2-r2pm-3hc6 | Incorrect Default Permissions in CRI-O | ### Impact
A bug was found in CRI-O where containers were incorrectly started 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)`. Normally, when executable programs have specified permitted file capabilities, otherwise unprivileged users and processes can execute those programs and gain the specified file capabilities up to the bounding set. Due to this bug, containers which included executable programs with inheritable file capabilities allowed otherwise unprivileged users and processes to additionally gain these inheritable file capabilities up to the container's bounding set. Containers which use Linux users and groups to perform privilege separation inside the container are most directly impacted.
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.
### Patches
This bug will been fixed in the following versions of CRI-O:
- v1.24.0
Users should update to the version corresponding to their minor release as soon as possible. Running containers should be stopped, deleted, and recreated for the inheritable capabilities to be reset.
This fix changes CRI-O behavior such that containers are started with a more typical Linux environment. Refer to `capabilities(7)` for a description of how capabilities work. Note that permitted file capabilities continue to allow for privileges to be raised up to the container's bounding set and that processes may add capabilities to their own inheritable set up to the container's bounding set per the rules described in the manual page. In all cases the container's bounding set provides an upper bound on the capabilities that can be assumed and provides for the container security sandbox.
### Workarounds
The entrypoint of a container can be modified to use a utility like `capsh(1)` to drop inheritable capabilities prior to the primary process starting.
### Credits
CRI-O would like to thank [Andrew G. Morgan](https://github.com/AndrewGMorgan) for responsibly disclosing this issue, as well as the Moby (Docker Engine) project for working with the other container engines in coordinating a fix.
### For more information
If you have any questions or comments about this advisory:
* [Open an issue](https://github.com/cri-o/cri-o/issues/new)
* Email us at [cncf-crio-security@lists.cncf.io](cncf-crio-security@lists.cncf.io) if you think you’ve found a security bug
------------------
https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L
4.8/Medium
|Metric |Value |Comments |
|--- |--- |--- |
|Attack Vector (AV) |Local |An attacker requires local control to launch a container with files that have inheritable capabilities. |
|Attack Complexity (AC) |Low |Modifying a file to have inheritable capabilities is not difficult. |
|Privileges Required (PR) |Low |An attacker requires enough privilege to cause a container to be launched with a compromised image. Moby's API is typically bound to a local Unix domain socket and requires calls to be made from a process that is either UID 0 or present in the configured group. |
|User Interaction (UI) |Required |An attacker must cause the compromised image to be run. |
|Scope (S) |Unchanged |The container boundary set by Moby, including the bounding capability set, is not modified. A successful attack gains access to privileges and resources within the boundary, not outside of it. |
|Confidentiality (C) |Low |An attacker may gain access to some confidential information through elevation of CAP_CHOWN, CAP_DAC_OVERRIDE, CAP_FOWNER, CAP_SETFCAP, or CAP_SETPCAP, but the exposed information is limited to that which is already inside the container. |
|Integrity (I) |Low |An attacker may be able to tamper with data inside the container through elevation of CAP_CHOWN, CAP_DAC_OVERRIDE, CAP_FOWNER, CAP_SETFCAP, or CAP_SETPCAP, or spoof packets with CAP_NET_RAW, but the tampered data is limited to that which is already inside the container. |
|Availability (A) |Low |An attacker may be able to affect the availability of an application running inside the container through elevation of CAP_KILL or CAP_NET_RAW, or may be able to affect availability through tampering with file dependencies. |
| {'CVE-2022-27652'} | 2022-04-28T18:10:23Z | 2022-04-22T20:42:46Z | MODERATE | null | {'CWE-276'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=2066839', 'https://github.com/cri-o/cri-o', 'https://nvd.nist.gov/vuln/detail/CVE-2022-27652', 'https://github.com/cri-o/cri-o/security/advisories/GHSA-4hj2-r2pm-3hc6'} | null |
Go | GHSA-jp32-vmm6-3vf5 | Directory Traversal in Kubernetes | Directory traversal vulnerability in Kubernetes, as used in Red Hat OpenShift Enterprise 3.0, allows attackers to write to arbitrary files via a crafted object type name, which is not properly handled before passing it to etcd. | {'CVE-2015-5305'} | 2021-05-20T16:19:56Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2015-5305', 'https://github.com/kubernetes/kubernetes/commit/68f2add9bd5d43b9da1424d87d88f83d120e17d0', 'https://bugzilla.redhat.com/show_bug.cgi?id=1273969', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-5305', 'https://access.redhat.com/errata/RHSA-2015:1945'} | null |
Go | GHSA-59qg-grp7-5r73 | Weave Net clusters susceptible to MitM attacks via IPv6 rogue router advertisements | ### Impact
An attacker able to run a process as root in a container is able to respond to DNS requests from the host and thereby insert themselves as a fake service.
In a cluster with an IPv4 internal network, if IPv6 is not totally disabled on the host (via ipv6.disable=1 on the kernel cmdline), it will be either unconfigured or configured on some interfaces, but it’s pretty likely that ipv6 forwarding is disabled, ie /proc/sys/net/ipv6/conf//forwarding == 0. Also by default, /proc/sys/net/ipv6/conf//accept_ra == 1. The combination of these 2 sysctls means that the host accepts router advertisements and configure the IPv6 stack using them.
By sending “rogue” router advertisements, an attacker can reconfigure the host to redirect part or all of the IPv6 traffic of the host to the attacker controlled container.
Even if there was no IPv6 traffic before, if the DNS returns A (IPv4) and AAAA (IPv6) records, many HTTP libraries will try to connect via IPv6 first then fallback to IPv4, giving an opportunity to the attacker to respond.
If by chance you also have on the host a vulnerability like last year’s RCE in apt (CVE-2019-3462), you can now escalate to the host.
### Patches
Weave Net version 2.6.3 (to be released soon) will disable the accept_ra option on the veth devices that it creates.
### Workarounds
Users should not run containers with CAP_NET_RAW capability. This has been the advice from Weave Net for years.
https://www.weave.works/docs/net/latest/kubernetes/kube-addon/#-securing-the-setup
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the Weave Net repo](https://github.com/weaveworks/weave/issues/new)
* Join the <a href="https://slack.weave.works/" target="_blank">Weave Users Slack</a>. | {'CVE-2020-11091'} | 2021-05-24T21:05:31Z | 2021-05-27T19:00:08Z | MODERATE | null | {'CWE-350'} | {'https://github.com/weaveworks/weave/security/advisories/GHSA-59qg-grp7-5r73', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11091', 'https://github.com/weaveworks/weave/commit/15f21f1899060f7716c70a8555a084e836f39a60'} | null |
Go | GHSA-f6mq-5m25-4r72 | Improper Validation of Specified Type of Input | Specific cstrings input may not be properly validated in the MongoDB Go Driver when marshalling Go objects into BSON. A malicious user could use a Go object with specific string to potentially inject additional fields into marshalled documents. This issue affects all MongoDB GO Drivers up to (and including) 1.5.0. | {'CVE-2021-20329'} | 2021-06-14T19:11:50Z | 2021-06-15T16:08:16Z | MODERATE | null | {'CWE-20', 'CWE-1287'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-20329', 'https://github.com/mongodb/mongo-go-driver/releases/tag/v1.5.1'} | null |
Go | GO-2021-0107 | null | Web Sockets do not execute any AuthenticateMethod methods which may be set, leading to a
nil pointer dereference if the returned UserData pointer is assumed to be non-nil, or
authentication bypass.
| null | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/ecnepsnai/web/commit/5a78f8d5c41ce60dcf9f61aaf47a7a8dc3e0002f', 'https://github.com/advisories/GHSA-5gjg-jgh4-gppm'} | null |
Go | GO-2020-0009 | null | On 32-bit platforms an attacker can manipulate a ciphertext encrypted with AES-CBC
with HMAC such that they can control how large the input buffer is when computing
the HMAC authentication tag. This can can allow a manipulated ciphertext to be
verified as authentic, opening the door for padding oracle attacks.
| {'CVE-2016-9123'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://www.openwall.com/lists/oss-security/2016/11/03/1', 'https://github.com/square/go-jose/commit/789a4c4bd4c118f7564954f441b29c153ccd6a96'} | null |
Go | GHSA-5gjg-jgh4-gppm | Websocket requests did not call AuthenticateMethod | ### Impact
Depending on implementation, a denial-of-service or privilege escalation vulnerability may occur in software that uses the `github.com/ecnepsnai/web` package with Web Sockets that have an AuthenticateMethod.
The `AuthenticateMethod` is not called, and `UserData` will be nil in request methods. Attempts to read the `UserData` may result in a panic.
This issue only affects web sockets where an `AuthenticateMethod` is supplied to the handle options. Users who do not use web sockets, or users who do not require authentication are not at risk.
#### Example
In the example below, one would expect that the `AuthenticateMethod` function would be called for each request to `/example`
```go
handleOptions := web.HandleOptions{
AuthenticateMethod: func(request *http.Request) interface{} {
// Assume there is logic here to check for an active sessions, look at cookies or headers, etc...
var session Session{} // Example
return session
},
}
server.Socket("/example", handle, handleOptions)
```
However, the method is not called, and therefor the `UserData` parameter of the request object in the handle will be nil, when it would have been expected to be the `session` object we returned.
### Patches
Release v1.5.2 fixes this vulnerability. The authenticate method is now called for websocket requests.
All users of the web package should update to v1.5.2 or later.
### Workarounds
You may work around this issue by making the authenticate method a named function, then calling that function at the start of the handle method for the websocket. Reject connections when the return value of the method is nil. | null | 2021-10-05T16:37:09Z | 2021-06-23T17:26:30Z | MODERATE | null | {'CWE-304'} | {'https://github.com/ecnepsnai/web/security/advisories/GHSA-5gjg-jgh4-gppm', 'https://github.com/ecnepsnai/web'} | null |
Go | GO-2021-0054 | null | Due to improper bounds checking, maliciously crafted JSON objects
can cause an out-of-bounds panic. If parsing user input, this may
be used as a denial of service vector.
| {'CVE-2020-36067'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/tidwall/gjson/issues/196', 'https://github.com/tidwall/gjson/commit/bf4efcb3c18d1825b2988603dea5909140a5302b'} | null |
Go | GO-2021-0111 | null | Due to improper input sanitization when marshalling Go objects into BSON, a maliciously constructed
Go structure could allow an attacker to inject additional fields into a MongoDB document. Users are
affected if they use this package to handle untrusted user input.
| {'CVE-2021-20329'} | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/mongodb/mongo-go-driver/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 | GHSA-66vw-v2x9-hw75 | Podman publishes a malicious image to public registries | Podman is a tool for managing OCI containers and pods. A privilege escalation flaw was found in Podman. This flaw allows an attacker to publish a malicious image to a public registry. Once this image is downloaded by a potential victim, the vulnerability is triggered after a user runs the 'podman top' command. This action gives the attacker access to the host filesystem, leading to information disclosure or denial of service. | {'CVE-2022-1227'} | 2022-05-03T06:15:16Z | 2022-04-30T00:00:35Z | HIGH | null | null | {'https://github.com/containers/podman/issues/10941', 'https://bugzilla.redhat.com/show_bug.cgi?id=2070368', 'https://github.com/containers/podman', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1227'} | null |
Go | GHSA-wqwf-x5cj-rg56 | Arbitrary Command Injection | In Kubernetes versions 1.9.0-1.9.9, 1.10.0-1.10.5, and 1.11.0-1.11.1, user input was handled insecurely while setting up volume mounts on Windows nodes, which could lead to command line argument injection. | {'CVE-2018-1002101'} | 2021-05-12T18:22:09Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-78'} | {'https://github.com/kubernetes/kubernetes/pull/65751', 'https://nvd.nist.gov/vuln/detail/CVE-2018-1002101', 'https://security.netapp.com/advisory/ntap-20190416-0008/', 'http://www.securityfocus.com/bid/106238', 'https://github.com/kubernetes/kubernetes/issues/65750', 'https://github.com/kubernetes/kubernetes/commit/d65039c56ce4de5f2efdc38aa1284eeb95f89169'} | null |
Go | GHSA-6w87-g839-9wv7 | Helm OCI credentials leaked into Argo CD logs | ### Impact
When Argo CD was connected to a Helm OCI repository with authentication enabled, the credentials used for accessing the remote repository were logged.
Anyone with access to the pod logs - either via access with appropriate permissions to the Kubernetes control plane or a third party log management system where the logs from Argo CD were aggregated - could have potentially obtained the credentials to the Helm OCI repository.
If you are using Helm OCI repositories with Argo CD, it is strongly recommended to upgrade Argo CD to the latest patch version and to change the credentials used to access the repositories.
### Patches
A patch for this vulnerability is available with the v1.8.7 and v1.7.14 releases of Argo CD.
### Workarounds
No workaround available
### References
N/A
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions)
* Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel `#argo-cd`
### Credits
This vulnerability was found and reported by a third-party who wishes to stay anonymous. We want to thank this third-party for disclosing this vulnerability to us in a responsible manner. | null | 2021-10-05T16:35:57Z | 2021-05-21T14:31:28Z | MODERATE | null | {'CWE-532'} | {'https://github.com/argoproj/argo-cd/security/advisories/GHSA-6w87-g839-9wv7', 'https://github.com/argoproj/argo-cd'} | null |
Go | GHSA-x5f3-qmwj-4f84 | Authentication bypass by capture-replay in github.com/cosmos/ethermint | Cosmos Network Ethermint <= v0.4.0 is affected by a cross-chain transaction replay vulnerability in the EVM module. Since ethermint uses the same chainIDEpoch and signature schemes with ethereum for compatibility, a verified signature in ethereum is still valid in ethermint with the same msg content and chainIDEpoch, which enables "cross-chain transaction replay" attack. | {'CVE-2021-25835'} | 2021-05-12T21:11:09Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-294', 'CWE-295'} | {'https://github.com/cosmos/ethermint/pull/692', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25835', 'https://github.com/cosmos/ethermint/releases/tag/v0.4.1', 'https://github.com/cosmos/ethermint/issues/687'} | null |
Go | GHSA-9hx4-qm7h-x84j | Cross-site Scripting in Gogs | Cross-site scripting (XSS) vulnerability in models/issue.go in Gogs (aka Go Git Service) 0.3.1-9 through 0.5.x before 0.5.8 allows remote attackers to inject arbitrary web script or HTML via the text parameter to api/v1/markdown. | {'CVE-2014-8683'} | 2021-05-20T16:31:56Z | 2021-06-29T18:32:53Z | MODERATE | null | {'CWE-79'} | {'https://github.com/gogits/gogs/commit/3abc41cccab2486012b46305827433ad6f5deade', 'https://github.com/gogits/gogs/releases/tag/v0.5.8', 'https://nvd.nist.gov/vuln/detail/CVE-2014-8683', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/98693', 'https://gogs.io/docs/intro/change_log.html', 'https://seclists.org/fulldisclosure/2014/Nov/31', 'https://www.securityfocus.com/archive/1/533996/100/0/threaded', 'https://seclists.org/fulldisclosure/2014/Nov/34', 'https://packetstormsecurity.com/files/129118/Gogs-Markdown-Renderer-Cross-Site-Scripting.html'} | null |
Go | GO-2020-0048 | null | [`LoadURL`] does not check the Content-Type of loaded resources,
which can cause a panic due to nil pointer deference if the loaded
resource is not XML. If user supplied URLs are loaded, this may be
used as a denial of service vector.
| {'CVE-2020-25614'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/antchfx/xmlquery/commit/5648b2f39e8d5d3fc903c45a4f1274829df71821', 'https://github.com/antchfx/xmlquery/issues/39'} | null |
Go | GO-2021-0097 | null | Due to improper bounds checking a number of methods can trigger a panic due to attempted
out-of-bounds reads. If the package is used to parse user supplied input this may be
used as a vector for a denial of service attack.
| {'CVE-2020-29242'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/dhowden/tag/commit/6b18201aa5c5535511802ddfb4e4117686b4866d', 'https://github.com/dhowden/tag/commit/d52dcb253c63a153632bfee5f269dd411dcd8e96', 'https://github.com/dhowden/tag/commit/4b595ed4fac79f467594aa92f8953f90f817116e', 'https://github.com/dhowden/tag/commit/a92213460e4838490ce3066ef11dc823cdc1740e'} | null |
Go | GHSA-2rmp-fw5r-j5qv | Improper Authentication in InfluxDB | InfluxDB before 1.7.6 has an authentication bypass vulnerability in the authenticate function in services/httpd/handler.go because a JWT token may have an empty SharedSecret (aka shared secret). | {'CVE-2019-20933'} | 2021-05-12T21:55:56Z | 2021-05-18T18:22:05Z | CRITICAL | null | {'CWE-287'} | {'https://lists.debian.org/debian-lts-announce/2020/12/msg00030.html', 'https://www.debian.org/security/2021/dsa-4823', 'https://github.com/ticarpi/jwt_tool/blob/a6ca3e0524a204b5add070bc6874cb4e7e5a9864/jwt_tool.py#L1368', 'https://github.com/influxdata/influxdb/issues/12927', 'https://github.com/influxdata/influxdb/commit/761b557315ff9c1642cf3b0e5797cd3d983a24c0', 'https://github.com/influxdata/influxdb/compare/v1.7.5...v1.7.6', 'https://nvd.nist.gov/vuln/detail/CVE-2019-20933'} | null |
Go | GHSA-m45g-f45x-vv22 | Improper input validation in CNCF Cortex | The Alertmanager in CNCF Cortex before 1.8.1 has a local file disclosure vulnerability when -experimental.alertmanager.enable-api is used. The HTTP basic auth password_file can be used as an attack vector to send any file content via a webhook. The alertmanager templates can be used as an attack vector to send any file content because the alertmanager can load any text file specified in the templates list. | {'CVE-2021-31232'} | 2021-05-20T21:19:40Z | 2021-06-23T17:20:38Z | MODERATE | null | {'CWE-20'} | {'https://github.com/cortexproject/cortex', 'https://lists.cncf.io/g/cortex-users/message/50', 'https://nvd.nist.gov/vuln/detail/CVE-2021-31232', 'https://community.grafana.com/c/security-announcements', 'https://github.com/cortexproject/cortex/pull/4129/files'} | null |
Go | GO-2021-0078 | null | The HTML parser does not properly handle "in frameset" insertion mode, and can be made
to panic when operating on malformed HTML that contains <template> tags. If operating
on user input, this may be a vector for a denial of service attack.
| {'CVE-2018-17075'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/golang/net/commit/aaf60122140d3fcf75376d319f0554393160eb50', 'https://bugs.chromium.org/p/chromium/issues/detail?id=829668', 'https://go-review.googlesource.com/123776', 'https://github.com/golang/go/issues/27016', 'https://go-review.googlesource.com/c/net/+/94838/9/html/parse.go#1906'} | null |
Go | GHSA-qvp4-rpmr-xwrr | Possible bypass of token claim validation when OAuth2 Introspection caching is enabled | ### Impact
When you make a request to an endpoint that requires the scope `foo` using an access token granted with that `foo` scope, introspection will be valid and that token will be cached. The problem comes when a second requests to an endpoint that requires the scope `bar` is made before the cache has expired. Whether the token is granted or not to the `bar` scope, introspection will be valid.
### Patches
A patch will be released with `v0.38.12-beta.1`.
### Workarounds
Per default, caching is disabled for the `oauth2_introspection` authenticator. When caching is disabled, this vulnerability does not exist.
### Trace
The cache is checked in [`func (a *AuthenticatorOAuth2Introspection) Authenticate(...)`](https://github.com/ory/oathkeeper/blob/6a31df1c3779425e05db1c2a381166b087cb29a4/pipeline/authn/authenticator_oauth2_introspection.go#L152). From [`tokenFromCache()`](https://github.com/ory/oathkeeper/blob/6a31df1c3779425e05db1c2a381166b087cb29a4/pipeline/authn/authenticator_oauth2_introspection.go#L97) it seems that it only validates the token expiration date, but ignores whether the token has or not the proper scopes.
### Post-Mortem
The vulnerability was introduced in PR #424. During review, we failed to require appropriate test coverage by the submitter which is the primary reason that the vulnerability passed the review process.
To avoid this from happening again we enabled codecov with a strict policy on the Ory Oathkeeper repository: Without an increase in code coverage the PR can not be merged.
To address this issue and any regressions we have added a test suite ensuring that the cache behaviour is correct in the different scenarios:
- Scope strategy is `none`, cache is enabled, and `requested_scope` is not empty -> cache will not be used;
- Scope strategy is `none`, cache is enabled, and `requested_scope` is empty -> cache will be used;
- Scope strategy is not `none`, cache is enabled, and `requested_scope` is not empty -> cache will be used;
as well as validating if `iss`, `aud`, `exp`, `token_use`, and scope are validated.
Additionally, we added [CodeQL scanning](https://github.com/ory/oathkeeper/commit/64ac7562669287d391cd72dfd43c5d71ff9f89a1) to the CI. | null | 2021-06-22T20:50:44Z | 2021-06-23T18:00:20Z | HIGH | null | {'CWE-863'} | {'https://github.com/ory/oathkeeper/security/advisories/GHSA-qvp4-rpmr-xwrr'} | null |
Go | GO-2020-0033 | null | Due to improper santization of user input, HTTPEngine.Handle allows
for directory traversal, allowing an attacker to read files outside of
the target directory that the server has permission to read.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/go-aah/aah/issues/266', 'https://github.com/go-aah/aah/commit/881dc9f71d1f7a4e8a9a39df9c5c081d3a2da1ec', 'https://github.com/go-aah/aah/pull/267'} | null |
Go | GHSA-qv95-g3gm-x542 | Privilege Escalation in Hashicorp Vault | HashiCorp Vault and Vault Enterprise through 1.7.4 and 1.8.3 allowed a user with write permission to an entity alias ID sharing a mount accessor with another user to acquire this other user’s policies by merging their identities. Fixed in Vault and Vault Enterprise 1.7.5 and 1.8.4. | {'CVE-2021-41802'} | 2021-10-20T17:39:34Z | 2021-10-12T16:39:01Z | MODERATE | null | {'CWE-732', 'CWE-269'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-41802', 'https://github.com/hashicorp/vault', 'https://discuss.hashicorp.com/t/hcsec-2021-27-vault-merging-multiple-entity-aliases-for-the-same-mount-may-allow-privilege-escalation/'} | null |
Go | GHSA-2p6r-37p9-89p2 | Authz Module Non-Determinism | ### Impact
Consensus failure for 0.43.x and 0.44.{0,1} users.
Funds and balances are safe.
### Patches
0.44.2
### Workarounds
Manually patch the code.
---
Full details posted in https://forum.cosmos.network/t/cosmos-sdk-vulnerability-retrospective-security-advisory-jackfruit-october-12-2021/5349. | {'CVE-2021-41135'} | 2021-10-21T14:32:55Z | 2021-10-21T17:46:57Z | MODERATE | null | {'CWE-754'} | {'https://github.com/cosmos/cosmos-sdk/releases/tag/v0.44.2', 'https://github.com/cosmos/cosmos-sdk/commit/68ab790a761e80d3674f821794cf18ccbfed45ee', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41135', 'https://github.com/cosmos/cosmos-sdk', 'https://forum.cosmos.network/t/cosmos-sdk-vulnerability-retrospective-security-advisory-jackfruit-october-12-2021/5349', 'https://github.com/cosmos/cosmos-sdk/security/advisories/GHSA-2p6r-37p9-89p2'} | null |
Go | GHSA-64rh-r86q-75ff | Hard coded cryptographic key in Kiali | A hard-coded cryptographic key vulnerability in the default configuration file was found in Kiali, all versions prior to 1.15.1. A remote attacker could abuse this flaw by creating their own JWT signed tokens and bypass Kiali authentication mechanisms, possibly gaining privileges to view and alter the Istio configuration. | {'CVE-2020-1764'} | 2021-05-06T21:51:32Z | 2021-05-18T18:28:59Z | HIGH | null | {'CWE-321', 'CWE-798'} | {'https://kiali.io/news/security-bulletins/kiali-security-001/', 'https://github.com/kiali/kiali/commit/ce48af57113c805a25179aaab1a0fac2fb93653f', 'https://bugzilla.redhat.com/show_bug.cgi?id=1810383', 'https://github.com/jpts/cve-2020-1764-poc', 'https://nvd.nist.gov/vuln/detail/CVE-2020-1764', 'https://github.com/kiali/kiali/commit/93f5cd0b6698e8fe8772afb8f35816f6c086aef1', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1764', 'https://github.com/kiali/kiali/commit/ac7bd6c7ddb2e01356e21d360dd1c718a90706ad', 'https://github.com/kiali/kiali/commit/faed1f5f90efae3df9fd6fb793f00ccc242b3a96'} | null |
Go | GHSA-9h4h-8w5p-f28w | Denial of Service in geth | cmd/evm/runner.go in Go Ethereum (aka geth) allows attackers to cause a denial of service (SEGV) via crafted bytecode. | {'CVE-2018-19184'} | 2021-05-20T18:58:40Z | 2021-06-29T21:23:15Z | HIGH | null | {'CWE-476'} | {'https://github.com/ethereum/go-ethereum/commit/83e2761c3a13524bd5d6597ac08994488cf872ef', 'https://github.com/ethereum/go-ethereum/commit/fb9f7261ec51e38eedb454594fc19f00de1a6834', 'https://github.com/ethereum/go-ethereum/issues/18069', 'https://nvd.nist.gov/vuln/detail/CVE-2018-19184'} | null |
Go | GHSA-h563-xh25-x54q | Workflow re-write vulnerability using input parameter | ### Impact
* Allow end-users to set input parameters, but otherwise expect workflows to be secure.
### Patches
Not yet.
### Workarounds
* Set `EXPRESSION_TEMPLATES=false` for the workflow controller
### References
* https://github.com/argoproj/argo-workflows/issues/6441
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [example link to repo](http://example.com)
* Email us at [example email address](mailto:example@example.com)
| {'CVE-2021-37914'} | 2021-08-30T23:23:11Z | 2021-08-09T20:37:50Z | MODERATE | null | {'CWE-20'} | {'github.com/argoproj/argo-workflows/v3', 'https://github.com/argoproj/argo-workflows/commit/2a2ecc916925642fd8cb1efd026588e6828f82e1', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37914', 'https://github.com/argoproj/argo-workflows/security/advisories/GHSA-h563-xh25-x54q', 'https://github.com/argoproj/argo-workflows/pull/6442', 'https://github.com/argoproj/argo-workflows/pull/6285', 'https://github.com/argoproj/argo-workflows/issues/6441'} | null |
Go | GHSA-6hv3-7c34-4hx8 | Information Exposure Through Environmental Variables | In Nomad before version 0.9.5, when rendering a task template, all environment variables were available to the rendering task. As a fix, only task environment variables are used. | {'CVE-2019-14802'} | 2021-05-12T17:59:46Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-526'} | {'https://github.com/hashicorp/nomad/releases/tag/v0.9.5', 'https://github.com/hashicorp/nomad/pull/6055', 'https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14802'} | null |
Go | GHSA-xg2h-wx96-xgxr | RandomAlphaNumeric and CryptoRandomAlphaNumeric are not as random as they should be | ### Impact
A security-sensitive bug was discovered by Open Source Developer *Erik Sundell of Sundell Open Source Consulting AB*.
The functions `RandomAlphaNumeric(int)` and `CryptoRandomAlphaNumeric(int)` are not as random as they should be. Small values of `int` in the functions above will return a smaller subset of results than they should. For example, `RandomAlphaNumeric(1)` will always return a digit in the 0-9 range, while `RandomAlphaNumeric(4)` will return around ~7 million of the ~13M possible permutations.
This is considered a security release because programs that rely upon random generators for passwords are at an increased risk of brute force-style password guessing. There is also a higher probability of collision.
The problem was the result of a mistaken regular expression that only accepted random strings if they contained a digit from `[0-9]`. That restriction has been removed.
### Patches
This issue has been corrected in v1.0.2.
### Workarounds
If you cannot upgrade to v1.0.2, you can work around the issue by calling `RandomAlphaNumericCustom(N, true, true)`|`CryptoRandomAlphaNumericCustom(N, true, true)` instead. (Where `N` is the desired length, and `true` is the literal boolean `true`.) | null | 2021-05-21T14:36:56Z | 2021-05-21T16:26:06Z | LOW | null | null | {'https://github.com/Masterminds/goutils/security/advisories/GHSA-xg2h-wx96-xgxr'} | null |
Go | GHSA-36xw-fx78-c5r4 | containerd-shim API Exposed to Host Network Containers | ## Impact
Access controls for the shim’s API socket verified that the connecting process had an effective UID of 0, but did not otherwise restrict access to the abstract Unix domain socket. This would allow malicious containers running in the same network namespace as the shim, with an effective UID of 0 but otherwise reduced privileges, to cause new processes to be run with elevated privileges.
## Patches
This vulnerability has been fixed in containerd 1.3.9 and 1.4.3. Users should update to these versions as soon as they are released. It should be noted that containers started with an old version of containerd-shim should be stopped and restarted, as running containers will continue to be vulnerable even after an upgrade.
## Workarounds
If you are not providing the ability for untrusted users to start containers in the same network namespace as the shim (typically the "host" network namespace, for example with `docker run --net=host` or `hostNetwork: true` in a Kubernetes pod) and run with an effective UID of 0, you are not vulnerable to this issue.
If you are running containers with a vulnerable configuration, you can deny access to all abstract sockets with AppArmor by adding a line similar to `deny unix addr=@**,` to your policy.
It is best practice to run containers with a reduced set of privileges, with a non-zero UID, and with isolated namespaces. The containerd maintainers strongly advise against sharing namespaces with the host. Reducing the set of isolation mechanisms used for a container necessarily increases that container's privilege, regardless of what container runtime is used for running that container.
## Credits
The containerd maintainers would like to thank Jeff Dileo of NCC Group for responsibly disclosing this issue in accordance with the [containerd security policy](https://github.com/containerd/project/blob/master/SECURITY.md) and for reviewing the patch.
## For more information
If you have any questions or comments about this advisory:
* [Open an issue](https://github.com/containerd/containerd/issues/new/choose)
* Email us at security@containerd.io if you think you’ve found a security bug. | {'CVE-2020-15257'} | 2021-05-27T19:46:55Z | 2021-05-24T17:00:22Z | MODERATE | null | {'CWE-669'} | {'https://www.debian.org/security/2021/dsa-4865', 'https://github.com/containerd/containerd/releases/tag/v1.4.3', 'https://security.gentoo.org/glsa/202105-33', 'https://github.com/containerd/containerd/security/advisories/GHSA-36xw-fx78-c5r4', 'https://github.com/containerd/containerd/commit/4a4bb851f5da563ff6e68a83dc837c7699c469ad', 'https://research.nccgroup.com/2020/12/10/abstract-shimmer-cve-2020-15257-host-networking-is-root-equivalent-again/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LNKXLOLZWO5FMAPX63ZL7JNKTNNT5NQD/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15257'} | null |
Go | GHSA-68wm-pfjf-wqp6 | Authentication bypassed with malformed request URI on nginx | ### Impact
This affects uses who are using nginx ngx_http_auth_request_module with Authelia, it allows a malicious individual who crafts a malformed HTTP request to bypass the authentication mechanism. It additionally could theoretically affect other proxy servers, but all of the ones we officially support except nginx do not allow malformed URI paths.
### Patches
The problem is rectified entirely in v4.29.3. As this patch is relatively straightforward we can back port this to any version upon request. Alternatively we are supplying a git patch to 4.25.1 which should be relatively straightforward to apply to any version, the git patches for specific versions can be found below.
<details><summary>Patch for 4.25.1:</summary><p>
```patch
From ca22f3d2c44ca7bef043ffbeeb06d6659c1d550f Mon Sep 17 00:00:00 2001
From: James Elliott <james-d-elliott@users.noreply.github.com>
Date: Wed, 19 May 2021 12:10:13 +1000
Subject: [PATCH] fix(handlers): verify returns 200 on malformed request
This is a git patch for commit at tag v4.25.1 to address a potential method to bypass authentication in proxies that forward malformed information to Authelia in the forward auth process. Instead of returning a 200 this ensures that Authelia returns a 401 when this occurs.
---
internal/handlers/handler_verify.go | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/internal/handlers/handler_verify.go b/internal/handlers/handler_verify.go
index 65c064ce..4dd9702d 100644
--- a/internal/handlers/handler_verify.go
+++ b/internal/handlers/handler_verify.go
@@ -396,7 +396,9 @@ func VerifyGet(cfg schema.AuthenticationBackendConfiguration) middlewares.Reques
targetURL, err := getOriginalURL(ctx)
if err != nil {
- ctx.Error(fmt.Errorf("Unable to parse target URL: %s", err), operationFailedMessage)
+ ctx.Logger.Error(fmt.Errorf("Unable to parse target URL: %s", err))
+ ctx.ReplyUnauthorized()
+
return
}
--
2.31.1
```
</p></details>
### Workarounds
The most relevant workaround is upgrading. **If you need assistance with an upgrade please contact us on [Matrix](https://riot.im/app/#/room/#authelia:matrix.org) or [Discord](https://discord.authelia.com).** Please just let us know you're needing help upgrading to above 4.29.2.
You can add an block which fails requests that contains a malformed URI in the internal location block. We have crafted one that should work in most instances, it basically checks no chars that are required to be URL-encoded for either the path or the query are in the URI. Basically this regex checks that the characters between the square braces are the only characters in the $request_uri header, if they exist, it returns a HTTP 401 status code. The characters in the regex match are tested to not cause a parsing error that would result in a failure, however they are not exhaustive since query strings seem to not always conform to the RFC.
<details><summary>authelia.conf:</summary><p>
```nginx
location /authelia {
internal;
# **IMPORTANT**
# This block rejects requests with a 401 which contain characters that are unable to be parsed.
# It is necessary for security prior to v4.29.3 due to the fact we returned an invalid code in the event of a parser error.
# You may comment this section if you're using Authelia v4.29.3 or above. We strongly recommend upgrading.
# RFC3986: http://tools.ietf.org/html/rfc3986
# Commentary on RFC regarding Query Strings: https://www.456bereastreet.com/archive/201008/what_characters_are_allowed_unencoded_in_query_strings/
if ($request_uri ~ [^a-zA-Z0-9_+-=\!@$%&*?~.:#'\;\(\)\[\]]) {
return 401;
}
# Include the remainder of the block here.
}
````
</p></details>
### Discovery
This issue was discovered by:
Siemens Energy
Cybersecurity Red Team
- Silas Francisco
- Ricardo Pesqueira
### Identifying active exploitation of the vulnerability
The following regex should match log entries that are an indication of the vulnerability being exploited:
```regex
level=error msg="Unable to parse target URL: Unable to parse URL (extracted from X-Original-URL header)?.*?: parse.*?net/url:.*github\.com/authelia/authelia/internal/handlers/handler_verify\.go
```
Example log entry ***with*** X-Original-URL configured:
```log
time="2021-05-21T16:31:15+10:00" level=error msg="Unable to parse target URL: Unable to parse URL extracted from X-Original-URL header: parse \"https://example.com/": net/url: invalid control character in URL" method=GET path=/api/verify remote_ip=192.168.1.10 stack="github.com/authelia/authelia/internal/middlewares/authelia_context.go:65 (*AutheliaCtx).Error\ngithub.com/authelia/authelia/internal/handlers/handler_verify.go:431 VerifyGet.func1\ngithub.com/authelia/authelia/internal/middlewares/authelia_context.go:50 AutheliaMiddleware.func1.1\ngithub.com/fasthttp/router@v1.3.12/router.go:414 (*Router).Handler\ngithub.com/authelia/authelia/internal/middlewares/log_request.go:14 LogRequestMiddleware.func1\ngithub.com/valyala/fasthttp@v1.24.0/server.go:2219 (*Server).serveConn\ngithub.com/valyala/fasthttp@v1.24.0/workerpool.go:223 (*workerPool).workerFunc\ngithub.com/valyala/fasthttp@v1.24.0/workerpool.go:195 (*workerPool).getCh.func1\nruntime/asm_amd64.s:1371 goexit"
```
Example log entry ***without*** X-Original-URL configured:
```log
time="2021-05-21T16:30:17+10:00" level=error msg="Unable to parse target URL: Unable to parse URL https://example.com/: parse \"https://example.com/": net/url: invalid control character in URL" method=GET path=/api/verify remote_ip=192.168.1.10 stack="github.com/authelia/authelia/internal/middlewares/authelia_context.go:65 (*AutheliaCtx).Error\ngithub.com/authelia/authelia/internal/handlers/handler_verify.go:431 VerifyGet.func1\ngithub.com/authelia/authelia/internal/middlewares/authelia_context.go:50 AutheliaMiddleware.func1.1\ngithub.com/fasthttp/router@v1.3.12/router.go:414 (*Router).Handler\ngithub.com/authelia/authelia/internal/middlewares/log_request.go:14 LogRequestMiddleware.func1\ngithub.com/valyala/fasthttp@v1.24.0/server.go:2219 (*Server).serveConn\ngithub.com/valyala/fasthttp@v1.24.0/workerpool.go:223 (*workerPool).workerFunc\ngithub.com/valyala/fasthttp@v1.24.0/workerpool.go:195 (*workerPool).getCh.func1\nruntime/asm_amd64.s:1371 goexit"
```
### For more information
If you have any questions or comments about this advisory:
* Open an issue at [authelia](https://github.com/authelia/authelia/issues)
* Email us at [security@authelia.com](mailto:security@authelia.com)
| {'CVE-2021-32637'} | 2021-05-28T18:08:47Z | 2021-12-20T16:57:16Z | CRITICAL | null | {'CWE-287'} | {'https://github.com/authelia/authelia/commit/c62dbd43d6e69ae81530e7c4f8763857f8ff1dda', 'https://github.com/authelia/authelia/security/advisories/GHSA-68wm-pfjf-wqp6', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32637'} | null |
Go | GHSA-m6wg-2mwg-4rfq | Use After Free | The proglottis Go wrapper before 0.1.1 for the GPGME library has a use-after-free, as demonstrated by use for container image pulls by Docker or CRI-O. This leads to a crash or potential code execution during GPG signature verification. | {'CVE-2020-8945'} | 2021-05-17T22:00:21Z | 2021-05-18T15:29:42Z | HIGH | null | {'CWE-416'} | {'https://github.com/proglottis/gpgme/compare/v0.1.0...v0.1.1', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/H6P6SSNKN4H6GSEVROHBDXA64PX7EOED/', 'https://github.com/proglottis/gpgme/pull/23', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8945', 'https://access.redhat.com/errata/RHSA-2020:0679', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KDBT77KV3U7BESJX3P4S4MPVDGRTAQA2/', 'https://access.redhat.com/errata/RHSA-2020:0697', 'https://github.com/proglottis/gpgme/commit/92153bcb59bd2f511e502262c46c7bd660e21733', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WXV7NZELYWRRCXATXU3FYD3G3WJT3WYM/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3SOCLOPTSYABTE4CLTSPDIFE6ZZZR4LX/', 'https://bugzilla.redhat.com/show_bug.cgi?id=1795838', 'https://access.redhat.com/errata/RHSA-2020:0689', 'https://github.com/containers/image/commit/4c7a23f82ef09127b0ff28366d1cf31316dd6cc1'} | null |
Go | GHSA-9c4x-5hgq-q3wh | Instance config inline secret exposure in Grafana | ### Impact
Some inline secrets are exposed in plaintext over the Grafana Agent HTTP server:
* Inline secrets for metrics instance configs in the base YAML file are exposed at `/-/config`
* Inline secrets for integrations are exposed at `/-/config`
* Inline secrets for Consul ACL tokens and ETCD basic auth when configured for the scraping service at `/-/config`.
* Inline secrets for the Kafka receiver for OpenTelemetry-Collector tracing at `/-/config`.
* Inline secrets for metrics instance configs loaded from the scraping service are exposed at `/agent/api/v1/configs/{name}`.
Inline secrets will be exposed to anyone being able to reach these endpoints.
Secrets found in these sections are used for:
* Delivering metrics to a Prometheus Remote Write system
* Authenticating against a system for discovering Prometheus targets
* Authenticating against a system for collecting metrics (scrape_configs and integrations)
* Authenticating against a Consul or ETCD for storing configurations to distribute in scraping service mode
* Authenticating against Kafka for receiving traces
Non-inlined secrets, such as `*_file`-based secrets, are not impacted by this vulnerability.
### Patches
Download [v0.20.1](https://github.com/grafana/agent/releases/tag/v0.20.1) or any version past [v0.21.2](https://github.com/grafana/agent/releases/tag/v0.21.2) to patch Grafana Agent. These patches obfuscate the listed impacted secrets from the vulnerable endpoints.
The patches also disable the endpoints by default. Pass the command-line flag `--config.enable-read-api` to opt-in and re-enable the endpoints.
### Workarounds
If for some reason you cannot upgrade, use non-inline secrets where possible. Not all configuration options may have a non-inline equivalent.
You also may desire to restrict API access to Grafana Agent, with some combination of:
* Restrict network interfaces Grafana Agent listens on through `http_listen_address` in the `server` block. `127.0.0.1` is the most restrictive, `0.0.0.0` is the default.
* Configure Grafana Agent to use HTTPS with client authentication.
* Use firewall rules to restrict external access to Grafana Agent's API. | {'CVE-2021-41090'} | 2021-12-14T15:32:21Z | 2021-12-08T19:52:40Z | MODERATE | null | {'CWE-312', 'CWE-200'} | {'https://github.com/grafana/agent/releases/tag/v0.20.1', 'https://github.com/grafana/agent', 'https://security.netapp.com/advisory/ntap-20211229-0004/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41090', 'https://github.com/grafana/agent/security/advisories/GHSA-9c4x-5hgq-q3wh', 'https://github.com/grafana/agent/pull/1152', 'https://github.com/grafana/agent/releases/tag/v0.21.2', 'https://github.com/grafana/agent/commit/af7fb01e31fe2d389e5f1c36b399ddc46b412b21', 'https://github.com/grafana/agent/commit/a5479755e946e5c7cddb793ee9adda8f5692ba11'} | null |
Go | GHSA-7mqr-2v3q-v2wm | Ignored errors on token revokation in github.com/ory/fosite | ### Impact
The `TokenRevocationHandler` ignores errors coming from the storage. This can lead to unexpected 200 status codes indicating successful revocation while the token is still valid. Whether an attacker can use this for her advantage depends on the ability to trigger errors in the store.
### References
[RFC 7009](https://tools.ietf.org/html/rfc7009#section-2.2.1) states that a 503 HTTP code must be returned when the server has a problem. | {'CVE-2020-15223'} | 2021-05-24T12:53:07Z | 2021-05-24T16:57:39Z | HIGH | null | {'CWE-755'} | {'https://tools.ietf.org/html/rfc7009#section-2.2.1', 'https://github.com/ory/fosite/commit/03dd55813f5521985f7dd64277b7ba0cf1441319', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15223', 'https://github.com/ory/fosite/security/advisories/GHSA-7mqr-2v3q-v2wm'} | null |
Go | GO-2021-0081 | null | The HTTP client used to connect to the container registry authorization
service explicitly disables TLS verification, allowing an attacker that
is able to MITM the connection to steal credentials.
| {'CVE-2019-10214'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10214', 'https://github.com/containers/image/pull/669', 'https://github.com/containers/image/commit/634605d06e738aec8332bcfd69162e7509ac7aaf', 'https://github.com/containers/image/issues/654'} | null |
Go | GHSA-wpfr-6297-9v57 | User object created with invalid provider data in GoTrue | ### Impact
_What kind of vulnerability is it? Who is impacted?_
Under certain circumstances a valid user object would have been created with invalid provider metadata.
This vulnerability affects everyone running an instance of GoTrue as a service. We advise you to update especially if you are using the provider metadata from the user object to secure other resources.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
A patch is available with the release of version [1.0.1 on Github](https://github.com/netlify/gotrue/releases/tag/v1.0.1).
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
If you don't rely on the provider metadata in the user object, you might not be affected. We still strongly recommend upgrading.
### References
_Are there any links users can visit to find out more?_
This problem was initially found and reported by the team at Supabase: https://github.com/supabase/gotrue/security/advisories/GHSA-5hvv-9cqv-894r. We want to thank them for the cooperation around this report.
In contrast to their advisory, we decided to set the severity to "Moderate" since the provider metadata is not an inherent security feature of this GoTrue codebase or the Netlify ecosystem.
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@netlify.com](mailto:security@netlify.com)
| null | 2022-02-09T22:29:01Z | 2022-02-09T22:29:01Z | MODERATE | null | null | {'https://github.com/netlify/gotrue', 'https://github.com/netlify/gotrue/security/advisories/GHSA-wpfr-6297-9v57', 'https://github.com/netlify/gotrue/pull/313', 'https://github.com/netlify/gotrue/releases/tag/v1.0.1', 'https://github.com/netlify/gotrue/commit/4d8a3b39fe485a5f83c70617d594be01130c5b83'} | null |
Go | GHSA-32rp-q37p-jg6w | Insecure plugin handling in Mattermost | Mattermost version 6.4.x and earlier fails to properly check the plugin version when a plugin is installed from the Marketplace, which allows an authenticated and an authorized user to install and exploit an old plugin version from the Marketplace which might have known vulnerabilities. | {'CVE-2022-1384'} | 2022-04-28T21:12:15Z | 2022-04-20T00:00:30Z | HIGH | null | {'CWE-862'} | {'github.com/mattermost/mattermost-server', 'https://mattermost.com/security-updates/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1384'} | null |
Go | GO-2020-0025 | null | Due to improper path santization, archives containing relative file
paths can cause files to be written (or overwritten) outside of the
target directory.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://snyk.io/research/zip-slip-vulnerability', 'https://github.com/cloudfoundry/archiver/commit/09b5706aa9367972c09144a450bb4523049ee840'} | null |
Go | GHSA-wxc4-f4m6-wwqv | Excessive Platform Resource Consumption within a Loop in Kubernetes | The Kubernetes API Server component in versions 1.1-1.14, and versions prior to 1.15.10, 1.16.7 and 1.17.3 allows an authorized user who sends malicious YAML payloads to cause the kube-apiserver to consume excessive CPU cycles while parsing YAML. | {'CVE-2019-11254'} | 2021-05-07T17:24:04Z | 2021-12-20T16:55:06Z | MODERATE | null | {'CWE-1050'} | {'https://security.netapp.com/advisory/ntap-20200413-0003/', 'https://github.com/kubernetes/kubernetes/issues/89535', 'https://nvd.nist.gov/vuln/detail/CVE-2019-11254', 'https://github.com/kubernetes/kubernetes/pull/87467/commits/b86df2bec4f377afc0ca03482ffad2f0a49a83b8', 'https://github.com/go-yaml/yaml/commit/53403b58ad1b561927d19068c655246f2db79d48', 'https://groups.google.com/d/msg/kubernetes-announce/ALL9s73E5ck/4yHe8J-PBAAJ'} | null |
Go | GHSA-jq42-hfch-42f3 | Action Commands (run/shell/exec) Against Library URIs Ignore Configured Remote Endpoint | # Impact
Due to incorrect use of a default URL, `singularity` action commands (`run`/`shell`/`exec`) specifying a container using a `library://` URI will always attempt to retrieve the container from the default remote endpoint (`cloud.sylabs.io`) rather than the configured remote endpoint.
An attacker may be able to push a malicious container to the default remote endpoint with a URI that is identical to the URI used by a victim with a non-default remote endpoint, thus executing the malicious container.
Only action commands (`run`/`shell`/`exec`) against `library://` URIs are affected. Other commands such as `pull` / `push` respect the configured remote endpoint.
# Patches
All users should upgrade to Singularity 3.7.4 or later.
# Workarounds
Users who only interact with the default remote endpoint or do not use the library:// url are not affected.
Installations with an execution control list configured to restrict execution to containers signed with specific secure keys are not affected.
# Acknowledgements
This issue was found by Mike Frisch and brought to our attention by Sylabs. Sylabs is making a [coordinated disclosure](https://github.com/sylabs/singularity/security/advisories/GHSA-5mv9-q7fq-9394).
# For more information
General questions about the impact of the advisory can be asked in the:
[Singularity Slack Channel](https://join.slack.com/t/hpcng/shared_invite/zt-qda4h1ls-OP0Uouq6sSmVE6i_0NrWdw)
[Singularity Mailing List](https://groups.google.com/a/lbl.gov/g/singularity)
Any sensitive security concerns should be directed to: [singularity-security@hpcng.org](mailto:singularity-security@hpcng.org)
| null | 2021-10-05T17:22:08Z | 2021-06-01T21:20:53Z | MODERATE | null | {'CWE-20'} | {'https://github.com/hpcng/singularity', 'https://github.com/sylabs/singularity/security/advisories/GHSA-5mv9-q7fq-9394', 'https://github.com/hpcng/singularity/security/advisories/GHSA-jq42-hfch-42f3'} | null |
Go | GHSA-6c7m-qwxj-mvhp | Broken encryption in EdgeX Foundry | ### Summary
Broken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors.
### Detailed Description
The app-functions-sdk exports an “aes” transform that user scripts can optionally call to encrypt data in the processing pipeline. No decrypt function is provided. Encryption is not enabled by default, but if used, the level of protection may be less than the user may expects due to a broken implementation in https://github.com/edgexfoundry/app-functions-sdk-go/blob/v1.0.0/pkg/transforms/encryption.go
Version v2.1.0 (EdgeX Foundry Jakarta release and later) of app-functions-sdk-go/v2 deprecates the “aes” transform and provides an improved “aes256” transform in its place. The broken implementation will remain in a deprecated state until it is removed in the next EdgeX major release to avoid breakage of existing software that depends on the broken implementation.
### Impact
As the broken transform is a library function that is not invoked by default, users who do not use the AES transform in their processing pipelines are unaffected. Those that are affected are urged to upgrade to the Jakarta EdgeX release and modify processing pipelines to use the new "aes256" transform.
#### Vulnerable go modules
- github.com/edgexfoundry/app-functions-sdk-go < v2.1.0
- github.com/edgexfoundry/app-functions-sdk-go/v2 < v2.1.0
- github.com/edgexfoundry/app-service-configurable < v2.1.0
#### Vulnerable containers
- https://hub.docker.com/r/edgexfoundry/app-service-configurable >= 2.0.0 < v2.1.0
- https://hub.docker.com/r/edgexfoundry/app-service-configurable-arm64 >= 2.0.0 < 2.1.0
- https://hub.docker.com/r/edgexfoundry/docker-app-service-configurable < 2.0.0
- https://hub.docker.com/r/edgexfoundry/docker-app-service-configurable-arm64 < 2.0.0
#### Vulnerable Snaps
- https://snapcraft.io/edgex-app-service-configurable >= 2.0.0 < 2.1.0
### Patches
Upgrade to 2.1.0 version of app-functions-sdk-go/v2, app-service-configurable, and related docker containers shown below and modify user scripts to use the new "aes256" transform in place of the existing "aes" transform.
#### Patched go modules
- github.com/edgexfoundry/app-functions-sdk-go/v2 v2.1.0
- github.com/edgexfoundry/app-service-configurable v2.1.0
Modification of user scripts is necessary for full remediation.
#### Patched containers
- https://hub.docker.com/r/edgexfoundry/app-service-configurable:>=2.1.0
- https://hub.docker.com/r/edgexfoundry/app-service-configurable-arm64:>=2.1.0
Modification of user scripts is necessary for full remediation.
#### Patched Snaps
- https://snapcraft.io/edgex-app-service-configurable >= 2.1.0
Modification of user scripts is necessary for full remediation.
### Workarounds
If unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption.
### References
* [2.0 documentation](https://docs.edgexfoundry.org/2.0/microservices/application/BuiltIn/#aes)
* [2.1 documentation](https://docs.edgexfoundry.org/2.1/microservices/application/BuiltIn/#encryption-deprecated)
* [GitHub issue](https://github.com/edgexfoundry/app-functions-sdk-go/issues/968)
### For more information
If you have any questions or comments about this advisory:
* Contact us in the [Slack #security channel](https://slack.edgexfoundry.org/)
* Open an issue in [edgex-go](https://github.com/edgexfoundry/edgex-go)
* Email us at [EdgeX-TSC-Security@lists.edgexfoundry.org](mailto:EdgeX-TSC-Security@lists.edgexfoundry.org) | {'CVE-2021-41278'} | 2021-11-24T19:01:48Z | 2021-11-19T20:55:16Z | MODERATE | null | {'CWE-327'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-41278', 'https://github.com/edgexfoundry/app-functions-sdk-go/security/advisories/GHSA-6c7m-qwxj-mvhp', 'https://github.com/edgexfoundry/app-functions-sdk-go', 'https://github.com/edgexfoundry/app-functions-sdk-go/commit/8fa13c6388ce76a6b878b54490eac61aa7d81165'} | null |
Go | GHSA-9q3g-m353-cp4p | Denial of Service in Packetbeat | Packetbeat versions prior to 5.6.4 are affected by a denial of service flaw in the PostgreSQL protocol handler. If Packetbeat is listening for PostgreSQL traffic and a user is able to send arbitrary network traffic to the monitored port, the attacker could prevent Packetbeat from properly logging other PostgreSQL traffic. | {'CVE-2017-11480'} | 2021-05-19T22:35:34Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-404'} | {'https://github.com/elastic/beats/pull/5457', 'https://nvd.nist.gov/vuln/detail/CVE-2017-11480', 'https://discuss.elastic.co/t/beats-5-6-4-security-update/106739'} | null |
Go | GHSA-gv9j-4w24-q7vx | Improper random number generation in github.com/coredns/coredns | ### Impact
CoreDNS before 1.6.6 (using go DNS package < 1.1.25) improperly generates random numbers because math/rand is used. The TXID becomes predictable, leading to response forgeries.
### Patches
The problem has been fixed in 1.6.6+.
### References
- [CVE-2019-19794](https://nvd.nist.gov/vuln/detail/CVE-2019-19794)
### For more information
Please consult [our security guide](https://github.com/coredns/coredns/blob/master/.github/SECURITY.md) for more information regarding our security process.
| null | 2022-03-01T21:03:11Z | 2022-03-01T21:03:11Z | MODERATE | null | {'CWE-330'} | {'https://github.com/coredns/coredns/security/advisories/GHSA-gv9j-4w24-q7vx', 'github.com/coredns/coredns'} | null |
Go | GHSA-76j4-gggq-7rg9 | SQLinjection in falcon-plus | Falcon-plus v0.3 was discovered to contain a SQL injection vulnerability via the parameter grpName in /config/service/host.go. | {'CVE-2022-26245'} | 2022-04-07T15:28:23Z | 2022-03-28T00:00:20Z | CRITICAL | null | {'CWE-89'} | {'github.com/open-falcon/falcon-plus', 'https://github.com/open-falcon/falcon-plus/issues/951', 'https://nvd.nist.gov/vuln/detail/CVE-2022-26245'} | null |
Go | GO-2020-0005 | null | Malformed WALs can be constructed such that [`WAL.ReadAll`][] can cause attempted
out of bounds reads, or creation of arbitarily sized slices, which may be used as
a DoS vector.
| {'CVE-2020-15106'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/etcd-io/etcd/blob/master/security/SECURITY_AUDIT.pdf', 'https://github.com/etcd-io/etcd/pull/11793', 'https://github.com/etcd-io/etcd/commit/f4b650b51dc4a53a8700700dc12e1242ac56ba07'} | null |
Go | GHSA-jcxc-rh6w-wf49 | Link Following in Iris | This affects all versions of package github.com/kataras/iris; all versions of package github.com/kataras/iris/v12. The unsafe handling of file names during upload using UploadFormFiles method may enable attackers to write to arbitrary locations outside the designated target folder. | {'CVE-2021-23772'} | 2022-01-05T18:09:47Z | 2022-01-06T21:36:19Z | HIGH | null | {'CWE-59'} | {'https://github.com/kataras/iris/commit/e213dba0d32ff66653e0ef124bc5088817264b08', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23772', 'https://github.com/kataras/iris', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMKATARASIRISV12-2325170', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMKATARASIRIS-2325169'} | null |
Go | GHSA-hv5f-73mr-7vvj | Cross-site Scripting in Mattermost | Mattermost 5.38 and earlier fails to sufficiently sanitize clipboard contents, which allows a user-assisted attacker to inject arbitrary web script in product deployments that explicitly disable the default CSP. | {'CVE-2021-37860'} | 2021-10-06T13:08:14Z | 2021-09-23T23:11:06Z | MODERATE | null | {'CWE-79'} | {'https://docs.mattermost.com/install/self-managed-changelog.html#release-v5-39-quality-release', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37860', 'https://mattermost.com/security-updates/', 'https://github.com/mattermost/mattermost-server/'} | null |
Go | GHSA-fp52-qw33-mfmw | Authentication Bypass by Spoofing and Insufficient Verification of Data Authenticity in Hashicorp Vault | HashiCorp Vault and Vault Enterprise versions 0.7.1 and newer, when configured with the AWS IAM auth method, may be vulnerable to authentication bypass. Fixed in 1.2.5, 1.3.8, 1.4.4, and 1.5.1.. | {'CVE-2020-16250'} | 2022-04-29T20:26:41Z | 2021-08-02T17:11:41Z | CRITICAL | null | {'CWE-345', 'CWE-290'} | {'https://www.hashicorp.com/blog/category/vault/', 'http://packetstormsecurity.com/files/159478/Hashicorp-Vault-AWS-IAM-Integration-Authentication-Bypass.html', 'https://github.com/hashicorp/vault', 'https://github.com/hashicorp/vault/blob/master/CHANGELOG.md#151', 'https://nvd.nist.gov/vuln/detail/CVE-2020-16250'} | null |
Go | GHSA-57v4-m9jx-mh8r | Improper Input Validation | A vulnerability was found in OVN Kubernetes in versions up to and including 0.3.0 where the Egress Firewall does not reliably apply firewall rules when there is multiple DNS rules. It could lead to potentially lose of confidentiality, integrity or availability of a service. | {'CVE-2021-3499'} | 2021-06-08T23:05:09Z | 2021-06-08T23:05:19Z | MODERATE | null | {'CWE-863'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=1949188', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3499', 'https://github.com/ovn-org/ovn-kubernetes/pull/2169'} | null |
Go | GHSA-7v5r-r995-q2x2 | SSRF in repository migration | Gogs is a self-hosted Git service. The malicious user is able to discover services in the internal network through repository migration functionality. All installations accepting public traffic are affected. Internal network CIDRs are prohibited to be used as repository migration targets. Users should upgrade to 0.12.5 or the latest 0.13.0+dev. Gogs should be ran in its own private network until users can update. | {'CVE-2022-0870'} | 2022-03-24T23:23:21Z | 2022-03-12T00:00:34Z | MODERATE | null | {'CWE-918'} | {'https://huntr.dev/bounties/327797d7-ae41-498f-9bff-cc0bf98cf531', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0870', 'https://github.com/gogs/gogs', 'https://github.com/gogs/gogs/commit/91f2cde5e95f146bfe4765e837e7282df6c7cabb'} | null |
Go | GO-2020-0013 | null | By default host key verification is disabled which allows for
man-in-the-middle attacks against SSH clients if
[`ClientConfig.HostKeyCallback`] is not set.
| {'CVE-2017-3204'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://bridge.grumpy-troll.org/2017/04/golang-ssh-security/', 'https://go-review.googlesource.com/38701', 'https://github.com/golang/go/issues/19767', 'https://github.com/golang/crypto/commit/e4e2799dd7aab89f583e1d898300d96367750991'} | null |
Go | GHSA-jq7p-26h5-w78r | Out-of-bounds read in Apache Thrift | In Apache Thrift 0.9.3 to 0.12.0, a server implemented in Go using TJSONProtocol or TSimpleJSONProtocol may panic when feed with invalid input data. | {'CVE-2019-0210'} | 2021-05-17T21:09:18Z | 2021-05-18T15:32:04Z | HIGH | null | {'CWE-125'} | {'https://access.redhat.com/errata/RHSA-2020:0804', 'https://nvd.nist.gov/vuln/detail/CVE-2019-0210', 'https://lists.apache.org/thread.html/r2832722c31d78bef7526e2c701ba4b046736e4c851473194a247392f@%3Ccommits.pulsar.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2020:0806', 'https://github.com/apache/thrift/commit/264a3f318ed3e9e51573f67f963c8509786bcec2', 'https://access.redhat.com/errata/RHSA-2020:0805', 'https://lists.apache.org/thread.html/r55609613abab203a1f2c1f3de050b63ae8f5c4a024df0d848d6915ff@%3Ccommits.pulsar.apache.org%3E', 'https://github.com/apache/thrift/blob/master/CHANGES.md#0130', 'http://mail-archives.apache.org/mod_mbox/thrift-dev/201910.mbox/%3C277A46CA87494176B1BBCF5D72624A2A%40HAGGIS%3E', 'https://security.gentoo.org/glsa/202107-32', 'https://lists.apache.org/thread.html/rab740e5c70424ef79fd095a4b076e752109aeee41c4256c2e5e5e142@%3Ccommits.pulsar.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2020:0811', 'https://lists.apache.org/thread.html/r36581cc7047f007dd6aadbdd34e18545ec2c1eb7ccdae6dd47a877a9@%3Ccommits.pulsar.apache.org%3E'} | null |
Go | GHSA-6hw5-6gcx-phmw | HashiCorp Consul and Consul Enterprise 1.10.1 Txn.Apply endpoint allowed services to register proxies for other services, enabling access to service traffic. | HashiCorp Consul and Consul Enterprise 1.10.1 Txn.Apply endpoint allowed services to register proxies for other services, enabling access to service traffic. Fixed in 1.8.15, 1.9.9 and 1.10.2. | {'CVE-2021-38698'} | 2021-09-16T18:57:24Z | 2021-09-08T20:14:56Z | MODERATE | null | {'CWE-863'} | {'https://github.com/hashicorp/consul/pull/10824', 'https://nvd.nist.gov/vuln/detail/CVE-2021-38698', 'https://discuss.hashicorp.com/t/hcsec-2021-24-consul-missing-authorization-check-on-txn-apply-endpoint/29026', 'https://www.hashicorp.com/blog/category/consul', 'https://github.com/hashicorp/consul'} | null |
Go | GO-2021-0058 | null | Due to the behavior of encoding/xml, a crafted XML document may cause
XML Digital Signature validation to be entirely bypassed, causing an
unsigned document to appear signed.
| {'CVE-2020-27846'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/crewjam/saml/security/advisories/GHSA-4hq8-gmxx-h6w9', 'https://github.com/crewjam/saml/commit/da4f1a0612c0a8dd0452cf8b3c7a6518f6b4d053'} | null |
Go | GHSA-xg75-q3q5-cqmv | Denial of Service in http-swagger | ### Impact
Allows an attacker to perform a DOS attack consisting of memory exhaustion on the host system.
### Patches
Yes. Please upgrade to v1.2.6.
### Workarounds
A workaround is to restrict the path prefix to the "GET" method. As shown below
```
func main() {
r := mux.NewRouter()
r.PathPrefix("/swagger/").Handler(httpSwagger.Handler(
httpSwagger.URL("http://localhost:1323/swagger/doc.json"), //The url pointing to API definition
httpSwagger.DeepLinking(true),
httpSwagger.DocExpansion("none"),
httpSwagger.DomID("#swagger-ui"),
)).Methods(http.MethodGet)
```
### References
Reporter dongguangli from https://www.huoxian.cn/ company
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [http-swagger](https://github.com/swaggo/http-swagger/issues)
| {'CVE-2022-24863'} | 2022-04-22T20:55:52Z | 2022-04-22T20:55:52Z | HIGH | null | {'CWE-400', 'CWE-755'} | {'https://github.com/swaggo/http-swagger/pull/62', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24863', 'https://github.com/swaggo/http-swagger/security/advisories/GHSA-xg75-q3q5-cqmv', 'https://github.com/swaggo/http-swagger/commit/b7d83e8fba85a7a51aa7e45e8244b4173f15049e', 'https://github.com/swaggo/http-swagger/releases/tag/v1.2.6', 'https://github.com/swaggo/http-swagger'} | null |
Go | GHSA-jp4j-47f9-2vc3 | Integer Overflow or Wraparound in NATS Server | An integer overflow in NATS Server 2.0.0 allows a remote attacker to crash the server by sending a crafted request. | {'CVE-2019-13126'} | 2021-05-17T16:35:04Z | 2021-05-18T18:14:55Z | HIGH | null | {'CWE-190'} | {'https://github.com/nats-io/nats-server/pull/1441', 'https://github.com/nats-io/nats-server/pull/1053', 'https://nvd.nist.gov/vuln/detail/CVE-2019-13126', 'https://github.com/nats-io/nats-server/commit/07ef71ff98f45f8c2711be4aeaf484610d891dda', 'https://github.com/nats-io/nats-server/commits/master', 'https://www.twistlock.com/labs-blog/finding-dos-vulnerability-nats-go-fuzz-cve-2019-13126/'} | null |
Go | GHSA-f5fj-7265-jxhj | Information Exposure | Gitea version prior to version 1.5.1 contains a CWE-200 vulnerability that can result in Exposure of users private email addresses. This attack appear to be exploitable via Watch a repository to receive email notifications. Emails received contain the other recipients even if they have the email set as private. This vulnerability appears to have been fixed in 1.5.1. | {'CVE-2018-1000803'} | 2021-05-12T18:09:38Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-200'} | {'https://github.com/go-gitea/gitea/commit/194a11eb110cd98fc2ba52861abf7770db6885a3', 'https://nvd.nist.gov/vuln/detail/CVE-2018-1000803', 'https://github.com/go-gitea/gitea/pull/4664', 'https://github.com/go-gitea/gitea/pull/4664/files#diff-146e0c2b5bb1ea96c9fb73d509456e57'} | null |
Go | GHSA-vx57-7f4q-fpc7 | Arbitrary redirects under /new endpoint | ### Impact
In 2.23.0, Prometheus changed its default UI to the New ui. To ensure a seamless transition, the URL's prefixed by /new redirect to /.
Due to a bug in the code, it is possible for an attacker to craft an URL that can redirect to any other URL, in the /new endpoint.
If a user visits a prometheus server with a specially crafted address (e.g.: `http://127.0.0.1:9090/new/new<url>`), they can be redirected to an arbitrary URL.
e.g. if a user visits http://127.0.0.1:9090/new/newhttp://www.google.com/, they will be redirected to http://google.com.
### Patches
The issue will be patched in 2.26.1 and 2.27.1 releases.
In 2.28.0, the /new endpoint will be removed completely.
### Workarounds
The workaround is to disable access to /new via a reverse proxy in front of Prometheus.
Note: Users who use a `--web.external-url=` flag _with a path_ (e.g. `--web.external-url=http://example.com/prometheus`) are not affected.
### For more information
If you have any questions or comments about this advisory, please use our community channels (https://prometheus.io/community).
Our security policy is available at https://prometheus.io/docs/operating/security/
| {'CVE-2021-29622'} | 2021-05-28T22:05:12Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-601'} | {'https://github.com/prometheus/prometheus/releases/tag/v2.27.1', 'https://github.com/prometheus/prometheus/security/advisories/GHSA-vx57-7f4q-fpc7', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29622', 'https://github.com/prometheus/prometheus/releases/tag/v2.26.1'} | null |
Go | GHSA-8cvr-4rrf-f244 | Infinite open connection causes OctoRPKI to hang forever | OctoRPKI does not limit the length of a connection, allowing for a slowloris DOS attack to take place which makes OctoRPKI wait forever. Specifically, the repository that OctoRPKI sends HTTP requests to will keep the connection open for a day before a response is returned, but does keep drip feeding new bytes to keep the connection alive.
## Patches
## For more information
If you have any questions or comments about this advisory email us at security@cloudflare.com
| {'CVE-2021-3909'} | 2021-11-10T18:18:28Z | 2021-11-10T20:15:44Z | MODERATE | null | {'CWE-400'} | {'https://github.com/cloudflare/cfrpki', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3909', 'https://github.com/cloudflare/cfrpki/releases/tag/v1.4.0', 'https://www.debian.org/security/2022/dsa-5041', 'https://github.com/cloudflare/cfrpki/security/advisories/GHSA-8cvr-4rrf-f244', 'https://www.debian.org/security/2021/dsa-5033'} | null |
Go | GHSA-362v-wg5p-64w2 | Incorrect Privilege Assignment in HashiCorp Vault | HashiCorp Vault and Vault Enterprise 1.8.x through 1.8.4 may have an unexpected interaction between glob-related policies and the Google Cloud secrets engine. Users may, in some situations, have more privileges than intended, e.g., a user with read permission for the /gcp/roleset/* path may be able to issue Google Cloud service account credentials. | {'CVE-2021-42135'} | 2021-10-20T17:28:19Z | 2021-10-12T18:41:16Z | HIGH | null | {'CWE-863', 'CWE-266'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-42135', 'https://discuss.hashicorp.com/t/hcsec-2021-28-vaults-google-cloud-secrets-engine-policies-with-globs-may-provide-additional-privileges-in-vault-1-8-0-onwards/', 'https://github.com/hashicorp/vault/blob/main/CHANGELOG.md#180', 'https://github.com/hashicorp/vault'} | null |
Go | GHSA-jj6m-r8jc-2gp7 | Asymmetric Resource Consumption (Amplification) in Docker containers created by Wings | ### Impact
All versions of Pterodactyl Wings preior to `1.4.4` are vulnerable to system resource exhaustion due to improper container process limits being defined. A malicious user can consume more resources than intended and cause downstream impacts to other clients on the same hardware, eventually causing the physical server to stop responding.
### Patches
Users should upgrade to `1.4.4`.
### Workarounds
There is no non-code based workaround for impacted versions of the software. Users running customized versions of this software can manually set a PID limit for containers created.
### For more information
If you have any questions or comments about this advisory:
* Contact us on [Discord](https://discord.gg/pterodactyl)
* Email us at `dane ät pterodactyl dot io` | {'CVE-2021-32699'} | 2021-10-21T13:26:03Z | 2021-06-23T18:03:18Z | MODERATE | null | {'CWE-405'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-32699', 'https://github.com/pterodactyl/wings', 'https://github.com/pterodactyl/wings/security/advisories/GHSA-jj6m-r8jc-2gp7', 'https://github.com/pterodactyl/wings/commit/e0078eee0a71d61573a94c75e6efcad069d78de3'} | null |
Go | GHSA-g54h-m393-cpwq | devices resource list treated as a blacklist by default | ### Impact
Contrary to the [OCI runtime specification](https://github.com/opencontainers/runtime-spec/blob/v1.0.2/config-linux.md#device-whitelist), `runc`'s implementation of the `linux.resources.devices` list was a black-list by default. This means that users who created their own `config.json` objects and didn't prefix a deny-all rule (`{"allow": false, "permissions": "rwm"}` or equivalent) were not provided protection by the `devices` cgroup. This would allow malicious containers (with sufficient privileges) to create arbitrary device inodes (assuming they have `CAP_MKNOD`) and operate on any device inodes they may have access to (assuming they have regular Unix DAC permissions).
However, most (if not all) programs that make use of `runc` include this deny-all rule. This was most likely added before the specification mandated a white-list of devices, and the fact that all programs wrote their own deny-all rule obscured the existence of this bug for several years. In fact, even the specification's examples include a default deny-all rule! We therefore believe that while this is a security bug (and has been fixed as such), it was almost certainly not exploitable in the wild due to the inclusion of default deny-all rules by all known users of `runc` -- hence why this advisory has low severity.
### Patches
This issue has been fixed in [a patch that was part of a larger rework of the devices cgroup code in runc](https://github.com/opencontainers/runc/pull/2391) -- which lead to the discovery of this security bug. Users should upgrade to 1.0.0-rc91 as soon as it is released, or wait for your distribution to backport the relevant fixes.
### Workarounds
If you are using `runc` directly, ensure that there is a deny-all entry at the beginning of `linux.resources.devices` -- such an entry would look like `{"allow": false, "permissions": "rwm"}` (all other fields are ignored, though `type` must be set to `"a"` or `null` if it is present).
Users which consume `runc` through another program should check whether their containers are operating under a white-list -- this can be done by reading `/sys/fs/cgroup/devices/devices.list` inside the container. If the file contains only the entry `a *:* rwm` (meaning the cgroup is in black-list mode, which likely means "allow all device access") then your containers are vulnerable to this issue.
As always, we recommend **in the strongest possible terms** that all of our users enable user namespaces on all of their workloads (or pressure their vendors to do so). User namespaces are one of the most significant defense-in-depth protections you can enable for containers, and have prevented many container-related vulnerabilities (both kernel 0days as well as bugs in container runtimes, such as this one).
### References
* https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/devices.html
* [opencontainers/runtime-spec/config-linux.md#device-whitelist](https://github.com/opencontainers/runtime-spec/blob/v1.0.2/config-linux.md#device-whitelist)
* https://github.com/opencontainers/runc/pull/2391
### For more information
If you have any questions or comments about this advisory:
* [Open an issue in this repo](https://github.com/opencontainers/runc/issues/new).
* Email us at <security@opencontainers.org>. | null | 2021-05-24T20:46:53Z | 2021-12-20T18:21:54Z | LOW | null | null | {'https://github.com/opencontainers/runc/security/advisories/GHSA-g54h-m393-cpwq'} | null |
Go | GHSA-mr6h-chqp-p9g2 | SQL Injection in gogs.io/gogs | SQL injection vulnerability in the GetIssues function in models/issue.go in Gogs (aka Go Git Service) 0.3.1-9 through 0.5.6.x before 0.5.6.1025 Beta allows remote attackers to execute arbitrary SQL commands via the label parameter to user/repos/issues. | {'CVE-2014-8681'} | 2021-05-19T21:48:08Z | 2021-06-29T18:32:44Z | MODERATE | null | {'CWE-89'} | {'http://seclists.org/fulldisclosure/2014/Nov/31', 'https://github.com/gogits/gogs/commit/83283bca4cb4e0f4ec48a28af680f0d88db3d2c8', 'https://github.com/gogits/gogs/releases/tag/v0.5.8', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/98695', 'https://nvd.nist.gov/vuln/detail/CVE-2014-8681', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-8681', 'https://www.exploit-db.com/exploits/35237', 'http://gogs.io/docs/intro/change_log.html', 'http://packetstormsecurity.com/files/129116/Gogs-Label-Search-Blind-SQL-Injection.html'} | null |
Go | GHSA-x6jv-5vfg-gm7x | Path traversal in ServcieCenter | Improper configuration will cause ServiceComb ServiceCenter Directory Traversal problem in ServcieCenter 1.x.x versions and fixed in 2.0.0. | {'CVE-2021-21501'} | 2021-08-30T19:32:48Z | 2021-09-01T18:35:52Z | HIGH | null | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-21501', 'https://lists.apache.org/thread.html/r337be65e504eac52a12e89d7de40345e5d335deee9dd7288f7f59b81%40%3Cdev.servicecomb.apache.org%3E', 'http://www.openwall.com/lists/oss-security/2021/08/10/3', 'https://github.com/apache/servicecomb-service-center', 'https://github.com/apache/servicecomb-service-center/pull/788'} | null |
Go | GHSA-4fqx-74rv-638w | SQL Injection | Pivotal Concourse version 5.0.0, contains an API that is vulnerable to SQL injection. An Concourse resource can craft a version identifier that can carry a SQL injection payload to the Concourse server, allowing the attacker to read privileged data. | {'CVE-2019-3792'} | 2021-05-12T18:21:05Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-89'} | {'https://github.com/concourse/concourse/blob/master/release-notes/v5.0.1.md#v501-note-1', 'https://nvd.nist.gov/vuln/detail/CVE-2019-3792', 'https://github.com/concourse/concourse/commit/dc3d15ab6c3a69890c9985f9c875d4c2949be727', 'https://pivotal.io/security/cve-2019-3792'} | null |
Go | GHSA-fx95-883v-4q4h | Path traversal in github.com/valyala/fasthttp | The package github.com/valyala/fasthttp before 1.34.0 is vulnerable to Directory Traversal via the ServeFile function, due to improper sanitization. It is possible to be exploited by using a backslash %5c character in the path. **Note:** This security issue impacts Windows users only. | {'CVE-2022-21221'} | 2022-03-29T22:03:08Z | 2022-03-18T00:01:11Z | HIGH | null | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-21221', 'https://github.com/valyala/fasthttp/commit/15262ecf3c602364639d465daba1e7f3604d00e8', 'https://github.com/valyala/fasthttp/issues/1226', 'https://github.com/valyala/fasthttp', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMVALYALAFASTHTTP-2407866', 'https://github.com/valyala/fasthttp/releases/tag/v1.34.0', 'https://github.com/valyala/fasthttp/commit/6b5bc7bb304975147b4af68df54ac214ed2554c1'} | null |
Go | GHSA-xw37-57qp-9mm4 | Consensus flaw during block processing in github.com/ethereum/go-ethereum | ### Impact
A consensus-vulnerability in Geth could cause a chain split, where vulnerable versions refuse to accept the canonical chain.
### Description
A flaw was repoted at 2020-08-11 by John Youngseok Yang (Software Platform Lab), where a particular sequence of transactions could cause a consensus failure.
- Tx 1:
- `sender` invokes `caller`.
- `caller` invokes `0xaa`. `0xaa` has 3 wei, does a self-destruct-to-self
- `caller` does a `1 wei` -call to `0xaa`, who thereby has 1 wei (the code in `0xaa` still executed, since the tx is still ongoing, but doesn't redo the selfdestruct, it takes a different path if callvalue is non-zero)
- Tx 2:
- `sender` does a 5-wei call to 0xaa. No exec (since no code).
In geth, the result would be that `0xaa` had `6 wei`, whereas OE reported (correctly) `5` wei. Furthermore, in geth, if the second tx was not executed, the `0xaa` would be destructed, resulting in `0 wei`. Thus obviously wrong.
It was determined that the root cause was this [commit](https://github.com/ethereum/go-ethereum/commit/223b950944f494a5b4e0957fd9f92c48b09037ad) from [this PR](https://github.com/ethereum/go-ethereum/pull/19953). The semantics of `createObject` was subtly changd, into returning a non-nil object (with `deleted=true`) where it previously did not if the account had been destructed. This return value caused the new object to inherit the old `balance`:
```golang
func (s *StateDB) CreateAccount(addr common.Address) {
newObj, prev := s.createObject(addr)
if prev != nil {
newObj.setBalance(prev.data.Balance)
}
}
```
It was determined that the minimal possible correct fix was
```diff
+++ b/core/state/statedb.go
@@ -589,7 +589,10 @@ func (s *StateDB) createObject(addr common.Address) (newobj, prev *stateObject)
s.journal.append(resetObjectChange{prev: prev, prevdestruct: prevdestruct})
}
s.setStateObject(newobj)
- return newobj, prev
+ if prev != nil && !prev.deleted {
+ return newobj, prev
+ }
+ return newobj, nil
```
### Patches
See above. The fix was included in Geth `v1.9.20` "Paragade".
### Credits
The bug was found by @johnyangk and reported via bounty@ethereum.org.
### 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-26265'} | 2021-05-21T21:15:07Z | 2021-06-29T21:14:16Z | MODERATE | null | {'CWE-682'} | {'https://github.com/ethereum/go-ethereum/releases/tag/v1.9.20', 'https://github.com/ethereum/go-ethereum/security/advisories/GHSA-xw37-57qp-9mm4', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26265', 'https://github.com/ethereum/go-ethereum/pull/21409'} | null |
Go | GO-2020-0029 | null | Due to improper HTTP header santization, a malicious user can spoof their
source IP address by setting the X-Forwarded-For header. This may allow
a user to bypass IP based restrictions, or obfuscate their true source.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/gin-gonic/gin/pull/182', 'https://github.com/gin-gonic/gin/commit/0099840c98ae1473c5ff0f18bc93a8e13ceed829'} | null |
Go | GHSA-4cxw-hq44-r344 | Off-by-one Error in v2fly/v2ray-core | v2fly/v2ray-core prior to 4.44.0 is vulnerable to an off-by-one error. Indexing operations on arrays, slices, or strings should use an index at most one less than the length. If the index is checked for being less than or equal to the length (`<=`), instead of less than the length (`<`), the index could be out of bounds. | {'CVE-2021-4070'} | 2022-03-03T19:17:50Z | 2022-02-24T00:00:52Z | CRITICAL | null | {'CWE-193'} | {'https://github.com/v2fly/v2ray-core/commit/c1af2bfd7aa59a4482aa7f6ec4b9208c1d350b5c', 'https://github.com/v2fly/v2ray-core', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4070', 'https://huntr.dev/bounties/8da19456-4d89-41ef-9781-a41efd6a1877'} | null |
Go | GHSA-465w-gg5p-85c9 | Insufficient Session Expiration in Kiali | An insufficient JWT validation vulnerability was found in Kiali versions 0.4.0 to 1.15.0 and was fixed in Kiali version 1.15.1, wherein a remote attacker could abuse this flaw by stealing a valid JWT cookie and using that to spoof a user session, possibly gaining privileges to view and alter the Istio configuration. | {'CVE-2020-1762'} | 2021-05-18T20:45:55Z | 2021-05-18T21:09:01Z | HIGH | null | {'CWE-613', 'CWE-384', 'CWE-295'} | {'https://kiali.io/news/security-bulletins/kiali-security-001/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-1762', 'https://github.com/kiali/kiali/commit/c91a0949683976f621cca213c1193831d63b381c', 'https://github.com/kiali/kiali/commit/93f5cd0b6698e8fe8772afb8f35816f6c086aef1', 'https://bugzilla.redhat.com/show_bug.cgi?id=1810387', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1762'} | null |
Go | GHSA-63qx-x74g-jcr7 | Path traversal and dereference of symlinks in Argo CD | ### Impact
All versions of Argo CD are vulnerable to a path traversal bug that allows to pass arbitrary values files to be consumed by Helm charts.
Additionally, it is possible to craft special Helm chart packages containing value files that are actually symbolic links, pointing to arbitrary files outside the repository's root directory.
If an attacker with permissions to create or update Applications knows or can guess the full path to a file containing valid YAML, they can create a malicious Helm chart to consume that YAML as values files, thereby gaining access to data they would otherwise have no access to.
The impact can especially become critical in environments that make use of encrypted value files (e.g. using plugins with git-crypt or SOPS) containing sensitive or confidential data, and decrypt these secrets to disk before rendering the Helm chart.
Also, because any error message from `helm template` is passed back to the user, and these error messages are quite verbose, enumeration of files on the repository server's file system is possible.
### Patches
A patch for this vulnerability has been released in the following Argo CD versions:
* v2.3.0
* v2.2.4
* v2.1.9
We urge users of Argo CD to update their installation to one of the fixed versions as listed above.
### Workarounds
No workaround for this issue.
### References
* https://apiiro.com/blog/malicious-kubernetes-helm-charts-can-be-used-to-steal-sensitive-information-from-argo-cd-deployments
* https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24348
### For more information
* Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions)
* Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel `#argo-cd`
### Credits
The path traversal vulnerability was discovered and reported by Moshe Zioni, VP Security Research, [Apiiro](https://www.apiiro.com).
During the development of a fix for the path traversal vulnerability, the Argo CD team discovered the related issue with symbolic links.
The Argo CD team would like to thank Moshe Zioni for the responsible disclosure, and the constructive discussions during handling this issue!
| {'CVE-2022-24348'} | 2022-02-07T19:06:18Z | 2022-02-07T19:06:18Z | HIGH | null | {'CWE-200', 'CWE-22'} | {'https://github.com/argoproj/argo-cd/security/advisories/GHSA-63qx-x74g-jcr7', 'https://github.com/argoproj/argo-cd/commit/78c2084f0febd159039ff785ddc2bd4ba1cecf88', 'https://github.com/argoproj/argo-cd', 'https://github.com/argoproj/argo-cd/releases/tag/v2.1.9', 'https://apiiro.com/blog/malicious-kubernetes-helm-charts-can-be-used-to-steal-sensitive-information-from-argo-cd-deployments/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24348', 'https://github.com/argoproj/argo-cd/releases/tag/v2.2.4'} | null |
Go | GHSA-c52f-pq47-2r9j | plugin.yaml file allows for duplicate entries in helm | ### Impact
During a security audit of Helm's code base, Helm maintainers identified a bug in which a Helm plugin can contain duplicates of the same entry, with the last one always used. If a plugin is compromised, this lowers the level of access that an attacker needs to modify a plugin's install hooks, causing a local execution attack.
To perform this attack, an attacker must have write access to the git repository or plugin archive (.tgz) while being downloaded (which can occur during a MITM attack on a non-SSL connection).
### Patches
This issue has been patched in Helm 2.16.11 and Helm 3.3.2.
### Workarounds
Make sure to install plugins using a secure connection protocol like SSL. | {'CVE-2020-15187'} | 2021-11-19T15:21:02Z | 2021-05-24T16:57:21Z | LOW | null | {'CWE-694', 'CWE-74'} | {'https://github.com/helm/helm/commit/d9ef5ce8bad512e325390c0011be1244b8380e4b', 'https://github.com/helm/helm', 'https://github.com/helm/helm/commit/6aab63765f99050b115f0aec3d6350c85e8da946', 'https://github.com/helm/helm/security/advisories/GHSA-c52f-pq47-2r9j', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15187'} | null |
Go | GHSA-gfh2-7jg5-653p | Denial of Service in docker2aci | docker2aci <= 0.12.3 has an infinite loop when handling local images with cyclic dependency chain. | {'CVE-2016-8579'} | 2021-05-20T16:29:42Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-835'} | {'https://github.com/appc/docker2aci/releases/tag/v0.13.0', 'https://www.securityfocus.com/bid/93560', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-8579', 'https://github.com/appc/docker2aci/pull/204/commits/54331ec7020e102935c31096f336d31f6400064f', 'https://github.com/appc/docker2aci/issues/203', 'https://nvd.nist.gov/vuln/detail/CVE-2016-8579'} | null |
Go | GHSA-6239-28c2-9mrm | Improper Removal of Sensitive Information Before Storage or Transfer in HashiCorp Vault | HashiCorp Vault and Vault Enterprise’s UI erroneously cached and exposed user-viewed secrets between sessions in a single shared browser. Fixed in 1.8.0 and pending 1.7.4 / 1.6.6 releases. | {'CVE-2021-38554'} | 2021-10-21T14:19:31Z | 2021-08-30T17:22:38Z | MODERATE | null | {'CWE-212'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-38554', 'https://github.com/hashicorp/vault/releases/tag/v1.7.4', 'https://github.com/hashicorp/vault', 'https://github.com/hashicorp/vault/releases/tag/v1.6.6', 'https://discuss.hashicorp.com/t/hcsec-2021-19-vault-s-ui-cached-user-viewed-secrets-between-shared-browser-sessions/28166'} | null |
Go | GHSA-q9vw-wr57-xjv3 | Information Exposure in Heketi | An access flaw was found in Heketi 5, where the heketi.json configuration file was world readable. An attacker having local access to the Heketi server could read plain-text passwords from the heketi.json file. | {'CVE-2017-15104'} | 2021-05-19T22:48:28Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-200', 'CWE-552'} | {'https://github.com/heketi/heketi/releases/tag/v5.0.1', 'https://bugzilla.redhat.com/show_bug.cgi?id=1510149', 'https://nvd.nist.gov/vuln/detail/CVE-2017-15104', 'https://github.com/heketi/heketi/commit/787bae461b23003a4daa4d1d639016a754cf6b00', 'https://access.redhat.com/security/cve/CVE-2017-15104', 'https://access.redhat.com/errata/RHSA-2017:3481'} | null |
Go | GO-2021-0063 | null | Due to a nil pointer dereference, a malicously crafted RPC message
can cause a panic. If handling RPC messages from untrusted clients,
this may be used as a denial of service vector.
| {'CVE-2020-26264'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/ethereum/go-ethereum/commit/bddd103a9f0af27ef533f04e06ea429cf76b6d46', 'https://github.com/ethereum/go-ethereum/pull/21896'} | null |
Go | GHSA-5x92-p4p5-33c4 | Path Traversal in HashiCorp Nomad | HashiCorp Nomad and Nomad Enterprise 0.9.0 up to 0.12.7 client Docker file sandbox feature may be subverted when not explicitly disabled or when using a volume mount type. Fixed in 0.12.8, 0.11.7, and 0.10.8. | {'CVE-2020-28348'} | 2021-05-12T21:53:03Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-22'} | {'https://github.com/hashicorp/nomad/blob/master/CHANGELOG.md#0128-november-10-2020', 'https://github.com/hashicorp/nomad/issues/9303', 'https://github.com/hashicorp/nomad/pull/9321', 'https://discuss.hashicorp.com/t/nomad-0-12-8-0-11-7-and-0-10-8-released/17491', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28348'} | null |
Go | GHSA-f3w5-v9xx-rp8p | Signature verification failure in Tendermint | _The root cause of this security vulnerability is in the Tendermint specification, and this advisory is a duplicate of https://github.com/tendermint/spec/security/advisories/GHSA-jqfc-687g-59pw._
### Impact
Tendermint light clients running versions 0.34.0 to 0.34.8 are unable to detect and punish a new kind of attack. We’re calling this a “forward lunatic attack,” or FLA. The severity of this vulnerability is _moderate_.
Note that an FLA cannot be successfully executed unless there are already ⅓+ Byzantine validators, and therefore outside of Tendermint’s security model; however, it is important to be able to detect and punish these kinds of attacks in order to incentivize correct behavior.
In an FLA, an attacking validator (with ⅓+ voting power) signs commit messages for arbitrary application state associated with a block height that hasn’t been seen yet, hence the name “forward lunatic attacks.” A malicious validator effectively executes a [lunatic attack](https://docs.tendermint.com/master/spec/light-client/accountability/#the-misbehavior-of-faulty-validators), but signs messages for a target block that is higher than the current block. This can be dangerous: Typically, misbehavior evidence is only created when there are conflicting blocks at the same height, but by targeting a block height that is far “ahead” of the current chain height, it’s possible that the chain will not produce a (conflicting) block at the target height in time to create evidence.
Prior to Tendermint v0.34.9, the light client could accept a bad header from its primary witness, and would not be able to form evidence of this deception, even if all the secondary witnesses were correct. Because the light client is responsible for verifying cross-chain state for IBC, a successful FLA could result in loss of funds. However, it is important to note that FLAs are only possible outside the Tendermint security model.
All FLAs, attempted and successful, leave traces of provable misbehavior on-chain. A faulty header contains signatures from the faulty validator, and even in unpatched versions of Tendermint Core, networks could use social consensus (off-chain action) to recover the network. The patches introduced in Tendermint Core v0.34.9 handle all evidence automatically and on-chain.
Note that this fix also allows for successful automatic reporting of FLAs, even after a chain halt. By adding a time to FetchBlock, light clients effectively have a backup way to determine if a halted chain should have continued, and it will be able to submit evidence as soon as the chain resumes.
### Patches
This problem has been patched in Tendermint Core v0.34.9.
### Workarounds
There are no workarounds. All users are recommended to upgrade to Tendermint Core v0.34.9 at their earliest possible convenience.
### Credits
Thank you to @MaximilianDiez for originally surfacing this issue, and to @cmwaters, @josef-widder, and @milosevic for creating fixes at both the implementation and specification level.
### 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) | null | 2021-05-20T20:10:47Z | 2021-12-20T18:17:41Z | MODERATE | null | {'CWE-347'} | {'https://github.com/tendermint/tendermint/security/advisories/GHSA-f3w5-v9xx-rp8p'} | null |
Go | GO-2020-0028 | null | Due to a nil pointer dereference, parsing a malformed zone file
containing TA records may cause a panic. If parsing user supplied
input, this may be used as a denial of service vector.
| {'CVE-2018-17419'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/miekg/dns/commit/501e858f679edecd4a38a86317ce50271014a80d', 'https://github.com/miekg/dns/issues/742'} | null |
Go | GHSA-h395-qcrw-5vmq | Inconsistent Interpretation of HTTP Requests in github.com/gin-gonic/gin | This affects all versions of package github.com/gin-gonic/gin under 1.7.0. When gin is exposed directly to the internet, a client's IP can be spoofed by setting the X-Forwarded-For header. | {'CVE-2020-28483'} | 2021-05-12T21:46:50Z | 2021-06-23T17:53:21Z | HIGH | null | {'CWE-113', 'CWE-444'} | {'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMGINGONICGIN-1041736', 'https://github.com/gin-gonic/gin/commit/bfc8ca285eb46dad60e037d57c545cd260636711', 'https://github.com/gin-gonic/gin/releases/tag/v1.7.0', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28483', 'https://github.com/gin-gonic/gin/pull/2632', 'https://github.com/gin-gonic/gin/pull/2474%23issuecomment-729696437'} | null |
Go | GHSA-v592-xf75-856p | Erroneous Proof of Work calculation in geth | ### Impact
An ethash mining DAG generation flaw in Geth could cause miners to erroneously calculate PoW in an upcoming epoch (estimated early January, 2021). This happened on the ETC chain on 2020-11-06. This issue is relevant only for miners, non-mining nodes are unaffected.
### Patches
This issue is also fixed as of 1.9.24. Thanks to @slavikus for bringing the issue to our attention and writing the fix.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)
* Email us at [security@ethereum.org](mailto:security@ethereum.org) | {'CVE-2020-26240'} | 2021-05-21T21:52:58Z | 2021-06-29T21:12:56Z | MODERATE | null | {'CWE-682'} | {'https://github.com/ethereum/go-ethereum/security/advisories/GHSA-v592-xf75-856p', 'https://github.com/ethereum/go-ethereum/pull/21793', 'https://blog.ethereum.org/2020/11/12/geth_security_release/', 'https://github.com/ethereum/go-ethereum/commit/d990df909d7839640143344e79356754384dcdd0', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26240'} | null |
Go | GHSA-4cx6-fj7j-pjx9 | Code injection in Stripe CLI on windows | ### Impact
A vulnerability in Stripe CLI exists on Windows when certain commands are run in a directory where an attacker has planted files. The commands are `stripe login`, `stripe config -e`, `stripe community`, and `stripe open`. MacOS and Linux are unaffected.
An attacker who successfully exploits the vulnerability can run arbitrary code in the context of the current user. The update addresses the vulnerability by throwing an error in these situations before the code can run.
There has been no evidence of exploitation of this vulnerability.
### Recommendation
Upgrade to Stripe CLI v1.7.13.
### Acknowledgments
Thanks to [trungpabc](https://hackerone.com/trungpabc) for reporting the issue.
### For more information
Email us at [security@stripe.com](mailto:security@stripe.com).
| {'CVE-2022-24753'} | 2022-03-18T21:10:48Z | 2022-03-10T18:17:50Z | HIGH | null | {'CWE-78'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-24753', 'https://github.com/stripe/stripe-cli/commit/be38da5c0191adb77f661f769ffff2fbc7ddf6cd', 'https://github.com/stripe/stripe-cli', 'https://github.com/stripe/stripe-cli/security/advisories/GHSA-4cx6-fj7j-pjx9'} | null |
Go | GHSA-mh3m-8c74-74xh | Denial of Service in graphql-go | ### Impact
This is a DoS vulnerability that is possible due to a bug in the library that would allow an attacker with specifically designed queries to cause stack overflow panics. Any user with access to the GraphQL handler can send these queries and cause stack overflows. This in turn could potentially compromise the ability of the server to serve data to its users. To make things worse the only mitigation in affected versions creates opportunities for other attacks. This issue is only available if you are using `graphql.MaxDepth` option in your schema (which is highly recommended in most cases).
### Patches
The issue has been patched in version `v1.3.0`. We have been trying to maintain backwards compatibility and avoid breaking changes so upgrading should not be problematic.
### Workarounds
The best workaround is to patch to a version greater than or equal to `v1.3.0`.
Otherwise, the only workaround in versions prior to `v1.3.0` is to disable the `graphql.MaxDepth` option from your schema. Unfortunately, this could potentially create opportunities for other attacks.
### References
There are no references or links. This issue was reported privately and was fixed before creating this Security Advisory.
### For more information
If you have any questions or comments feel free to reach out to @pavelnikolov or @tony on the Gopher Slack. | {'CVE-2022-21708'} | 2022-01-31T21:59:33Z | 2022-01-27T15:28:06Z | MODERATE | null | {'CWE-400'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-21708', 'https://github.com/graph-gophers/graphql-go', 'https://github.com/graph-gophers/graphql-go/commit/eae31ca73eb3473c544710955d1dbebc22605bfe', 'https://github.com/graph-gophers/graphql-go/security/advisories/GHSA-mh3m-8c74-74xh'} | null |
Go | GHSA-557g-r22w-9wvx | Incorrect Permission Assignment for Critical Resource in Singularity | An issue was discovered in Singularity 3.1.0 to 3.2.0-rc2, a malicious user with local/network access to the host system (e.g. ssh) could exploit this vulnerability due to insecure permissions allowing a user to edit files within `/run/singularity/instances/sing/<user>/<instance>`. The manipulation of those files can change the behavior of the starter-suid program when instances are joined resulting in potential privilege escalation on the host. | {'CVE-2019-11328'} | 2021-05-17T15:50:05Z | 2021-12-20T18:25:33Z | HIGH | null | {'CWE-269'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5O3TPL5OOTIZEI4H6IQBCCISBARJ6WL3/', 'http://www.securityfocus.com/bid/108360', 'http://www.openwall.com/lists/oss-security/2019/05/16/1', 'https://github.com/sylabs/singularity/releases/tag/v3.2.0', 'https://github.com/sylabs/singularity/commit/618c9d56802399adb329c23ea2b70598eaff4a31', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LNU5BUHFOTYUZVHFUSX2VG4S3RCPUEMA/', 'https://nvd.nist.gov/vuln/detail/CVE-2019-11328', 'http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00059.html', 'http://lists.opensuse.org/opensuse-security-announce/2019-10/msg00028.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LIHV7DSEVTB5SUPEZ2UXGS3Q6WMEQSO2/'} | null |
Go | GHSA-vrxp-mg9f-hwf3 | Improperly Implemented path matching for in-toto-golang | ### Impact
Authenticated attackers posing as functionaries (i.e., within a trusted set of users for a layout) are able to create attestations that may bypass DISALLOW rules in the same layout. An attacker with access to trusted private keys, may issue an attestation that contains a disallowed artifact by including path traversal semantics (e.g., foo vs dir/../foo).
### Patches
The problem has been fixed in version 0.3.0.
### Workarounds
Exploiting this vulnerability is dependent on the specific policy applied.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [in-toto-golang](http://github.com/in-toto/in-toto-golang)
* Email us at [in-toto-public](mailto:in-toto-public@googlegroups.com)
* If this is a sensitive security-relevant disclosure, please send a PGP encrypted email to santiagotorres@purdue.edu or jcappos@nyu.edu
| {'CVE-2021-41087'} | 2021-09-21T21:51:18Z | 2021-09-22T20:37:09Z | MODERATE | null | {'CWE-345', 'CWE-22'} | {'https://github.com/in-toto/in-toto-golang', 'https://github.com/in-toto/in-toto-golang/commit/f2c57d1e0f15e3ffbeac531829c696b72ecc4290', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41087', 'https://github.com/in-toto/in-toto-golang/security/advisories/GHSA-vrxp-mg9f-hwf3'} | null |
Go | GHSA-4g4p-42wc-9f3m | Git LFS can execute a Git binary from the current directory | ### Impact
On Windows, if Git LFS operates on a malicious repository with a `git.bat` or `git.exe` file in the current directory, that program would be executed, permitting the attacker to execute arbitrary code. This does not affect Unix systems.
This occurs because on Windows, Go includes (and prefers) the current directory when the name of a command run does not contain a directory separator.
### Patches
This version should be patched in v2.12.1, which will be released in coordination with this security advisory.
### Workarounds
Other than avoiding untrusted repositories, there is no workaround.
### For more information
If you have any questions or comments about this advisory:
* Start a discussion in [the Git LFS discussion page](https://github.com/git-lfs/git-lfs/discussions).
* If you cannot open a discussion, please email the core team using their usernames at `github.com`.
| {'CVE-2020-27955'} | 2022-04-20T16:25:04Z | 2022-02-11T23:39:18Z | CRITICAL | null | {'CWE-427'} | {'https://legalhackers.com/advisories/Git-LFS-RCE-Exploit-CVE-2020-27955.html', 'https://github.com/git-lfs/git-lfs', 'https://github.com/git-lfs/git-lfs/security/advisories/GHSA-4g4p-42wc-9f3m', 'https://github.com/git-lfs/git-lfs/releases', 'https://nvd.nist.gov/vuln/detail/CVE-2020-27955', 'http://seclists.org/fulldisclosure/2020/Nov/1'} | null |
Go | GHSA-q347-cg56-pcq4 | SSRF in repository migration | ### Impact
The malicious user is able to discover services in the internal network through repository migration functionality. All installations accepting public traffic are affected.
### Patches
Internal network CIDRs are prohibited to be used as repository migration targets. Users should upgrade to 0.12.5 or the latest 0.13.0+dev.
### Workarounds
Run Gogs in its own private network.
### References
https://www.huntr.dev/bounties/327797d7-ae41-498f-9bff-cc0bf98cf531/
### For more information
If you have any questions or comments about this advisory, please post on #6754.
| null | 2022-03-14T22:57:00Z | 2022-03-14T22:57:00Z | MODERATE | null | {'CWE-918'} | {'https://www.huntr.dev/bounties/327797d7-ae41-498f-9bff-cc0bf98cf531/', 'https://github.com/gogs/gogs', 'https://github.com/gogs/gogs/security/advisories/GHSA-q347-cg56-pcq4'} | null |
Go | GHSA-wmrx-57hm-mw7r | Arbitrary file reads in HashiCorp Nomad | Nomad is an easy-to-use, flexible, and performant workload orchestrator that can deploy a mix of microservice, batch, containerized, and non-containerized applications. HashiCorp Nomad and Nomad Enterprise 0.9.2 through 1.0.17, 1.1.11, and 1.2.5 allow operators with read-fs and alloc-exec (or job-submit) capabilities to read arbitrary files on the host filesystem as root. There are currently no known workarounds. Users are recommended to upgrade as soon as possible to avoid this issue. | {'CVE-2022-24683'} | 2022-03-24T22:47:39Z | 2022-02-18T00:00:34Z | HIGH | null | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-24683', 'https://security.netapp.com/advisory/ntap-20220318-0008/', 'https://discuss.hashicorp.com', 'github.com/hashicorp/nomad', 'https://discuss.hashicorp.com/t/hcsec-2022-02-nomad-alloc-filesystem-and-container-escape/35560'} | null |
Go | GHSA-q9mp-79cp-9g8j | Improper Authentication | Traefik 2.x, in certain configurations, allows HTTPS sessions to proceed without mutual TLS verification in a situation where ERR_BAD_SSL_CLIENT_AUTH_CERT should have occurred. | {'CVE-2019-20894'} | 2021-08-02T22:18:22Z | 2021-09-02T22:00:09Z | HIGH | null | {'CWE-287', 'CWE-295'} | {'https://github.com/containous/traefik/pull/7008', 'https://nvd.nist.gov/vuln/detail/CVE-2019-20894', 'https://github.com/containous/traefik/issues/5312', 'https://github.com/containous/traefik/commit/2b353971696717e980521b0e4baa1eba66c8d2bf'} | null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.